<p dir="ltr">Hello Kavous,</p>
<p dir="ltr">Actually on this particular subject, myself and you are both speaking un-authoritatively(at least for me). The one with final view on all these, is the representatives of the numbers community (NRO-EC and NRO-NC(which also doubles as ASO)).</p>
<p dir="ltr">It may therefore be good to ask the numbers community what they prefer and if ICANN board okays it then we are good to go. I have only stated my personal views based on my experience (little as it may be) within the numbers community. </p>
<p dir="ltr">Regards</p>
<div class="gmail_quote">On 25 Jan 2016 9:02 p.m., "Kavouss Arasteh" <<a href="mailto:kavouss.arasteh@gmail.com">kavouss.arasteh@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div><span></span></div><div><div>Dear all,</div><div>If something was incorrectly in the current text that does not justify to follow that inappropriate text.</div><div>If you hold someone upside down for a century it does not justify to continue to do that.</div><div>Is there is a dictatorship it does not mean that dsmocracy should not be put in place democracy.</div><div>Inappropriate precedence SHALL NOT be pursued .</div><div>I therefore have difficulties to accept ratification.</div><div>Regards</div><div>Kavousd <br><div> </div><br>Sent from my iPhone</div><div><br>On 25 Jan 2016, at 19:04, Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com" target="_blank">seun.ojedeji@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><p dir="ltr">Hello Kavous,</p>
<p dir="ltr">The word ratify has been existing on the gPDP and other RIR PDP documents and does not pose any misunderstanding. <br>
gPDP(section 6a): <a href="http://archive.icann.org/en/aso/aso-mou-attachmentA-29oct04.htm" target="_blank">http://archive.icann.org/en/aso/aso-mou-attachmentA-29oct04.htm</a></p>
<p dir="ltr">The reason why it may be good to include that word is to ensure that the 2 current roles of ICANN as it concerns numbers is clearly captured (re policy and operator wise).</p>
<p dir="ltr">For instance ICANN(IANA) only implements the IETF protocols (I am told there was a time board approval was in the loop), so if we used the word implement only, we may not be clearly reflecting the role of ICANN on numbers globally.</p>
<p dir="ltr">Whether ICANN should remain in the position of ratifying global policies is a question that I believe is out of scope for this WG.</p>
<p dir="ltr">Regards</p>
<div class="gmail_quote">On 25 Jan 2016 17:52, "Kavouss Arasteh" <<a href="mailto:kavouss.arasteh@gmail.com" target="_blank">kavouss.arasteh@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Dear Becky,</div><div>Thanks for search and your three options .</div><div>I personally support your option 2 since Options 1 and 3 uses the term" ratifies" which is very strong words and has a high level of legal connotations due to the fact that we may need to specify the criteria of ratification ( simple majority, super majority and so on....)whereas the term " implement" has an operational cobnnotation.</div><div>Regards</div><div>Kavouss </div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-01-25 17:39 GMT+01:00 Burr, Becky <span dir="ltr"><<a href="mailto:Becky.Burr@neustar.biz" target="_blank">Becky.Burr@neustar.biz</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif">
<div>
<div>
<div><span style="font-size:16px">Update in advance of call:</span></div>
<div><span style="font-size:16px"><br>
</span></div>
<div><span style="font-size:16px">The ASO language still seems to be something of a moving target. I believe the following 3 versions are in play:</span></div>
<div><span style="font-size:16px"><br>
</span></div>
<div>
<p class="MsoNormal"><span style="font-family:"Avenir Book"">Version 1: Coordinates the allocation and assignment at the top-most level of Internet Protocol ("IP") and Autonomous System ("AS") numbers.
</span><span style="font-family:"Avenir Book"">Further, it <span style="background:yellow">
ratifies</span>, at the global level, policies related to these IP and AS numbers and developed according to the
</span><span style="font-family:"Avenir Book"">ICANN Address Supporting Organization (ASO) Memorandum of Understanding
</span><span style="font-family:"Avenir Book"">between ICANN and the </span><span style="font-family:"Avenir Book"">Number Resource Organization dated 21 October, 2004, as may be amended from time to time in accordance with its terms.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Avenir Book""> </span></p>
<p class="MsoNormal"><span style="font-family:"Avenir Book"">Version 2: Coordinates the allocation and assignment at the top-most level of Internet Protocol (“IP”) and Autonomous System (“AS”) numbers. Further, it
<span style="background:yellow">implements,</span> at the global level, policies related to these IP and AS numbers and developed pursuant to the Memorandum of Understanding between ICANN and the Number Resource Organization dated 21 October,
2004, as may be amended from time to time in accordance with its terms.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Avenir Book""> </span></p>
<p class="MsoNormal"><span style="font-family:"Avenir Book"">Version 3: Coordinates the allocation and assignment at the top-most level of Internet Protocol (“IP”) and Autonomous System (“AS”) numbers. Further, it
<span style="background:yellow">ratifies and implements</span>, at the global level, policies related to these IP and AS numbers and developed pursuant to the </span><span style="font-family:"Avenir Book"">ICANN Address Supporting Organization
(ASO) Memorandum of Understanding </span><span style="font-family:"Avenir Book"">between ICANN and the </span><span style="font-family:"Avenir Book"">Number Resource Organization dated 21 October, 2004, as may be amended from time to time in accordance
with its terms.</span><span style="font-family:"Avenir Book";font-size:16pt"><u></u><u></u></span></p>
</div>
<div style="font-size:14px">
<div><br>
</div>
<p class="MsoNormal" style="margin-top:12pt"></p>
<p class="MsoNormal" style="margin-top:12pt"><b><span style="line-height:115%;font-size:9pt">J. Beckwith Burr</span></b><b><span style="color:rgb(38,38,38);line-height:115%;font-size:10pt">
</span></b><b><span style="color:rgb(51,102,255);line-height:115%;font-size:9pt"><br>
</span></b><b><span style="color:rgb(0,134,86);line-height:115%;font-size:9pt">Neustar, Inc.</span></b><b><span style="color:rgb(6,134,88);line-height:115%;font-size:9pt">
</span></b><span style="color:rgb(125,125,125);line-height:115%;font-size:9pt">/</span><b><span style="color:rgb(6,134,88);line-height:115%;font-size:9pt">
</span></b><span style="color:rgb(125,125,125);line-height:115%;font-size:9pt">Deputy General Counsel & Chief Privacy Officer<br>
1775 Pennsylvania Avenue NW, Washington D.C. 20006</span><span style="color:gray;line-height:115%;font-size:9pt"><br>
</span><b><span style="color:rgb(0,134,86);line-height:115%;font-size:9pt">Office:</span></b><b><span style="color:rgb(125,125,125);line-height:115%;font-size:9pt">
</span></b><span style="color:rgb(125,125,125);line-height:115%;font-size:9pt"><a href="tel:%2B1.202.533.2932" value="+12025332932" target="_blank">+1.202.533.2932</a>
</span><b><span style="color:rgb(0,134,86);line-height:115%;font-size:9pt">Mobile:</span></b><b><span style="color:rgb(125,125,125);line-height:115%;font-size:9pt">
</span></b><span style="color:rgb(125,125,125);line-height:115%;font-size:9pt"><a href="tel:%2B1.202.352.6367" value="+12023526367" target="_blank">+1.202.352.6367</a>
<strong><span style="font-family:Arial">/</span></strong></span><span style="color:rgb(6,134,88);line-height:115%;font-size:9pt">
</span><a href="http://www.neustar.biz" target="_blank"><b><span style="color:rgb(0,134,86);line-height:115%;font-size:9pt">neustar.biz</span></b></a><span style="color:gray;line-height:115%;font-size:9pt"><u></u><u></u></span></p>
</div>
</div>
</div>
<div style="font-size:14px"><br>
</div>
<span style="font-size:14px">
<div style="border-width:1pt medium medium;border-style:solid none none;border-color:rgb(181,196,223) currentColor currentColor;padding:3pt 0in 0in;text-align:left;color:black;font-family:Calibri;font-size:11pt">
<span style="font-weight:bold">From: </span>Alice Jansen <<a href="mailto:alice.jansen@icann.org" target="_blank">alice.jansen@icann.org</a>><br>
<span style="font-weight:bold">Date: </span>Monday, January 25, 2016 at 5:05 AM<br>
<span style="font-weight:bold">To: </span>Accountability Community <<a href="mailto:accountability-cross-community@icann.org" target="_blank">accountability-cross-community@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>[CCWG-ACCT] Recommendation 5 - Mission - 3rd reading conclusions<br>
</div>
<div><br>
</div>
<div>
<div>
<div style="color:rgb(0,0,0);font-family:Avenir,sans-serif;font-size:12px">
<u><font face="Avenir">Sent on behalf of CoChairs </font></u></div>
<div>
<div>
<div><span style="color:rgb(0,0,0);font-family:Avenir,sans-serif;font-size:12px">
<div>
<span>
<div>
<span>
<div>
<span>
<div>
<span>
<div>
<span>
<div>
<span>
<div>
<div style="color:rgb(0,0,0);font-family:Avenir,sans-serif;font-size:12px">
<u><font face="Avenir"><br>
</font></u></div>
<div><font face="Avenir"><font face="Avenir,sans-serif">Please find below the conclusions (3rd </font>reading<font face="Avenir,sans-serif">) of our mission deliberations during call #78. The updated document is attached. </font></font></div>
</div>
</span></div>
</span></div>
</span></div>
</span></div>
</span></div>
</span></div>
</span>
<div><br>
</div>
<div>
<div>Conclusions:</div>
<div>1. On Consumer Trust: agreement to keep Third Draft Proposal language. Reference to Consumer Trust should not be added to Core Values. It will be included at part of AOC reviews.</div>
<div>2. Discuss ALAC concern regarding removal of the words “where feasible and appropriate” in Core Value 4 that states : Depending on market mechanisms to promote and sustain a healthy competitive environment in the DNS market</div>
<div>3. Awaiting Board input on root servers</div>
<div>4. On numbers language, wordsmithing is needed based on input from lawyers - see
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__mm.icann.org_pipermail_accountability-2Dcross-2Dcommunity_2016-2DJanuary_009725.html&d=CwQGaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=lzj8v1kvCk6YVY-j-3w2qOhWX5mMI5IPL9r5LunULM0&s=4L1cGahaUtTeaOP1eJ6G0Uk5DeFP3lkZmW-Nm78o5GM&e=" target="_blank">
http://mm.icann.org/pipermail/accountability-cross-community/2016-January/009725.html</a> and proposed language from ASO: "Coordinates the allocation and assignment at the top-most level of Internet Protocol (“IP”) and Autonomous System (“AS”) numbers. Further,
it ratifies, at the global level, policies related to these IP and AS numbers and developed according to the ASO-MoU." </div>
<div>5. On RSSAC language: </div>
<div>[RSSAC PROPOSED TEXT: Facilitates coordinatesion of the operation and evolution of the DNS root name server system.] </div>
<div>[BOARD PROPOSED TEXT: Coordinates the operation and evolution of the DNS root name server system. In this role, ICANN’s Mission is to [to be provided by RSSAC]. ICANN retains an operational role as well as considers inputs from the communities dependent
on the root server system.]</div>
<div>6. Discuss the issue around the scope of ICANN’s agreements with contracted parties (page 10). 3rd draft provisions are : </div>
<blockquote style="margin:0px 0px 0px 40px;padding:0px;border:currentColor">
<div>a. ICANN shall not impose regulations on services that use the Internet’s unique identifiers, or the content that such services carry or provide.</div>
<div>b. ICANN shall have the ability to negotiate, enter into and enforce agreements with contracted parties in furtherance service of its Mission.</div>
<div>c. Take into consideration legal advice : “For clients facing similar dilemmas, a common approach is to draft general principles into governing documents and provide a mechanism for interpreting them in specific situations. We recommend that the CCWG
agree upon and articulate mission principles at a general level appropriate for inclusion in the Bylaws, understanding that refinement and interpretation will be needed thereafter”. </div>
</blockquote>
<div>7. Grandfathering. Discuss questions raised by lawyers : </div>
<blockquote style="margin:0px 0px 0px 40px;padding:0px;border:currentColor">
<div>a. What is the effective cut-off date for the grandfathering? This could be a specified date in the future, or could be an event, such as the date of adoption of the relevant Fundamental Bylaw.</div>
<div>b. Should RAs that are in the process of being put in place but have not yet been finalized and signed as of the effective date, be included or excluded? If that should depend on how far along in the process they are, what should be the standard for deciding
that point?</div>
<div>c. Should renewals of existing RAs, unchanged, that contain PICs covered by the grandfathering clause, be included? If so, should there be a limit on the number of renewals that will be covered? Should grandfathering cover PICs that are not modified,
even though other provisions of the agreement are changed?</div>
<div>d. What if an existing RA/RAA includes a grandfathered PIC, and the agreement is modified, by mutual agreement or otherwise -- is it still grandfathered? </div>
<div>e. Should all grandfathering have a sunset date, i.e., a point far enough in the future on which all grandfathering protection will expire?</div>
</blockquote>
<div>8. Discuss request to provide impact assessment as requested by several group members. </div>
<div style="color:rgb(0,0,0);font-family:-webkit-standard;font-size:12px">
<br>
</div>
</div>
</div>
<div style="color:rgb(0,0,0);font-family:Avenir,sans-serif;font-size:12px">
<div><font face="Avenir">Fourth reading is planned for Tuesday, 26 January.</font></div>
<div><font face="Avenir"><br>
</font></div>
<div><font face="Avenir">Best regards</font></div>
<div><font face="Avenir"><br>
</font></div>
<div><font face="Avenir">Mathieu, Thomas, León</font></div>
</div>
</div>
<div style="color:rgb(0,0,0);font-family:Avenir,sans-serif;font-size:12px">
<font face="Avenir"><br>
</font></div>
</div>
</div>
</div>
</span>
</div>
<br>_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br></blockquote></div>
</div></blockquote></div></div></blockquote></div>