[ALAC] Fwd: [IANA-issues] Fwd: [ianatransition] A Progress Update: Ensuring the Security, Stability and Resiliency of Root Zone Maintenance

Sun Mar 20 13:26:58 UTC 2016

WOW.. what else  is happening that we don't know about? so much for
transparency!

---------- Forwarded message ----------
From: Olivier MJ Crepin-Leblond <ocl at gih.com>
Date: Sat, Mar 19, 2016 at 11:21 PM
Subject: Re: [IANA-issues] Fwd: [ianatransition] A Progress Update:
Ensuring the Security, Stability and Resiliency of Root Zone Maintenance
To: iana-issues at atlarge-lists.icann.org

Hello all,

just to add my points of view on this, which I have shared in another list:

--- cut here ---

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 **little or no influence** 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)

On 20/03/2016 09:56, Olivier MJ Crepin-Leblond wrote:

FYI

-------- Forwarded Message --------
Subject: [ianatransition] A Progress Update: Ensuring the Security,
Stability and Resiliency of Root Zone Maintenance
Date: Fri, 18 Mar 2016 20:35:53 +0000
From: Grace Abuhamad <grace.abuhamad at icann.org> <grace.abuhamad at icann.org>
To: ianatransition at icann.org <ianatransition at icann.org>
<ianatransition at icann.org>

Original link:
<https://www.icann.org/news/blog/a-progress-update-ensuring-the-security-stability-and-resiliency-of-root-zone-maintenance>
https://www.icann.org/news/blog/a-progress-update-ensuring-the-security-stability-and-resiliency-of-root-zone-maintenance
.

A Progress Update: Ensuring the Security, Stability and Resiliency of Root
Zone Maintenance
<https://www.icann.org/news/blog/a-progress-update-ensuring-the-security-stability-and-resiliency-of-root-zone-maintenance#>
<https://www.icann.org/news/blog/a-progress-update-ensuring-the-security-stability-and-resiliency-of-root-zone-maintenance#>
<https://www.icann.org/news/blog/a-progress-update-ensuring-the-security-stability-and-resiliency-of-root-zone-maintenance#>
<https://www.icann.org/news/blog/a-progress-update-ensuring-the-security-stability-and-resiliency-of-root-zone-maintenance#>
<https://www.icann.org/news/blog/a-progress-update-ensuring-the-security-stability-and-resiliency-of-root-zone-maintenance#>
<https://www.icann.org/news/blog/a-progress-update-ensuring-the-security-stability-and-resiliency-of-root-zone-maintenance#>

On 10 March 2016, a plan to transition the IANA stewardship from the U.S.
government's oversight to a global multistakeholder community was submitted
to NTIA for consideration. Witnessing the extraordinary efforts of the
multistakeholder community to develop these proposals has been impressive
and humbling.

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 IANA stewardship transition. One of
the tasks that must be completed is for ICANN and Verisign to enter into a Root
ZoneMaintainer Agreement (RZMA). Another is to extend the .com Registry
Agreement to run for the same term as the RZMA, which ICANN 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.

As noted in the IANA Stewardship Transition Coordination Group (ICG)
proposal, the complete and finalized transition requires revising the
relationship between the current IANA Functions Operator (ICANN), the
current Root Zone Maintainer (Verisign) and the current Root Zone Administrator
(NTIA). Specifically, the role of NTIA will be eliminated and a written
agreement between ICANN and Verisign establishing each party's role will
need to be in place once that happens.

On 4 March 2015, NTIA officially requested that ICANN and Verisign work
together to develop a proposal on how best to transition NTIA'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. ICANN 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.

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 ICANN
improvements
to the Root Zone 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 ICANN to transition the
function to another service provider after an agreed-upon number of years.

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.

Once ICANN and Verisign have completed the draft agreement, it will be
posted for a 30-day community review period. This is in accordance with
ICANN's transparency as well as in keeping with the recommendation in the
ICG proposal to make the draft proposal available for public review prior
to execution.

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.

   - Root Zone Administrator Proposal Related to the IANA Functions
   Stewardship Transition
   <https://www.ntia.doc.gov/files/ntia/publications/root_zone_administrator_proposal-relatedtoiana_functionsste-final.pdf>
[PDF,
   247 KB]
   - IANA Stewardship Transition Implementation
   <https://www.icann.org/stewardship-implementation>
   - IANA Stewardship and Accountability
   <https://www.icann.org/stewardship-accountability>

_______________________________________________
Iana-issues mailing
listIana-issues at atlarge-lists.icann.orghttps://mm.icann.org/mailman/listinfo/iana-issues

-- 
Olivier MJ Crépin-Leblond, PhDhttp://www.gih.com/ocl.html

_______________________________________________
Iana-issues mailing list
Iana-issues at atlarge-lists.icann.org
https://mm.icann.org/mailman/listinfo/iana-issues
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://atlarge-lists.icann.org/pipermail/alac/attachments/20160320/bd1eb664/attachment.html>