<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EstiloCorreo17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=ES link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I believe that it is correct allowing ccTLDs keeping their autonomy and own rules of operation in each country. Thus, ICANN keep also the argument that each country has sovereignty in its own territory but the all the rest of gTLDs are out of the sovereignty of the countries and they should be managed by ICANN rules. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hector<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Héctor Ariel Manoff<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Vitale, Manoff & Feilbogen<o:p></o:p></span></b></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Viamonte 1145 10º Piso<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>C1053ABW Buenos Aires<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>República Argentina<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Te: (54-11) 4371-6100<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Fax: (54-11) 4371-6365<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>E-mail: <a href="mailto:amanoff@vmf.com.ar"><span style='color:blue'>amanoff@vmf.com.ar</span></a><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Web: </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'><a href="http://www.vmf.com.ar"><span lang=EN-US style='color:blue'>http://www.vmf.com.ar</span></a></span><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'><o:p></o:p></span></p></div><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> chapter-delegates-bounces@elists.isoc.org [mailto:chapter-delegates-bounces@elists.isoc.org] <b>En nombre de </b>Steve Crocker<br><b>Enviado el:</b> lunes, 31 de marzo de 2014 5:23<br><b>Para:</b> Patrik Fältström; Seun Ojedeji<br><b>CC:</b> Michael Froomkin; internetpolicy@elists.isoc.org; ianaxfer@elists.isoc.org; ISOC Chapter Delegates<br><b>Asunto:</b> Re: [Chapter-delegates] [Internet Policy] [IANAxfer] An initial proposalregarding IANA development<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Patrik, Seun, et al,<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Here’s a small detail worth thinking about. Although some ccTLDs have agreements with ICANN, many do not. Further, many ccTLDs are not members of the ccNSO, the Supporting Organization that represents the ccTLDs within ICANN. None of this matters when it comes to providing each ccTLD with updates to its portion of the root zone. ICANN serves *every* ccTLD, even those that operate in locations the U.S. Government imposes trade restrictions.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>This is the way it’s been since the inception of ICANN. I don’t see any reason this needs to change. I would not envision ICANN *requiring* any sort of agreement with each of the ccTLDs. (We have sometimes sought such an agreement and may do so in the future, but it will not be a requirement.)<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Re the arrangements with Verisign, I would expect the adjustments to be only the minimum that’s required. I would expect their operational role and ICANN’s operational re updates and publishing of the root zone and the creation and use of DNSSEC keys to remain the same. It’s the *stewardship* not the actual operation that’s the subject of discussion.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Steve<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Mar 31, 2014, at 4:10 AM, Patrik Fältström <<a href="mailto:patrik@frobbit.se">patrik@frobbit.se</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><br><br><o:p></o:p></p><div><p class=MsoNormal>On 31 mar 2014, at 03:57, Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com">seun.ojedeji@gmail.com</a>> wrote:<o:p></o:p></p><div><p class=MsoNormal><br><br><o:p></o:p></p><div><div><p class=MsoNormal>On Sun, Mar 30, 2014 at 10:22 PM, Patrik Fältström <<a href="mailto:patrik@frobbit.se" target="_blank">patrik@frobbit.se</a>> wrote:<o:p></o:p></p></div><div><div><div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm;z-index:auto'><div><div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On 30 mar 2014, at 13:49, Patrick Ryan <<a href="mailto:patrickryan@google.com" target="_blank">patrickryan@google.com</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></div><div><p class=MsoNormal>I think personally one could think of a model where we have the various responsibilities layered:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>A. Primary layer:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>A.1. ICANN (as the party running the IANA function) signs an AOC with each body that asks for IANA services.<o:p></o:p></p></div><div><p class=MsoNormal>A.2. ICANN to be able to provide the service required signs whatever AOC/MOU/Contract needed with Verisign and whoever else that have to be involved, so that ICANN can deliver whatever it promises under A.1.<o:p></o:p></p></div></div></blockquote><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Unless i am forgetting/missing something, I think this part is already inplace, and there may be no need to have to repeat the signing process(re-call the scope of those who require the IANA service is quite broad). The only aspect which perhaps needs to be updated is the relationship between ICANN and Verisign (since verisign contract is with the USG). So ICANN needs to sign a contract with Verisign (just as he already have signed contract with other registries)<o:p></o:p></p></div></div></div></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>There is today a cooperative agreement between NTIA and Verisign that contain things I do believe are related to the root zone management. Those details in that agreement should, I think, be replaced by a contract between ICANN and Verisign. This is not these operational actions that Verisign do are to be moved elsewhere (to IANA). But if the basis for the discussion is to not change operations of the root zone management, then I would like to see ICANN take over the pieces of the Cooperative Agreement related to the root zone management.<o:p></o:p></p></div><div><p class=MsoNormal><br><br><o:p></o:p></p><div><div><div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm;z-index:auto'><div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>B. Secondary layer:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>B.1. ICANN signs whatever paperwork with the parties that for example uses the parameters that are allocated according to the policies set up under category A.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></blockquote><div><p class=MsoNormal>I am wondering how this differ from Item A2.1 that you mentioned above?<o:p></o:p></p></div></div></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>B1 has to do with for example the registries for each TLD be able to get an agreement with ICANN. In the same way as each organisation getting any other parameter from ICANN (i.e. the RIRs, each entity that have something in the IANA registry). This for the protocol parameters have to be discussed somewhat more whether it is for example for most of them IAB that is the other end of the agreement, ISOC or whether it is really each individual. For PEN it could be the organisation. For character sets...<o:p></o:p></p></div><div><p class=MsoNormal><br><br><o:p></o:p></p><div><div><div><div><p class=MsoNormal> <o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm;z-index:auto'><div><div><p class=MsoNormal>C. Tertiary layer:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>That way, at least via A.1 and B.1 we get a mesh of accountability agreements that should ensure that things works.<o:p></o:p></p></div></div></blockquote><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Speaking about accountability, i think the bylaw should drive the accountability process. The role of the board needs to be reviewed. Now i know they always say board members represent the interest of the organisation. Yes i agree, however i believe the interest of the organisation should be in the bylaw and board should respect such. Now the content of the bylaw should respect the PDP of ICANN. It is well know that the PDP of ICANN has a bottom up approach hence the community interest is represented.<o:p></o:p></p></div><div><p class=MsoNormal>So for me, i think more work needs to be done in reviewing the exiting bylaw and ensuring it holds the board members accountable and then the board members holds the organisation (in this case the CEO) accountable in an open and transparent manner.<o:p></o:p></p></div></div></div></div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>But to whom are they accountable? I was more thinking of to whom the accountability was. But of course you talk about the internal implementation of the accountability and that is also important discussion.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal> Patrik<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>_______________________________________________<br>To manage your ISOC subscriptions or unsubscribe,<br>please log into the ISOC Member Portal:<br><a href="https://portal.isoc.org/">https://portal.isoc.org/</a><br>Then choose Interests & Subscriptions from the My Account menu.<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>