<div dir="ltr"><div>WOW.. what else is happening that we don't know about? so much for transparency!</div><div><br></div><div><br></div><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Olivier MJ Crepin-Leblond</b> <span dir="ltr"><<a href="mailto:ocl@gih.com">ocl@gih.com</a>></span><br>Date: Sat, Mar 19, 2016 at 11:21 PM<br>Subject: Re: [IANA-issues] Fwd: [ianatransition] A Progress Update: Ensuring the Security, Stability and Resiliency of Root Zone Maintenance<br>To: <a href="mailto:iana-issues@atlarge-lists.icann.org">iana-issues@atlarge-lists.icann.org</a><br><br><br>
<div bgcolor="#FFFFFF" text="#000000">
Hello all,<br>
<br>
just to add my points of view on this, which I have shared in
another list:<br>
<br>
--- cut here ---<br>
<pre>When the proposal will be up for Public Comment, I am sure that the
At-Large Advisory Committee will have comments. For the time being, I
personally have noted two main points:
1. That the whole discussion of the agreement between ICANN and Verisign
is fraught with secrecy. Whilst the whole Community was involved with
the CWG IANA Stewardship and CCWG Accountability, the actual
relationship between Verisign & ICANN was launched as a separate process
that concerned only Verisign & ICANN. We are seeing the same pattern as
for the establishment of the Registry and the Registrar Accreditation
Agreements - and when the ALAC has enquired about this in the past, it
was told "these are commercial agreements that you have no business
putting your nose in". So much for transparency. And unfortunately this
lack of transparency is vehemently defended by contracted parties. So
the community has <b><span>*</span>little or no influence<span>*</span></b> in what the relationship with
Verisign will be.
2. Because of (1), the community has very little knowledge of what the
exact current terms of contract are with Verisign. We were told that the
provision of the IANA Operator services was provided in the past at
cost. Now we're told there will be compensation. We're also told that
there will be "certain service level agreements" -- when the set of
service level expectations negotiated between ICANN and the Operational
Communities is very close to being completed already. We're also told
that the function could be transitioned "after an agreed-upon number of
years" when the community powers could be effected as soon as they are
in place. And finally, I note that it appears that the .com Registry
Agreement has been linked to the RZMA "which ICANN and Verisign believed
enhances the security, stability and resiliency of the root zone
infrastructure". I'd like to get SSAC's point of view on this.
That's all for the time being. I am eagerly waiting for the Public
Comment period.
Kindest regards,
Olivier
(own views)</pre><div><div class="h5">
<br>
<br>
<div>On 20/03/2016 09:56, Olivier MJ
Crepin-Leblond wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">
FYI<br>
<div><br>
<br>
-------- Forwarded Message --------
<table border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<th align="RIGHT" nowrap valign="BASELINE">Subject:
</th>
<td>[ianatransition] A Progress Update: Ensuring the
Security, Stability and Resiliency of Root Zone
Maintenance</td>
</tr>
<tr>
<th align="RIGHT" nowrap valign="BASELINE">Date:
</th>
<td>Fri, 18 Mar 2016 20:35:53 +0000</td>
</tr>
<tr>
<th align="RIGHT" nowrap valign="BASELINE">From:
</th>
<td>Grace Abuhamad <a href="mailto:grace.abuhamad@icann.org" target="_blank"><grace.abuhamad@icann.org></a></td>
</tr>
<tr>
<th align="RIGHT" nowrap valign="BASELINE">To: </th>
<td><a href="mailto:ianatransition@icann.org" target="_blank">ianatransition@icann.org</a>
<a href="mailto:ianatransition@icann.org" target="_blank"><ianatransition@icann.org></a></td>
</tr>
</tbody>
</table>
<br>
<br>
<div>
<div>
<div><font face="Calibri,sans-serif">Original link: </font><a href="https://www.icann.org/news/blog/a-progress-update-ensuring-the-security-stability-and-resiliency-of-root-zone-maintenance" target="_blank"></a><a href="https://www.icann.org/news/blog/a-progress-update-ensuring-the-security-stability-and-resiliency-of-root-zone-maintenance" target="_blank">https://www.icann.org/news/blog/a-progress-update-ensuring-the-security-stability-and-resiliency-of-root-zone-maintenance</a>.</div>
</div>
</div>
<span>
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px"><span style="font-family:Calibri,sans-serif">
<div>
<div><br>
</div>
<div><br>
</div>
<div>
<h1 style="font-size:1.31rem;margin:0px 0px 10px;font-family:Lato,Helvetica,Arial,sans-serif;color:rgb(51,51,51);padding:0px 0px 1rem;border-bottom-width:1px;border-bottom-style:solid;border-bottom-color:rgb(207,207,207);line-height:normal;background-color:rgb(255,255,255);font-weight:500!important"> A Progress Update: Ensuring the
Security, <abbr title="Security, Stability and
Resiliency" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">Stability</abbr> and <abbr title="Security Stability & Resiliency (SSR)" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">Resiliency </abbr>of <abbr title="Root Zone" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">Root Zone </abbr>Maintenance</h1>
<div style="font-size:1.62rem;margin-bottom:30px;color:rgb(51,51,51);font-family:helvetica,arial,sans-serif;line-height:normal;background-color:rgb(255,255,255)"><a title="LinkedIn" href="https://www.icann.org/news/blog/a-progress-update-ensuring-the-security-stability-and-resiliency-of-root-zone-maintenance#" style="color:gray;margin-right:7.5px;margin-bottom:5px;line-height:initial;float:left;padding:0px 2px;width:auto;background-color:transparent;text-decoration:none!important;background-position:initial initial;background-repeat:initial initial" target="_blank"><span style="display:inline-block;line-height:1;font-family:FontAwesome;font-size:1.2rem"></span></a><a title="Facebook" href="https://www.icann.org/news/blog/a-progress-update-ensuring-the-security-stability-and-resiliency-of-root-zone-maintenance#" style="color:gray;margin-right:7.5px;margin-bottom:5px;line-height:initial;float:left;padding:0px 2px;width:auto;background-color:transparent;text-decoration:none!important;background-position:initial initial;background-repeat:initial initial" target="_blank"><span style="display:inline-block;line-height:1;font-family:FontAwesome;font-size:1.2rem"></span></a><a title="Tweet" href="https://www.icann.org/news/blog/a-progress-update-ensuring-the-security-stability-and-resiliency-of-root-zone-maintenance#" style="color:gray;margin-right:7.5px;margin-bottom:5px;line-height:initial;float:left;padding:0px 2px;width:auto;background-color:transparent;text-decoration:none!important;background-position:initial initial;background-repeat:initial initial" target="_blank"><span style="display:inline-block;line-height:1;font-family:FontAwesome;font-size:1.2rem"></span></a><a title="Sina
Weibo" href="https://www.icann.org/news/blog/a-progress-update-ensuring-the-security-stability-and-resiliency-of-root-zone-maintenance#" style="color:gray;margin-right:7.5px;margin-bottom:5px;line-height:initial;float:left;padding:0px 2px;width:auto;background-color:transparent;text-decoration:none!important;background-position:initial initial;background-repeat:initial initial" target="_blank"><span style="display:inline-block;line-height:1;font-family:FontAwesome;font-size:1.2rem"></span></a><a title="Email" href="https://www.icann.org/news/blog/a-progress-update-ensuring-the-security-stability-and-resiliency-of-root-zone-maintenance#" style="color:gray;margin-right:7.5px;margin-bottom:5px;line-height:initial;float:left;padding:0px 2px;width:auto;background-color:transparent;text-decoration:none!important;background-position:initial initial;background-repeat:initial initial" target="_blank"><span style="display:inline-block;line-height:1;font-family:FontAwesome;font-size:1.2rem"></span></a><a href="https://www.icann.org/news/blog/a-progress-update-ensuring-the-security-stability-and-resiliency-of-root-zone-maintenance#" style="color:gray;margin-right:7.5px;margin-bottom:5px;line-height:initial;float:left;padding:0px 2px;width:auto;background-color:transparent;text-decoration:none!important;background-position:initial initial;background-repeat:initial initial" target="_blank"><span style="display:inline-block;line-height:1;font-family:FontAwesome;font-size:1.2rem"></span></a></div>
<div style="color:rgb(51,51,51);font-family:helvetica,arial,sans-serif;font-size:16px;line-height:normal;background-color:rgb(255,255,255)">
<p style="line-height:1.4rem;font-size:1rem;margin:0px 0px 1.25rem">
On 10 March 2016, a plan to transition the <abbr title="Internet Assigned Numbers Authority" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">IANA</abbr> stewardship
from the U.S. government's oversight to a global
multistakeholder community was submitted to <abbr title="US National Telecommunications and
Information Agency" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">NTIA</abbr> for consideration.
Witnessing the extraordinary efforts of the
multistakeholder community to develop these
proposals has been impressive and humbling.</p>
<p style="line-height:1.4rem;font-size:1rem;margin:0px 0px 1.25rem">
While the community has been working hard to
finalize the proposals included in the plan, my
team and I have been diligently preparing for the
implementation phase of the anticipated <abbr title="Internet Assigned Numbers Authority" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">IANA</abbr> stewardship
transition. One of the tasks that must be
completed is for <abbr title="Internet Corporation
for Assigned Names and Numbers" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">ICANN</abbr> and
Verisign to enter into a <abbr title="Root Zone" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">Root Zone</abbr>Maintainer
Agreement (RZMA). Another is to extend the .com
Registry Agreement to run for the same term as the
RZMA, which <abbr title="Internet Corporation for
Assigned Names and Numbers" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">ICANN</abbr> and Verisign believe
enhances the security, stability and resiliency of
the root zone infrastructure. Today, I want to
provide you with some background information on
the RZMA and an update on our progress.</p>
<p style="line-height:1.4rem;font-size:1rem;margin:0px 0px 1.25rem">
As noted in the <abbr title="Internet Assigned
Numbers Authority" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">IANA</abbr> Stewardship Transition
Coordination Group (<abbr title="IANA Stewardship
Transition Coordination Group" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">ICG</abbr>)
proposal, the complete and finalized transition
requires revising the relationship between the
current <abbr title="Internet Assigned Numbers
Authority" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">IANA</abbr> Functions
Operator (<abbr title="Internet Corporation for
Assigned Names and Numbers" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">ICANN</abbr>), the current <abbr title="Root Zone" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">Root Zone</abbr> Maintainer
(Verisign) and the current <abbr title="Root Zone" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">Root Zone</abbr> Administrator
(<abbr title="US National Telecommunications and
Information Agency" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">NTIA</abbr>). Specifically, the role
of <abbr title="US National Telecommunications and
Information Agency" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">NTIA</abbr> will be eliminated and a
written agreement between <abbr title="Internet
Corporation for Assigned Names and Numbers" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">ICANN</abbr> and
Verisign establishing each party's role will need
to be in place once that happens.</p>
<p style="line-height:1.4rem;font-size:1rem;margin:0px 0px 1.25rem">
On 4 March 2015, <abbr title="US National
Telecommunications and Information Agency" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">NTIA</abbr> officially
requested that <abbr title="Internet Corporation
for Assigned Names and Numbers" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">ICANN</abbr> and
Verisign work together to develop a proposal on
how best to transition <abbr title="US National
Telecommunications and Information Agency" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">NTIA</abbr>'s
administrative role associated with root zone
management. Of paramount importance is
accomplishing this in a manner that maintains the
security, stability and resiliency of the root
zone management process. <abbr title="Internet
Corporation for Assigned Names and Numbers" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">ICANN</abbr> and
Verisign are close to having terms and conditions
that accomplish this essential objective and that
clearly define the respective roles and
responsibilities of each party.</p>
<p style="line-height:1.4rem;font-size:1rem;margin:0px 0px 1.25rem">
In general, we have already agreed that Verisign
will be compensated for performance of the
maintainer function and will have obligations to
meet certain service-level agreements (SLAs) that
the parties may adjust to address recommendations
of the Customer Standing Committee pursuant to a
change control process anticipated in the
agreement. This change process is being defined to
allow for the community to introduce through <abbr title="Internet Corporation for Assigned Names
and Numbers" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">ICANN</abbr> improvements
to the <abbr title="Root Zone" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">Root Zone</abbr> Management System as
well. While the term of the RZMA is intended to
promote the security, stability and resiliency of
root zone maintenance operations by having
Verisign continue in its role, the agreement also
provides a capability for the community, through a
consensus-based community-driven process, to
cause <abbr title="Internet Corporation for
Assigned Names and Numbers" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">ICANN</abbr> to transition the
function to another service provider after an
agreed-upon number of years.</p>
<p style="line-height:1.4rem;font-size:1rem;margin:0px 0px 1.25rem">
There are some remaining issues that need to be
resolved before we finalize a draft of the
agreement. It's difficult to enumerate these
issues because discussions are ongoing and the
status of the issues changes frequently. However,
we are making good progress and expect to complete
a draft soon.</p>
<p style="line-height:1.4rem;font-size:1rem;margin:0px 0px 1.25rem">
Once <abbr title="Internet Corporation for
Assigned Names and Numbers" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">ICANN</abbr> and Verisign have
completed the draft agreement, it will be posted
for a 30-day community review period. This is in
accordance with <abbr title="Internet Corporation
for Assigned Names and Numbers" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">ICANN</abbr>'s
transparency as well as in keeping with the
recommendation in the <abbr title="IANA
Stewardship Transition Coordination Group" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">ICG</abbr> proposal
to make the draft proposal available for public
review prior to execution.</p>
<p style="line-height:1.4rem;font-size:1rem;margin:0px 0px 1.25rem">
There is still work to do but we are making good
progress. I encourage you to explore the web pages
listed below for more information and to keep
abreast of the latest developments.</p>
<ul style="padding:0px;line-height:1.4rem;margin:0px 0px 1.25rem 20px">
<li style="line-height:1.4rem;margin:0px 0px 15px 20px"><a href="https://www.ntia.doc.gov/files/ntia/publications/root_zone_administrator_proposal-relatedtoiana_functionsste-final.pdf" style="color:rgb(0,152,213);text-decoration:none;clear:both;background-color:transparent;background-position:initial initial;background-repeat:initial initial" target="_blank"><abbr title="Root Zone" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">Root Zone</abbr> Administrator
Proposal Related to the <abbr title="Internet
Assigned Numbers Authority" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">IANA</abbr> Functions
Stewardship Transition</a> [PDF, 247 KB]</li>
<li style="line-height:1.4rem;margin:0px 0px 15px 20px"><a href="https://www.icann.org/stewardship-implementation" style="color:rgb(0,152,213);text-decoration:none;clear:both;background-color:transparent;background-position:initial initial;background-repeat:initial initial" target="_blank"><abbr title="Internet Assigned Numbers Authority" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">IANA</abbr> Stewardship
Transition Implementation</a></li>
<li style="line-height:1.4rem;margin:0px 0px 15px 20px"><a href="https://www.icann.org/stewardship-accountability" style="color:rgb(0,152,213);text-decoration:none;clear:both;background-color:transparent;background-position:initial initial;background-repeat:initial initial" target="_blank"><abbr title="Internet Assigned Numbers Authority" style="direction:ltr;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(153,153,153)">IANA</abbr> Stewardship
and Accountability</a></li>
</ul>
</div>
</div>
</div>
</span></div>
</span> <br>
</div>
<br>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
Iana-issues mailing list
<a href="mailto:Iana-issues@atlarge-lists.icann.org" target="_blank">Iana-issues@atlarge-lists.icann.org</a>
<a href="https://mm.icann.org/mailman/listinfo/iana-issues" target="_blank">https://mm.icann.org/mailman/listinfo/iana-issues</a><span class="HOEnZb"><font color="#888888">
</font></span></pre><span class="HOEnZb"><font color="#888888">
</font></span></blockquote><span class="HOEnZb"><font color="#888888">
<br>
<pre cols="72">--
Olivier MJ Crépin-Leblond, PhD
<a href="http://www.gih.com/ocl.html" target="_blank">http://www.gih.com/ocl.html</a>
</pre>
</font></span></div>
<br>_______________________________________________<br>
Iana-issues mailing list<br>
<a href="mailto:Iana-issues@atlarge-lists.icann.org">Iana-issues@atlarge-lists.icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/iana-issues" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/iana-issues</a><br>
<br></div><br></div>