< draft-ietf-ianaplan-icg-response-03.txt   draft-ietf-ianaplan-icg-response-04.txt >
IANAPLAN E. Lear, Ed. IANAPLAN E. Lear, Ed.
Internet-Draft R. Housley, Ed. Internet-Draft R. Housley, Ed.
Intended status: Informational November 14, 2014 Intended status: Informational November 21, 2014
Expires: May 18, 2015 Expires: May 25, 2015
Draft Response to the Internet Coordination Group Request for Proposals Draft Response to the Internet Coordination Group Request for Proposals
on the IANA protocol parameters registries on the IANA protocol parameters registries
draft-ietf-ianaplan-icg-response-03 draft-ietf-ianaplan-icg-response-04
Abstract Abstract
This document contains the a response to a request for proposals from This document contains the a response to a request for proposals from
the IANA Stewardship Transition Coordination Group regarding the the IANA Stewardship Transition Coordination Group regarding the
protocol parameters registries. It is meant to be included in an protocol parameters registries. It is meant to be included in an
aggregate proposal that also includes contributions covering domain aggregate proposal that also includes contributions covering domain
names and numbering resources that will be submitted from their names and numbering resources that will be submitted from their
respective operational communities. The IETF community is invited to respective operational communities. The IETF community is invited to
comment and propose changes to this document. comment and propose changes to this document.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 18, 2015. This Internet-Draft will expire on May 25, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 18 skipping to change at page 2, line 18
Table of Contents Table of Contents
1. IETF Introduction . . . . . . . . . . . . . . . . . . . . . . 2 1. IETF Introduction . . . . . . . . . . . . . . . . . . . . . . 2
2. The Formal RFP Response . . . . . . . . . . . . . . . . . . . 3 2. The Formal RFP Response . . . . . . . . . . . . . . . . . . . 3
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
4. Security Considerations . . . . . . . . . . . . . . . . . . . 17 4. Security Considerations . . . . . . . . . . . . . . . . . . . 17
5. IAB Note . . . . . . . . . . . . . . . . . . . . . . . . . . 17 5. IAB Note . . . . . . . . . . . . . . . . . . . . . . . . . . 17
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 17 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 17
7. Informative References . . . . . . . . . . . . . . . . . . . 17 7. Informative References . . . . . . . . . . . . . . . . . . . 17
Appendix A. Changes . . . . . . . . . . . . . . . . . . . . . . 19 Appendix A. Changes . . . . . . . . . . . . . . . . . . . . . . 19
A.1. Changes from -02 to -03 . . . . . . . . . . . . . . . . . 19 A.1. Changes from -03 to -04 . . . . . . . . . . . . . . . . . 19
A.2. Changes from -01 to -02 . . . . . . . . . . . . . . . . . 20 A.2. Changes from -02 to -03 . . . . . . . . . . . . . . . . . 20
A.3. Changes from -00 to -01 . . . . . . . . . . . . . . . . . 20 A.3. Changes from -01 to -02 . . . . . . . . . . . . . . . . . 20
A.4. Changes from -00 to -01 . . . . . . . . . . . . . . . . . 20
Appendix B. The Charter of the IANA Stewardship Coordination Appendix B. The Charter of the IANA Stewardship Coordination
Group (ICG . . . . . . . . . . . . . . . . . . . . . 20 Group (ICG . . . . . . . . . . . . . . . . . . . . . 21
Appendix C. IANA Stewardship Transition Coordination Group Appendix C. IANA Stewardship Transition Coordination Group
Request for Proposals . . . . . . . . . . . . . . . 23 Request for Proposals . . . . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29
1. IETF Introduction 1. IETF Introduction
In March of 2014 the U.S. National Telecommunications & Information In March of 2014 the U.S. National Telecommunications & Information
Administration (NTIA) announced its intent to transition oversight of Administration (NTIA) announced its intent to transition oversight of
Internet Assigned Numbers Authority (IANA) functions. In that Internet Assigned Numbers Authority (IANA) functions. In that
announcement, NTIA asked the Internet Corporation for Assigned Names announcement, NTIA asked the Internet Corporation for Assigned Names
and Numbers (ICANN) to establish a process to deliver a proposal for and Numbers (ICANN) to establish a process to deliver a proposal for
transition. As part of that process, the IANA Stewardship Transition transition. As part of that process, the IANA Stewardship Transition
skipping to change at page 11, line 39 skipping to change at page 11, line 39
involvement from the NTIA. Therefore, no new organizaitons or involvement from the NTIA. Therefore, no new organizaitons or
structures are needed. structures are needed.
IANA protocol parameters registry updates will continue to function IANA protocol parameters registry updates will continue to function
day-to-day, as they have been doing for the last decade or more. The day-to-day, as they have been doing for the last decade or more. The
IETF community is quite satisfied with the current arrangement with IETF community is quite satisfied with the current arrangement with
ICANN. RFC 2860 remains in force and has served the IETF community ICANN. RFC 2860 remains in force and has served the IETF community
very well. RFC 6220 has laid out an appropriate service description very well. RFC 6220 has laid out an appropriate service description
and requirements. and requirements.
The protocol parameters registries are in the public domain. It is However in the absence of the NTIA contract a few new arrangements
the preference of the IETF community that all relevant parties may be needed in order to ensure the IETF community's expectations
acknowledge that fact as part of the transition. are met. Those expectations are the following:
It is possible in the future that the operation of the protocol o The protocol parameters registries are in the public domain. It
parameters registries may be transitioned from ICANN to subsequent is the preference of the IETF community that all relevant parties
operator(s). It is the preference of the IETF community that, as acknowledge that fact as part of the transition.
part of the NTIA transition, ICANN acknowledge that it will carry out
the obligations established under C.7.3 and I.61 of the current IANA o It is possible in the future that the operation of the protocol
functions contract between ICANN and the NTIA [NTIA-Contract] to parameters registries may be transitioned from ICANN to subsequent
achieve a smooth transition to subsequent operator(s), should the operator(s). It is the preference of the IETF community that, as
need arise. Furthermore, in the event of a transition it is the part of the NTIA transition, ICANN acknowledge that it will carry
expectation of the IETF community that ICANN, the IETF, and out the obligations established under C.7.3 and I.61 of the
subsequent operator(s) will work together to minimize disruption in current IANA functions contract between ICANN and the
the use the protocol parameters registries or other resources NTIA[NTIA-Contract] to achieve a smooth transition to subsequent
currently located at iana.org. operator(s), should the need arise. Furthermore, in the event of
a transition it is the expectation of the IETF community that
ICANN, the IETF, and subsequent operator(s) will work together to
minimize disruption in the use the protocol parameters registries
or other resources currently located at iana.org.
Discussions during IETF 89 in London led to the following guiding Discussions during IETF 89 in London led to the following guiding
principles for IAB efforts that impact IANA protocol parameter principles for IAB efforts that impact IANA protocol parameter
registries. These principles must be taken together; their order is registries. These principles must be taken together; their order is
not significant. not significant.
1. The IETF protocol parameters registries function has been and 1. The IETF protocol parameters registries function has been and
continues to be capably provided by the Internet technical community. continues to be capably provided by the Internet technical community.
The strength and stability of the function and its foundation within The strength and stability of the function and its foundation within
skipping to change at page 14, line 32 skipping to change at page 14, line 38
guide IAB, IAOC, and the rest of the IETF community as they work with guide IAB, IAOC, and the rest of the IETF community as they work with
ICANN to establish future IANA performance metrics and operational ICANN to establish future IANA performance metrics and operational
procedures, as they have in the past. procedures, as they have in the past.
As no services are expected to change, no continuity issues are As no services are expected to change, no continuity issues are
anticipated, and there are no new technical or operational methods anticipated, and there are no new technical or operational methods
proposed by the IETF to test. The IETF leadership, ICANN, and the proposed by the IETF to test. The IETF leadership, ICANN, and the
RIRs maintain an ongoing informal dialog to spot any unforeseen RIRs maintain an ongoing informal dialog to spot any unforeseen
issues that might arise as a result of other changes. issues that might arise as a result of other changes.
What is necessary as part of transition is the completion of What is necessary as part of transition is the completion of any
supplemental agreement(s) discussed in the previous section of this supplemental agreement(s) necessary to achieve the requirements
RFP. outlined in our response in Section III of this RFP.
>>> >>>
>>> V. NTIA Requirements >>> V. NTIA Requirements
>>> >>>
>>> Additionally, NTIA has established that the transition proposal >>> Additionally, NTIA has established that the transition proposal
>>> must meet the following five requirements: >>> must meet the following five requirements:
>>> >>>
>>> "Support and enhance the multistakeholder model;" >>> "Support and enhance the multistakeholder model;"
>>> >>>
IETF Response: IETF Response:
Everyone is welcome to participate in IETF activities. The policies Everyone is welcome to participate in IETF activities. The policies
and procedures are outlined in the documents we named above. In- and procedures are outlined in the documents we named above. In-
person attendance is not required for participation, and many people person attendance is not required for participation, and many people
participate in email discussions that have never attended an IETF participate in email discussions that have never attended an IETF
meeting. An email account is the only requirement to participate. meeting. An email account is the only requirement to participate.
The IETF makes use of both formal and informal lines of communication The IETF makes use of both formal and informal lines of communication
to collaborate with other organizations within the multistakeholder to collaborate with other organizations within the multistakeholder
ecosystem. ecosystem.
skipping to change at page 17, line 43 skipping to change at page 17, line 46
This section to be filled in by the IAB. This section to be filled in by the IAB.
6. Acknowledgments 6. Acknowledgments
This document describes processes that have been developed by many This document describes processes that have been developed by many
members of the community over many years. The initial version of members of the community over many years. The initial version of
this document was developed collaboratively through both the IAB IANA this document was developed collaboratively through both the IAB IANA
Strategy Program and the IETF IANAPLAN WG. Particular thanks go to Strategy Program and the IETF IANAPLAN WG. Particular thanks go to
Jari Arkko, John Klensin, Andrei Robachevsky, Andrew Sullivan, Leslie Jari Arkko, John Klensin, Andrei Robachevsky, Andrew Sullivan, Leslie
Daigle, Marc Blanchet, Barry Leiba, Brian Carpenter, Greg Wood, John Daigle, Marc Blanchet, Barry Leiba, Brian Carpenter, Greg Wood, John
Curran, Milton Mueller, Alissa Cooper, Andrei Robachevsky, Miles Curran, Milton Mueller, Alissa Cooper, Andrei Robachevsky, and
Fidelman, Richard Hill, and Suzanne Woolf. Suzanne Woolf.
7. Informative References 7. Informative References
[METRICS] , "Performance Standards Metrics Report", , [METRICS] , "Performance Standards Metrics Report", ,
<http://www.iana.org/performance/metrics>. <http://www.iana.org/performance/metrics>.
[MOUSUP] , "Supplements to RFC 2860 (the Memorandum of [MOUSUP] , "Supplements to RFC 2860 (the Memorandum of
Understanding between the IETF and ICANN)", , Understanding between the IETF and ICANN)", ,
<http://iaoc.ietf.org/contracts.html>. <http://iaoc.ietf.org/contracts.html>.
skipping to change at page 19, line 46 skipping to change at page 19, line 49
[RFC7249] Housley, R., "Internet Numbers Registries", RFC 7249, May [RFC7249] Housley, R., "Internet Numbers Registries", RFC 7249, May
2014. 2014.
[RFC7282] Resnick, P., "On Consensus and Humming in the IETF", RFC [RFC7282] Resnick, P., "On Consensus and Humming in the IETF", RFC
7282, June 2014. 7282, June 2014.
Appendix A. Changes Appendix A. Changes
NOTE: This section to be removed by RFC Editor at publication. NOTE: This section to be removed by RFC Editor at publication.
A.1. Changes from -02 to -03 A.1. Changes from -03 to -04
o Additional text regarding what is needed in Section III.
o Appropriate language modifications in section IV to match the
above changes in III.
o Acknowledgments edits.
A.2. Changes from -02 to -03
o Terminology consistency. o Terminology consistency.
o Add IAB section. o Add IAB section.
o Changes based on WG discussion on what we prefer as part of the o Changes based on WG discussion on what we prefer as part of the
transition regarding IPR. transition regarding IPR.
o Add discussion about .ARPA domain. o Add discussion about .ARPA domain.
skipping to change at page 20, line 22 skipping to change at page 20, line 33
o Additional text around coordination with ICANN. o Additional text around coordination with ICANN.
o Working groups can adopt items within their charters. o Working groups can adopt items within their charters.
o IAB appointments generally last two years. o IAB appointments generally last two years.
o Add mention of the Trust. o Add mention of the Trust.
o Security Considerations update. o Security Considerations update.
A.2. Changes from -01 to -02 A.3. Changes from -01 to -02
o A better description special registries and BGP ASNs. o A better description special registries and BGP ASNs.
o Clarity on how the address space and ASNs are delegated. o Clarity on how the address space and ASNs are delegated.
o Many editorials corrected. o Many editorials corrected.
o Mention of the annual review as part of the SLAs. o Mention of the annual review as part of the SLAs.
o Change about how overlap is presented. o Change about how overlap is presented.
o A number of small wording changes based on feedback. o A number of small wording changes based on feedback.
A.3. Changes from -00 to -01 A.4. Changes from -00 to -01
o Front matter greatly reduced. o Front matter greatly reduced.
o Appendices with charter and RFP added. o Appendices with charter and RFP added.
o Jurisdiction text changed. o Jurisdiction text changed.
o Proposed changes include supplemental agreement(s) to address o Proposed changes include supplemental agreement(s) to address
jurisdiction, dispute resolution, and IPR, including names and jurisdiction, dispute resolution, and IPR, including names and
marks. marks.
 End of changes. 14 change blocks. 
33 lines changed or deleted 46 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/