From nurani at netnod.se Thu Jan 1 20:41:55 2015 From: nurani at netnod.se (Nurani Nimpuno) Date: Thu, 1 Jan 2015 20:41:55 +0100 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] Editorial version of Internet Number Community IANA Stewardship, Proposal published References: <54A13E5B.6080205@nic.ad.jp> Message-ID: <61B51358-3077-4351-A1BD-EB765F758C33@netnod.se> FYI. Nurani Nimpuno Begin forwarded message: > From: Izumi Okutani > Subject: [NRO-IANAXFER] Editorial version of Internet Number Community IANA Stewardship, Proposal published > Date: 29 december 2014 12:43:23 CET > To: ianaxfer at nro.net > > Dear Colleagues, > > > CRISP Team has published an editorial version of the Internet > numbers community's response to the Request For Proposals issued by the > IANA Stewardship Coordination Group (ICG): > > http://www.nro.net/crisp-proposal-first-draft-1-1 > > From the initial draft we published on 19th Dec [*], we have made > editorial changes only. No changes are made in contents of the proposal. > > [*] > https://www.nro.net/wp-content/uploads/CRISP-IANA-PROPOSAL-First-Draft1.pdf > > The editorial changes are intended to clarify our answers to RFP, by > re-ordering answers in the same order as questions listed in each > Section. Some small additions have been made to address points that had > not been answered in the earlier draft. Finally, there are some changes > made for stylistic reasons. > > The deadline of the comments to be submitted to > mailing list remains the same: Monday 5th Jan 2015. > > Please let us know if you have any questions about version 1.1 of our > draft proposal, and we continue to welcome feedback from the community. > > > Best Regards, > Consolidated RIR IANA Stewardship Proposal Team (CRISP Team) > > _______________________________________________ > ianaxfer mailing list > ianaxfer at nro.net > https://www.nro.net/mailman/listinfo/ianaxfer From nurani at netnod.se Thu Jan 1 21:05:58 2015 From: nurani at netnod.se (Nurani Nimpuno) Date: Thu, 1 Jan 2015 21:05:58 +0100 Subject: [cooperation-wg] Fwd: [CRISP-TEAM] CRISP Team 7th Teleconference Friday January 2nd at 13:00 UTC References: <54A3DB57.5090302@lacnic.net> Message-ID: <9A45FE69-DEF2-460F-87B0-39A40D8AAFEB@netnod.se> Dear colleagues, Please find details below about the 7th CRISP teleconference. The CRISP teleconferences are open to observers. Kind regards, Nurani Nimpuno On behalf of the RIPE CRISP team Begin forwarded message: > From: Maria Gayo > Date: 31 december 2014 12:17:43 CET > To: crisp at nro.net > Subject: [CRISP-TEAM] CRISP Team 7th Teleconference Friday January 2nd at 13:00 UTC > Reply-To: mgayo at lacnic.net > > > This is an invitation to join the 7th CRISP Teleconference. > > Regards > > > Mar?a Gayo > (on behalf of the NRO Secretariat) > > Webex details below > > -------------- > > > CRISP Team 7th Teleconference > Friday, January 2, 2015 > 1:00 pm | UTC | 2 hr > > Join WebEx meeting > Meeting number: > 700 449 709 > Meeting password: > crispteam > > Join by phone > 0800-051-3810 Call-in toll-free number (UK) > +44-203-478-5289 Call-in toll number (UK) > Access code: 700 449 709 > Global call-in numbers | Toll-free calling restrictions > > Add this meeting to your calendar. > > Can't join the meeting? Contact support. > > IMPORTANT NOTICE: Please note that this WebEx service allows audio and other information sent during the session to be recorded, which may be discoverable in a legal matter. By joining this session, you automatically consent to such recordings. If you do not consent to being recorded, discuss your concerns with the host or do not join the session. > -- > Mar?a Gayo > Coordinadora de Comunicaciones > Communications Coordinator > # 4206 > Casa de Internet de > Latinoam?rica y el Caribe > Rambla Rep. de M?xico 6125 > 11400 Montevideo-Uruguay > +598 2604 22 22 www.lacnic.net > _______________________________________________ > CRISP mailing list > CRISP at nro.net > https://www.nro.net/mailman/listinfo/crisp -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jdjdgeea.png Type: image/png Size: 5594 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: jgfifgdh.png Type: image/png Size: 6213 bytes Desc: not available URL: From nurani at netnod.se Fri Jan 2 13:55:41 2015 From: nurani at netnod.se (Nurani Nimpuno) Date: Fri, 2 Jan 2015 13:55:41 +0100 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] Draft Agenda for 7th CRISP Teleconference Re: CRISP 7th Teleconference Friday January 2nd at 13:00 UTC References: <54A5EB55.1010503@nic.ad.jp> Message-ID: FYI. Begin forwarded message: > From: Izumi Okutani > Subject: [NRO-IANAXFER] Draft Agenda for 7th CRISP Teleconference Re: CRISP 7th Teleconference Friday January 2nd at 13:00 UTC > Date: 2 januari 2015 01:50:29 CET > To: ianaxfer at nro.net > > Dear Colleagues, > > > This is the draft agenda for the coming 7th CRISP Teleconference on Friday January 2nd at 13:00 UTC. > > The call is open to observers as usual - please see the invitation from the NRO Secretariat for details of joining the call. > > ---- > 1. Agenda Review > > 2. Actions Review > a. Mintutes from the last meeting > b. Recordings > c. Publish Issues status list on NRO Website > d. Issues raised (IRP,Contract,Review Team) > > 3. Feedback from the community > a. Other RIR community list > b. Status of continued topics > c. New topics raised > > 4. Next Steps > a. CRISP Team's general direction per issue > b. Volunteers to work on wording and communication > c. Updating the issues list > > 5. Next Meeting > > 6. AOB > ---- > > > Regards, > Izumi Okutani > > > On 2014/12/31 20:13, Maria Gayo wrote: >> >> >> >> This is an invitation to join the 7th CRISP Teleconference. >> >> Regards >> >> >> Mar?a Gayo >> (on behalf of the NRO Secretariat) >> >> Webex details below >> >> -------------- >> >> >> *CRISP Team 7th Teleconference* >> >> Friday, January 2, 2015 >> >> 1:00 pm | UTC | 2 hr >> >> *Join WebEx meeting* >> >> >> Meeting number: >> >> >> >> 700 449 709 >> >> Meeting password: >> >> >> >> crispteam >> >> *Join by phone* >> >> *0800-051-3810* Call-in toll-free number (UK) >> >> *+44-203-478-5289* Call-in toll number (UK) >> >> Access code: 700 449 709 >> >> Global call-in numbers >> | >> Toll-free calling restrictions >> >> Add this meeting >> to >> your calendar. >> >> Can't join the meeting? Contact support. >> >> IMPORTANT NOTICE: Please note that this WebEx service allows audio and other >> information sent during the session to be recorded, which may be discoverable in >> a legal matter. By joining this session, you automatically consent to such >> recordings. If you do not consent to being recorded, discuss your concerns with >> the host or do not join the session. >> >> >> >> >> >> >> >> -- >> Embedded Image >> *Mar?a Gayo* >> Coordinadora de Comunicaciones >> Communications Coordinator >> *# 4206* >> Embedded Image >> *Casa de Internet de >> Latinoam?rica y el Caribe* >> Rambla Rep. de M?xico 6125 >> 11400 Montevideo-Uruguay >> +598 2604 22 22 www.lacnic.net >> >> >> >> >> _______________________________________________ >> ianaxfer mailing list >> ianaxfer at nro.net >> https://www.nro.net/mailman/listinfo/ianaxfer >> > > > _______________________________________________ > ianaxfer mailing list > ianaxfer at nro.net > https://www.nro.net/mailman/listinfo/ianaxfer From nurani at netnod.se Fri Jan 2 16:39:17 2015 From: nurani at netnod.se (Nurani Nimpuno) Date: Fri, 2 Jan 2015 16:39:17 +0100 Subject: [cooperation-wg] Fwd: [CRISP-TEAM] CRISP Team 8th Teleconference January 5th 2015 @ 13:00 UTC References: Message-ID: <798B2388-4BA8-4621-8485-37570E849EB4@netnod.se> Fyi. The CRISP teleconferences are open to observers. Nurani Begin forwarded message: > From: German Valdez > Date: 2 januari 2015 16:03:18 CET > To: , > Subject: [CRISP-TEAM] CRISP Team 8th Teleconference January 5th 2015 @ 13:00 UTC > > Hi > > Please find below webex information for the 8th CRISP Team teleconference to be held on Monday January 5th 2015 at 13:00 UTC > > Regards > > German Valdez > NRO > > > ====== > > CRISP Team 8thTeleconference > Monday, January 5, 2015 > 1:00pm | UTC | 2 hr > > Join WebEx meeting > https://ripencc.webex.com/ripencc/j.php?MTID=mc7fe8904fb98d0e4132409b1f6362d5d > > Meeting number: > 701 103 817 > Meeting password: > crispteam > > Join by phone > 0800-051-3810 Call-in toll-free number (UK) > +44-203-478-5289 Call-in toll number (UK) > Accesscode: 701 103 817 > Global call-in numbers | > > https://ripencc.webex.com/ripencc/globalcallin.php?serviceType=MC&ED=359012912&tollFree=1 > > Toll-free calling restrictions > > http://www.webex.com/pdf/tollfree_restrictions.pdf > > > Add this meeting to your calendar. > > Can't join the m Contact support. > > IMPORTANT NOTICE: Please note thatsession. > > _______________________________________________ > CRISP mailing list > CRISP at nro.net > https://www.nro.net/mailman/listinfo/crisp -------------- next part -------------- An HTML attachment was scrubbed... URL: From nurani at netnod.se Fri Jan 2 20:52:26 2015 From: nurani at netnod.se (Nurani Nimpuno) Date: Fri, 2 Jan 2015 20:52:26 +0100 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] Editorial version of Internet Number Community IANA Stewardship, Proposal published References: <54A6E0A5.2030506@nic.ad.jp> Message-ID: <20EB2E8D-FB2C-43B3-902E-5047CF048843@netnod.se> Dear colleagues, Firstly, a very happy new year to all of you! :) I hope you all had a well deserved rest. As you may know, the CRISP team, tasked with coming up with a proposal for the Internet numbers community on the IANA stewardship transition, has published a first draft. We would warmly welcome any comments you have on this draft, on the global mailing list. The deadline for feedback on this draft is 5 January. The second draft will be distributed on 8 January, and the very final proposal is due for submission 15 January. Kind regards, Nurani on behalf of the RIPE CRISP team -- Nurani Nimpuno Head of Outreach & Communications, Netnod , http://www.netnod.se Box 30194 | SE-104 25 Stockholm | Sweden --------------------------------------------- Begin forwarded message: > From: Izumi Okutani > Subject: Re: [NRO-IANAXFER] Editorial version of Internet Number Community IANA Stewardship, Proposal published > Date: 2 januari 2015 19:17:09 CET > To: ianaxfer at nro.net > > Dear Colleagues, > > > > This is a friendly reminder that the deadline for providing feedback to the first draft of the proposal from Internet Number Community on IANA Stewardship is: 5 January 2015. > > Based on the request made by a community member on this mailing list, please find below the text format of the first proposal. This is identical to the edited version of the first proposal published at: > > https://www.nro.net/wp-content/uploads/CRISP-IANA-PROPOSAL-Draft-24122014-clean.pdf > > We continue to welcome your feedback on mailing list. > > > > Best Regards, > > Izumi Okutani > Chair, Consolidated RIR IANA Stewardship Proposal (CRISP) team > > ------------------------------------------------------------------------------- > Draft Response to the Internet Coordination Group Request for > Proposals on IANA from the RIR community > 1. Proposal type > > Identify which category of the IANA functions this submission proposes to address: > > [ ] Names > [ ?] Numbers > [ ] Protocol Parameters > > > > I. Description of Community?s Use of IANA > > This section should list the specific, distinct IANA services or activities your community relies > on. For each IANA service or activity on which your community relies, please provide the following: > > ? A description of the service or activity. > ? A description of the customer(s) of the service or activity. > ? What registries are involved in providing the service or > activity. > ? A description of any overlaps or interdependencies between > your IANA requirements and the > functions required by other customer communities > > ------- > ? A description of the service or activity. > > The relevant IANA activities to the number resource communities are the allocation of IPv4 addresses, IPv6 addresses, and Autonomous System Numbers (?ASNs?) to the Regional Internet Registries (?RIRs?) as well as the delegation of the ?IN-ADDR.ARPA? and ?IP6.ARPA? DNS trees in accordance with the allocation of IPv4 and IPv6 addresses. > > ? A description of the customer(s) of the service or activity. > > The RIRs manage the registration and distribution of Internet number resources (IPv4 and IPv6 addresses and ASNs) to members within their service regions. The five RIRs in operation at this point in time are: > > AFRINIC Serving Africa Founded in 2005 > APNIC Serving the Asia Pacific region Founded in 1993 > ARIN Serving North America Founded in 1997 > LACNIC Serving South America and the Caribbean Founded in 2001 > RIPE NCC Serving Europe, Central Asia and the Middle East Founded in 1992 > > The five RIRs manage the distribution and registration of Internet number resources at the regional level, having received blocks of unused resources from the global pools managed by the IANA operator. The RIRs also facilitate the policy development processes of their > respective communities. > > The five RIRs have a long-standing and straightforward operational relationship with IANA. IANA maintains the global pools of Internet number resources from which the RIRs receive allocations to distribute to their communities. The RIRs also coordinate with IANA to correctly register any resources that are returned to the global pools. Collectively, the system for administering Internet number resources is referred to as the "Internet Number Registry System" and is described > in detail in RFC 7020. > > ------- > ? What registries are involved in providing the service or > activity. > > The most relevant IANA registries are the IPv4 address registry, the IPv6 address registry, and the ASN registry. Delegation of ?IN-ADDR.ARPA? and ?IP6.ARPA?domain names also requires interaction with the .ARPA zone registry. > > ------- > ? A description of any overlaps or interdependencies between > your IANA requirements and the > functions required by other customer communities. > > The Internet Engineering Task Force (?IETF?) is responsible for policy relating to the entire IP address space and AS number space. Through the IANA protocol parameters registries, the IETF delegates unicast IP address ("IANA IPv4 Address Space Registry" and "IPv6 Global Unicast Allocations Registry") and AS number space (?ASN Registry) to the RIR system [RFC7020]. Note that within each IANA registry, there are also reserved values or ranges, and special-purpose registries, which are outside the Internet Numbers Registry System and instead administered under the direction of the IETF. The delineation of the specific ranges delegated to the Internet Number Registry system is provided in RFC 7249. It is expected that the boundary between IETF-managed and Internet Number Registry-managed parts of the number spaces may change from time to time, with agreement between the IETF and the RIRs. Potential reasons for changes include the possibility > that the IETF may release some previously reserved space for general use, or may reserve some previously unused space for a special purpose. > The global Internet community also depends upon the IANA operator for administration of the special-purpose ?IN-ADDR.ARPA? and ?IP6.ARPA? DNS zones which are associated with IPv4 and IPv6 number resources respectively. These zones are delegated to IANA by the Internet Architecture Board (?IAB?) and ?[s]ub-delegations within this hierarchy are undertaken in accordance with the IANA?s address allocation practices? (RFC3172). The IANA operator administers these zones as ?agreed technical work items? per the IETF- Internet Corporation for Assigned Names and Numbers (?ICANN?) IANA MoU. It is important to note that this work is outside the scope of the National > Telecommunications and Information Administration (?NTIA?) contract. > > Relevant links: > IETF-ICANN MoU Concerning the Technical Work of the Internet Assigned Numbers Authority: > https://www.icann.org/resources/unthemed-pages/ietf-icann-mou-2000-03-01-en > ?The Internet Numbers Registry System?, RFC 7020: https://tools.ietf.org/html/rfc7020 ?Internet > Numbers Registries?, RFC 7249: https://tools.ietf.org/html/rfc7249 > > > > II. Existing, Pre-Transition Arrangements > > This section should describe how existing IANA-related arrangements work, prior to the transition. > > A. Policy Sources > > This section should identify the specific source(s) of policy which must be followed by the IANA functions operator in its conduct of the services or activities described above. If there are distinct sources of policy or policy development for different IANA activities, then please describe these separately. For each source of policy or policy development, please provide the following: > > ? Which IANA service or activity (identified in Section I) is > affected. > ? A description of how policy is developed and established and > who is involved in policy development and establishment. > ? A description of how disputes about policy are resolved. > ? References to documentation of policy development and dispute > resolution processes. > > ------- > ? Which IANA service or activity (identified in Section I) is > affected. > > The Internet number resource registries. > > It is important to note that allocations of Internet number resources from IANA to the RIRs and its registrations in IANA registries, as well as delegations of ?IN-ADDR.ARPA? and ?IP6.ARPA? domains, described in Section I, are conducted between IANA and the RIRs without involvement by the NTIA. > > ------- > ? A description of how policy is developed and established and > who is involved in policy development and establishment. > > The policies under which the IANA operator manages the global pools of Internet number resources (excluding those address ranges reserved by the IETF for specific technical purposes) are developed and agreed by the five RIR communities via open, transparent and bottom-up policy development processes. Each RIR community engages in its own regional policy development process; these processes are open to all stakeholders regardless of specific background or interest. Links to each of the five regional Policy Development Processes (?PDPs?) are included under in the RIR Governance Matrix published on the Number Resource Organization (?NRO?) website [www.nro.net/about-the-nro/rir-governance- matrix]. > > Any individual may submit a global proposal. Each RIR community must ratify an identical version of the proposed policy. The NRO Executive Council (?NRO EC?) then refers the coordinated proposal to the Address Supporting Organization (?ASO?) Address Council (?ASO AC?), which reviews the process by which the proposal was developed and, under the terms of the ASO Memorandum of Understanding (?ASO MoU?), passes it to the ICANN Board of Directors for ratification as a global policy. > > There are currently three global policies relating to management of the global pools of IPv4 addresses, IPv6 addresses and AS Numbers [https://www.nro.net/policies]: > > (a) IANA Policy for Allocation of IPv6 Blocks to Regional Internet Registries; > (b) IANA Policy for Allocation of ASN Blocks to Regional Internet Registries; and > (c) Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA. > > There is a fourth global policy agreed by the RIR communities, ICP-2, "Criteria for Establishment of New Regional Internet Registries". > > The global Policy Development Process (?gPDP?) described in ?Global Policy Development Process Document? [https://www.nro.net/documents/global-policy-development- process] is used for all of the number-related IANA activities described in Section I, but the policy that > ?IN-ADDR.ARPA? and ?IP6.ARPA? domains must be delegated following IPv4 and IPv6 address allocations is specified by the IETF (most recently in RFC 3172). > > ------- > ? A description of how disputes about policy are resolved. > > The gPDP is formally described in "Attachment A" of the ASO MoU, signed by ICANN and the RIRs in 2004 (and signed by AFRINIC when it was established as the fifth RIR in 2005). This MoU includes provisions for resolving disputes between ICANN and the RIRs or their communities. It is important to note that while the gPDP allows for the ICANN Board to dispute the outcome of a consensus community decision (escalating to mediation between ICANN and the RIRs), it does not include any role for the IANA contract holder (currently the NTIA). The ASO MoU is an agreement between the RIR communities and ICANN; NTIA has no oversight role in policy-making as regards management of the global Internet number resource pools, and its transition out of its current role would have minimal effect on the policy-making framework. > > A separate MoU, the NRO MoU, establishes the NRO as "a coordinating mechanism of the RIRs to act collectively on matters relating to the interests of the RIRs", and includes provisions for dispute resolutions between RIRs on issues relating to global policy development or implementation. > > It is the responsibility of the NRO Number Council (?NRO NC?), a group comprising three community members selected by each of the five RIR communities, to confirm that the documented RIR PDPs have been followed in the development and approval of a new policy or policy change. Further, this group reviews the policy followed by each of the RIR communities to assure itself that the significant viewpoints of interested parties were adequately considered,and only after this confirmation does it then consider forwarding global policy proposals to the ICANN Board for ratification. > > The NRO NC also acts in the role of the ICANN ASO AC, and as such, presents the agreed global policy proposal to the ICANN Board for ratification and operational implementation. > > The ICANN Board reviews the received global number resource policy proposals and may ask questions and otherwise consult with the ASO Address Council and/or the individual RIRs acting collectively > through the NRO. The ICANN Board may also consult with other parties as the Board considers appropriate. If the ICANN Board rejects the proposed policy, it delivers to the ASO ACa statement of its concerns with the proposed policy, including in particular an explanation of the significant viewpoints that were not adequately considered during the regular RIR processes. By agreement of all RIRs, the ASO AC may forward a new proposed policy (either reaffirming the previous proposal or > a modified proposal) to the ICANN Board. If the resubmitted proposed policy is rejected for a second time by ICANN, then the RIRs or ICANN shall refer the matter to mediation. > > In case of disputes where mediation has failed to resolve the dispute, the ICANN ASO MoU agreement provides for arbitration via ICC rules in the jurisdiction of Bermuda or such other location as is agreed between the RIRs and ICANN. It is also worth noting that the RIRs have been participating (as the ASO) in the periodic independent review processes for Accountability and Transparency (ATRT) that is called for per ICANN?s Bylaws. > > ------- > ? References to documentation of policy development and dispute > resolution processes. > > Relevant links: > ICANN ASO MoU: https://www.nro.net/documents/icann-address-supporting-organization-aso- mou > NRO MoU: https://www.nro.net/documents/nro-memorandum-of-understanding > About the NRO Number Council: https://www.nro.net/about-the-nro/the-nro-number-council RIR > Governance Matrix: https://www.nro.net/about-the-nro/rir-governance-matrix > Global Policies: https://www.nro.net/policies > > > > B. Oversight and Accountability > > This section should describe all the ways in which oversight is conducted over IANA?s provision of the services and activities listed in Section I and all the ways in which IANA is currently held accountable for the provision of those services. For each oversight or accountability mechanism, please provide as many of the following as are applicable: > > ? Which IANA service or activity (identified in Section I) is > affected. > ? If the policy sources identified in Section II.A are affected, > identify which ones are affected and explain in what way. > ? A description of the entity or entities that provide oversight > or perform accountability functions, including how individuals > are selected or removed from participation in those entities. > ? A description of the mechanism (e.g., contract, reporting > scheme, auditing scheme, etc.). > This should include a description of the consequences of the > IANA functions operator not meeting the standards established > by the mechanism, the extent to which the output of the > mechanism is transparent and the terms under which the > mechanism may change. > ? Jurisdiction(s) in which the mechanism applies and the legal > basis on which the mechanism rests. > > ------- > ? Which IANA service or activity (identified in Section I) is > affected. > > The Internet number resource registries. > > ------- > ? If the policy sources identified in Section II.A are affected, > identify which ones are affected and explain in what way. > > A decision by the NTIA to discontinue its stewardship of the IANA functions, and therefore its contractual relationship with the IANA functions operator, would not have any significant impact on the continuity of Internet number-related IANA services currently provided by ICANN. However, it would remove a significant element of oversight from the current system. > > There is no contractual obligation directly to the Internet number resource community for the IANA operator to provide IANA registry services for the Internet number registries; IANA services for > the Internet number registries are provided by ICANN since its formation as a result of the NTIA IANA Functions contract and hence IANA services for the Internet number registries are presently > subject to change per that agreement. > > ------- > ? A description of the entity or entities that provide oversight > or perform accountability functions, including how individuals > are selected or removed from participation in those entities. > > All institutional actors with a role in management of Internet number resources are accountable to the open communities that make and agree on the policies under which those resources are distributed and registered. The mechanisms used to ensure and enforce this accountability differ for each of these actors. > > 1. NTIA > ICANN, as the current operator of the IANA functions, is obligated by the NTIA agreement to carry out management of the global IP address and AS Number pools according to policies developed by the communities. > > While the IANA operator escalation and reporting mechanisms are public in nature, the Internet number community is primarily represented in oversight of the IANA operator performance by the RIRs, which are member-based based organizations with elected governance boards. > Currently, the NTIA does not have an oversight role in this regard. > > The ultimate consequence of failing to meet the performance standards or reporting requirements is understood to be a decision by the contracting party (the NTIA) to terminate or not renew the IANA > functions agreement with the current contractor (ICANN). > > 2. The Regional Internet Registries > > Administration by the IANA operator consists predominantly of processing of requests from the RIRs for issuance of additional number resources. The five RIRs are intimately familiar with global number resource policies under which the requests are made and maintain communications with the IANA operations team throughout the request process. > > The RIRs are not-for-profit membership associations, and as such are accountable to their members by law. The specific governance processes for each RIR differ depending on where they have been established and the decisions made by their membership, but in all RIRs, members have the right to vote individuals onto the governing Board and to vote on specific funding or operational resolutions. > > At the same time, an RIR's registration and allocation practices are directed by policies developed by its community. Each RIR community's PDP defines how these policies are developed, agreed and accepted for operational implementation. > > The corporate governance documents and PDPs of each RIR and its community are accessible via the RIR Governance Matrix, published on the NRO website. > > ------- > ? A description of the mechanism (e.g., contract, reporting > scheme, auditing scheme, etc.). > This should include a description of the consequences of the IANA functions operator not meeting the standards established by the mechanism, the extent to which the output of the mechanism is > transparent and the terms under which the mechanism may change. > > The NTIA IANA Agreement currently defines obligations of the IANA operator for Internet number resources. > > This obligation is specifically noted in section C.2.9.3 of the NTIA agreement: > > C.2.9.3 Allocate Internet Numbering Resources --The Contractor shall have responsibility for allocated and unallocated IPv4 and IPv6 address space and Autonomous System Number (ASN) space based on established guidelines and policies as developed by interested and affected parties as enumerated in Section C.1.3. > > The NTIA agreement also lays out specific deliverables for the IANA operator (ICANN) to produce as a condition of the agreement (see "Section F ? Deliveries and Performance"), including performance > standards developed in cooperation with the affected parties (in the case of the Internet number resource pools, the affected parties include the RIRs and their communities), customer complaint > procedures and regular performance reporting. > > These deliverables are met by ICANN via monthly reporting on their performance in processing requests for the allocation of Internet number resources; these reports include IANA operator performance against key metrics of accuracy, timeliness, and transparency, as well as the performance metrics for individual requests. The IANA operations team also provides escalation procedures for use in resolving any issues with requests, as per the "IANA Customer Service Complaint Resolution Process". > > ------- > ? Jurisdiction(s) in which the mechanism applies and the legal > basis on which the mechanism rests. > > Jurisdiction for this current mechanism is the United States of America under applicable Federal government contracting laws and regulations. > > Relevant links: > NTIA IANA Agreement: http://www.ntia.doc.gov/page/iana-functions-purchase-order > ICANN ASO MoU: https://www.nro.net/documents/icann-address-supporting-organization-aso- mou > NRO MoU: https://www.nro.net/documents/nro-memorandum-of-understanding > IANA Customer Service Complaint Resolution Process: http://www.iana.org/help/escalation- procedure > IANA Performance Standards Metrics Report: http://www.iana.org/performance/metrics > RIR Governance Matrix: https://www.nro.net/about-the-nro/rir-governance-matrix > > > > III. Proposed Post-Transition Oversight and Accountability Arrangements > > This section should describe what changes your community is proposing to the arrangements listed in Section II.B in light of the transition. If your community is proposing to replace one or more existing arrangements with new arrangements, that replacement should be explained and all of the elements listed in Section II.B should be described for the new arrangements. Your community should > provide its rationale and justification for the new arrangements. > > If your community?s proposal carries any implications for the interface between the IANA functions and existing policy arrangements described in Section II.A, those implications should be described > here. > > If your community is not proposing changes to arrangements listed in Section II.B, the rationale and justification for that choice should be provided here. > > ------- > The elements of this proposal are as follows: > > (1) ICANN to continue as the IANA functions operator on number > resources; > (2) Service level agreement with the IANA functions operator on > number resources; and > (3) Establishment of a Review Committee, with representatives > from each RIR, to advise the NRO EC on the review of the > IANA functions operator?s performance and meeting of > identified service levels. > > To maintain stability and continuity in operations of the Internet number-related IANA services, very minimal changes to the arrangements listed in Section II.B are proposed, including the identification of the proposed initial IANA functions operator. As noted in numerous NRO > communications over the past decade, the RIRs have been very satisfied with the performance of ICANN in the role of IANA functions operator. Taking this into account, and considering the strong desires expressed in the five RIR communities' IANA stewardship discussions for stability and a minimum of operational change, the Internet numbering community believes that ICANN should remain in the role of IANA functions operator for at least the initial term of the new contract. > > A decision by the NTIA to discontinue its stewardship of the IANA functions, and therefore its contractual relationship with the IANA functions operator, would not have any significant impact on > the continuity of Internet number-related IANA services currently provided by ICANN. However, it would remove a significant element of oversight from the current system. > > The following is a proposal to replace the current NTIA IANA agreement with a new contract that more directly reflects and enforces the IANA functions operator's accountability to the open, > bottom-up numbers community. Other than the replacement of the NTIA with the five RIRs as the party(ies) with whom the IANA functions operator would contract for provision of Internet number-related IANA services, the overall arrangements in Section II.B would remain with no change. > > The proposed arrangement involves the same IANA service or activity, policy sources identified in Section II.A are unaffected, the entities that provide oversight or perform accountability functions (the RIRs) remain the same, the consequence for failure to meet performance standards remains termination or decision not to renew the IANA functions agreement with the then-current contractor, and jurisdiction will be dependent on the chosen IANA functions operator. > > The Internet numbering community proposes that a new contract be established between the IANA functions operator and the five RIRs. The contract, essentially an IANA Service Level Agreement, would obligate the IANA functions operator to carry out those IANA functions relating to the global Internet number pools according to policies developed by the regional communities via the gPDP as well as management of the delegations within IN-ADDR.ARPA and IP6.ARPA domains. The agreement would include specific requirements for performance and reporting commensurate with current mechanisms, and would specify consequences should the contractor fail to meet those requirements, the means for the resolution of disputes between the parties, and the terms for renewal or termination of the contract. IANA operations should be > reliable and consistent, with any registry changes made in an open and transparent manner to the global community. The agreement should also require the IANA operator to appropriately coordinate with any other operator of IANA-related registry services. > > To ensure the service level defined in the proposed contract is maintained and provided by the IANA functions operator, the NRO EC will conduct periodic reviews of the service level of the IANA number resource functions that serves each RIR and their respective communities. The NRO EC shall establish a Review Committee that will advise and assist the NRO EC in its periodic review. Any such Review Committee should be a team composed of representatives from each RIR region that will, as needed, undertake a review of the level of service received from the IANA functions operator and report to the NRO EC any concerns regarding any observed failure by the IANA functions operator to meet its contractual obligations under the proposed contract. Any such Review Committee will advise the NRO EC in its capacity solely to oversee the performance of the IANA number resource functions and the Review Committee?s advice and comment will be limited to the processes followed in the IANA functions operator?s performance under the proposed contract. > > If your community?s proposal carries any implications for the interface between the IANA functions and existing policy arrangements described in Section II.A, those implications should be described > here. > > This proposal carries no implication for the interface between IANA functions and existing policy arrangements described in Section II.A. The text in "Attachment A" of the ICANN ASO MoU meets the current and anticipated requirements for a community-driven global policy development process. > > As an additional measure of security and stability, the RIRs have documented their individual accountability and governance mechanisms, and asked the community-based Number Resource Organization Number Council (NRO NC) to undertake a review of these mechanisms and make > recommendations for improvements that may be warranted given the nature of the stewardship transition for Internet number resources. > > > IV. Transition Implications > > This section should describe what your community views as the implications of the changes it proposed in Section III. These implications may include some or all of the following, or other > implications specific to your community: > > ? Description of operational requirements to achieve continuity > of service and possible new service integration throughout the > transition. > ? Risks to operational continuity and how they will be addressed. > ? Description of any legal framework requirements in the absence > of the NTIA contract. > ? Description of how you have tested or evaluated the > workability of any new technical or > operational methods proposed in this document and how they > compare to established arrangements. > > ------- > ? Description of operational requirements to achieve continuity > of service and possible new service integration throughout the > transition. > ? Risks to operational continuity and how they will be addressed. > > The intent of the proposal described above is to: > > 1. Minimize risks to operational continuity of the management of the Internet number- related IANA functions, and; > 2. Retain the existing framework for making those policies that describe the management of the global Internet number resource pools, as this framework is already structured to ensure open, bottom-up development of such policies. > > Under current arrangements, the NTIA is responsible for extending or renewing the IANA functions agreement, and setting the terms of that contract. A new contract with the five RIRs and the IANA functions operator as signatories would shift the responsibility for renewing, setting terms or terminating the contract to the RIRs, who would coordinate their decisions via the NRO EC (made up of the RIR Directors and Chief Executives). Decisions made regarding the contract would be based on operational circumstances, past performance and input from open, regional communities. > > The shift from the existing contractual arrangement to another contractual arrangement (perhaps relying on a set of distinct contracts) covering the IANA functions operator?s ongoing management > of all the IANA functions should result in no operational change for management of the global Internet number resource pools. This will help minimize any operational or continuity risks associated with stewardship transition. > > By building on the existing Internet registry system (which is open to participation from all interested parties) and its structures, the proposal reduces the risk associated with creating new organizations whose accountability is unproven. > > The necessary agreement proposed for IANA operation services for the Internet number registries can be established well before the NTIA target date for transition (September 2015), as there are no changes to existing service levels or reporting that are being proposed, only a change in contracting party to align with the delegated policy authority. > > ------- > ? Description of any legal framework requirements in the absence > of the NTIA contract. > > The necessary legal framework in the absence of the NTIA contract will be fulfilled by the proposed agreement between the IANA functions operator and the five RIRs. As stated in Section III above, > the contract, essentially an IANA Service Level Agreement, would obligate the IANA functions operator to carry out those IANA functions relating to the global Internet number pools according to policies developed by the regional communities via the gPDP as well as > management of the delegations within IN-ADDR.ARPA and IP6.ARPA domains. The agreement would include specific requirements for performance and reporting commensurate with current mechanisms, and would specify consequences should the contractor fail to meet those requirements, the means for the resolution of disputes between the parties, and the terms for renewal or termination of the contract. IANA operations should be reliable and consistent, with any registry changes made in an open and transparent manner to the global community. > > The agreement should also require the IANA operator to appropriately coordinate with any other operator of IANA-related registry services. The contract would also provide for jurisdiction and governing law regarding the new arrangement. > > ------- > ? Description of how you have tested or evaluated the > workability of any new technical or > operational methods proposed in this document and how they > compare to established arrangements. > ? Risks to operational continuity and how they will be addressed. > > This proposal does not propose any new technical or operational methods. There is inclusion of a proposed Review Committee to be established by the five RIRs acting cooperatively and coordinating > through the NRO EC; however, this does not carry any new operational method as the IANA functions operator would remain accountable to the party with whom it is contracting, in this case, the five RIRs in place of the NTIA. The proposed Review Committee is a tool for the five RIRs to evaluate and review performance of the IANA functions provided. > > > > V. NTIA Requirements > > Additionally, NTIA has established that the transition proposal must meet the following five requirements: > > ? Support and enhance the multistakeholder model; > ? Maintain the security, stability, and resiliency of the > Internet DNS; > ? Meet the needs and expectation of the global customers and > partners of the IANA services; > ? Maintain the openness of the Internet. > ? The proposal must not replace the NTIA role with a > government-led or an inter-governmental organization solution. > > This section should explain how your community?s proposal meets these requirements and how it responds to the global interest in the IANA functions. > > ------- > The proposal for the IANA stewardship transition for the Internet number registries builds upon the existing, successful framework used by the Internet number community today. The major characteristics of this approach include: > > 1. Global number policy development which is open and transparent to any and all participants > 2. Continuance of existing IANA service levels, escalation processes, and reporting mechanisms > 3. Maintenance of independent review and ratification for developed global Internet number resource policy > 4. Continued use of periodic third-party independent reviews of accountability and transparency of processes > 5. No change of the existing IANA operator for maximum stability and security of operational processes and systems > 6. Accountable, member-based, globally-distributed RIR organizations providing routine IANA operational oversight for the Internet number registries > 7. No new organization is proposed. However, a new process within the RIR structures is proposed, where a Review Committee is established to advise and assist the NRO EC in its periodic review of the service level provided by the IANA functions operator. > > As a result of the approach taken (and its characteristics as outlined above), it is clear that the proposal from the Internet number community meets the stated NTIA requirements. > > > VI. Community Process > > This section should describe the process your community used for developing this proposal, including: > > ? The steps that were taken to develop the proposal and to > determine consensus. > ? Links to announcements, agendas, mailing lists, consultations > and meeting proceedings. > ? An assessment of the level of consensus behind your > community?s proposal, including a description of areas of > contention or disagreement. > > ------- > 1. Regional and global process > > Each of the five RIR communities is discussing the IANA stewardship issues via mailing lists, at their RIR meetings and in other community forums. While these discussions have been uniformly open and transparent, with all discussions archived on mailing lists and meeting records, each community has adopted a specific process of their own choosing to reach an agreed community output. > > The results from the five regional processes fed a global process that produced this document. More details about the regional and global processes are given below, interspersed with links to relevant documents. > > 2. AFRINIC regional process: > The AFRINIC community held a consultative meeting on 25 May to 6 June 2014 during the Africa Internet Summit (AIS'2014) in Djibouti in the "IANA oversight transition" workshop. As a follow up to the meeting, AFRINIC setup a mailing list to provide a platform for the African > Internet community to discuss the IANA Oversight Transition process. The mailing list was announced on July 4, 2014 to develop a community position. The list and its archives can be found at: > https://lists.afrinic.net/mailman/listinfo.cgi/ianaoversight > > A Dedicated web portal was setup for sharing information on the IANA stewardship transition with the AFRINIC community and is also available at http://afrinic.net/en/community/iana-oversight-transition > > AFRINIC also conducted a survey seeking community input on the IANA Stewardship Transition. The results of the survey are published > at: http://afrinic.net/images/stories/Initiatives/%20survey%20on%20the%20iana%20stewardship > %20transition.pdf > > > The last face-to-face meeting at which IANA oversight transition consultations were held with the community was during the AFRINIC-21 meeting in Mauritius, 22-28 November 2014. The recordings of > the session are available at http://meeting.afrinic.net/afrinic-21/en/vod > > Discussions continued on the ianaoversight at afrinic.net mailing list, until the closure of the comments from the number resources communities set by the CRISP Team on 12th Jan 2015. > > 3. APNIC regional process: > APNIC, as the secretariat for the APNIC community has set up a public mailing list (announced on 1 Apr 2014) to develop a community position, and have discussions about the proposal from the region on IANA stewardship transition: http://mailman.apnic.net/mailman/listinfo/IANAxfer > > Webpage, dedicated to sharing up-to-date information on the IANA stewardship transition was set up, for the APNIC community members and wider community members who are interested in this issue can be updated: http://www.apnic.net/community/iana-transition > > Draft proposal was discussed at the dedicated session at the APNIC 38 Meeting, which saw the general community consensus. The meeting provided > remote participation tools to enable wider participation from communities across Asia Pacific and beyond, with live webcasts well as Adobe Connect virtual conference room. > > https://conference.apnic.net/38/program#iana > > The discussions continued on the "ianaxfer at apnic.net." mailing list, > until the closure of the comments from the number resources communities set by CRISP Team as 12th Jan 2015. > > 4. ARIN regional process: > > > > 5. LACNIC regional process: > > > > > 6. RIPE regional process: > The RIPE community agreed at the RIPE 68 Meeting in May 2014 that the development of a community position on IANA stewardship should take place in the RIPE Cooperation Working Group, and via that working group's public mailing list: https://www.ripe.net/ripe/mail/wg- lists/cooperation > > The RIPE NCC, as secretariat for the RIPE community, also facilitated discussions on the IANA stewardship in national and regional forums across the RIPE NCC service region. Summaries of these discussions were posted to the RIPE Cooperation Working Group mailing list and on the RIPE website: > https://www.ripe.net/iana-discussions > > Between September and November 2014, RIPE community discussion centered around developing a set of principles reflecting the communities primary concerns in the development of an alternative IANA stewardship arrangement. These discussions are reflected in the discussions on the mailing list from that time: http://www.ripe.net/ripe/mail/archives/cooperation- wg/ > > Discussions at the RIPE 69 Meeting in November 2014 saw general community consensus on the principles discussed on the mailing list, and support expressed for the three community members selected to join the Consolidated RIR IANA Stewardship Proposal (CRISP) team. > > RIPE Cooperation Working Group Session: https://ripe69.ripe.net/programme/meeting- plan/coop-wg/#session1 > RIPE 69 Closing Plenary Session: https://ripe69.ripe.net/archives/video/10112/ > > ------- > 7. Global process (CRISP Team) > On 16 October 2014, the NRO EC proposed the formation of a Consolidated RIR IANA Stewardship > > Proposal (CRISP) team to develop a single Internet numbering community proposal to the IANA Stewardship Coordination Group (ICG). Each RIR community selected three members (two community members and one RIR staff) to participate in the team. The participants selected were: > > AFRINIC Region > Alan P. Barrett ? Independent Consultant > Mwendwa Kivuva ? Network Infrastructure Services, University of Nairobi Ernest Byaruhanga (Appointed RIR staff) > > ARIN Region > Bill Woodcock ? President and Research Director of Packet Clearing House > John Sweeting ? Sr. Director, Network Architecture & Engineering at Time Warner Cable > Michael Abejuela (Appointed RIR staff) > > APNIC Region > Dr Govind ? CEO NIXI > Izumi Okutani ? Policy Liaison JPNIC > Craig Ng (Appointed RIR staff) > > LACNIC Region > Nico Scheper - Curacao IX > Esteban Lescano - Cabase Argentina > Andr?s Piazza (Appointed RIR staff) > > RIPE NCC Region > Nurani Nimpuno ? Head of Outreach & Communications at Netnod > Andrei Robachevsky ? Technology Programme Manager at the Internet Society Paul Rendek (Appointed > RIR staff) > > Steps and timeline for proposal development and links to announcements, mailing lists, and > proceedings - https://www.nro.net/nro-and-internet-governance/iana-oversight/timeline-for-rirs- > engagement-in-iana-stewardship-transition-process > > ------- > 8. Assessment of consensus level > > > > > On 2014/12/29 20:43, Izumi Okutani wrote: >> Dear Colleagues, >> >> >> CRISP Team has published an editorial version of the Internet >> numbers community's response to the Request For Proposals issued by the >> IANA Stewardship Coordination Group (ICG): >> >> http://www.nro.net/crisp-proposal-first-draft-1-1 >> >> From the initial draft we published on 19th Dec [*], we have made >> editorial changes only. No changes are made in contents of the proposal. >> >> [*] >> https://www.nro.net/wp-content/uploads/CRISP-IANA-PROPOSAL-First-Draft1.pdf >> >> The editorial changes are intended to clarify our answers to RFP, by >> re-ordering answers in the same order as questions listed in each >> Section. Some small additions have been made to address points that had >> not been answered in the earlier draft. Finally, there are some changes >> made for stylistic reasons. >> >> The deadline of the comments to be submitted to >> mailing list remains the same: Monday 5th Jan 2015. >> >> Please let us know if you have any questions about version 1.1 of our >> draft proposal, and we continue to welcome feedback from the community. >> >> >> Best Regards, >> Consolidated RIR IANA Stewardship Proposal Team (CRISP Team) >> > > > _______________________________________________ > ianaxfer mailing list > ianaxfer at nro.net > https://www.nro.net/mailman/listinfo/ianaxfer From marty at akamai.com Sat Jan 3 03:02:18 2015 From: marty at akamai.com (Hannigan, Martin) Date: Fri, 2 Jan 2015 21:02:18 -0500 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] Editorial version of Internet Number Community IANA Stewardship, Proposal published In-Reply-To: <20EB2E8D-FB2C-43B3-902E-5047CF048843@netnod.se> References: <54A6E0A5.2030506@nic.ad.jp> <20EB2E8D-FB2C-43B3-902E-5047CF048843@netnod.se> Message-ID: <0D75AEC2-7FC2-43F6-9765-064D14BD3A83@akamai.com> Hi Nurani, Is the ianaxfer@ list open for posting or do we need to subscribe, which is typical for mailman? I recall earlier that we all agreed this list would be post by members, view by public. Best, -M< On Jan 2, 2015, at 2:52 PM, Nurani Nimpuno wrote: > Dear colleagues, > > Firstly, a very happy new year to all of you! :) > I hope you all had a well deserved rest. > > As you may know, the CRISP team, tasked with coming up with a proposal for the Internet numbers community on the IANA stewardship transition, has published a first draft. > > We would warmly welcome any comments you have on this draft, on the global mailing list. The deadline for feedback on this draft is 5 January. > > The second draft will be distributed on 8 January, and the very final proposal is due for submission 15 January. > > > Kind regards, > Nurani > on behalf of the RIPE CRISP team > > -- > Nurani Nimpuno > Head of Outreach & Communications, Netnod > > , http://www.netnod.se > Box 30194 | SE-104 25 Stockholm | Sweden > --------------------------------------------- > > Begin forwarded message: > >> From: Izumi Okutani >> Subject: Re: [NRO-IANAXFER] Editorial version of Internet Number Community IANA Stewardship, Proposal published >> Date: 2 januari 2015 19:17:09 CET >> To: ianaxfer at nro.net >> >> Dear Colleagues, >> >> >> >> This is a friendly reminder that the deadline for providing feedback to the first draft of the proposal from Internet Number Community on IANA Stewardship is: 5 January 2015. >> >> Based on the request made by a community member on this mailing list, please find below the text format of the first proposal. This is identical to the edited version of the first proposal published at: >> >> https://www.nro.net/wp-content/uploads/CRISP-IANA-PROPOSAL-Draft-24122014-clean.pdf >> >> We continue to welcome your feedback on mailing list. >> >> >> >> Best Regards, >> >> Izumi Okutani >> Chair, Consolidated RIR IANA Stewardship Proposal (CRISP) team >> >> ------------------------------------------------------------------------------- >> Draft Response to the Internet Coordination Group Request for >> Proposals on IANA from the RIR community >> 1. Proposal type >> >> Identify which category of the IANA functions this submission proposes to address: >> >> [ ] Names >> [ ?] Numbers >> [ ] Protocol Parameters >> >> >> >> I. Description of Community?s Use of IANA >> >> This section should list the specific, distinct IANA services or activities your community relies >> on. For each IANA service or activity on which your community relies, please provide the following: >> >> ? A description of the service or activity. >> ? A description of the customer(s) of the service or activity. >> ? What registries are involved in providing the service or >> activity. >> ? A description of any overlaps or interdependencies between >> your IANA requirements and the >> functions required by other customer communities >> >> ------- >> ? A description of the service or activity. >> >> The relevant IANA activities to the number resource communities are the allocation of IPv4 addresses, IPv6 addresses, and Autonomous System Numbers (?ASNs?) to the Regional Internet Registries (?RIRs?) as well as the delegation of the ?IN-ADDR.ARPA? and ?IP6.ARPA? DNS trees in accordance with the allocation of IPv4 and IPv6 addresses. >> >> ? A description of the customer(s) of the service or activity. >> >> The RIRs manage the registration and distribution of Internet number resources (IPv4 and IPv6 addresses and ASNs) to members within their service regions. The five RIRs in operation at this point in time are: >> >> AFRINIC Serving Africa Founded in 2005 >> APNIC Serving the Asia Pacific region Founded in 1993 >> ARIN Serving North America Founded in 1997 >> LACNIC Serving South America and the Caribbean Founded in 2001 >> RIPE NCC Serving Europe, Central Asia and the Middle East Founded in 1992 >> >> The five RIRs manage the distribution and registration of Internet number resources at the regional level, having received blocks of unused resources from the global pools managed by the IANA operator. The RIRs also facilitate the policy development processes of their >> respective communities. >> >> The five RIRs have a long-standing and straightforward operational relationship with IANA. IANA maintains the global pools of Internet number resources from which the RIRs receive allocations to distribute to their communities. The RIRs also coordinate with IANA to correctly register any resources that are returned to the global pools. Collectively, the system for administering Internet number resources is referred to as the "Internet Number Registry System" and is described >> in detail in RFC 7020. >> >> ------- >> ? What registries are involved in providing the service or >> activity. >> >> The most relevant IANA registries are the IPv4 address registry, the IPv6 address registry, and the ASN registry. Delegation of ?IN-ADDR.ARPA? and ?IP6.ARPA?domain names also requires interaction with the .ARPA zone registry. >> >> ------- >> ? A description of any overlaps or interdependencies between >> your IANA requirements and the >> functions required by other customer communities. >> >> The Internet Engineering Task Force (?IETF?) is responsible for policy relating to the entire IP address space and AS number space. Through the IANA protocol parameters registries, the IETF delegates unicast IP address ("IANA IPv4 Address Space Registry" and "IPv6 Global Unicast Allocations Registry") and AS number space (?ASN Registry) to the RIR system [RFC7020]. Note that within each IANA registry, there are also reserved values or ranges, and special-purpose registries, which are outside the Internet Numbers Registry System and instead administered under the direction of the IETF. The delineation of the specific ranges delegated to the Internet Number Registry system is provided in RFC 7249. It is expected that the boundary between IETF-managed and Internet Number Registry-managed parts of the number spaces may change from time to time, with agreement between the IETF and the RIRs. Potential reasons for changes include the possibility >> that the IETF may release some previously reserved space for general use, or may reserve some previously unused space for a special purpose. >> The global Internet community also depends upon the IANA operator for administration of the special-purpose ?IN-ADDR.ARPA? and ?IP6.ARPA? DNS zones which are associated with IPv4 and IPv6 number resources respectively. These zones are delegated to IANA by the Internet Architecture Board (?IAB?) and ?[s]ub-delegations within this hierarchy are undertaken in accordance with the IANA?s address allocation practices? (RFC3172). The IANA operator administers these zones as ?agreed technical work items? per the IETF- Internet Corporation for Assigned Names and Numbers (?ICANN?) IANA MoU. It is important to note that this work is outside the scope of the National >> Telecommunications and Information Administration (?NTIA?) contract. >> >> Relevant links: >> IETF-ICANN MoU Concerning the Technical Work of the Internet Assigned Numbers Authority: >> https://www.icann.org/resources/unthemed-pages/ietf-icann-mou-2000-03-01-en >> ?The Internet Numbers Registry System?, RFC 7020: https://tools.ietf.org/html/rfc7020 ?Internet >> Numbers Registries?, RFC 7249: https://tools.ietf.org/html/rfc7249 >> >> >> >> II. Existing, Pre-Transition Arrangements >> >> This section should describe how existing IANA-related arrangements work, prior to the transition. >> >> A. Policy Sources >> >> This section should identify the specific source(s) of policy which must be followed by the IANA functions operator in its conduct of the services or activities described above. If there are distinct sources of policy or policy development for different IANA activities, then please describe these separately. For each source of policy or policy development, please provide the following: >> >> ? Which IANA service or activity (identified in Section I) is >> affected. >> ? A description of how policy is developed and established and >> who is involved in policy development and establishment. >> ? A description of how disputes about policy are resolved. >> ? References to documentation of policy development and dispute >> resolution processes. >> >> ------- >> ? Which IANA service or activity (identified in Section I) is >> affected. >> >> The Internet number resource registries. >> >> It is important to note that allocations of Internet number resources from IANA to the RIRs and its registrations in IANA registries, as well as delegations of ?IN-ADDR.ARPA? and ?IP6.ARPA? domains, described in Section I, are conducted between IANA and the RIRs without involvement by the NTIA. >> >> ------- >> ? A description of how policy is developed and established and >> who is involved in policy development and establishment. >> >> The policies under which the IANA operator manages the global pools of Internet number resources (excluding those address ranges reserved by the IETF for specific technical purposes) are developed and agreed by the five RIR communities via open, transparent and bottom-up policy development processes. Each RIR community engages in its own regional policy development process; these processes are open to all stakeholders regardless of specific background or interest. Links to each of the five regional Policy Development Processes (?PDPs?) are included under in the RIR Governance Matrix published on the Number Resource Organization (?NRO?) website [www.nro.net/about-the-nro/rir-governance- matrix]. >> >> Any individual may submit a global proposal. Each RIR community must ratify an identical version of the proposed policy. The NRO Executive Council (?NRO EC?) then refers the coordinated proposal to the Address Supporting Organization (?ASO?) Address Council (?ASO AC?), which reviews the process by which the proposal was developed and, under the terms of the ASO Memorandum of Understanding (?ASO MoU?), passes it to the ICANN Board of Directors for ratification as a global policy. >> >> There are currently three global policies relating to management of the global pools of IPv4 addresses, IPv6 addresses and AS Numbers [https://www.nro.net/policies]: >> >> (a) IANA Policy for Allocation of IPv6 Blocks to Regional Internet Registries; >> (b) IANA Policy for Allocation of ASN Blocks to Regional Internet Registries; and >> (c) Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA. >> >> There is a fourth global policy agreed by the RIR communities, ICP-2, "Criteria for Establishment of New Regional Internet Registries". >> >> The global Policy Development Process (?gPDP?) described in ?Global Policy Development Process Document? [https://www.nro.net/documents/global-policy-development- process] is used for all of the number-related IANA activities described in Section I, but the policy that >> ?IN-ADDR.ARPA? and ?IP6.ARPA? domains must be delegated following IPv4 and IPv6 address allocations is specified by the IETF (most recently in RFC 3172). >> >> ------- >> ? A description of how disputes about policy are resolved. >> >> The gPDP is formally described in "Attachment A" of the ASO MoU, signed by ICANN and the RIRs in 2004 (and signed by AFRINIC when it was established as the fifth RIR in 2005). This MoU includes provisions for resolving disputes between ICANN and the RIRs or their communities. It is important to note that while the gPDP allows for the ICANN Board to dispute the outcome of a consensus community decision (escalating to mediation between ICANN and the RIRs), it does not include any role for the IANA contract holder (currently the NTIA). The ASO MoU is an agreement between the RIR communities and ICANN; NTIA has no oversight role in policy-making as regards management of the global Internet number resource pools, and its transition out of its current role would have minimal effect on the policy-making framework. >> >> A separate MoU, the NRO MoU, establishes the NRO as "a coordinating mechanism of the RIRs to act collectively on matters relating to the interests of the RIRs", and includes provisions for dispute resolutions between RIRs on issues relating to global policy development or implementation. >> >> It is the responsibility of the NRO Number Council (?NRO NC?), a group comprising three community members selected by each of the five RIR communities, to confirm that the documented RIR PDPs have been followed in the development and approval of a new policy or policy change. Further, this group reviews the policy followed by each of the RIR communities to assure itself that the significant viewpoints of interested parties were adequately considered,and only after this confirmation does it then consider forwarding global policy proposals to the ICANN Board for ratification. >> >> The NRO NC also acts in the role of the ICANN ASO AC, and as such, presents the agreed global policy proposal to the ICANN Board for ratification and operational implementation. >> >> The ICANN Board reviews the received global number resource policy proposals and may ask questions and otherwise consult with the ASO Address Council and/or the individual RIRs acting collectively >> through the NRO. The ICANN Board may also consult with other parties as the Board considers appropriate. If the ICANN Board rejects the proposed policy, it delivers to the ASO ACa statement of its concerns with the proposed policy, including in particular an explanation of the significant viewpoints that were not adequately considered during the regular RIR processes. By agreement of all RIRs, the ASO AC may forward a new proposed policy (either reaffirming the previous proposal or >> a modified proposal) to the ICANN Board. If the resubmitted proposed policy is rejected for a second time by ICANN, then the RIRs or ICANN shall refer the matter to mediation. >> >> In case of disputes where mediation has failed to resolve the dispute, the ICANN ASO MoU agreement provides for arbitration via ICC rules in the jurisdiction of Bermuda or such other location as is agreed between the RIRs and ICANN. It is also worth noting that the RIRs have been participating (as the ASO) in the periodic independent review processes for Accountability and Transparency (ATRT) that is called for per ICANN?s Bylaws. >> >> ------- >> ? References to documentation of policy development and dispute >> resolution processes. >> >> Relevant links: >> ICANN ASO MoU: https://www.nro.net/documents/icann-address-supporting-organization-aso- mou >> NRO MoU: https://www.nro.net/documents/nro-memorandum-of-understanding >> About the NRO Number Council: https://www.nro.net/about-the-nro/the-nro-number-council RIR >> Governance Matrix: https://www.nro.net/about-the-nro/rir-governance-matrix >> Global Policies: https://www.nro.net/policies >> >> >> >> B. Oversight and Accountability >> >> This section should describe all the ways in which oversight is conducted over IANA?s provision of the services and activities listed in Section I and all the ways in which IANA is currently held accountable for the provision of those services. For each oversight or accountability mechanism, please provide as many of the following as are applicable: >> >> ? Which IANA service or activity (identified in Section I) is >> affected. >> ? If the policy sources identified in Section II.A are affected, >> identify which ones are affected and explain in what way. >> ? A description of the entity or entities that provide oversight >> or perform accountability functions, including how individuals >> are selected or removed from participation in those entities. >> ? A description of the mechanism (e.g., contract, reporting >> scheme, auditing scheme, etc.). >> This should include a description of the consequences of the >> IANA functions operator not meeting the standards established >> by the mechanism, the extent to which the output of the >> mechanism is transparent and the terms under which the >> mechanism may change. >> ? Jurisdiction(s) in which the mechanism applies and the legal >> basis on which the mechanism rests. >> >> ------- >> ? Which IANA service or activity (identified in Section I) is >> affected. >> >> The Internet number resource registries. >> >> ------- >> ? If the policy sources identified in Section II.A are affected, >> identify which ones are affected and explain in what way. >> >> A decision by the NTIA to discontinue its stewardship of the IANA functions, and therefore its contractual relationship with the IANA functions operator, would not have any significant impact on the continuity of Internet number-related IANA services currently provided by ICANN. However, it would remove a significant element of oversight from the current system. >> >> There is no contractual obligation directly to the Internet number resource community for the IANA operator to provide IANA registry services for the Internet number registries; IANA services for >> the Internet number registries are provided by ICANN since its formation as a result of the NTIA IANA Functions contract and hence IANA services for the Internet number registries are presently >> subject to change per that agreement. >> >> ------- >> ? A description of the entity or entities that provide oversight >> or perform accountability functions, including how individuals >> are selected or removed from participation in those entities. >> >> All institutional actors with a role in management of Internet number resources are accountable to the open communities that make and agree on the policies under which those resources are distributed and registered. The mechanisms used to ensure and enforce this accountability differ for each of these actors. >> >> 1. NTIA >> ICANN, as the current operator of the IANA functions, is obligated by the NTIA agreement to carry out management of the global IP address and AS Number pools according to policies developed by the communities. >> >> While the IANA operator escalation and reporting mechanisms are public in nature, the Internet number community is primarily represented in oversight of the IANA operator performance by the RIRs, which are member-based based organizations with elected governance boards. >> Currently, the NTIA does not have an oversight role in this regard. >> >> The ultimate consequence of failing to meet the performance standards or reporting requirements is understood to be a decision by the contracting party (the NTIA) to terminate or not renew the IANA >> functions agreement with the current contractor (ICANN). >> >> 2. The Regional Internet Registries >> >> Administration by the IANA operator consists predominantly of processing of requests from the RIRs for issuance of additional number resources. The five RIRs are intimately familiar with global number resource policies under which the requests are made and maintain communications with the IANA operations team throughout the request process. >> >> The RIRs are not-for-profit membership associations, and as such are accountable to their members by law. The specific governance processes for each RIR differ depending on where they have been established and the decisions made by their membership, but in all RIRs, members have the right to vote individuals onto the governing Board and to vote on specific funding or operational resolutions. >> >> At the same time, an RIR's registration and allocation practices are directed by policies developed by its community. Each RIR community's PDP defines how these policies are developed, agreed and accepted for operational implementation. >> >> The corporate governance documents and PDPs of each RIR and its community are accessible via the RIR Governance Matrix, published on the NRO website. >> >> ------- >> ? A description of the mechanism (e.g., contract, reporting >> scheme, auditing scheme, etc.). >> This should include a description of the consequences of the IANA functions operator not meeting the standards established by the mechanism, the extent to which the output of the mechanism is >> transparent and the terms under which the mechanism may change. >> >> The NTIA IANA Agreement currently defines obligations of the IANA operator for Internet number resources. >> >> This obligation is specifically noted in section C.2.9.3 of the NTIA agreement: >> >> C.2.9.3 Allocate Internet Numbering Resources --The Contractor shall have responsibility for allocated and unallocated IPv4 and IPv6 address space and Autonomous System Number (ASN) space based on established guidelines and policies as developed by interested and affected parties as enumerated in Section C.1.3. >> >> The NTIA agreement also lays out specific deliverables for the IANA operator (ICANN) to produce as a condition of the agreement (see "Section F ? Deliveries and Performance"), including performance >> standards developed in cooperation with the affected parties (in the case of the Internet number resource pools, the affected parties include the RIRs and their communities), customer complaint >> procedures and regular performance reporting. >> >> These deliverables are met by ICANN via monthly reporting on their performance in processing requests for the allocation of Internet number resources; these reports include IANA operator performance against key metrics of accuracy, timeliness, and transparency, as well as the performance metrics for individual requests. The IANA operations team also provides escalation procedures for use in resolving any issues with requests, as per the "IANA Customer Service Complaint Resolution Process". >> >> ------- >> ? Jurisdiction(s) in which the mechanism applies and the legal >> basis on which the mechanism rests. >> >> Jurisdiction for this current mechanism is the United States of America under applicable Federal government contracting laws and regulations. >> >> Relevant links: >> NTIA IANA Agreement: http://www.ntia.doc.gov/page/iana-functions-purchase-order >> ICANN ASO MoU: https://www.nro.net/documents/icann-address-supporting-organization-aso- mou >> NRO MoU: https://www.nro.net/documents/nro-memorandum-of-understanding >> IANA Customer Service Complaint Resolution Process: http://www.iana.org/help/escalation- procedure >> IANA Performance Standards Metrics Report: http://www.iana.org/performance/metrics >> RIR Governance Matrix: https://www.nro.net/about-the-nro/rir-governance-matrix >> >> >> >> III. Proposed Post-Transition Oversight and Accountability Arrangements >> >> This section should describe what changes your community is proposing to the arrangements listed in Section II.B in light of the transition. If your community is proposing to replace one or more existing arrangements with new arrangements, that replacement should be explained and all of the elements listed in Section II.B should be described for the new arrangements. Your community should >> provide its rationale and justification for the new arrangements. >> >> If your community?s proposal carries any implications for the interface between the IANA functions and existing policy arrangements described in Section II.A, those implications should be described >> here. >> >> If your community is not proposing changes to arrangements listed in Section II.B, the rationale and justification for that choice should be provided here. >> >> ------- >> The elements of this proposal are as follows: >> >> (1) ICANN to continue as the IANA functions operator on number >> resources; >> (2) Service level agreement with the IANA functions operator on >> number resources; and >> (3) Establishment of a Review Committee, with representatives >> from each RIR, to advise the NRO EC on the review of the >> IANA functions operator?s performance and meeting of >> identified service levels. >> >> To maintain stability and continuity in operations of the Internet number-related IANA services, very minimal changes to the arrangements listed in Section II.B are proposed, including the identification of the proposed initial IANA functions operator. As noted in numerous NRO >> communications over the past decade, the RIRs have been very satisfied with the performance of ICANN in the role of IANA functions operator. Taking this into account, and considering the strong desires expressed in the five RIR communities' IANA stewardship discussions for stability and a minimum of operational change, the Internet numbering community believes that ICANN should remain in the role of IANA functions operator for at least the initial term of the new contract. >> >> A decision by the NTIA to discontinue its stewardship of the IANA functions, and therefore its contractual relationship with the IANA functions operator, would not have any significant impact on >> the continuity of Internet number-related IANA services currently provided by ICANN. However, it would remove a significant element of oversight from the current system. >> >> The following is a proposal to replace the current NTIA IANA agreement with a new contract that more directly reflects and enforces the IANA functions operator's accountability to the open, >> bottom-up numbers community. Other than the replacement of the NTIA with the five RIRs as the party(ies) with whom the IANA functions operator would contract for provision of Internet number-related IANA services, the overall arrangements in Section II.B would remain with no change. >> >> The proposed arrangement involves the same IANA service or activity, policy sources identified in Section II.A are unaffected, the entities that provide oversight or perform accountability functions (the RIRs) remain the same, the consequence for failure to meet performance standards remains termination or decision not to renew the IANA functions agreement with the then-current contractor, and jurisdiction will be dependent on the chosen IANA functions operator. >> >> The Internet numbering community proposes that a new contract be established between the IANA functions operator and the five RIRs. The contract, essentially an IANA Service Level Agreement, would obligate the IANA functions operator to carry out those IANA functions relating to the global Internet number pools according to policies developed by the regional communities via the gPDP as well as management of the delegations within IN-ADDR.ARPA and IP6.ARPA domains. The agreement would include specific requirements for performance and reporting commensurate with current mechanisms, and would specify consequences should the contractor fail to meet those requirements, the means for the resolution of disputes between the parties, and the terms for renewal or termination of the contract. IANA operations should be >> reliable and consistent, with any registry changes made in an open and transparent manner to the global community. The agreement should also require the IANA operator to appropriately coordinate with any other operator of IANA-related registry services. >> >> To ensure the service level defined in the proposed contract is maintained and provided by the IANA functions operator, the NRO EC will conduct periodic reviews of the service level of the IANA number resource functions that serves each RIR and their respective communities. The NRO EC shall establish a Review Committee that will advise and assist the NRO EC in its periodic review. Any such Review Committee should be a team composed of representatives from each RIR region that will, as needed, undertake a review of the level of service received from the IANA functions operator and report to the NRO EC any concerns regarding any observed failure by the IANA functions operator to meet its contractual obligations under the proposed contract. Any such Review Committee will advise the NRO EC in its capacity solely to oversee the performance of the IANA number resource functions and the Review Committee?s advice and comment will be limited to the processes followed in the IANA functions operator?s performance under the proposed contract. >> >> If your community?s proposal carries any implications for the interface between the IANA functions and existing policy arrangements described in Section II.A, those implications should be described >> here. >> >> This proposal carries no implication for the interface between IANA functions and existing policy arrangements described in Section II.A. The text in "Attachment A" of the ICANN ASO MoU meets the current and anticipated requirements for a community-driven global policy development process. >> >> As an additional measure of security and stability, the RIRs have documented their individual accountability and governance mechanisms, and asked the community-based Number Resource Organization Number Council (NRO NC) to undertake a review of these mechanisms and make >> recommendations for improvements that may be warranted given the nature of the stewardship transition for Internet number resources. >> >> >> IV. Transition Implications >> >> This section should describe what your community views as the implications of the changes it proposed in Section III. These implications may include some or all of the following, or other >> implications specific to your community: >> >> ? Description of operational requirements to achieve continuity >> of service and possible new service integration throughout the >> transition. >> ? Risks to operational continuity and how they will be addressed. >> ? Description of any legal framework requirements in the absence >> of the NTIA contract. >> ? Description of how you have tested or evaluated the >> workability of any new technical or >> operational methods proposed in this document and how they >> compare to established arrangements. >> >> ------- >> ? Description of operational requirements to achieve continuity >> of service and possible new service integration throughout the >> transition. >> ? Risks to operational continuity and how they will be addressed. >> >> The intent of the proposal described above is to: >> >> 1. Minimize risks to operational continuity of the management of the Internet number- related IANA functions, and; >> 2. Retain the existing framework for making those policies that describe the management of the global Internet number resource pools, as this framework is already structured to ensure open, bottom-up development of such policies. >> >> Under current arrangements, the NTIA is responsible for extending or renewing the IANA functions agreement, and setting the terms of that contract. A new contract with the five RIRs and the IANA functions operator as signatories would shift the responsibility for renewing, setting terms or terminating the contract to the RIRs, who would coordinate their decisions via the NRO EC (made up of the RIR Directors and Chief Executives). Decisions made regarding the contract would be based on operational circumstances, past performance and input from open, regional communities. >> >> The shift from the existing contractual arrangement to another contractual arrangement (perhaps relying on a set of distinct contracts) covering the IANA functions operator?s ongoing management >> of all the IANA functions should result in no operational change for management of the global Internet number resource pools. This will help minimize any operational or continuity risks associated with stewardship transition. >> >> By building on the existing Internet registry system (which is open to participation from all interested parties) and its structures, the proposal reduces the risk associated with creating new organizations whose accountability is unproven. >> >> The necessary agreement proposed for IANA operation services for the Internet number registries can be established well before the NTIA target date for transition (September 2015), as there are no changes to existing service levels or reporting that are being proposed, only a change in contracting party to align with the delegated policy authority. >> >> ------- >> ? Description of any legal framework requirements in the absence >> of the NTIA contract. >> >> The necessary legal framework in the absence of the NTIA contract will be fulfilled by the proposed agreement between the IANA functions operator and the five RIRs. As stated in Section III above, >> the contract, essentially an IANA Service Level Agreement, would obligate the IANA functions operator to carry out those IANA functions relating to the global Internet number pools according to policies developed by the regional communities via the gPDP as well as >> management of the delegations within IN-ADDR.ARPA and IP6.ARPA domains. The agreement would include specific requirements for performance and reporting commensurate with current mechanisms, and would specify consequences should the contractor fail to meet those requirements, the means for the resolution of disputes between the parties, and the terms for renewal or termination of the contract. IANA operations should be reliable and consistent, with any registry changes made in an open and transparent manner to the global community. >> >> The agreement should also require the IANA operator to appropriately coordinate with any other operator of IANA-related registry services. The contract would also provide for jurisdiction and governing law regarding the new arrangement. >> >> ------- >> ? Description of how you have tested or evaluated the >> workability of any new technical or >> operational methods proposed in this document and how they >> compare to established arrangements. >> ? Risks to operational continuity and how they will be addressed. >> >> This proposal does not propose any new technical or operational methods. There is inclusion of a proposed Review Committee to be established by the five RIRs acting cooperatively and coordinating >> through the NRO EC; however, this does not carry any new operational method as the IANA functions operator would remain accountable to the party with whom it is contracting, in this case, the five RIRs in place of the NTIA. The proposed Review Committee is a tool for the five RIRs to evaluate and review performance of the IANA functions provided. >> >> >> >> V. NTIA Requirements >> >> Additionally, NTIA has established that the transition proposal must meet the following five requirements: >> >> ? Support and enhance the multistakeholder model; >> ? Maintain the security, stability, and resiliency of the >> Internet DNS; >> ? Meet the needs and expectation of the global customers and >> partners of the IANA services; >> ? Maintain the openness of the Internet. >> ? The proposal must not replace the NTIA role with a >> government-led or an inter-governmental organization solution. >> >> This section should explain how your community?s proposal meets these requirements and how it responds to the global interest in the IANA functions. >> >> ------- >> The proposal for the IANA stewardship transition for the Internet number registries builds upon the existing, successful framework used by the Internet number community today. The major characteristics of this approach include: >> >> 1. Global number policy development which is open and transparent to any and all participants >> 2. Continuance of existing IANA service levels, escalation processes, and reporting mechanisms >> 3. Maintenance of independent review and ratification for developed global Internet number resource policy >> 4. Continued use of periodic third-party independent reviews of accountability and transparency of processes >> 5. No change of the existing IANA operator for maximum stability and security of operational processes and systems >> 6. Accountable, member-based, globally-distributed RIR organizations providing routine IANA operational oversight for the Internet number registries >> 7. No new organization is proposed. However, a new process within the RIR structures is proposed, where a Review Committee is established to advise and assist the NRO EC in its periodic review of the service level provided by the IANA functions operator. >> >> As a result of the approach taken (and its characteristics as outlined above), it is clear that the proposal from the Internet number community meets the stated NTIA requirements. >> >> >> VI. Community Process >> >> This section should describe the process your community used for developing this proposal, including: >> >> ? The steps that were taken to develop the proposal and to >> determine consensus. >> ? Links to announcements, agendas, mailing lists, consultations >> and meeting proceedings. >> ? An assessment of the level of consensus behind your >> community?s proposal, including a description of areas of >> contention or disagreement. >> >> ------- >> 1. Regional and global process >> >> Each of the five RIR communities is discussing the IANA stewardship issues via mailing lists, at their RIR meetings and in other community forums. While these discussions have been uniformly open and transparent, with all discussions archived on mailing lists and meeting records, each community has adopted a specific process of their own choosing to reach an agreed community output. >> >> The results from the five regional processes fed a global process that produced this document. More details about the regional and global processes are given below, interspersed with links to relevant documents. >> >> 2. AFRINIC regional process: >> The AFRINIC community held a consultative meeting on 25 May to 6 June 2014 during the Africa Internet Summit (AIS'2014) in Djibouti in the "IANA oversight transition" workshop. As a follow up to the meeting, AFRINIC setup a mailing list to provide a platform for the African >> Internet community to discuss the IANA Oversight Transition process. The mailing list was announced on July 4, 2014 to develop a community position. The list and its archives can be found at: >> https://lists.afrinic.net/mailman/listinfo.cgi/ianaoversight >> >> A Dedicated web portal was setup for sharing information on the IANA stewardship transition with the AFRINIC community and is also available at http://afrinic.net/en/community/iana-oversight-transition >> >> AFRINIC also conducted a survey seeking community input on the IANA Stewardship Transition. The results of the survey are published >> at: http://afrinic.net/images/stories/Initiatives/%20survey%20on%20the%20iana%20stewardship >> %20transition.pdf >> >> >> The last face-to-face meeting at which IANA oversight transition consultations were held with the community was during the AFRINIC-21 meeting in Mauritius, 22-28 November 2014. The recordings of >> the session are available at http://meeting.afrinic.net/afrinic-21/en/vod >> >> Discussions continued on the ianaoversight at afrinic.net mailing list, until the closure of the comments from the number resources communities set by the CRISP Team on 12th Jan 2015. >> >> 3. APNIC regional process: >> APNIC, as the secretariat for the APNIC community has set up a public mailing list (announced on 1 Apr 2014) to develop a community position, and have discussions about the proposal from the region on IANA stewardship transition: http://mailman.apnic.net/mailman/listinfo/IANAxfer >> >> Webpage, dedicated to sharing up-to-date information on the IANA stewardship transition was set up, for the APNIC community members and wider community members who are interested in this issue can be updated: http://www.apnic.net/community/iana-transition >> >> Draft proposal was discussed at the dedicated session at the APNIC 38 Meeting, which saw the general community consensus. The meeting provided >> remote participation tools to enable wider participation from communities across Asia Pacific and beyond, with live webcasts well as Adobe Connect virtual conference room. >> >> https://conference.apnic.net/38/program#iana >> >> The discussions continued on the "ianaxfer at apnic.net." mailing list, >> until the closure of the comments from the number resources communities set by CRISP Team as 12th Jan 2015. >> >> 4. ARIN regional process: >> >> >> >> 5. LACNIC regional process: >> >> >> >> >> 6. RIPE regional process: >> The RIPE community agreed at the RIPE 68 Meeting in May 2014 that the development of a community position on IANA stewardship should take place in the RIPE Cooperation Working Group, and via that working group's public mailing list: https://www.ripe.net/ripe/mail/wg- lists/cooperation >> >> The RIPE NCC, as secretariat for the RIPE community, also facilitated discussions on the IANA stewardship in national and regional forums across the RIPE NCC service region. Summaries of these discussions were posted to the RIPE Cooperation Working Group mailing list and on the RIPE website: >> https://www.ripe.net/iana-discussions >> >> Between September and November 2014, RIPE community discussion centered around developing a set of principles reflecting the communities primary concerns in the development of an alternative IANA stewardship arrangement. These discussions are reflected in the discussions on the mailing list from that time: http://www.ripe.net/ripe/mail/archives/cooperation- wg/ >> >> Discussions at the RIPE 69 Meeting in November 2014 saw general community consensus on the principles discussed on the mailing list, and support expressed for the three community members selected to join the Consolidated RIR IANA Stewardship Proposal (CRISP) team. >> >> RIPE Cooperation Working Group Session: https://ripe69.ripe.net/programme/meeting- plan/coop-wg/#session1 >> RIPE 69 Closing Plenary Session: https://ripe69.ripe.net/archives/video/10112/ >> >> ------- >> 7. Global process (CRISP Team) >> On 16 October 2014, the NRO EC proposed the formation of a Consolidated RIR IANA Stewardship >> >> Proposal (CRISP) team to develop a single Internet numbering community proposal to the IANA Stewardship Coordination Group (ICG). Each RIR community selected three members (two community members and one RIR staff) to participate in the team. The participants selected were: >> >> AFRINIC Region >> Alan P. Barrett ? Independent Consultant >> Mwendwa Kivuva ? Network Infrastructure Services, University of Nairobi Ernest Byaruhanga (Appointed RIR staff) >> >> ARIN Region >> Bill Woodcock ? President and Research Director of Packet Clearing House >> John Sweeting ? Sr. Director, Network Architecture & Engineering at Time Warner Cable >> Michael Abejuela (Appointed RIR staff) >> >> APNIC Region >> Dr Govind ? CEO NIXI >> Izumi Okutani ? Policy Liaison JPNIC >> Craig Ng (Appointed RIR staff) >> >> LACNIC Region >> Nico Scheper - Curacao IX >> Esteban Lescano - Cabase Argentina >> Andr?s Piazza (Appointed RIR staff) >> >> RIPE NCC Region >> Nurani Nimpuno ? Head of Outreach & Communications at Netnod >> Andrei Robachevsky ? Technology Programme Manager at the Internet Society Paul Rendek (Appointed >> RIR staff) >> >> Steps and timeline for proposal development and links to announcements, mailing lists, and >> proceedings - https://www.nro.net/nro-and-internet-governance/iana-oversight/timeline-for-rirs- >> engagement-in-iana-stewardship-transition-process >> >> ------- >> 8. Assessment of consensus level >> >> >> >> >> On 2014/12/29 20:43, Izumi Okutani wrote: >>> Dear Colleagues, >>> >>> >>> CRISP Team has published an editorial version of the Internet >>> numbers community's response to the Request For Proposals issued by the >>> IANA Stewardship Coordination Group (ICG): >>> >>> http://www.nro.net/crisp-proposal-first-draft-1-1 >>> >>> From the initial draft we published on 19th Dec [*], we have made >>> editorial changes only. No changes are made in contents of the proposal. >>> >>> [*] >>> https://www.nro.net/wp-content/uploads/CRISP-IANA-PROPOSAL-First-Draft1.pdf >>> >>> The editorial changes are intended to clarify our answers to RFP, by >>> re-ordering answers in the same order as questions listed in each >>> Section. Some small additions have been made to address points that had >>> not been answered in the earlier draft. Finally, there are some changes >>> made for stylistic reasons. >>> >>> The deadline of the comments to be submitted to >>> mailing list remains the same: Monday 5th Jan 2015. >>> >>> Please let us know if you have any questions about version 1.1 of our >>> draft proposal, and we continue to welcome feedback from the community. >>> >>> >>> Best Regards, >>> Consolidated RIR IANA Stewardship Proposal Team (CRISP Team) >>> >> >> >> _______________________________________________ >> ianaxfer mailing list >> ianaxfer at nro.net >> https://www.nro.net/mailman/listinfo/ianaxfer > > > > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 842 bytes Desc: Message signed with OpenPGP using GPGMail URL: From nurani at netnod.se Sat Jan 3 09:05:00 2015 From: nurani at netnod.se (Nurani Nimpuno) Date: Sat, 3 Jan 2015 09:05:00 +0100 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] Editorial version of Internet Number Community IANA Stewardship, Proposal published In-Reply-To: <0D75AEC2-7FC2-43F6-9765-064D14BD3A83@akamai.com> References: <54A6E0A5.2030506@nic.ad.jp> <20EB2E8D-FB2C-43B3-902E-5047CF048843@netnod.se> <0D75AEC2-7FC2-43F6-9765-064D14BD3A83@akamai.com> Message-ID: Hi Martin, The ianaxfer list us publicly archived, but you do need to subscribe to the list in order to post to it. Kind regards, Nurani > On 3 jan 2015, at 03:02, "Hannigan, Martin" wrote: > > > > Hi Nurani, > > Is the ianaxfer@ list open for posting or do we need to subscribe, which is typical for mailman? I recall earlier that we all agreed this list would be post by members, view by public. > > Best, > > -M< > > >> On Jan 2, 2015, at 2:52 PM, Nurani Nimpuno wrote: >> >> Dear colleagues, >> >> Firstly, a very happy new year to all of you! :) >> I hope you all had a well deserved rest. >> >> As you may know, the CRISP team, tasked with coming up with a proposal for the Internet numbers community on the IANA stewardship transition, has published a first draft. >> >> We would warmly welcome any comments you have on this draft, on the global mailing list. The deadline for feedback on this draft is 5 January. >> >> The second draft will be distributed on 8 January, and the very final proposal is due for submission 15 January. >> >> >> Kind regards, >> Nurani >> on behalf of the RIPE CRISP team >> >> -- >> Nurani Nimpuno >> Head of Outreach & Communications, Netnod >> >> , http://www.netnod.se >> Box 30194 | SE-104 25 Stockholm | Sweden >> --------------------------------------------- >> >> Begin forwarded message: >> >>> From: Izumi Okutani >>> Subject: Re: [NRO-IANAXFER] Editorial version of Internet Number Community IANA Stewardship, Proposal published >>> Date: 2 januari 2015 19:17:09 CET >>> To: ianaxfer at nro.net >>> >>> Dear Colleagues, >>> >>> >>> >>> This is a friendly reminder that the deadline for providing feedback to the first draft of the proposal from Internet Number Community on IANA Stewardship is: 5 January 2015. >>> >>> Based on the request made by a community member on this mailing list, please find below the text format of the first proposal. This is identical to the edited version of the first proposal published at: >>> >>> https://www.nro.net/wp-content/uploads/CRISP-IANA-PROPOSAL-Draft-24122014-clean.pdf >>> >>> We continue to welcome your feedback on mailing list. >>> >>> >>> >>> Best Regards, >>> >>> Izumi Okutani >>> Chair, Consolidated RIR IANA Stewardship Proposal (CRISP) team >>> >>> ------------------------------------------------------------------------------- >>> Draft Response to the Internet Coordination Group Request for >>> Proposals on IANA from the RIR community >>> 1. Proposal type >>> >>> Identify which category of the IANA functions this submission proposes to address: >>> >>> [ ] Names >>> [ ?] Numbers >>> [ ] Protocol Parameters >>> >>> >>> >>> I. Description of Community?s Use of IANA >>> >>> This section should list the specific, distinct IANA services or activities your community relies >>> on. For each IANA service or activity on which your community relies, please provide the following: >>> >>> ? A description of the service or activity. >>> ? A description of the customer(s) of the service or activity. >>> ? What registries are involved in providing the service or >>> activity. >>> ? A description of any overlaps or interdependencies between >>> your IANA requirements and the >>> functions required by other customer communities >>> >>> ------- >>> ? A description of the service or activity. >>> >>> The relevant IANA activities to the number resource communities are the allocation of IPv4 addresses, IPv6 addresses, and Autonomous System Numbers (?ASNs?) to the Regional Internet Registries (?RIRs?) as well as the delegation of the ?IN-ADDR.ARPA? and ?IP6.ARPA? DNS trees in accordance with the allocation of IPv4 and IPv6 addresses. >>> >>> ? A description of the customer(s) of the service or activity. >>> >>> The RIRs manage the registration and distribution of Internet number resources (IPv4 and IPv6 addresses and ASNs) to members within their service regions. The five RIRs in operation at this point in time are: >>> >>> AFRINIC Serving Africa Founded in 2005 >>> APNIC Serving the Asia Pacific region Founded in 1993 >>> ARIN Serving North America Founded in 1997 >>> LACNIC Serving South America and the Caribbean Founded in 2001 >>> RIPE NCC Serving Europe, Central Asia and the Middle East Founded in 1992 >>> >>> The five RIRs manage the distribution and registration of Internet number resources at the regional level, having received blocks of unused resources from the global pools managed by the IANA operator. The RIRs also facilitate the policy development processes of their >>> respective communities. >>> >>> The five RIRs have a long-standing and straightforward operational relationship with IANA. IANA maintains the global pools of Internet number resources from which the RIRs receive allocations to distribute to their communities. The RIRs also coordinate with IANA to correctly register any resources that are returned to the global pools. Collectively, the system for administering Internet number resources is referred to as the "Internet Number Registry System" and is described >>> in detail in RFC 7020. >>> >>> ------- >>> ? What registries are involved in providing the service or >>> activity. >>> >>> The most relevant IANA registries are the IPv4 address registry, the IPv6 address registry, and the ASN registry. Delegation of ?IN-ADDR.ARPA? and ?IP6.ARPA?domain names also requires interaction with the .ARPA zone registry. >>> >>> ------- >>> ? A description of any overlaps or interdependencies between >>> your IANA requirements and the >>> functions required by other customer communities. >>> >>> The Internet Engineering Task Force (?IETF?) is responsible for policy relating to the entire IP address space and AS number space. Through the IANA protocol parameters registries, the IETF delegates unicast IP address ("IANA IPv4 Address Space Registry" and "IPv6 Global Unicast Allocations Registry") and AS number space (?ASN Registry) to the RIR system [RFC7020]. Note that within each IANA registry, there are also reserved values or ranges, and special-purpose registries, which are outside the Internet Numbers Registry System and instead administered under the direction of the IETF. The delineation of the specific ranges delegated to the Internet Number Registry system is provided in RFC 7249. It is expected that the boundary between IETF-managed and Internet Number Registry-managed parts of the number spaces may change from time to time, with agreement between the IETF and the RIRs. Potential reasons for changes include the possibility >>> that the IETF may release some previously reserved space for general use, or may reserve some previously unused space for a special purpose. >>> The global Internet community also depends upon the IANA operator for administration of the special-purpose ?IN-ADDR.ARPA? and ?IP6.ARPA? DNS zones which are associated with IPv4 and IPv6 number resources respectively. These zones are delegated to IANA by the Internet Architecture Board (?IAB?) and ?[s]ub-delegations within this hierarchy are undertaken in accordance with the IANA?s address allocation practices? (RFC3172). The IANA operator administers these zones as ?agreed technical work items? per the IETF- Internet Corporation for Assigned Names and Numbers (?ICANN?) IANA MoU. It is important to note that this work is outside the scope of the National >>> Telecommunications and Information Administration (?NTIA?) contract. >>> >>> Relevant links: >>> IETF-ICANN MoU Concerning the Technical Work of the Internet Assigned Numbers Authority: >>> https://www.icann.org/resources/unthemed-pages/ietf-icann-mou-2000-03-01-en >>> ?The Internet Numbers Registry System?, RFC 7020: https://tools.ietf.org/html/rfc7020 ?Internet >>> Numbers Registries?, RFC 7249: https://tools.ietf.org/html/rfc7249 >>> >>> >>> >>> II. Existing, Pre-Transition Arrangements >>> >>> This section should describe how existing IANA-related arrangements work, prior to the transition. >>> >>> A. Policy Sources >>> >>> This section should identify the specific source(s) of policy which must be followed by the IANA functions operator in its conduct of the services or activities described above. If there are distinct sources of policy or policy development for different IANA activities, then please describe these separately. For each source of policy or policy development, please provide the following: >>> >>> ? Which IANA service or activity (identified in Section I) is >>> affected. >>> ? A description of how policy is developed and established and >>> who is involved in policy development and establishment. >>> ? A description of how disputes about policy are resolved. >>> ? References to documentation of policy development and dispute >>> resolution processes. >>> >>> ------- >>> ? Which IANA service or activity (identified in Section I) is >>> affected. >>> >>> The Internet number resource registries. >>> >>> It is important to note that allocations of Internet number resources from IANA to the RIRs and its registrations in IANA registries, as well as delegations of ?IN-ADDR.ARPA? and ?IP6.ARPA? domains, described in Section I, are conducted between IANA and the RIRs without involvement by the NTIA. >>> >>> ------- >>> ? A description of how policy is developed and established and >>> who is involved in policy development and establishment. >>> >>> The policies under which the IANA operator manages the global pools of Internet number resources (excluding those address ranges reserved by the IETF for specific technical purposes) are developed and agreed by the five RIR communities via open, transparent and bottom-up policy development processes. Each RIR community engages in its own regional policy development process; these processes are open to all stakeholders regardless of specific background or interest. Links to each of the five regional Policy Development Processes (?PDPs?) are included under in the RIR Governance Matrix published on the Number Resource Organization (?NRO?) website [www.nro.net/about-the-nro/rir-governance- matrix]. >>> >>> Any individual may submit a global proposal. Each RIR community must ratify an identical version of the proposed policy. The NRO Executive Council (?NRO EC?) then refers the coordinated proposal to the Address Supporting Organization (?ASO?) Address Council (?ASO AC?), which reviews the process by which the proposal was developed and, under the terms of the ASO Memorandum of Understanding (?ASO MoU?), passes it to the ICANN Board of Directors for ratification as a global policy. >>> >>> There are currently three global policies relating to management of the global pools of IPv4 addresses, IPv6 addresses and AS Numbers [https://www.nro.net/policies]: >>> >>> (a) IANA Policy for Allocation of IPv6 Blocks to Regional Internet Registries; >>> (b) IANA Policy for Allocation of ASN Blocks to Regional Internet Registries; and >>> (c) Global Policy for Post Exhaustion IPv4 Allocation Mechanisms by the IANA. >>> >>> There is a fourth global policy agreed by the RIR communities, ICP-2, "Criteria for Establishment of New Regional Internet Registries". >>> >>> The global Policy Development Process (?gPDP?) described in ?Global Policy Development Process Document? [https://www.nro.net/documents/global-policy-development- process] is used for all of the number-related IANA activities described in Section I, but the policy that >>> ?IN-ADDR.ARPA? and ?IP6.ARPA? domains must be delegated following IPv4 and IPv6 address allocations is specified by the IETF (most recently in RFC 3172). >>> >>> ------- >>> ? A description of how disputes about policy are resolved. >>> >>> The gPDP is formally described in "Attachment A" of the ASO MoU, signed by ICANN and the RIRs in 2004 (and signed by AFRINIC when it was established as the fifth RIR in 2005). This MoU includes provisions for resolving disputes between ICANN and the RIRs or their communities. It is important to note that while the gPDP allows for the ICANN Board to dispute the outcome of a consensus community decision (escalating to mediation between ICANN and the RIRs), it does not include any role for the IANA contract holder (currently the NTIA). The ASO MoU is an agreement between the RIR communities and ICANN; NTIA has no oversight role in policy-making as regards management of the global Internet number resource pools, and its transition out of its current role would have minimal effect on the policy-making framework. >>> >>> A separate MoU, the NRO MoU, establishes the NRO as "a coordinating mechanism of the RIRs to act collectively on matters relating to the interests of the RIRs", and includes provisions for dispute resolutions between RIRs on issues relating to global policy development or implementation. >>> >>> It is the responsibility of the NRO Number Council (?NRO NC?), a group comprising three community members selected by each of the five RIR communities, to confirm that the documented RIR PDPs have been followed in the development and approval of a new policy or policy change. Further, this group reviews the policy followed by each of the RIR communities to assure itself that the significant viewpoints of interested parties were adequately considered,and only after this confirmation does it then consider forwarding global policy proposals to the ICANN Board for ratification. >>> >>> The NRO NC also acts in the role of the ICANN ASO AC, and as such, presents the agreed global policy proposal to the ICANN Board for ratification and operational implementation. >>> >>> The ICANN Board reviews the received global number resource policy proposals and may ask questions and otherwise consult with the ASO Address Council and/or the individual RIRs acting collectively >>> through the NRO. The ICANN Board may also consult with other parties as the Board considers appropriate. If the ICANN Board rejects the proposed policy, it delivers to the ASO ACa statement of its concerns with the proposed policy, including in particular an explanation of the significant viewpoints that were not adequately considered during the regular RIR processes. By agreement of all RIRs, the ASO AC may forward a new proposed policy (either reaffirming the previous proposal or >>> a modified proposal) to the ICANN Board. If the resubmitted proposed policy is rejected for a second time by ICANN, then the RIRs or ICANN shall refer the matter to mediation. >>> >>> In case of disputes where mediation has failed to resolve the dispute, the ICANN ASO MoU agreement provides for arbitration via ICC rules in the jurisdiction of Bermuda or such other location as is agreed between the RIRs and ICANN. It is also worth noting that the RIRs have been participating (as the ASO) in the periodic independent review processes for Accountability and Transparency (ATRT) that is called for per ICANN?s Bylaws. >>> >>> ------- >>> ? References to documentation of policy development and dispute >>> resolution processes. >>> >>> Relevant links: >>> ICANN ASO MoU: https://www.nro.net/documents/icann-address-supporting-organization-aso- mou >>> NRO MoU: https://www.nro.net/documents/nro-memorandum-of-understanding >>> About the NRO Number Council: https://www.nro.net/about-the-nro/the-nro-number-council RIR >>> Governance Matrix: https://www.nro.net/about-the-nro/rir-governance-matrix >>> Global Policies: https://www.nro.net/policies >>> >>> >>> >>> B. Oversight and Accountability >>> >>> This section should describe all the ways in which oversight is conducted over IANA?s provision of the services and activities listed in Section I and all the ways in which IANA is currently held accountable for the provision of those services. For each oversight or accountability mechanism, please provide as many of the following as are applicable: >>> >>> ? Which IANA service or activity (identified in Section I) is >>> affected. >>> ? If the policy sources identified in Section II.A are affected, >>> identify which ones are affected and explain in what way. >>> ? A description of the entity or entities that provide oversight >>> or perform accountability functions, including how individuals >>> are selected or removed from participation in those entities. >>> ? A description of the mechanism (e.g., contract, reporting >>> scheme, auditing scheme, etc.). >>> This should include a description of the consequences of the >>> IANA functions operator not meeting the standards established >>> by the mechanism, the extent to which the output of the >>> mechanism is transparent and the terms under which the >>> mechanism may change. >>> ? Jurisdiction(s) in which the mechanism applies and the legal >>> basis on which the mechanism rests. >>> >>> ------- >>> ? Which IANA service or activity (identified in Section I) is >>> affected. >>> >>> The Internet number resource registries. >>> >>> ------- >>> ? If the policy sources identified in Section II.A are affected, >>> identify which ones are affected and explain in what way. >>> >>> A decision by the NTIA to discontinue its stewardship of the IANA functions, and therefore its contractual relationship with the IANA functions operator, would not have any significant impact on the continuity of Internet number-related IANA services currently provided by ICANN. However, it would remove a significant element of oversight from the current system. >>> >>> There is no contractual obligation directly to the Internet number resource community for the IANA operator to provide IANA registry services for the Internet number registries; IANA services for >>> the Internet number registries are provided by ICANN since its formation as a result of the NTIA IANA Functions contract and hence IANA services for the Internet number registries are presently >>> subject to change per that agreement. >>> >>> ------- >>> ? A description of the entity or entities that provide oversight >>> or perform accountability functions, including how individuals >>> are selected or removed from participation in those entities. >>> >>> All institutional actors with a role in management of Internet number resources are accountable to the open communities that make and agree on the policies under which those resources are distributed and registered. The mechanisms used to ensure and enforce this accountability differ for each of these actors. >>> >>> 1. NTIA >>> ICANN, as the current operator of the IANA functions, is obligated by the NTIA agreement to carry out management of the global IP address and AS Number pools according to policies developed by the communities. >>> >>> While the IANA operator escalation and reporting mechanisms are public in nature, the Internet number community is primarily represented in oversight of the IANA operator performance by the RIRs, which are member-based based organizations with elected governance boards. >>> Currently, the NTIA does not have an oversight role in this regard. >>> >>> The ultimate consequence of failing to meet the performance standards or reporting requirements is understood to be a decision by the contracting party (the NTIA) to terminate or not renew the IANA >>> functions agreement with the current contractor (ICANN). >>> >>> 2. The Regional Internet Registries >>> >>> Administration by the IANA operator consists predominantly of processing of requests from the RIRs for issuance of additional number resources. The five RIRs are intimately familiar with global number resource policies under which the requests are made and maintain communications with the IANA operations team throughout the request process. >>> >>> The RIRs are not-for-profit membership associations, and as such are accountable to their members by law. The specific governance processes for each RIR differ depending on where they have been established and the decisions made by their membership, but in all RIRs, members have the right to vote individuals onto the governing Board and to vote on specific funding or operational resolutions. >>> >>> At the same time, an RIR's registration and allocation practices are directed by policies developed by its community. Each RIR community's PDP defines how these policies are developed, agreed and accepted for operational implementation. >>> >>> The corporate governance documents and PDPs of each RIR and its community are accessible via the RIR Governance Matrix, published on the NRO website. >>> >>> ------- >>> ? A description of the mechanism (e.g., contract, reporting >>> scheme, auditing scheme, etc.). >>> This should include a description of the consequences of the IANA functions operator not meeting the standards established by the mechanism, the extent to which the output of the mechanism is >>> transparent and the terms under which the mechanism may change. >>> >>> The NTIA IANA Agreement currently defines obligations of the IANA operator for Internet number resources. >>> >>> This obligation is specifically noted in section C.2.9.3 of the NTIA agreement: >>> >>> C.2.9.3 Allocate Internet Numbering Resources --The Contractor shall have responsibility for allocated and unallocated IPv4 and IPv6 address space and Autonomous System Number (ASN) space based on established guidelines and policies as developed by interested and affected parties as enumerated in Section C.1.3. >>> >>> The NTIA agreement also lays out specific deliverables for the IANA operator (ICANN) to produce as a condition of the agreement (see "Section F ? Deliveries and Performance"), including performance >>> standards developed in cooperation with the affected parties (in the case of the Internet number resource pools, the affected parties include the RIRs and their communities), customer complaint >>> procedures and regular performance reporting. >>> >>> These deliverables are met by ICANN via monthly reporting on their performance in processing requests for the allocation of Internet number resources; these reports include IANA operator performance against key metrics of accuracy, timeliness, and transparency, as well as the performance metrics for individual requests. The IANA operations team also provides escalation procedures for use in resolving any issues with requests, as per the "IANA Customer Service Complaint Resolution Process". >>> >>> ------- >>> ? Jurisdiction(s) in which the mechanism applies and the legal >>> basis on which the mechanism rests. >>> >>> Jurisdiction for this current mechanism is the United States of America under applicable Federal government contracting laws and regulations. >>> >>> Relevant links: >>> NTIA IANA Agreement: http://www.ntia.doc.gov/page/iana-functions-purchase-order >>> ICANN ASO MoU: https://www.nro.net/documents/icann-address-supporting-organization-aso- mou >>> NRO MoU: https://www.nro.net/documents/nro-memorandum-of-understanding >>> IANA Customer Service Complaint Resolution Process: http://www.iana.org/help/escalation- procedure >>> IANA Performance Standards Metrics Report: http://www.iana.org/performance/metrics >>> RIR Governance Matrix: https://www.nro.net/about-the-nro/rir-governance-matrix >>> >>> >>> >>> III. Proposed Post-Transition Oversight and Accountability Arrangements >>> >>> This section should describe what changes your community is proposing to the arrangements listed in Section II.B in light of the transition. If your community is proposing to replace one or more existing arrangements with new arrangements, that replacement should be explained and all of the elements listed in Section II.B should be described for the new arrangements. Your community should >>> provide its rationale and justification for the new arrangements. >>> >>> If your community?s proposal carries any implications for the interface between the IANA functions and existing policy arrangements described in Section II.A, those implications should be described >>> here. >>> >>> If your community is not proposing changes to arrangements listed in Section II.B, the rationale and justification for that choice should be provided here. >>> >>> ------- >>> The elements of this proposal are as follows: >>> >>> (1) ICANN to continue as the IANA functions operator on number >>> resources; >>> (2) Service level agreement with the IANA functions operator on >>> number resources; and >>> (3) Establishment of a Review Committee, with representatives >>> from each RIR, to advise the NRO EC on the review of the >>> IANA functions operator?s performance and meeting of >>> identified service levels. >>> >>> To maintain stability and continuity in operations of the Internet number-related IANA services, very minimal changes to the arrangements listed in Section II.B are proposed, including the identification of the proposed initial IANA functions operator. As noted in numerous NRO >>> communications over the past decade, the RIRs have been very satisfied with the performance of ICANN in the role of IANA functions operator. Taking this into account, and considering the strong desires expressed in the five RIR communities' IANA stewardship discussions for stability and a minimum of operational change, the Internet numbering community believes that ICANN should remain in the role of IANA functions operator for at least the initial term of the new contract. >>> >>> A decision by the NTIA to discontinue its stewardship of the IANA functions, and therefore its contractual relationship with the IANA functions operator, would not have any significant impact on >>> the continuity of Internet number-related IANA services currently provided by ICANN. However, it would remove a significant element of oversight from the current system. >>> >>> The following is a proposal to replace the current NTIA IANA agreement with a new contract that more directly reflects and enforces the IANA functions operator's accountability to the open, >>> bottom-up numbers community. Other than the replacement of the NTIA with the five RIRs as the party(ies) with whom the IANA functions operator would contract for provision of Internet number-related IANA services, the overall arrangements in Section II.B would remain with no change. >>> >>> The proposed arrangement involves the same IANA service or activity, policy sources identified in Section II.A are unaffected, the entities that provide oversight or perform accountability functions (the RIRs) remain the same, the consequence for failure to meet performance standards remains termination or decision not to renew the IANA functions agreement with the then-current contractor, and jurisdiction will be dependent on the chosen IANA functions operator. >>> >>> The Internet numbering community proposes that a new contract be established between the IANA functions operator and the five RIRs. The contract, essentially an IANA Service Level Agreement, would obligate the IANA functions operator to carry out those IANA functions relating to the global Internet number pools according to policies developed by the regional communities via the gPDP as well as management of the delegations within IN-ADDR.ARPA and IP6.ARPA domains. The agreement would include specific requirements for performance and reporting commensurate with current mechanisms, and would specify consequences should the contractor fail to meet those requirements, the means for the resolution of disputes between the parties, and the terms for renewal or termination of the contract. IANA operations should be >>> reliable and consistent, with any registry changes made in an open and transparent manner to the global community. The agreement should also require the IANA operator to appropriately coordinate with any other operator of IANA-related registry services. >>> >>> To ensure the service level defined in the proposed contract is maintained and provided by the IANA functions operator, the NRO EC will conduct periodic reviews of the service level of the IANA number resource functions that serves each RIR and their respective communities. The NRO EC shall establish a Review Committee that will advise and assist the NRO EC in its periodic review. Any such Review Committee should be a team composed of representatives from each RIR region that will, as needed, undertake a review of the level of service received from the IANA functions operator and report to the NRO EC any concerns regarding any observed failure by the IANA functions operator to meet its contractual obligations under the proposed contract. Any such Review Committee will advise the NRO EC in its capacity solely to oversee the performance of the IANA number resource functions and the Review Committee?s advice and comment will be limited to the processes followed in the IANA functions operator?s performance under the proposed contract. >>> >>> If your community?s proposal carries any implications for the interface between the IANA functions and existing policy arrangements described in Section II.A, those implications should be described >>> here. >>> >>> This proposal carries no implication for the interface between IANA functions and existing policy arrangements described in Section II.A. The text in "Attachment A" of the ICANN ASO MoU meets the current and anticipated requirements for a community-driven global policy development process. >>> >>> As an additional measure of security and stability, the RIRs have documented their individual accountability and governance mechanisms, and asked the community-based Number Resource Organization Number Council (NRO NC) to undertake a review of these mechanisms and make >>> recommendations for improvements that may be warranted given the nature of the stewardship transition for Internet number resources. >>> >>> >>> IV. Transition Implications >>> >>> This section should describe what your community views as the implications of the changes it proposed in Section III. These implications may include some or all of the following, or other >>> implications specific to your community: >>> >>> ? Description of operational requirements to achieve continuity >>> of service and possible new service integration throughout the >>> transition. >>> ? Risks to operational continuity and how they will be addressed. >>> ? Description of any legal framework requirements in the absence >>> of the NTIA contract. >>> ? Description of how you have tested or evaluated the >>> workability of any new technical or >>> operational methods proposed in this document and how they >>> compare to established arrangements. >>> >>> ------- >>> ? Description of operational requirements to achieve continuity >>> of service and possible new service integration throughout the >>> transition. >>> ? Risks to operational continuity and how they will be addressed. >>> >>> The intent of the proposal described above is to: >>> >>> 1. Minimize risks to operational continuity of the management of the Internet number- related IANA functions, and; >>> 2. Retain the existing framework for making those policies that describe the management of the global Internet number resource pools, as this framework is already structured to ensure open, bottom-up development of such policies. >>> >>> Under current arrangements, the NTIA is responsible for extending or renewing the IANA functions agreement, and setting the terms of that contract. A new contract with the five RIRs and the IANA functions operator as signatories would shift the responsibility for renewing, setting terms or terminating the contract to the RIRs, who would coordinate their decisions via the NRO EC (made up of the RIR Directors and Chief Executives). Decisions made regarding the contract would be based on operational circumstances, past performance and input from open, regional communities. >>> >>> The shift from the existing contractual arrangement to another contractual arrangement (perhaps relying on a set of distinct contracts) covering the IANA functions operator?s ongoing management >>> of all the IANA functions should result in no operational change for management of the global Internet number resource pools. This will help minimize any operational or continuity risks associated with stewardship transition. >>> >>> By building on the existing Internet registry system (which is open to participation from all interested parties) and its structures, the proposal reduces the risk associated with creating new organizations whose accountability is unproven. >>> >>> The necessary agreement proposed for IANA operation services for the Internet number registries can be established well before the NTIA target date for transition (September 2015), as there are no changes to existing service levels or reporting that are being proposed, only a change in contracting party to align with the delegated policy authority. >>> >>> ------- >>> ? Description of any legal framework requirements in the absence >>> of the NTIA contract. >>> >>> The necessary legal framework in the absence of the NTIA contract will be fulfilled by the proposed agreement between the IANA functions operator and the five RIRs. As stated in Section III above, >>> the contract, essentially an IANA Service Level Agreement, would obligate the IANA functions operator to carry out those IANA functions relating to the global Internet number pools according to policies developed by the regional communities via the gPDP as well as >>> management of the delegations within IN-ADDR.ARPA and IP6.ARPA domains. The agreement would include specific requirements for performance and reporting commensurate with current mechanisms, and would specify consequences should the contractor fail to meet those requirements, the means for the resolution of disputes between the parties, and the terms for renewal or termination of the contract. IANA operations should be reliable and consistent, with any registry changes made in an open and transparent manner to the global community. >>> >>> The agreement should also require the IANA operator to appropriately coordinate with any other operator of IANA-related registry services. The contract would also provide for jurisdiction and governing law regarding the new arrangement. >>> >>> ------- >>> ? Description of how you have tested or evaluated the >>> workability of any new technical or >>> operational methods proposed in this document and how they >>> compare to established arrangements. >>> ? Risks to operational continuity and how they will be addressed. >>> >>> This proposal does not propose any new technical or operational methods. There is inclusion of a proposed Review Committee to be established by the five RIRs acting cooperatively and coordinating >>> through the NRO EC; however, this does not carry any new operational method as the IANA functions operator would remain accountable to the party with whom it is contracting, in this case, the five RIRs in place of the NTIA. The proposed Review Committee is a tool for the five RIRs to evaluate and review performance of the IANA functions provided. >>> >>> >>> >>> V. NTIA Requirements >>> >>> Additionally, NTIA has established that the transition proposal must meet the following five requirements: >>> >>> ? Support and enhance the multistakeholder model; >>> ? Maintain the security, stability, and resiliency of the >>> Internet DNS; >>> ? Meet the needs and expectation of the global customers and >>> partners of the IANA services; >>> ? Maintain the openness of the Internet. >>> ? The proposal must not replace the NTIA role with a >>> government-led or an inter-governmental organization solution. >>> >>> This section should explain how your community?s proposal meets these requirements and how it responds to the global interest in the IANA functions. >>> >>> ------- >>> The proposal for the IANA stewardship transition for the Internet number registries builds upon the existing, successful framework used by the Internet number community today. The major characteristics of this approach include: >>> >>> 1. Global number policy development which is open and transparent to any and all participants >>> 2. Continuance of existing IANA service levels, escalation processes, and reporting mechanisms >>> 3. Maintenance of independent review and ratification for developed global Internet number resource policy >>> 4. Continued use of periodic third-party independent reviews of accountability and transparency of processes >>> 5. No change of the existing IANA operator for maximum stability and security of operational processes and systems >>> 6. Accountable, member-based, globally-distributed RIR organizations providing routine IANA operational oversight for the Internet number registries >>> 7. No new organization is proposed. However, a new process within the RIR structures is proposed, where a Review Committee is established to advise and assist the NRO EC in its periodic review of the service level provided by the IANA functions operator. >>> >>> As a result of the approach taken (and its characteristics as outlined above), it is clear that the proposal from the Internet number community meets the stated NTIA requirements. >>> >>> >>> VI. Community Process >>> >>> This section should describe the process your community used for developing this proposal, including: >>> >>> ? The steps that were taken to develop the proposal and to >>> determine consensus. >>> ? Links to announcements, agendas, mailing lists, consultations >>> and meeting proceedings. >>> ? An assessment of the level of consensus behind your >>> community?s proposal, including a description of areas of >>> contention or disagreement. >>> >>> ------- >>> 1. Regional and global process >>> >>> Each of the five RIR communities is discussing the IANA stewardship issues via mailing lists, at their RIR meetings and in other community forums. While these discussions have been uniformly open and transparent, with all discussions archived on mailing lists and meeting records, each community has adopted a specific process of their own choosing to reach an agreed community output. >>> >>> The results from the five regional processes fed a global process that produced this document. More details about the regional and global processes are given below, interspersed with links to relevant documents. >>> >>> 2. AFRINIC regional process: >>> The AFRINIC community held a consultative meeting on 25 May to 6 June 2014 during the Africa Internet Summit (AIS'2014) in Djibouti in the "IANA oversight transition" workshop. As a follow up to the meeting, AFRINIC setup a mailing list to provide a platform for the African >>> Internet community to discuss the IANA Oversight Transition process. The mailing list was announced on July 4, 2014 to develop a community position. The list and its archives can be found at: >>> https://lists.afrinic.net/mailman/listinfo.cgi/ianaoversight >>> >>> A Dedicated web portal was setup for sharing information on the IANA stewardship transition with the AFRINIC community and is also available at http://afrinic.net/en/community/iana-oversight-transition >>> >>> AFRINIC also conducted a survey seeking community input on the IANA Stewardship Transition. The results of the survey are published >>> at: http://afrinic.net/images/stories/Initiatives/%20survey%20on%20the%20iana%20stewardship >>> %20transition.pdf >>> >>> >>> The last face-to-face meeting at which IANA oversight transition consultations were held with the community was during the AFRINIC-21 meeting in Mauritius, 22-28 November 2014. The recordings of >>> the session are available at http://meeting.afrinic.net/afrinic-21/en/vod >>> >>> Discussions continued on the ianaoversight at afrinic.net mailing list, until the closure of the comments from the number resources communities set by the CRISP Team on 12th Jan 2015. >>> >>> 3. APNIC regional process: >>> APNIC, as the secretariat for the APNIC community has set up a public mailing list (announced on 1 Apr 2014) to develop a community position, and have discussions about the proposal from the region on IANA stewardship transition: http://mailman.apnic.net/mailman/listinfo/IANAxfer >>> >>> Webpage, dedicated to sharing up-to-date information on the IANA stewardship transition was set up, for the APNIC community members and wider community members who are interested in this issue can be updated: http://www.apnic.net/community/iana-transition >>> >>> Draft proposal was discussed at the dedicated session at the APNIC 38 Meeting, which saw the general community consensus. The meeting provided >>> remote participation tools to enable wider participation from communities across Asia Pacific and beyond, with live webcasts well as Adobe Connect virtual conference room. >>> >>> https://conference.apnic.net/38/program#iana >>> >>> The discussions continued on the "ianaxfer at apnic.net." mailing list, >>> until the closure of the comments from the number resources communities set by CRISP Team as 12th Jan 2015. >>> >>> 4. ARIN regional process: >>> >>> >>> >>> 5. LACNIC regional process: >>> >>> >>> >>> >>> 6. RIPE regional process: >>> The RIPE community agreed at the RIPE 68 Meeting in May 2014 that the development of a community position on IANA stewardship should take place in the RIPE Cooperation Working Group, and via that working group's public mailing list: https://www.ripe.net/ripe/mail/wg- lists/cooperation >>> >>> The RIPE NCC, as secretariat for the RIPE community, also facilitated discussions on the IANA stewardship in national and regional forums across the RIPE NCC service region. Summaries of these discussions were posted to the RIPE Cooperation Working Group mailing list and on the RIPE website: >>> https://www.ripe.net/iana-discussions >>> >>> Between September and November 2014, RIPE community discussion centered around developing a set of principles reflecting the communities primary concerns in the development of an alternative IANA stewardship arrangement. These discussions are reflected in the discussions on the mailing list from that time: http://www.ripe.net/ripe/mail/archives/cooperation- wg/ >>> >>> Discussions at the RIPE 69 Meeting in November 2014 saw general community consensus on the principles discussed on the mailing list, and support expressed for the three community members selected to join the Consolidated RIR IANA Stewardship Proposal (CRISP) team. >>> >>> RIPE Cooperation Working Group Session: https://ripe69.ripe.net/programme/meeting- plan/coop-wg/#session1 >>> RIPE 69 Closing Plenary Session: https://ripe69.ripe.net/archives/video/10112/ >>> >>> ------- >>> 7. Global process (CRISP Team) >>> On 16 October 2014, the NRO EC proposed the formation of a Consolidated RIR IANA Stewardship >>> >>> Proposal (CRISP) team to develop a single Internet numbering community proposal to the IANA Stewardship Coordination Group (ICG). Each RIR community selected three members (two community members and one RIR staff) to participate in the team. The participants selected were: >>> >>> AFRINIC Region >>> Alan P. Barrett ? Independent Consultant >>> Mwendwa Kivuva ? Network Infrastructure Services, University of Nairobi Ernest Byaruhanga (Appointed RIR staff) >>> >>> ARIN Region >>> Bill Woodcock ? President and Research Director of Packet Clearing House >>> John Sweeting ? Sr. Director, Network Architecture & Engineering at Time Warner Cable >>> Michael Abejuela (Appointed RIR staff) >>> >>> APNIC Region >>> Dr Govind ? CEO NIXI >>> Izumi Okutani ? Policy Liaison JPNIC >>> Craig Ng (Appointed RIR staff) >>> >>> LACNIC Region >>> Nico Scheper - Curacao IX >>> Esteban Lescano - Cabase Argentina >>> Andr?s Piazza (Appointed RIR staff) >>> >>> RIPE NCC Region >>> Nurani Nimpuno ? Head of Outreach & Communications at Netnod >>> Andrei Robachevsky ? Technology Programme Manager at the Internet Society Paul Rendek (Appointed >>> RIR staff) >>> >>> Steps and timeline for proposal development and links to announcements, mailing lists, and >>> proceedings - https://www.nro.net/nro-and-internet-governance/iana-oversight/timeline-for-rirs- >>> engagement-in-iana-stewardship-transition-process >>> >>> ------- >>> 8. Assessment of consensus level >>> >>> >>> >>> >>>> On 2014/12/29 20:43, Izumi Okutani wrote: >>>> Dear Colleagues, >>>> >>>> >>>> CRISP Team has published an editorial version of the Internet >>>> numbers community's response to the Request For Proposals issued by the >>>> IANA Stewardship Coordination Group (ICG): >>>> >>>> http://www.nro.net/crisp-proposal-first-draft-1-1 >>>> >>>> From the initial draft we published on 19th Dec [*], we have made >>>> editorial changes only. No changes are made in contents of the proposal. >>>> >>>> [*] >>>> https://www.nro.net/wp-content/uploads/CRISP-IANA-PROPOSAL-First-Draft1.pdf >>>> >>>> The editorial changes are intended to clarify our answers to RFP, by >>>> re-ordering answers in the same order as questions listed in each >>>> Section. Some small additions have been made to address points that had >>>> not been answered in the earlier draft. Finally, there are some changes >>>> made for stylistic reasons. >>>> >>>> The deadline of the comments to be submitted to >>>> mailing list remains the same: Monday 5th Jan 2015. >>>> >>>> Please let us know if you have any questions about version 1.1 of our >>>> draft proposal, and we continue to welcome feedback from the community. >>>> >>>> >>>> Best Regards, >>>> Consolidated RIR IANA Stewardship Proposal Team (CRISP Team) >>> >>> >>> _______________________________________________ >>> ianaxfer mailing list >>> ianaxfer at nro.net >>> https://www.nro.net/mailman/listinfo/ianaxfer > From hph at oslo.net Sat Jan 3 11:38:57 2015 From: hph at oslo.net (Hans Petter Holen) Date: Sat, 03 Jan 2015 11:38:57 +0100 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] Editorial version of Internet Number Community IANA Stewardship, Proposal published In-Reply-To: <0D75AEC2-7FC2-43F6-9765-064D14BD3A83@akamai.com> References: <54A6E0A5.2030506@nic.ad.jp> <20EB2E8D-FB2C-43B3-902E-5047CF048843@netnod.se> <0D75AEC2-7FC2-43F6-9765-064D14BD3A83@akamai.com> Message-ID: <54A7C6C1.9080901@oslo.net> On 03.01.15 03.02, Hannigan, Martin wrote: > Is the ianaxfer@ list open for posting or do we need to subscribe, which is typical for mailman? I recall earlier that we all agreed this list would be post by members, view by public. if you want to participate in the discussions I would urge you to subscribe. If you simply want to raise points without engaging in the discussions, I have noticed that the CRISP team members pay attention to what is discussed on the regional lists (like cooperation-wg). From listening in to their conf-calls I hear that they very much value input from the community. -- Hans Petter Holen Mobile +47 45 06 60 54 | hph at oslo.net | http://hph.oslo.net From nurani at netnod.se Sat Jan 3 23:17:24 2015 From: nurani at netnod.se (Nurani Nimpuno) Date: Sat, 3 Jan 2015 23:17:24 +0100 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] Editorial version of Internet Number Community IANA Stewardship, Proposal published In-Reply-To: <54A7C6C1.9080901@oslo.net> References: <54A6E0A5.2030506@nic.ad.jp> <20EB2E8D-FB2C-43B3-902E-5047CF048843@netnod.se> <0D75AEC2-7FC2-43F6-9765-064D14BD3A83@akamai.com> <54A7C6C1.9080901@oslo.net> Message-ID: Thanks Hans Petter. > On 3 jan 2015, at 11:38, Hans Petter Holen wrote: > >> On 03.01.15 03.02, Hannigan, Martin wrote: >> Is the ianaxfer@ list open for posting or do we need to subscribe, which is typical for mailman? I recall earlier that we all agreed this list would be post by members, view by public. > if you want to participate in the discussions I would urge you to subscribe. Indeed! This is the time to provide your input. After the 5th we will produce a new draft and then we are getting very close to the submission deadline. > If you simply want to raise points without engaging in the discussions, I have noticed that the CRISP team members pay attention to what is discussed on the regional lists (like cooperation-wg). We do our best of course in representing the views raised in the RIPE community. That is part of our role on the CRISP team. But I do encourage people to directly engage on the global list. It allows you to respond directly to some of the issues raised as well as arguing for your own points. > From listening in to their conf-calls I hear that they very much value input from the community. Very much. Thanks. Nurani > -- > Hans Petter Holen > Mobile +47 45 06 60 54 | hph at oslo.net | http://hph.oslo.net > > From nurani at netnod.se Sun Jan 4 20:59:38 2015 From: nurani at netnod.se (Nurani Nimpuno) Date: Sun, 4 Jan 2015 20:59:38 +0100 Subject: [cooperation-wg] Fwd: [CRISP-TEAM] CRISP Team 8th Teleconference January 5th 2015 @ 13:00 UTC References: Message-ID: <2999907F-0CED-48F4-8862-0624417B796F@netnod.se> Dear colleagues, Please find details below about the 8th CRISP teleconference. The CRISP teleconferences are open to observers. Kind regards, Nurani Nimpuno On behalf of the RIPE CRISP team Begin forwarded message: > From: German Valdez > Subject: [CRISP-TEAM] CRISP Team 8th Teleconference January 5th 2015 @ 13:00 UTC > Date: 2 januari 2015 16:03:18 CET > To: , > > Hi > > Please find below webex information for the 8th CRISP Team teleconference to be held on Monday January 5th 2015 at 13:00 UTC > > Regards > > German Valdez > NRO > > > ====== > > CRISP Team 8thTeleconference > Monday, January 5, 2015 > 1:00pm | UTC | 2 hr > > Join WebEx meeting > https://ripencc.webex.com/ripencc/j.php?MTID=mc7fe8904fb98d0e4132409b1f6362d5d > > Meeting number: > 701 103 817 > Meeting password: > crispteam > > Join by phone > 0800-051-3810 Call-in toll-free number (UK) > +44-203-478-5289 Call-in toll number (UK) > Accesscode: 701 103 817 > Global call-in numbers | > > https://ripencc.webex.com/ripencc/globalcallin.php?serviceType=MC&ED=359012912&tollFree=1 > > Toll-free calling restrictions > > http://www.webex.com/pdf/tollfree_restrictions.pdf > > > Add this meeting to your calendar. > > Can't join the m Contact support. > > IMPORTANT NOTICE: Please note thatsession. > > _______________________________________________ > CRISP mailing list > CRISP at nro.net > https://www.nro.net/mailman/listinfo/crisp -------------- next part -------------- An HTML attachment was scrubbed... URL: From nurani at netnod.se Mon Jan 5 10:08:30 2015 From: nurani at netnod.se (Nurani Nimpuno) Date: Mon, 5 Jan 2015 10:08:30 +0100 Subject: [cooperation-wg] Video archives of CRISP teleconferences available Message-ID: <491DECC3-F6B5-4A5E-8CAA-9D1EC8EECDCA@netnod.se> Dear colleagues, Just a quick note to let you know that video archives of all CRISP teleconferences are publicly available (on youtube) from the NRO website (in addition to the audio files and minutes published). You will find all CRISP related information, including the latest draft proposal text, a matrix of all input received, and the process timeline at: https://www.nro.net/crisp-team Kind regards, Nurani Nimpuno on behalf of the CRISP RIPE team -- Nurani Nimpuno Head of Outreach & Communications, Netnod , http://www.netnod.se Box 30194 | SE-104 25 Stockholm | Sweden --------------------------------------------- From chrisb at ripe.net Mon Jan 5 10:58:22 2015 From: chrisb at ripe.net (Chris Buckridge) Date: Mon, 5 Jan 2015 10:58:22 +0100 Subject: [cooperation-wg] Last Day to Comment on IANA Stewardship Draft References: Message-ID: <863491EF-B0E2-4ED4-92EB-4C90882E4341@ripe.net> Dear colleagues, A reminder that today is the last day for commenting on the first draft of the Internet numbers community?s IANA stewardship proposal. The draft, produced by the Consolidated RIR IANA Stewardship Proposal (CRISP) team, is available at: https://www.nro.net/wp-content/uploads/CRISP-IANA-PROPOSAL-First-Draft1.pdf After the comment period closes, the CRISP team will prepare a second public draft, based on the feedback received. The timeline for the remaining CRISP team work is: Second draft to be published: 8 Jan 2015 Final proposal to be sent to IANA Stewardship Transition Coordination Group (ICG): 15 Jan 2015 The CRISP team will hold its eighth teleconference today, 5 January, at 13:00 UTC. Details on how to join the call as an observer are included at the end of this email. More background on the IANA stewardship transition process is available at: https://www.ripe.net/iana-oversight-transition Details on the CRISP team, including members, timelines and working methods, are available at: https://nro.net/crisp-team Best regards, Chris Buckridge RIPE NCC ====== CRISP Team 8thTeleconference Monday, January 5, 2015 1:00pm | UTC | 2 hr Join WebEx meeting https://ripencc.webex.com/ripencc/j.php?MTID=mc7fe8904fb98d0e4132409b1f6362d5d Meeting number: 701 103 817 Meeting password: crispteam Join by phone 0800-051-3810 Call-in toll-free number (UK) +44-203-478-5289 Call-in toll number (UK) Accesscode: 701 103 817 Global call-in numbers: https://ripencc.webex.com/ripencc/globalcallin.php?serviceType=MC&ED=359012912&tollFree=1 Toll-free calling restrictions: http://www.webex.com/pdf/tollfree_restrictions.pdf -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2608 bytes Desc: not available URL: From nurani at netnod.se Mon Jan 5 11:50:52 2015 From: nurani at netnod.se (Nurani Nimpuno) Date: Mon, 5 Jan 2015 11:50:52 +0100 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] Draft Agenda for 8th Teleconfererence Re: CRISP Team 8th Teleconference January 5th 2015 @ 13:00 UTC References: <54AA6A2B.1000107@nic.ad.jp> Message-ID: fyi Begin forwarded message: > From: Izumi Okutani > Subject: [NRO-IANAXFER] Draft Agenda for 8th Teleconfererence Re: CRISP Team 8th Teleconference January 5th 2015 @ 13:00 UTC > Date: 5 januari 2015 11:40:43 CET > To: ianaxfer at nro.net > > Dear Colleagues, > > > Please see the draft agenda for CRISP Team 8th Teleconference January > 5th 2015 @ 13:00 UTC. > > Observers are welcome to join the call as usual. > > --- > 1. Agenda Review > > 2. Actions Review > a. Minutes > b. Recordings of past meetings > c. Version control of drafts > > 3. Confirm new comments since the 7th call > a. Each RIR region > b. Global list > > 3. Follow up of issues discussed > a. IPR > b. Contract > c. Review Commitee > > 4. Issues not yes discussed > a. Details of the Review Process > b. RIR Accountability, > c. Determining consensus for the final draft > > 6. Preparation for the 2nd draft > a. Topics to be reflected in the 2nd draft > b. Announcement > > 7. Next Meeting > > 8. AOB > --- > > > Regards, > Izumi Okutani > CRISP Team > > On 2015/01/03 0:03, German Valdez wrote: >> Hi >> >> Please find below webex information for the 8th CRISP Team teleconference to be held on Monday January 5th 2015 at 13:00 UTC >> >> Regards >> >> German Valdez >> NRO >> >> >> ====== >> >> CRISP Team 8thTeleconference >> Monday, January 5, 2015 >> 1:00pm | UTC | 2 hr >> >> Join WebEx meeting >> https://ripencc.webex.com/ripencc/j.php?MTID=mc7fe8904fb98d0e4132409b1f6362d5d >> >> Meeting number: >> 701 103 817 >> Meeting password: >> crispteam >> >> Join by phone >> 0800-051-3810 Call-in toll-free number (UK) >> +44-203-478-5289 Call-in toll number (UK) >> Accesscode: 701 103 817 >> Global call-in numbers | >> >> https://ripencc.webex.com/ripencc/globalcallin.php?serviceType=MC&ED=359012912&tollFree=1 >> >> Toll-free calling restrictions >> >> http://www.webex.com/pdf/tollfree_restrictions.pdf >> >> >> Add this meeting to your calendar. >> >> Can't join the m Contact support. >> >> IMPORTANT NOTICE: Please note thatsession. >> >> >> >> >> _______________________________________________ >> ianaxfer mailing list >> ianaxfer at nro.net >> https://www.nro.net/mailman/listinfo/ianaxfer >> > > > _______________________________________________ > ianaxfer mailing list > ianaxfer at nro.net > https://www.nro.net/mailman/listinfo/ianaxfer From nurani at netnod.se Wed Jan 7 09:50:00 2015 From: nurani at netnod.se (Nurani Nimpuno) Date: Wed, 7 Jan 2015 09:50:00 +0100 Subject: [cooperation-wg] Fwd: [CRISP-TEAM] CRISP Team 9th Teleconference, Wednesday 7th January 2015 at 13:00 UTC References: <54AAEBE1.9040801@lacnic.net> Message-ID: <7F1C15CB-A889-41A2-9654-2F5FAC54FFCE@netnod.se> FYI. A placeholder extra teleconference has been scheduled today at 14.00 CET, to discuss any outstanding issues before the finalisation of the 2nd draft of the CRISP proposal. The CRISP teleconferences are open to observers. Kind regards, Nurani Nimpuno On behalf of the RIPE CRISP team Begin forwarded message: > From: Maria Gayo > Subject: [CRISP-TEAM] CRISP Team 9th Teleconference, Wednesday 7th January 2015 at 13:00 UTC > Date: 5 januari 2015 20:54:09 CET > To: crisp at nro.net > Reply-To: mgayo at lacnic.net > > Please find below webex information for the 9th CRISP Team teleconference to be held on Wednesday 7th January 2015 at 13:00 UTC > > > > Regards > > Mar?a Gayo > (on behalf of the NRO Secretariat) > > > -------- > > CRISP Team 9th Teleconference > > Wednesday, January 7th, 2015 > > 1:00 pm UTC > > Join Webex meeting https://lacnic.webex.com/lacnic/j.php?MTID=me72f52dfbfd3075087e0f7d746af0391 > > Meeting number: 576 519 399 > > Meeting password: lcn2015 > > Join by phone > > 1-877-668-4490 Call-in toll-free number > > 1-408-792-6300 Call-in toll number > > Access code: 576 519 399 > > Add this meeting to your calendar : > https://lacnic.webex.com/lacnic/j.php?MTID=m2d0e4b80f02040f773c0643a4b428587 > > Can?t join this meeting? Contact support https://lacnic.webex.com/lacnic/mc or florencia at lacnic.net Phone: 598-26042222 > Mar?a Gayo > Coordinadora de Comunicaciones > Communications Coordinator > # 4206 > Casa de Internet de > Latinoam?rica y el Caribe > Rambla Rep. de M?xico 6125 > 11400 Montevideo-Uruguay > +598 2604 22 22 www.lacnic.net _______________________________________________ > CRISP mailing list > CRISP at nro.net > https://www.nro.net/mailman/listinfo/crisp -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: fcfahagd.png Type: image/png Size: 5594 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bagfigjc.png Type: image/png Size: 6213 bytes Desc: not available URL: From nurani at netnod.se Wed Jan 7 10:11:22 2015 From: nurani at netnod.se (Nurani Nimpuno) Date: Wed, 7 Jan 2015 10:11:22 +0100 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] Thank you for the feedback and update on CRISP Team Status References: <54ACF2CE.3080505@nic.ad.jp> Message-ID: <8ABC3099-C782-418C-BD0C-83C176A4037F@netnod.se> FYI. Nurani Begin forwarded message: > From: Izumi Okutani > Subject: [NRO-IANAXFER] Thank you for the feedback and update on CRISP Team Status > Date: 7 januari 2015 09:48:14 CET > To: ianaxfer at nro.net > > Dear Colleagues, > > > CRISP Team would like to thank everyone who have provided your inputs to > the first draft of our proposal. > > We have closed comments for the first draft, and completed to form CRISP > Team's position on all issues express on mailing list > at the 8th CRISP Team call, at UTC13:00 Mon 5th Jan. > > CRISP Team is now working to publish the second draft, which is planned > to be published on Thu 8th Jan. We will make an announcement on this > mailing list, and call for comments from the global community once it is > published, as we did for the first draft. > > In the meantime, attached is the status list of issue raised on > for you to confirm status of CRISP Team > considerations. Please note this is to be updated as our work progresses. > > We are planning to publish the updated issues status list when we > publish our second draft. > > Thank you once again for taking your time to review the first draft of > our proposal and sharing your views. > > > Best Regards, > Izumi Okutani > CRISP Team Chair -------------- next part -------------- A non-text attachment was scrubbed... Name: NRODiscussionList_20150106.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 18819 bytes Desc: not available URL: -------------- next part -------------- > _______________________________________________ > ianaxfer mailing list > ianaxfer at nro.net > https://www.nro.net/mailman/listinfo/ianaxfer From nurani at netnod.se Wed Jan 7 12:19:18 2015 From: nurani at netnod.se (Nurani Nimpuno) Date: Wed, 7 Jan 2015 12:19:18 +0100 Subject: [cooperation-wg] Fwd: [CRISP-TEAM] Draft Agenda for the 7th call Re: CRISP Team 9th Teleconference, Wednesday 7th January 2015 at 13:00 UTC References: <54AD15CA.50201@nic.ad.jp> Message-ID: FYI Begin forwarded message: > From: Izumi Okutani > Subject: [CRISP-TEAM] Draft Agenda for the 7th call Re: CRISP Team 9th Teleconference, Wednesday 7th January 2015 at 13:00 UTC > Date: 7 januari 2015 12:17:30 CET > To: crisp at nro.net > > Dear Colleagues, > > > Below is the draft agenda for the coming 7th CRISP Team Teleconference on Wednesday 7th January 2015 at 13:00 UTC. > > This is open to any observers as usual. > > --- > 1. Agenda Review > > 2. Actions Review > a. Minutes > b. Version Control of the drafts > c. Announcement of the comments closed on the IANAXFER list > > 2. Issues after the last call > a. Contract details (continued discussions) > b. Defining Review Commitee process > c. Community engagement in developing contract > > 3. Confirm status of issues > a. Issues to be reviewed on the ML (no discusssions at the call) > b. Reflecting CRISP Team positions per issues > (IRP, Review Commitee, SLA) > c. Issues Status list > > 4. Preparation for the 2nd draft announcement > a. draft announcement & its timing > b. Deadline of comments to be submitted for texts > c. Timing to share the updated version within CRISP Team > > 5. Next call > > 6. AOB > --- > > > Regards, > Izumi Okutani > CRISP Team > > On 2015/01/06 4:54, Maria Gayo wrote: >> Please find below webex information for the 9th CRISP Team teleconference to be >> held on Wednesday 7th January 2015 at 13:00 UTC >> >> Regards >> >> Mar?a Gayo >> (on behalf of the NRO Secretariat) >> >> >> -------- >> >> ***CRISP Team 9th Teleconference* >> >> Wednesday, January 7th, 2015 >> >> 1:00 pm UTC >> >> *Join Webex meeting >> *https://lacnic.webex.com/lacnic/j.php?MTID=me72f52dfbfd3075087e0f7d746af0391 >> >> Meeting number: 576 519 399 >> >> Meeting password: lcn2015 >> >> *Join by phone* >> >> 1-877-668-4490 Call-in toll-free number >> >> 1-408-792-6300 Call-in toll number >> >> Access code: 576 519 399 >> >> *Add this meeting to your calendar :* >> >> https://lacnic.webex.com/lacnic/j.php?MTID=m2d0e4b80f02040f773c0643a4b428587 >> >> Can?t join this meeting? Contact support https://lacnic.webex.com/lacnic/mc or >> florencia at lacnic.net Phone: 598-26042222 >> >> Embedded Image >> *Mar?a Gayo* >> Coordinadora de Comunicaciones >> Communications Coordinator >> *# 4206* >> Embedded Image >> *Casa de Internet de >> Latinoam?rica y el Caribe* >> Rambla Rep. de M?xico 6125 >> 11400 Montevideo-Uruguay >> +598 2604 22 22 www.lacnic.net >> >> >> >> _______________________________________________ >> CRISP mailing list >> CRISP at nro.net >> https://www.nro.net/mailman/listinfo/crisp >> > > > _______________________________________________ > CRISP mailing list > CRISP at nro.net > https://www.nro.net/mailman/listinfo/crisp From nurani at netnod.se Thu Jan 8 14:17:16 2015 From: nurani at netnod.se (Nurani Nimpuno) Date: Thu, 8 Jan 2015 14:17:16 +0100 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] Last minute CRISP Team Teleconference January 8th 2015 13:00 UTC References: Message-ID: fyi Begin forwarded message: > From: German Valdez > Subject: [NRO-IANAXFER] Last minute CRISP Team Teleconference January 8th 2015 13:00 UTC > Date: 8 januari 2015 14:13:42 CET > To: > > > Hi > > On behalf of CRISP Team I?m attaching a webex invitation to follow their meeting right now. > > Meeting was called in very last minute to finalise details for the publication of the second draft proposal for the ICG > > Meeting is running right now and you are invited to join and follow the discussion/ > > Regards > > German Valdez > NRO > > > > Thursday, January 8, 2015 > 12:47 pm | UTC | 1 hr > > Join WebEx meeting > Meeting number: 707 924 572 > Meeting password: 12345 > > Join by phone > 0800-051-3810 Call-in toll-free number (UK) > +44-203-478-5289 Call-in toll number (UK) > Access code: 707 924 572 > Toll-free calling restrictions > > _______________________________________________ > ianaxfer mailing list > ianaxfer at nro.net > https://www.nro.net/mailman/listinfo/ianaxfer -------------- next part -------------- An HTML attachment was scrubbed... URL: From nurani at netnod.se Thu Jan 8 17:27:53 2015 From: nurani at netnod.se (Nurani Nimpuno) Date: Thu, 8 Jan 2015 17:27:53 +0100 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] Internet Number Community IANA Stewardship Proposal: Final Call for Comments References: <54AEAE74.5070002@nic.ad.jp> Message-ID: <4B4EB6BB-CBA5-42FD-AD66-E1638093D83E@netnod.se> Dear colleagues, Today the Consolidated RIR IANA Stewardship Proposal (CRISP) team publishes the second draft of the Internet numbers community proposal on the transition of the IANA stewardship. This is intended as a final call for community feedback ahead of the submitting the finalised proposal to the IANA Stewardship Transition Coordination Group (ICG) on Thursday, 15 January. We understand that many in the RIPE community have a strong interest in this process, and feedback provided in this working group and elsewhere has been crucial in reaching the current draft. While there is still an opportunity to provide comments on the current text, we would also like to strongly encourage RIPE community members in favour of this proposal to express their support on this list or via the ianaxfer at nro.net mailing list. A quantifiable level of community support may be important in strengthening the Internet numbers community?s position later in the IANA stewardship transition process. As previously, the timeline for responding is quite tight, with a deadline of Monday, 12 January, for all comments. Best regards, Nurani Nimpuno on behalf of the RIPE CRISP team Begin forwarded message: > From: Izumi Okutani > Subject: [NRO-IANAXFER] Internet Number Community IANA Stewardship Proposal: Final Call for Comments > Date: 8 januari 2015 17:21:08 CET > To: "ianaxfer at nro.net" > > Dear colleagues, > > > Please find the second draft of the Internet numbers community's > response to the Request For Proposals issued by the IANA Stewardship > Coordination Group (ICG). > > This draft has been prepared by the Consolidated RIR IANA Stewardship > Proposal (CRISP) Team, with considerations of feedback received from the > global community on mailing list. > > We have incorporated the following key points in the second draft: > > - Additional description on contract details, review committee and > intellectual property rights > - Description revised on Section V. NITA Requirements and VI. > Community Process for more clarity > - No changes are made to key elements of the proposal > > The CRISP Team have considered all comments expressed on > mailing list before the deadline of 5th Jan 2015, and > would now like to make the final call for comments from the global > community on the draft proposal, before submitting to the ICG. > > Second Draft proposal: > ------------------------ > Clean Version : > > > Redline Version: > > > The deadline for providing feedback: Mon, 12 January 2015 23:59 UTC > Feedback should be sent to : mailing list > > Community Inputs Considered by the CRISP Team: > ------------------------------------------ > You can check the status of the issues raised by the community and > proposed the CRISP Team positions at: > > > > Key dates: > ----------- > Second draft to be published : 8 Jan 2015 > Second draft comments close : 12 Jan 2015, 23:59 UTC > Final proposal to be sent to ICG : 15 Jan 2015 > > How to Engage in Discussions: > ----------------------------- > All global discussions, for the CRISP team to consider as community > feedback, will be conducted at mailing list. > All the CRISP Team discussions are open to observers. > > Next Step: > ----------- > In developing the final draft based on further feedback, the CRISP > Team will ensure it has completed considerations of all substantial > issues raised by the global community, which are compiled in the > published issues list. The proposal will only incorporate issues that > the CRISP team believes have received consensus support from the > community. > > References: > ------------ > * Discussions by the CRISP Team > Details of all the CRISP team's work to date, including recordings, > minutes and agendas of all the CRISP Team teleconferences and a > public archive of the internal CRISP team mailing list, are > available at: > https://nro.net/crisp-team > > * Other links: > - The ICG request for proposals: > > > - The IANA Stewardship Transition Discussion in each RIR region: > > > - First Draft proposal (Edited version) > > > > _______________________________________________ > ianaxfer mailing list > ianaxfer at nro.net > https://www.nro.net/mailman/listinfo/ianaxfer From nurani at netnod.se Fri Jan 9 11:30:14 2015 From: nurani at netnod.se (Nurani Nimpuno) Date: Fri, 9 Jan 2015 11:30:14 +0100 Subject: [cooperation-wg] Fwd: [CRISP-TEAM] Webex information CRISP Team 10th Teleconference Friday January 9th 2015 13:00 UTC References: Message-ID: <201394E0-9318-4002-B0AB-34B1EC522D2B@netnod.se> fyi Begin forwarded message: > From: German Valdez > Subject: [CRISP-TEAM] Webex information CRISP Team 10th Teleconference Friday January 9th 2015 13:00 UTC > Date: 8 januari 2015 10:21:58 CET > To: , > > > Hi > > Please find below webex information for the CRISP Team 10th Teleconference to be held on Friday January 9th 2015 at 13:00 > > Regards > > German Valdez > NRO > > > CRISP Team 10th Teleconference > Friday, January 9, 2015 > 1:00 pm | UTC | 1 hr > > Join WebEx meeting > Meeting number: 704 117 664 > Meeting password: crispteam > > Join by phone > 0800-051-3810 Call-in toll-free number (UK) > +44-203-478-5289 Call-in toll number (UK) > Access code: 704 117 664 > Global call-in numbers | Toll-free calling restrictions > > > _______________________________________________ > CRISP mailing list > CRISP at nro.net > https://www.nro.net/mailman/listinfo/crisp -------------- next part -------------- An HTML attachment was scrubbed... URL: From nurani at netnod.se Fri Jan 9 11:31:51 2015 From: nurani at netnod.se (Nurani Nimpuno) Date: Fri, 9 Jan 2015 11:31:51 +0100 Subject: [cooperation-wg] Fwd: [CRISP-TEAM] Agenda for the 10th call References: <54AFABDA.4040308@nic.ad.jp> Message-ID: fyi Begin forwarded message: > From: Izumi Okutani > Subject: [CRISP-TEAM] Agenda for the 10th call > Date: 9 januari 2015 11:22:18 CET > To: "crisp at nro.net" > > CRISP Team, > > > This is the draft agenda for today's call, at UTC13:00 9th Jan. > > It's not a must to disucuss agenda item 6 today. > > We are receiving e-mail inputs for item 5, so hopefully not as bad as it > looks! > > I'll send this to the IANAXFER list shortly but still feel free to add > anything else. > > > ---- > 1. Agenda Review > > 2. Actions Review > a. Minutes > b. Announcements to relevant stakeholders > > 3. Confirm pending issues > a. LACNIC region chart > b. Numbering scheme in Section III > c. Possibility of reformatting Section III > d. PDF of issues list > e. CRISP Website improvements > > 4. Confirm comments received > a. Each RIR region > b. Global list > > 5. CRISP Team position per issue > a. More details of dispute resolution > b. Reflect low input in RIR processes Section VI > c. Option of having NRO as an operator > d. Change in ICANN Bylaws for global PDP > e. SLA text is a must to approve the proposal > f. No of past arbitration cases: to backup the proposal > g. How to know whether arbitration works > h. Editorial comments (Link, LACNIC region coverage) > > 6. Preparation for the final draft > a. Who will take care of which section > b. Timeline of each preparation phase > c. Time to submit to ICG > d. Updating issues list > > 7. Next Meeting > a. Reconfirm schedule of future CRISP Calls > b. Date of the 11th Call > > 8. AOB > ---- > > > Thanks, > Izumi > > _______________________________________________ > CRISP mailing list > CRISP at nro.net > https://www.nro.net/mailman/listinfo/crisp From nurani at netnod.se Fri Jan 9 18:58:56 2015 From: nurani at netnod.se (Nurani Nimpuno) Date: Fri, 9 Jan 2015 18:58:56 +0100 Subject: [cooperation-wg] Fwd: [CRISP-TEAM] CRISP Team Next Week Teleconferences References: <3CFA2071-3618-478E-A7AB-8E6686926F1D@nro.net> Message-ID: Fyi Nurani Begin forwarded message: > From: German Valdez > Date: 9 januari 2015 16:18:28 CET > To: > Cc: crisp at nro.net > Subject: [CRISP-TEAM] CRISP Team Next Week Teleconferences > > Hi > > CRISP Team agreed to hold teleconferences everyday from Monday January 12th to Thursday January 15th at 13:00 UTC > > Below is the Webex link to each of this calls. CRISP Teleconferences are open for observers. > > CRISP Team 11th Teleconference > Monday January 12th 13:00 UTC > https://ripencc.webex.com/ripencc/j.php?MTID=m4d32f787812d13e9be87b1b7894cc4a0 > > CRISP Team 12th Teleconference > Tuesday January 13th 13:00 UTC > https://ripencc.webex.com/ripencc/j.php?MTID=m2d8a95c8e162b85ecaf1a201f8f52b09 > > CRISP Team 13th Teleconference > Wednesday January 14th 13:00 UTC > https://ripencc.webex.com/ripencc/j.php?MTID=m9744d9eed680a5d820d85058dd3f6579 > > CRISP Team 14th Teleconference > Thursday January 15th 13:00 UTC > https://ripencc.webex.com/ripencc/j.php?MTID=m7dbe974c18e86ed3657559764a7db5b6 > > Kind regards > > German Valdez > NRO > > > _______________________________________________ > CRISP mailing list > CRISP at nro.net > https://www.nro.net/mailman/listinfo/crisp -------------- next part -------------- An HTML attachment was scrubbed... URL: From niall.oreilly at ucd.ie Sat Jan 10 17:20:26 2015 From: niall.oreilly at ucd.ie (Niall O'Reilly) Date: Sat, 10 Jan 2015 16:20:26 +0000 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] Internet Number Community IANA Stewardship Proposal: Final Call for Comments In-Reply-To: <4B4EB6BB-CBA5-42FD-AD66-E1638093D83E@netnod.se> References: <54AEAE74.5070002@nic.ad.jp> <4B4EB6BB-CBA5-42FD-AD66-E1638093D83E@netnod.se> Message-ID: At Thu, 8 Jan 2015 17:27:53 +0100, Nurani Nimpuno wrote: > > Dear colleagues, > > Today the Consolidated RIR IANA Stewardship Proposal (CRISP) team > publishes the second draft of the Internet numbers community > proposal on the transition of the IANA stewardship. I have reviewed the "redline" PDF version of this draft, and attach a signature covering this file, made with my PGP key (ID AE995ED9), so as to remove any doubt as to which version of the document I have reviewed. This draft of the proposal seems to me to say what is needed as input from the number-resources community to the process of transition of the contract for the IANA function, proposing - to keep operational processes undisturbed, - to transfer the contracting-party role from NTIA to the RIRs co-ordinated through the NRO, - to keep number-resource data in the public domain, and - to vest other IANA-related intellectual property in a safe place; and explaining very clearly - how the RIR processes have been developed, - how these processes work, and - how these processes have been used to prepare the current proposal. Congratulations and thanks to the CRISP Team for such a thorough job, done at a time of the year when so many of us were enjoying a break. Good job! I shall communicate a number of editorial suggestions ("nits") directly to the CRISP team. Best regards, Niall O'Reilly -------------- next part -------------- A non-text attachment was scrubbed... Name: CRISP-IANA-PROPOSAL-Draft-08012015-redline-updated.pdf.sig Type: application/octet-stream Size: 72 bytes Desc: not available URL: -------------- next part -------------- From nick at inex.ie Mon Jan 12 00:55:11 2015 From: nick at inex.ie (Nick Hilliard) Date: Sun, 11 Jan 2015 23:55:11 +0000 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] Internet Number Community IANA Stewardship Proposal: Final Call for Comments In-Reply-To: <4B4EB6BB-CBA5-42FD-AD66-E1638093D83E@netnod.se> References: <54AEAE74.5070002@nic.ad.jp> <4B4EB6BB-CBA5-42FD-AD66-E1638093D83E@netnod.se> Message-ID: <54B30D5F.4000107@inex.ie> Nurani, Thanks to all who contributed to this document. I have been following the updates over the last month and have read through the proposal; it looks like a sound basis in terms of ensuring long term stability of global Internet number resources. Particular thanks to the RIR community members who were involved in drafting the proposal. It has also been very helpful to get regular updates to the RIPE Co-operation Working Group, as it reaffirms CRISP's community-centred approach to the the IANA transfer program. A couple of questions: 1. has the IETF Trust agreed in principal to accept IPR transfer of the IANA trademark and iana.org domain? 2. Re: III.A.4.ix, the IETF Trust is not "public domain" so it may be appropriate to use a different phrase in this paragraph, e.g. "to the community via an appropriate holding mechanism as described in section III.A.2", or something along those lines. 3. which jurisdiction / governing law will be used for the proposed new IANA contract between the RIRs and ICANN? The State of California / US Federal law? or will this be left for a future discussion? 4. III.A.4.x: resolution of disputes should first use arbitration (although it may be difficult to get an appropriate arbiter), and then through the legal system. Overall, this looks like an excellent document and I fully support it. Kind regards, Nick Hilliard Chief Technical Officer http://www.inex.ie/ INEX - Internet Neutral Exchange Association Citywest Business Campus, Dublin 24 Ireland On 08/01/2015 16:27, Nurani Nimpuno wrote: > Dear colleagues, > > Today the Consolidated RIR IANA Stewardship Proposal (CRISP) team publishes the second draft of the Internet numbers community proposal on the transition of the IANA stewardship. This is intended as a final call for community feedback ahead of the submitting the finalised proposal to the IANA Stewardship Transition Coordination Group (ICG) on Thursday, 15 January. > > We understand that many in the RIPE community have a strong interest in this process, and feedback provided in this working group and elsewhere has been crucial in reaching the current draft. > > While there is still an opportunity to provide comments on the current text, we would also like to strongly encourage RIPE community members in favour of this proposal to express their support on this list or via the ianaxfer at nro.net mailing list. A quantifiable level of community support may be important in strengthening the Internet numbers community?s position later in the IANA stewardship transition process. > > As previously, the timeline for responding is quite tight, with a deadline of Monday, 12 January, for all comments. > > Best regards, > > Nurani Nimpuno > on behalf of the RIPE CRISP team > > > Begin forwarded message: > >> From: Izumi Okutani >> Subject: [NRO-IANAXFER] Internet Number Community IANA Stewardship Proposal: Final Call for Comments >> Date: 8 januari 2015 17:21:08 CET >> To: "ianaxfer at nro.net" >> >> Dear colleagues, >> >> >> Please find the second draft of the Internet numbers community's >> response to the Request For Proposals issued by the IANA Stewardship >> Coordination Group (ICG). >> >> This draft has been prepared by the Consolidated RIR IANA Stewardship >> Proposal (CRISP) Team, with considerations of feedback received from the >> global community on mailing list. >> >> We have incorporated the following key points in the second draft: >> >> - Additional description on contract details, review committee and >> intellectual property rights >> - Description revised on Section V. NITA Requirements and VI. >> Community Process for more clarity >> - No changes are made to key elements of the proposal >> >> The CRISP Team have considered all comments expressed on >> mailing list before the deadline of 5th Jan 2015, and >> would now like to make the final call for comments from the global >> community on the draft proposal, before submitting to the ICG. >> >> Second Draft proposal: >> ------------------------ >> Clean Version : >> >> >> Redline Version: >> >> >> The deadline for providing feedback: Mon, 12 January 2015 23:59 UTC >> Feedback should be sent to : mailing list >> >> Community Inputs Considered by the CRISP Team: >> ------------------------------------------ >> You can check the status of the issues raised by the community and >> proposed the CRISP Team positions at: >> >> >> >> Key dates: >> ----------- >> Second draft to be published : 8 Jan 2015 >> Second draft comments close : 12 Jan 2015, 23:59 UTC >> Final proposal to be sent to ICG : 15 Jan 2015 >> >> How to Engage in Discussions: >> ----------------------------- >> All global discussions, for the CRISP team to consider as community >> feedback, will be conducted at mailing list. >> All the CRISP Team discussions are open to observers. >> >> Next Step: >> ----------- >> In developing the final draft based on further feedback, the CRISP >> Team will ensure it has completed considerations of all substantial >> issues raised by the global community, which are compiled in the >> published issues list. The proposal will only incorporate issues that >> the CRISP team believes have received consensus support from the >> community. >> >> References: >> ------------ >> * Discussions by the CRISP Team >> Details of all the CRISP team's work to date, including recordings, >> minutes and agendas of all the CRISP Team teleconferences and a >> public archive of the internal CRISP team mailing list, are >> available at: >> https://nro.net/crisp-team >> >> * Other links: >> - The ICG request for proposals: >> >> >> - The IANA Stewardship Transition Discussion in each RIR region: >> >> >> - First Draft proposal (Edited version) >> >> >> >> _______________________________________________ >> ianaxfer mailing list >> ianaxfer at nro.net >> https://www.nro.net/mailman/listinfo/ianaxfer > > > From rhill at hill-a.ch Mon Jan 12 10:45:52 2015 From: rhill at hill-a.ch (Richard Hill) Date: Mon, 12 Jan 2015 10:45:52 +0100 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] Internet Number Community IANA Stewardship Proposal: Final Call for Comments In-Reply-To: <54B30D5F.4000107@inex.ie> Message-ID: Please see below. > -----Original Message----- > From: cooperation-wg [mailto:cooperation-wg-bounces at ripe.net]On Behalf > Of Nick Hilliard > Sent: lundi, 12. janvier 2015 00:55 > To: Nurani Nimpuno; RIPE Cooperation Working Group > Subject: Re: [cooperation-wg] Fwd: [NRO-IANAXFER] Internet Number > Community IANA Stewardship Proposal: Final Call for Comments > > SNIP > > 4. III.A.4.x: resolution of disputes should first use arbitration > (although > it may be difficult to get an appropriate arbiter), and then through the > legal system. Arbitration is an alternative to national courts. That is, if an arbitration clause is included, then the dispute will not go through the regular court system (unless the validity of the arbitation is challenged, or there are issues enforcing the arbitration award). Best, Richard > > Overall, this looks like an excellent document and I fully support it. > > > Kind regards, > Nick Hilliard > Chief Technical Officer > > http://www.inex.ie/ > INEX - Internet Neutral Exchange Association > Citywest Business Campus, > Dublin 24 > Ireland > > On 08/01/2015 16:27, Nurani Nimpuno wrote: > > Dear colleagues, > > > > Today the Consolidated RIR IANA Stewardship Proposal (CRISP) > team publishes the second draft of the Internet numbers community > proposal on the transition of the IANA stewardship. This is > intended as a final call for community feedback ahead of the > submitting the finalised proposal to the IANA Stewardship > Transition Coordination Group (ICG) on Thursday, 15 January. > > > > We understand that many in the RIPE community have a strong > interest in this process, and feedback provided in this working > group and elsewhere has been crucial in reaching the current draft. > > > > While there is still an opportunity to provide comments on the > current text, we would also like to strongly encourage RIPE > community members in favour of this proposal to express their > support on this list or via the ianaxfer at nro.net mailing list. A > quantifiable level of community support may be important in > strengthening the Internet numbers community?s position later in > the IANA stewardship transition process. > > > > As previously, the timeline for responding is quite tight, with > a deadline of Monday, 12 January, for all comments. > > > > Best regards, > > > > Nurani Nimpuno > > on behalf of the RIPE CRISP team > > > > > > Begin forwarded message: > > > >> From: Izumi Okutani > >> Subject: [NRO-IANAXFER] Internet Number Community IANA > Stewardship Proposal: Final Call for Comments > >> Date: 8 januari 2015 17:21:08 CET > >> To: "ianaxfer at nro.net" > >> > >> Dear colleagues, > >> > >> > >> Please find the second draft of the Internet numbers community's > >> response to the Request For Proposals issued by the IANA Stewardship > >> Coordination Group (ICG). > >> > >> This draft has been prepared by the Consolidated RIR IANA Stewardship > >> Proposal (CRISP) Team, with considerations of feedback > received from the > >> global community on mailing list. > >> > >> We have incorporated the following key points in the second draft: > >> > >> - Additional description on contract details, review committee and > >> intellectual property rights > >> - Description revised on Section V. NITA Requirements and VI. > >> Community Process for more clarity > >> - No changes are made to key elements of the proposal > >> > >> The CRISP Team have considered all comments expressed on > >> mailing list before the deadline of 5th Jan > 2015, and > >> would now like to make the final call for comments from the global > >> community on the draft proposal, before submitting to the ICG. > >> > >> Second Draft proposal: > >> ------------------------ > >> Clean Version : > >> > >> > >> Redline Version: > >> > >> > >> The deadline for providing feedback: Mon, 12 January 2015 23:59 UTC > >> Feedback should be sent to : mailing list > >> > >> Community Inputs Considered by the CRISP Team: > >> ------------------------------------------ > >> You can check the status of the issues raised by the community and > >> proposed the CRISP Team positions at: > >> > >> > >> > >> Key dates: > >> ----------- > >> Second draft to be published : 8 Jan 2015 > >> Second draft comments close : 12 Jan 2015, 23:59 UTC > >> Final proposal to be sent to ICG : 15 Jan 2015 > >> > >> How to Engage in Discussions: > >> ----------------------------- > >> All global discussions, for the CRISP team to consider as community > >> feedback, will be conducted at mailing list. > >> All the CRISP Team discussions are open to observers. > >> > >> Next Step: > >> ----------- > >> In developing the final draft based on further feedback, the CRISP > >> Team will ensure it has completed considerations of all substantial > >> issues raised by the global community, which are compiled in the > >> published issues list. The proposal will only incorporate issues that > >> the CRISP team believes have received consensus support from the > >> community. > >> > >> References: > >> ------------ > >> * Discussions by the CRISP Team > >> Details of all the CRISP team's work to date, including recordings, > >> minutes and agendas of all the CRISP Team teleconferences and a > >> public archive of the internal CRISP team mailing list, are > >> available at: > >> https://nro.net/crisp-team > >> > >> * Other links: > >> - The ICG request for proposals: > >> > >> > >> - The IANA Stewardship Transition Discussion in each RIR region: > >> > >> > >> - First Draft proposal (Edited version) > >> > >> > >> > >> _______________________________________________ > >> ianaxfer mailing list > >> ianaxfer at nro.net > >> https://www.nro.net/mailman/listinfo/ianaxfer > > > > > > > > > > From maria at sunet.se Mon Jan 12 19:49:51 2015 From: maria at sunet.se (=?utf-8?Q?Maria_H=C3=A4ll?=) Date: Mon, 12 Jan 2015 19:49:51 +0100 Subject: [cooperation-wg] Second draft of the Internet numbers community proposal on the transition of the IANA stewardship. Message-ID: Dear all The Consolidated RIR IANA Stewardship Proposal (CRISP) team have published the second draft of the Internet numbers community proposal on the transition of the IANA stewardship. I strongly support this draft proposal, as an important step to strengthen the Internet numbers community?s position further on in this process. Thx to the CRISP team for all your work! _________________________________ Best regards, Maria H?ll (speaking only as myself) Co-chair Coop WG / CEO SUNET - Swedish University Network From nurani at netnod.se Tue Jan 13 08:17:31 2015 From: nurani at netnod.se (Nurani Nimpuno) Date: Tue, 13 Jan 2015 08:17:31 +0100 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] Final call for comments closed Re: Internet Number Community IANA Stewardship Proposal: Final Call for Comments References: <54B483D1.9060206@nic.ad.jp> Message-ID: <160C88E2-F35E-4428-9845-0B8616EA3CEA@netnod.se> Dear Colleagues, Thank you all for your valuable input on the CRISP draft proposal. Please see the mail below from the CRISP Chair Izumi Okutani about the next steps in incorporating the input received and developing the final version to be submitted to the ICG. Kind regards, Nurani On behalf of the CRISP RIPE team Begin forwarded message: > From: Izumi Okutani > Subject: [NRO-IANAXFER] Final call for comments closed Re: Internet Number Community IANA Stewardship Proposal: Final Call for Comments > Date: 13 januari 2015 03:32:49 CET > To: "ianaxfer at nro.net" > > Dear Colleagues, > > > Thank you for all the inputs you have given to the second draft of our > proposal. > > > The CRISP Team now has moved into developing our proposal to be > submitted to the ICG on 15th Jan based on the comments received before > 12 Jan 2015, 23:59 UTC. > > > > Best Regards, > Izumi Okutani > The CRISP Team > > On 2015/01/13 2:57, Izumi Okutani wrote: >> Dear Colleagues, >> >> >> This is a reminder that the CRISP Team will close to receive all >> comments for the second draft of our proposal as of : >> >>> Second draft comments close : 12 Jan 2015, 23:59 UTC >> >> >> Please send in all your comments before the above time, for the CRISP >> Team to consider your input in developing the final proopsal to be >> submitted to the ICG. >> >> >> Thank you to those who have expressed and shared your comments on this >> list already. >> >> >> Best Regards, >> Izumi Okutani >> The CRISP Team >> >> >> On 2015/01/09 1:21, Izumi Okutani wrote: >>> Dear colleagues, >>> >>> >>> Please find the second draft of the Internet numbers community's >>> response to the Request For Proposals issued by the IANA Stewardship >>> Coordination Group (ICG). >>> >>> This draft has been prepared by the Consolidated RIR IANA Stewardship >>> Proposal (CRISP) Team, with considerations of feedback received from the >>> global community on mailing list. >>> >>> We have incorporated the following key points in the second draft: >>> >>> - Additional description on contract details, review committee and >>> intellectual property rights >>> - Description revised on Section V. NITA Requirements and VI. >>> Community Process for more clarity >>> - No changes are made to key elements of the proposal >>> >>> The CRISP Team have considered all comments expressed on >>> mailing list before the deadline of 5th Jan 2015, and >>> would now like to make the final call for comments from the global >>> community on the draft proposal, before submitting to the ICG. >>> >>> Second Draft proposal: >>> ------------------------ >>> Clean Version : >>> >>> >>> Redline Version: >>> >>> >>> The deadline for providing feedback: Mon, 12 January 2015 23:59 UTC >>> Feedback should be sent to : mailing list >>> >>> Community Inputs Considered by the CRISP Team: >>> ------------------------------------------ >>> You can check the status of the issues raised by the community and >>> proposed the CRISP Team positions at: >>> >>> >>> >>> Key dates: >>> ----------- >>> Second draft to be published : 8 Jan 2015 >>> Second draft comments close : 12 Jan 2015, 23:59 UTC >>> Final proposal to be sent to ICG : 15 Jan 2015 >>> >>> How to Engage in Discussions: >>> ----------------------------- >>> All global discussions, for the CRISP team to consider as community >>> feedback, will be conducted at mailing list. >>> All the CRISP Team discussions are open to observers. >>> >>> Next Step: >>> ----------- >>> In developing the final draft based on further feedback, the CRISP >>> Team will ensure it has completed considerations of all substantial >>> issues raised by the global community, which are compiled in the >>> published issues list. The proposal will only incorporate issues that >>> the CRISP team believes have received consensus support from the >>> community. >>> >>> References: >>> ------------ >>> * Discussions by the CRISP Team >>> Details of all the CRISP team's work to date, including recordings, >>> minutes and agendas of all the CRISP Team teleconferences and a >>> public archive of the internal CRISP team mailing list, are >>> available at: >>> https://nro.net/crisp-team >>> >>> * Other links: >>> - The ICG request for proposals: >>> >>> >>> - The IANA Stewardship Transition Discussion in each RIR region: >>> >>> >>> - First Draft proposal (Edited version) >>> >>> >> > > > _______________________________________________ > ianaxfer mailing list > ianaxfer at nro.net > https://www.nro.net/mailman/listinfo/ianaxfer From izumi at nic.ad.jp Tue Jan 13 10:42:50 2015 From: izumi at nic.ad.jp (Izumi Okutani) Date: Tue, 13 Jan 2015 18:42:50 +0900 Subject: [cooperation-wg] [NRO-IANAXFER] Second draft of the Internet numbers community proposal on the transition of the IANA stewardship. In-Reply-To: References: Message-ID: <54B4E89A.1000003@nic.ad.jp> Dear Maria, Thank you for expressing explicit and strong support for the second version of the of the Internet numbers community proposal on the transition of the IANA stewardship. While I note you are speaking only as yourself, I appreciate all the inputs received from the colleagues in the RIPE region to the IANAXFER mailing list. Best Regards, Izumi Okutani The CRISP Team On 2015/01/13 3:49, Maria H?ll wrote: > Dear all > > The Consolidated RIR IANA Stewardship Proposal (CRISP) team have published the second draft of the Internet numbers community proposal on the transition of the IANA stewardship. > > I strongly support this draft proposal, as an important step to strengthen the Internet numbers community???s position further on in this process. > > Thx to the CRISP team for all your work! > > > _________________________________ > Best regards, > > Maria H??ll (speaking only as myself) > Co-chair Coop WG / CEO SUNET - Swedish University Network > > > > _______________________________________________ > ianaxfer mailing list > ianaxfer at nro.net > https://www.nro.net/mailman/listinfo/ianaxfer > From nurani at netnod.se Tue Jan 13 13:27:34 2015 From: nurani at netnod.se (Nurani Nimpuno) Date: Tue, 13 Jan 2015 13:27:34 +0100 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] Draft agenda for 12th CRISP Team Telelconference Re: CRISP Team Next Week Teleconferences References: <54B50AB8.9020001@nic.ad.jp> Message-ID: <4B4DD2DE-F48A-41F1-A15D-F2F7EFDB3FB9@netnod.se> fyi Begin forwarded message: > From: Izumi Okutani > Subject: [NRO-IANAXFER] Draft agenda for 12th CRISP Team Telelconference Re: CRISP Team Next Week Teleconferences > Date: 13 januari 2015 13:08:24 CET > To: ianaxfer at nro.net > > Dear Colleagues, > > > Please find below the draft agenda for coming 12th CRISP Team > Teleconference at UTC13:00 13th Jan. > > As in all CRISP Team calls, it is open to observers. > > > --- > 1. Agenda Review > > 2. Actions Review > a. Minutes > b. NRO CRISP Website improvement > c. HTML and text versions > d. Metadata in docx file > > 3. Confirm discussions status > a. each RIR region > b. global list > > 4. Editorial suggestions > a. Confirm status > b. Paul Wilson's suggested changes > c. Timeline to work > > 5. Confirm status of editorial suggestions > a. Community review SLA > b. Review Committee > c. Contract Fee > > 6. CRISP Team positions per issue > a. Continue discussions in RIR meetings > b. Consistence in IPR description > IIIA2 and IIIA3iii > c. Comment from Pindar Wong > d. Further input about cost > > 7. Timeline and how we work for the final submission > a. Schedule > b. Who does what > > 8. Next Meeting > > 9. AOB > --- > > > On 2015/01/10 0:18, German Valdez wrote: >> Hi >> >> CRISP Team agreed to hold teleconferences everyday from Monday January 12th to Thursday January 15th at 13:00 UTC >> >> Below is the Webex link to each of this calls. CRISP Teleconferences are open for observers. >> >> CRISP Team 11th Teleconference >> Monday January 12th 13:00 UTC >> https://ripencc.webex.com/ripencc/j.php?MTID=m4d32f787812d13e9be87b1b7894cc4a0 >> >> CRISP Team 12th Teleconference >> Tuesday January 13th 13:00 UTC >> https://ripencc.webex.com/ripencc/j.php?MTID=m2d8a95c8e162b85ecaf1a201f8f52b09 >> >> CRISP Team 13th Teleconference >> Wednesday January 14th 13:00 UTC >> https://ripencc.webex.com/ripencc/j.php?MTID=m9744d9eed680a5d820d85058dd3f6579 >> >> CRISP Team 14th Teleconference >> Thursday January 15th 13:00 UTC >> https://ripencc.webex.com/ripencc/j.php?MTID=m7dbe974c18e86ed3657559764a7db5b6 >> >> Kind regards >> >> German Valdez >> NRO >> >> >> >> >> >> _______________________________________________ >> ianaxfer mailing list >> ianaxfer at nro.net >> https://www.nro.net/mailman/listinfo/ianaxfer >> > > > _______________________________________________ > ianaxfer mailing list > ianaxfer at nro.net > https://www.nro.net/mailman/listinfo/ianaxfer From nurani at netnod.se Wed Jan 14 12:09:22 2015 From: nurani at netnod.se (Nurani Nimpuno) Date: Wed, 14 Jan 2015 12:09:22 +0100 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] Draf Agenda for CRISP Team 13th Teleconference Re: CRISP Team Next Week Teleconferences References: <54B64DBF.4060001@nic.ad.jp> Message-ID: <9D4D99A6-0E0A-464F-BEE9-7F7D365FD9DD@netnod.se> FYI Nurani Begin forwarded message: > From: Izumi Okutani > Subject: [NRO-IANAXFER] Draf Agenda for CRISP Team 13th Teleconference Re: CRISP Team Next Week Teleconferences > Date: 14 januari 2015 12:06:39 CET > To: "ianaxfer at nro.net" > > Dear Colleagues, > > Please find below the draft agenda for coming 13th CRISP Team > Teleconference at UTC13:00 14th Jan. > > As in all CRISP Team calls, it is open to observers. > >> CRISP Team 13th Teleconference >> Wednesday January 14th 13:00 UTC >> > https://ripencc.webex.com/ripencc/j.php?MTID=m9744d9eed680a5d820d85058dd3f6579 > > > --- > 1. Agenda Review > > 2. Actions Review > a. Minutes > b. NRO CRISP Website improvement > > 3. Confirm texts to be incorporated > a. Suggested edits > b. Consulting the community about SLA > c. Review Committee selection > d. Contract Fee > e. Move description of RIRs, NRO, NRO EC > f. reconfirm numbering scheme > g. II.B.3.i. NTIA > h. IIIA3 SLA > i. I.D. > j. VI. description of APNIC region process > > 4. What to revert back > > 5.Agree on a common term > a. Internet number community > b. the IANA Number Services Operator > c. singular/plural > > 6. Confirm Timeline > > 7. Next Meeting > > 8. AOB > > --- > > Best Regards, > Izumi Okutani > The CRISP Team > > > On 2015/01/10 0:18, German Valdez wrote: >> Hi >> >> CRISP Team agreed to hold teleconferences everyday from Monday January 12th to Thursday January 15th at 13:00 UTC >> >> Below is the Webex link to each of this calls. CRISP Teleconferences are open for observers. >> >> CRISP Team 11th Teleconference >> Monday January 12th 13:00 UTC >> https://ripencc.webex.com/ripencc/j.php?MTID=m4d32f787812d13e9be87b1b7894cc4a0 >> >> CRISP Team 12th Teleconference >> Tuesday January 13th 13:00 UTC >> https://ripencc.webex.com/ripencc/j.php?MTID=m2d8a95c8e162b85ecaf1a201f8f52b09 >> >> CRISP Team 13th Teleconference >> Wednesday January 14th 13:00 UTC >> https://ripencc.webex.com/ripencc/j.php?MTID=m9744d9eed680a5d820d85058dd3f6579 >> >> CRISP Team 14th Teleconference >> Thursday January 15th 13:00 UTC >> https://ripencc.webex.com/ripencc/j.php?MTID=m7dbe974c18e86ed3657559764a7db5b6 >> >> Kind regards >> >> German Valdez >> NRO >> >> >> >> >> >> _______________________________________________ >> CRISP mailing list >> CRISP at nro.net >> https://www.nro.net/mailman/listinfo/crisp >> > > > _______________________________________________ > ianaxfer mailing list > ianaxfer at nro.net > https://www.nro.net/mailman/listinfo/ianaxfer From nurani at netnod.se Thu Jan 15 13:47:27 2015 From: nurani at netnod.se (Nurani Nimpuno) Date: Thu, 15 Jan 2015 13:47:27 +0100 Subject: [cooperation-wg] Fwd: [CRISP-TEAM] Draft Agenda for 14th CRISP TeamTeleconference References: <54B7B6BD.8010208@nic.ad.jp> Message-ID: <3C1568F7-C347-466C-A632-E147E99594BF@netnod.se> FYI Begin forwarded message: > From: Izumi Okutani > Subject: [CRISP-TEAM] Draft Agenda for 14th CRISP TeamTeleconference > Date: 15 januari 2015 13:46:53 CET > To: "ianaxfer at nro.net" , "crisp at nro.net" > > Dear Colleagues, > > Please find below the draft agenda for coming 14th CRISP Team > Teleconference at UTC13:00 15th Jan. > > CRISP Team 14th Teleconference > Thursday January 15th 13:00 UTC > https://ripencc.webex.com/ripencc/j.php?MTID=m7dbe974c18e86ed3657559764a7db5b6 > > > As in all CRISP Team calls, it is open to observers. > > --- > 1. Agenda Review > > 2. Actions Reivew > a. Minutes > b. Header of the proposal > > 3, Summary of the comments status > > 4. Outstanding issues > > 5. Definitions > > 6. Announcement > > 7. Cover Letter > > 8. Issues list > > 9. Next Steps > a. Reconfirm the pen > b. Reconfirm Timeline > > 10. AOB > --- > > > > > > _______________________________________________ > CRISP mailing list > CRISP at nro.net > https://www.nro.net/mailman/listinfo/crisp From nurani at netnod.se Fri Jan 16 00:28:28 2015 From: nurani at netnod.se (Nurani Nimpuno) Date: Fri, 16 Jan 2015 00:28:28 +0100 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] Response to the IANA Stewardship Transition Coordination Group Request for Proposals on the IANA from the Internet Number Community References: <54B84CA2.9040207@nic.ad.jp> Message-ID: <4A7DA75E-7B55-476C-8524-F73C4013C727@netnod.se> Dear Colleagues, Please find below the Internet numbers community's response to the RFP issued by the IANA Stewardship Coordination Group (ICG), submitted by the Consolidated RIR IANA Stewardship Proposal (CRISP) Team. As the CRISP Chair Izumi Okutani notes, we have observed several explicit expressions of support for our proposal, and we believe that there was consensus from the Internet numbers community on the CRISP proposal. We would like to thank everyone in the RIPE community who has contributed with input and guidance in this process. Kind regards, Nurani Nimpuno on behalf of the CRISP RIPE team (Paul Rendek, Andrei Robachevsky & Nurani Nimpuno) Begin forwarded message: > From: Izumi Okutani > Subject: [NRO-IANAXFER] Response to the IANA Stewardship Transition Coordination Group Request for Proposals on the IANA from the Internet Number Community > Date: 16 januari 2015 00:26:26 CET > To: icg-proposal at icann.org > Cc: "ianaxfer at nro.net" > > Dear Alissa Cooper and the ICG members, > > > On behalf of the Consolidated RIR IANA Stewardship Proposal Team (CRISP > Team), I respectfully submit the attached response to the IANA > Stewardship Transition Coordination Group Request for Proposals on the > IANA from the Internet Number Community. > > > Best Regards, > Izumi Okutani > Chair, CRISP Team -------------- next part -------------- A non-text attachment was scrubbed... Name: CRISP ICG Cover Letter 15012015.pdf Type: application/pdf Size: 27124 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ICG RFP Number Resource Proposal.pdf Type: application/pdf Size: 272774 bytes Desc: not available URL: -------------- next part -------------- > _______________________________________________ > ianaxfer mailing list > ianaxfer at nro.net > https://www.nro.net/mailman/listinfo/ianaxfer From paf at frobbit.se Fri Jan 16 13:16:40 2015 From: paf at frobbit.se (=?utf-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?=) Date: Fri, 16 Jan 2015 07:16:40 -0500 Subject: [cooperation-wg] Fwd: [NRO-IANAXFER] Response to the IANA Stewardship Transition Coordination Group Request for Proposals on the IANA from the Internet Number Community In-Reply-To: <4A7DA75E-7B55-476C-8524-F73C4013C727@netnod.se> References: <54B84CA2.9040207@nic.ad.jp> <4A7DA75E-7B55-476C-8524-F73C4013C727@netnod.se> Message-ID: <1FFD86E5-07FE-4056-A339-8F267CB527FF@frobbit.se> Nurani, Paul, Andrei, My warmest congratulations for the hard work you have put in. Very well done! Patrik > On 15 jan 2015, at 18:28, Nurani Nimpuno wrote: > > Dear Colleagues, > > Please find below the Internet numbers community's response to the RFP issued by the IANA Stewardship Coordination Group (ICG), submitted by the Consolidated RIR IANA Stewardship Proposal (CRISP) Team. > > As the CRISP Chair Izumi Okutani notes, we have observed several explicit expressions of support for our proposal, and we believe that there was consensus from the Internet numbers community on the CRISP proposal. > > We would like to thank everyone in the RIPE community who has contributed with input and guidance in this process. > > Kind regards, > > Nurani Nimpuno > on behalf of the CRISP RIPE team (Paul Rendek, Andrei Robachevsky & Nurani Nimpuno) > > Begin forwarded message: > >> From: Izumi Okutani >> Subject: [NRO-IANAXFER] Response to the IANA Stewardship Transition Coordination Group Request for Proposals on the IANA from the Internet Number Community >> Date: 16 januari 2015 00:26:26 CET >> To: icg-proposal at icann.org >> Cc: "ianaxfer at nro.net" >> >> Dear Alissa Cooper and the ICG members, >> >> >> On behalf of the Consolidated RIR IANA Stewardship Proposal Team (CRISP >> Team), I respectfully submit the attached response to the IANA >> Stewardship Transition Coordination Group Request for Proposals on the >> IANA from the Internet Number Community. >> >> >> Best Regards, >> Izumi Okutani >> Chair, CRISP Team > >> _______________________________________________ >> ianaxfer mailing list >> ianaxfer at nro.net >> https://www.nro.net/mailman/listinfo/ianaxfer -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: Message signed with OpenPGP using GPGMail URL: From chrisb at ripe.net Wed Jan 21 10:36:51 2015 From: chrisb at ripe.net (Chris Buckridge) Date: Wed, 21 Jan 2015 10:36:51 +0100 Subject: [cooperation-wg] ICG Update on Circle ID Message-ID: <6CD07768-3085-4220-B601-AD4A66CC7878@ripe.net> Hi all, After the flurry of recent activity on this list regarding the CRISP team?s work on a numbers community proposal to the IANA Stewardship Transition Coordination Group (ICG), things have been comparatively quiet over the last few days. But the IANA stewardship transition process is far from over - ICG Chair, Alissa Cooper, has posted an article discussing the global process so far and the next steps for the ICG. It makes for a good summary of events so far and preview of what to expect over the coming months: http://www.circleid.com/posts/20150120_iana_transition_planning_proceeding_in_fine_internet_style/ In addition, the RIPE NCC has posted an short video on the RIR community and CRISP processes to date and a high-level preview of next steps: https://www.youtube.com/watch?v=ihB4ZyDvFwM Hopefully both of these will help inform the RIPE community?s continuing participation in the IANA stewardship transition process. Best regards, Chris ? Chris Buckridge Senior External Relations Officer RIPE NCC -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2608 bytes Desc: not available URL: From chrisb at ripe.net Mon Jan 26 11:01:29 2015 From: chrisb at ripe.net (Chris Buckridge) Date: Mon, 26 Jan 2015 11:01:29 +0100 Subject: [cooperation-wg] Contribute to the EuroDIG 2015 Planning Meeting Message-ID: <9328C0AE-E6B5-4B55-8EFD-214B94799AF0@ripe.net> Dear colleagues, On Tuesday, 27 January (tomorrow), EuroDIG, the European Dialogue on Internet Governance, will hold an open planning meeting in Sofia, Bulgaria, for the annual EuroDIG meeting, which will also be held in Sofia in June: www.eurodig.org/get-involved/planning-meeting/ The planning meeting is open to the public, with remote participation options available. Participants will consider themes and topics for inclusion on the EuroDIG agenda, based on the submissions received during last year?s open call. This is an important opportunity to help shape the European Internet governance discussion and ensure that issues of importance to the RIPE community are included on the agenda. A few thoughts on how to participate: - As noted above, there will be remote participation available, allowing you to follow all discussions in real time via Webex: https://intgovforum.webex.com/intgovforum/j.php?MTID=m0928b71d1e86068d0d651e1d65e87bb0 - RIPE NCC staff and other participants will be tweeting throughout the day, noting any important developments or topics - you can follow via the #EuroDIG hashtag, and RIPE NCC staff will be monitoring tweets with this hashtag, so you can contribute to the discussion in this way. - A report on outcomes from this meeting will be sent to the Cooperation Working Group mailing list, and further discussion here is welcome. The RIPE NCC is an institutional partner of EuroDIG and is pleased to be contributing to the planning and coordination of the upcoming EuroDIG 2015 event. Best regards, Chris Buckridge Senior External Relations Officer RIPE NCC -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2608 bytes Desc: not available URL: