<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.23942">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2 face=宋体>+1</FONT></DIV>
<DIV><FONT size=2 face=宋体></FONT> </DIV>
<DIV><FONT size=2 face=宋体></FONT> </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV style="FONT: 9pt 宋体">----- Original Message ----- </DIV>
<DIV style="FONT: 9pt 宋体; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=seun.ojedeji@gmail.com href="mailto:seun.ojedeji@gmail.com">Seun
Ojedeji</A> </DIV>
<DIV style="FONT: 9pt 宋体"><B>To:</B> <A title=carlton.samuels@gmail.com
href="mailto:carlton.samuels@gmail.com">Carlton Samuels</A> </DIV>
<DIV style="FONT: 9pt 宋体"><B>Cc:</B> <A title=alac@atlarge-lists.icann.org
href="mailto:alac@atlarge-lists.icann.org">ALAC</A> ; <A title=cpwg@icann.org
href="mailto:cpwg@icann.org">CPWG</A> ; <A title=alan.greenberg@mcgill.ca
href="mailto:alan.greenberg@mcgill.ca">Alan Greenberg</A> </DIV>
<DIV style="FONT: 9pt 宋体"><B>Sent:</B> Sunday, February 17, 2019 6:14 AM</DIV>
<DIV style="FONT: 9pt 宋体"><B>Subject:</B> Re: [CPWG] [ALAC] ALAC Statement to
accompany EPDP Phase 1 FinalReport</DIV>
<DIV><BR></DIV>
<DIV dir=auto>If ALAC member support to Carlton's comments could make any
difference, I do support this.
<DIV dir=auto><BR>While final draft has been replaced with "strong concerns" I
think the last paragraph still reads that we object a number of sections yet
we are supporting the entire package and that again doesn't read well.</DIV>
<DIV dir=auto><BR></DIV>
<DIV dir=auto>Regards<BR><BR>
<DIV dir=auto data-smartmail="gmail_signature">Sent from
my mobile<BR>Kindly excuse brevity and typos</DIV></DIV></DIV><BR>
<DIV class=gmail_quote>
<DIV dir=ltr>On Sat, 16 Feb 2019, 21:21 Carlton Samuels <<A
href="mailto:carlton.samuels@gmail.com">carlton.samuels@gmail.com</A>
wrote:<BR></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV dir=ltr>
<DIV style="FONT-FAMILY: tahoma,sans-serif; FONT-SIZE: large"
class=gmail_default>The ALAC is being asked to go along with the EPDP
proposal despite our representative team's concerns with several aspects of
the output. It appears the decision is to 'go along to get along' and
hope for better in Phase II. So we want to be seen as 'cooperative' without
filing a minority report and appear obdurate, which as a chartered member,
we have every right to do. </DIV>
<DIV style="FONT-FAMILY: tahoma,sans-serif; FONT-SIZE: large"
class=gmail_default><BR></DIV>
<DIV style="FONT-FAMILY: tahoma,sans-serif; FONT-SIZE: large"
class=gmail_default>Maybe its because I generally hate these
'one-the-one-hand-and on-the-other-hand' tomes. They create confused minds
and you come across looking like nitpickers. </DIV>
<DIV style="FONT-FAMILY: tahoma,sans-serif; FONT-SIZE: large"
class=gmail_default><BR></DIV>
<DIV style="FONT-FAMILY: tahoma,sans-serif; FONT-SIZE: large"
class=gmail_default>So, might I suggest that for this exercise in diplomacy,
you will have to use the labels 'concern[s]' and 'difficulty' with a bit
more precision. Maybe a suggestion from the language used by my
university's Finance and General Purpose [management] Committee would
help.<BR></DIV>
<DIV style="FONT-FAMILY: tahoma,sans-serif; FONT-SIZE: large"
class=gmail_default><BR></DIV>
<DIV style="FONT-FAMILY: tahoma,sans-serif; FONT-SIZE: large"
class=gmail_default>When a member object to any portion of a resolution or
decision and it appears non-negotiable, the member maintains integrity by
saying they have a 'difficulty' with the specific topic and cannot support
it. </DIV>
<DIV style="FONT-FAMILY: tahoma,sans-serif; FONT-SIZE: large"
class=gmail_default><BR></DIV>
<DIV style="FONT-FAMILY: tahoma,sans-serif; FONT-SIZE: large"
class=gmail_default>Expressing 'a concern' means that the current view could
be adjusted and there is room for negotiations. </DIV>
<DIV style="FONT-FAMILY: tahoma,sans-serif; FONT-SIZE: large"
class=gmail_default><BR></DIV>
<DIV style="FONT-FAMILY: tahoma,sans-serif; FONT-SIZE: large"
class=gmail_default>-Carlton </DIV>
<DIV>
<DIV dir=ltr class=m_-5592704112106721504gmail_signature
data-smartmail="gmail_signature">
<DIV dir=ltr>
<DIV>
<DIV dir=ltr>
<DIV><BR>==============================<BR><I><FONT
face="comic sans ms, sans-serif">Carlton A Samuels</FONT></I><BR><FONT
face="comic sans ms, sans-serif"><I>Mobile: 876-818-1799<BR><FONT
color=#33cc00>Strategy, Process, Governance, Assessment &
Turnaround</FONT></I></FONT><BR>=============================</DIV></DIV></DIV></DIV></DIV></DIV><BR></DIV><BR>
<DIV class=gmail_quote>
<DIV dir=ltr class=gmail_attr>On Fri, Feb 15, 2019 at 10:38 PM Alan
Greenberg <<A href="mailto:alan.greenberg@mcgill.ca" rel=noreferrer
target=_blank>alan.greenberg@mcgill.ca</A>> wrote:<BR></DIV>
<BLOCKQUOTE
style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>As discussed today the statement has been modified to
address the <BR>issues raised on the CPWG teleconference. The SSAC has
also issue a <BR>statement <BR>(<A
href="https://mm.icann.org/pipermail/gnso-epdp-team/2019-February/001682.html"
rel="noreferrer noreferrer"
target=_blank>https://mm.icann.org/pipermail/gnso-epdp-team/2019-February/001682.html</A>)
<BR>and I took the opportunity to add a few comments prompted by their
document.<BR><BR>A redline and clean version is
attached.<BR><BR>Alan_______________________________________________<BR>ALAC
mailing list<BR><A href="mailto:ALAC@atlarge-lists.icann.org"
rel=noreferrer target=_blank>ALAC@atlarge-lists.icann.org</A><BR><A
href="https://atlarge-lists.icann.org/mailman/listinfo/alac"
rel="noreferrer noreferrer"
target=_blank>https://atlarge-lists.icann.org/mailman/listinfo/alac</A><BR><BR>At-Large
Online: <A href="http://www.atlarge.icann.org" rel="noreferrer noreferrer"
target=_blank>http://www.atlarge.icann.org</A><BR>ALAC Working Wiki: <A
href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)"
rel="noreferrer noreferrer"
target=_blank>https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</A></BLOCKQUOTE></DIV>_______________________________________________<BR>ALAC
mailing list<BR><A href="mailto:ALAC@atlarge-lists.icann.org" rel=noreferrer
target=_blank>ALAC@atlarge-lists.icann.org</A><BR><A
href="https://atlarge-lists.icann.org/mailman/listinfo/alac"
rel="noreferrer noreferrer"
target=_blank>https://atlarge-lists.icann.org/mailman/listinfo/alac</A><BR><BR>At-Large
Online: <A href="http://www.atlarge.icann.org" rel="noreferrer noreferrer"
target=_blank>http://www.atlarge.icann.org</A><BR>ALAC Working Wiki: <A
href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)"
rel="noreferrer noreferrer"
target=_blank>https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</A></BLOCKQUOTE></DIV>
<P>
<HR>
<P></P>_______________________________________________<BR>CPWG mailing
list<BR>CPWG@icann.org<BR>https://mm.icann.org/mailman/listinfo/cpwg<BR></BLOCKQUOTE></BODY></HTML>