Becky, Nigel, Thank you for being so active and pushing things (and us) forward. Taking into account the latest developments and discussions around the draft IANA Function Agreement, I think everybody agrees that the ccNSO Council may need to consider additional action, for example, recommending changes to the Agreement to meet the concerns raised by our members and participants in the CWG. In order to meet the public comment deadline of 9 September, this will be one of the topics on our 1 September call. In the meantime I suggest two actions: 1) we monitor the CWG-Stewardship discussions around the IANA Functions Agreement closely and ask our ccTLD colleagues on the CWG if and how we as the ccNSO Council can be of assistance, for example, by submitting a statement proposing amendments to Agreement in support of their findings. The next opportunity to discuss this with our CWG members and participants will be next week on 25 August. 2) in addition, we should also follow the recommendation of the Triage Committee by sending out information to all relevant mailing lists. Finally, I also believe, and this is for the record, that the impact on ccTLDs should be rated as 'high' (now it is 'middle'). Have a lovely weekend! Kindest regards, ]{atrina -----Original Message----- From: owner-ccnso-council@icann.org [mailto:owner-ccnso-council@icann.org] On Behalf Of Nigel Roberts Sent: Thursday, August 18, 2016 6:37 PM To: Burr, Becky <Becky.Burr@neustar.biz> Cc: Joke Braeken <joke.braeken@icann.org>; ccnso-council@icann.org Subject: Re: [ccnso-council] [ 34 - 2016 ] IANA Naming Function Agreement Agree. This is something for discussion and if necessary, a Council Resolution. On 18/08/16 15:15, Burr, Becky wrote:
Stephen and I have been working on identifying issues and solutions. I think this is an important issue for the council to speak on
*J. Beckwith Burr**** **Neustar, Inc.***/**Deputy General Counsel & Chief Privacy Officer 1775 Pennsylvania Avenue NW, Washington D.C. 20006 *Office:***+1.202.533.2932 *Mobile:***+1.202.352.6367 */**neustar.biz* <http://www.neustar.biz>
From: Joke Braeken <joke.braeken@icann.org <mailto:joke.braeken@icann.org>> Date: Thursday, August 18, 2016 at 9:55 AM To: "'ccnso-council@icann. org'" <ccnso-council@icann.org <mailto:ccnso-council@icann.org>> Subject: [ccnso-council] [ 34 - 2016 ] - IANA Naming Function Agreement
Dear Councillors,
Please find below the proposed Triage recommendation 34-2016. Kindly provide me (by sending an email to joke.braeken@icann.org <mailto:joke.braeken@icann.org>) with your input by the end of Monday 22 August 2016, 23:59 UTC, in case you do not agree with the proposed recommendation. Thank you.
#######
Topic: [ 34 - 2016 ] - IANA Naming Function Agreement
Originator: ICANN
Summary of request:
This public comment proceeding seeks community input on the proposed IANA Naming Function Agreement. In order to reflect the recommendations contained in the proposals by the IANA Stewardship Transition Coordination Group (ICG) as provided to the ICANN Board and transmitted to NTIA on 10 March 2016, ICANN must incorporate an affiliate referred to as PTI, and put in place an agreement between ICANN and PTI granting PTI the right to perform the IANA naming function.
https://www.icann.org/public-comments/iana-naming-function-agreement-2016-08 -10-en
<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2 Dcomments_iana-2Dnaming-2Dfunction-2Dagreement-2D2016-2D08-2D10-2Den&d=DQMGa Q&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=C RtdozK1vvh5SxjcLCUFJcemRjS2xc1yhUm3Iqf1Azk&s=gGIlFi0_ZMHfMw1oiWsenVYefhq-xps KoAcrxuJjzus&e=>
Date received: 11 August 2016
Last day for Comments/input/response, if any: 9 September 2016
Recommended action, if any: send to cctldworld@
Expertise needed, if any: managerial, operational, legal, regulatory
Date of submission to Triage Committee: 11 August 2016
Recommendation received by Triage Committee: 16 August 2016
Date of submission to Council: 18 August 2016
Deadline Council decision: 22 August 2016, 23:59 UTC
Impact on ccNSO/ccTLDs: middle
########
Best regards,
Joke Braeken
ccNSO Policy Advisor
joke.braeken@icann.org <mailto:joke.braeken@icann.org>
Follow @ccNSO on Twitter: https://twitter.com/ccNSO
<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ccNSO&d=DQ MGaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k& m=CRtdozK1vvh5SxjcLCUFJcemRjS2xc1yhUm3Iqf1Azk&s=Q36QYWFCYLHC_b-XPG07m147VDjW J_CXO5BXiLA1Igo&e=>
Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/
<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_ccnso _&d=DQMGaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDD kMr4k&m=CRtdozK1vvh5SxjcLCUFJcemRjS2xc1yhUm3Iqf1Azk&s=V2S8igJYTN-RDznQ1qR34p 0tk-NUCM42YqCVf6yKl3c&e=>
<https://urldefense.proofpoint.com/v2/url?u=http-3A__ccnso.icann.org&d=DQMGa Q&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=C RtdozK1vvh5SxjcLCUFJcemRjS2xc1yhUm3Iqf1Azk&s=hRknT5QuLh9Bz5O9KMmJQ5tx_gcTI1y F05jz_Tl_MEA&e=>