Dear Gabi, In this particular case, to better understand the recommendation, I would like to know the arguments behind it. Reading the request (but possibly misunderstanding it) and considering the importance of the IANA services, a recommendation to the council to follow up on the Cheers, Roelof Meijer SIDN | Meander 501 | 6825 MD | P.O. Box 5022 | 6802 EA | ARNHEM | THE NETHERLANDS T +31 (0)26 352 55 00 | M +31 (0)6 11 395 775 | F +31 (0)26 352 55 05 roelof.meijer@sidn.nl<mailto:roelof.meijer@sidn.nl> | www.sidn.nl<http://www.sidn.nl/> request would not have surprised me From: owner-ccnso-council@icann.org [mailto:owner-ccnso-council@icann.org] On Behalf Of Gabriella Schittek Sent: woensdag 26 juni 2013 9:43 To: ccnso-council@icann.org Subject: [ccnso-council] Triage committee recommendation on IANA consultation * PGP - S/MIME Signed by an unverified key: 26-6-2013 at 9:42:55 Dear Councillors, The Triage Committee reviewed IANA's call for consultations on Source of Policies & User Instructions for Internet Number Resource Requests - the recommendation is just to forward to the community and encourage individual input to be submitted (this has also been done). If you disagree with the recommendation and would like to bring it further, please, let us know by the end of Friday, 28 June. Thanks! Gabi == Topic: IANA consultation on Source of Policies & User Instructions for Internet Number Resource Requests Originator: ICANN/IANA Summary of request: The IANA functions contract between ICANN and the United States Department of Commerce, NTIA to maintain the continuity and stability of services related to certain interdependent Internet technical management functions, IANA, calls for a public consultation to help satisfy the following objectives: C.2.6 Transparency and Accountability - [No later than 1 October 2013], the Contractor shall, in collaboration with all interested and affected parties as enumerated in Section C.1.3, develop user instructions including technical requirements for each corresponding IANA function and post via a website. C.2.7 Responsibility and Respect for Stakeholders - [No later than 1 October 2013], the Contractor shall, in collaboration with all interested and affected parties as enumerated in Section C.1.3, develop for each of the IANA functions a process for documenting the source of the policies and procedures and how it will apply the relevant policies and procedures for the corresponding IANA function and post via a website. The interested and affected parties are identified in C.1.3 as: ...the multi-stakeholder, private sector led, bottom-up policy development model for the domain name system (DNS) that the Internet Corporation for Assigned Names and Numbers (ICANN) represents; the Internet Engineering Task Force (IETF) and the Internet Architecture Board (IAB); Regional Internet Registries (RIRs); top-level domain (TLD) operators/managers (e.g., country codes and generic); governments; and the Internet user community. The IANA functions are identified in C.2.9 as: (1) the coordination of the assignment of technical Internet protocol parameters; (2) the administration of certain responsibilities associated with the Internet DNS root zone management; (3) the allocation of Internet numbering resources; and (4) other services related to the management of the ARPA and INT top-level domains (TLDs). This consultation relates to the user instructions for the allocation of Internet numbering resources. Date received: 25 June 2013 Last day for Comments/input/response, if any: 7 August 2013 Recommended action, if any: Post to relevant ccTLD email lists, encourage individual comments (done). Expertise needed, if any: Technical, managerial Last date of Council decision: End of business Day 28 June 2013. Impact on ccNSO/ccTLDs: Middle-low * Gabriella Schittek <gabriella.schittek@icann.org<mailto:gabriella.schittek@icann.org>> * Issuer: DigiCert Inc - Unverified