[menog] Updates on the IANA Stewardship Transition

[Fahd Batayneh]

https://www.icann.org/news/blog/implementation-planning-execution-and-ntia-s
-response

 

 

In order to fulfill the tasks assigned by NTIA
<https://www.ntia.doc.gov/press-release/2014/ntia-announces-intent-transitio
n-key-internet-domain-name-functions>  and the community-developed proposals
for the IANA stewardship transition
<https://www.icann.org/news/announcement-2016-03-10-en> , ICANN and the
multistakeholder community have dedicated significant time and resources
over the past eight months developing plans for implementation. The ICANN
community and staff continue to work hard to ensure that all necessary tasks
are completed and the proposals can be implemented in a timely manner in
advance of 30 September 2016 to allow the IANA functions contract to expire.

 

On 9 June 2016, NTIA requested
<https://www.icann.org/en/system/files/correspondence/strickling-to-crocker-
09jun16-en.pdf>  that ICANN submit an implementation planning status report
by 12 August 2016. Last Friday, ICANN submitted
<https://www.icann.org/en/system/files/correspondence/marby-to-strickling-12
aug16-en.pdf>  a report
<https://www.icann.org/en/system/files/files/iana-stewardship-implementation
-planning-status-12aug16-en.pdf>  to NTIA that stated: "All required tasks
specified in NTIA's 9 June 2016 letter are complete, and all other tasks in
support of the transition are either in a final review stage or awaiting
approval, which will be complete in advance of 30 September 2016 to allow
the IANA functions contract to expire."

 

In a letter to ICANN today
<https://www.ntia.doc.gov/files/ntia/publications/20160816marby.pdf> , NTIA
stated, "NTIA has thoroughly reviewed the report. Based on that review,
barring any significant impediment, NTIA intends to allow the IANA functions
contract to expire as of October 1."

 

ICANN is pleased with NTIA's statement and is focused on the remaining tasks
to be completed by 30 September 2016:

 

*	Finalize the
<https://www.icann.org/public-comments/draft-pti-bylaws-2016-07-12-en> PTI
Bylaws: ICANN is currently incorporating comments received during the public
comment process that ran from 12 July-11 August and will post a final
version on 18 August.
*	Finalize the
<https://www.icann.org/public-comments/iana-naming-function-agreement-2016-0
8-10-en> ICANN-PTI Naming Function Agreement, which includes the customer
service complaint and escalation mechanisms defined by the CWG-Stewardship:
This Agreement is currently out for public comment until 9 September 2016,
and a final version will be posted on 16 September 2016.
*	Finalize the
<http://mm.icann.org/pipermail/cwg-stewardship/2016-August/005522.html>
ICANN-PTI Services Agreement: The Agreement is currently being reviewed and
discussed with the multistakeholder community, and a final version will be
posted on 16 September 2016.

 

In addition, there are four agreements and documents that have been
finalized and require signatures, or ICANN Board and/or PTI Board approval
before they can be considered complete:

 

*	The Root Zone Maintainer Agreement.
*	The ICANN-PTI Protocol Parameters Subcontracting Agreement.
*	The ICANN-PTI Numbers Subcontracting Agreement.
*	The PTI Conflict of Interest Policy, Board Code of Conduct, and
Expected Standards of Behavior.

 

I encourage anyone who is interested in the details of both the completed
and ongoing implementation tasks to read ICANN's 31-page implementation
planning status report
<https://www.icann.org/en/system/files/files/iana-stewardship-implementation
-planning-status-12aug16-en.pdf> . ICANN is confident that everything will
be implemented in advance of 30 September 2016 to allow the IANA functions
contract to expire. The global multistakeholder community, with the support
of ICANN the organization, is ready for the IANA stewardship transition to
occur.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.menog.org/pipermail/menog/attachments/20160817/f9915a82/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5543 bytes
Desc: not available
Url : http://lists.menog.org/pipermail/menog/attachments/20160817/f9915a82/attachment.bin