< draft-ietf-ianaplan-icg-response-07.txt   draft-ietf-ianaplan-icg-response-08.txt >
IANAPLAN E. Lear, Ed. IANAPLAN E. Lear, Ed.
Internet-Draft R. Housley, Ed. Internet-Draft
Intended status: Informational December 18, 2014 Intended status: Informational R. Housley, Ed.
Expires: June 21, 2015 Expires: June 25, 2015
December 22, 2014
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-07 draft-ietf-ianaplan-icg-response-08
Abstract Abstract
The U.S. NTIA has solicited a request from ICANN to propose how the The U.S. NTIA has solicited a request from ICANN to propose how the
NTIA should end its oversight of the IANA functions. After broad NTIA should end its oversight of the IANA functions. After broad
consultations, ICANN has in turn created the IANA Stewardship consultations, ICANN has in turn created the IANA Stewardship
Transition Coordination Group. That group solicited proposals for Transition Coordination Group. That group solicited proposals for
thre three major IANA functions: names, numbers, and protocol thre three major IANA functions: names, numbers, and protocol
parameters. This document contains the IETF response to that parameters. This document contains the IETF response to that
solicitation for protocol parameters. It is meant to be included in solicitation for protocol parameters. It is meant to be included in
skipping to change at page 1, line 40 skipping to change at page 1, line 41
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 June 21, 2015. This Internet-Draft will expire on June 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 19 skipping to change at page 2, line 20
described in the Simplified BSD License. described in the Simplified BSD License.
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 . . . . . . . . . . . . . . . . . . . . . 19 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
4. Security Considerations . . . . . . . . . . . . . . . . . . . 19 4. Security Considerations . . . . . . . . . . . . . . . . . . . 19
5. IAB Note . . . . . . . . . . . . . . . . . . . . . . . . . . 19 5. IAB Note . . . . . . . . . . . . . . . . . . . . . . . . . . 19
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 19 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 19
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 20
7.1. Normative References . . . . . . . . . . . . . . . . . . 20 7.1. Normative References . . . . . . . . . . . . . . . . . . 20
7.2. Informative References . . . . . . . . . . . . . . . . . 21 7.2. Informative References . . . . . . . . . . . . . . . . . 21
Appendix A. Changes . . . . . . . . . . . . . . . . . . . . . . 22 Appendix A. Changes . . . . . . . . . . . . . . . . . . . . . . 22
A.1. Changes from -06 to -07 . . . . . . . . . . . . . . . . . 22 A.1. Changes from -07 to -08 . . . . . . . . . . . . . . . . . 22
A.2. Changes from -05 to -06 . . . . . . . . . . . . . . . . . 22 A.2. Changes from -06 to -07 . . . . . . . . . . . . . . . . . 23
A.3. Changes from -04 to -05 . . . . . . . . . . . . . . . . . 23 A.3. Changes from -05 to -06 . . . . . . . . . . . . . . . . . 23
A.4. Changes from -03 to -04 . . . . . . . . . . . . . . . . . 23 A.4. Changes from -04 to -05 . . . . . . . . . . . . . . . . . 23
A.5. Changes from -02 to -03 . . . . . . . . . . . . . . . . . 23 A.5. Changes from -03 to -04 . . . . . . . . . . . . . . . . . 23
A.6. Changes from -01 to -02 . . . . . . . . . . . . . . . . . 23 A.6. Changes from -02 to -03 . . . . . . . . . . . . . . . . . 23
A.7. Changes from -00 to -01 . . . . . . . . . . . . . . . . . 24 A.7. Changes from -01 to -02 . . . . . . . . . . . . . . . . . 24
A.8. Changes from -00 to -01 . . . . . . . . . . . . . . . . . 24
Appendix B. The Charter of the IANA Stewardship Coordination Appendix B. The Charter of the IANA Stewardship Coordination
Group (ICG . . . . . . . . . . . . . . . . . . . . . 24 Group (ICG . . . . . . . . . . . . . . . . . . . . . 24
Appendix C. IANA Stewardship Transition Coordination Group Appendix C. IANA Stewardship Transition Coordination Group
Request for Proposals . . . . . . . . . . . . . . . 27 Request for Proposals . . . . . . . . . . . . . . . 27
Appendix D. Completed ICG response for the NTIA . . . . . . . . 33 Appendix D. Completed ICG response for the NTIA . . . . . . . . 33
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33
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
skipping to change at page 3, line 18 skipping to change at page 3, line 20
introduction that is sourced solely within the IETF. Section 2 introduction that is sourced solely within the IETF. Section 2
contains the questionnaire that was written by the ICG and a formal contains the questionnaire that was written by the ICG and a formal
response by the IETF. We have quoted questions from that response by the IETF. We have quoted questions from that
questionnaire with ">>> ", and we have prefaced answers to questions questionnaire with ">>> ", and we have prefaced answers to questions
being asked with "IETF Response:". Note that there are small changes being asked with "IETF Response:". Note that there are small changes
to the questions asked in order to match the RFC format. to the questions asked in order to match the RFC format.
We note that the following text was stated as footnote in the We note that the following text was stated as footnote in the
original RFP: original RFP:
In this RFP, "IANA" refers to the functions currently In this RFP, "IANA" refers to the functions currently
specified in the agreement between NTIA and ICANN specified in the agreement between NTIA and ICANN
[http://www.ntia.doc.gov/page/iana-functions-purchase-order] as [http://www.ntia.doc.gov/page/iana-functions-purchase-order] as
well as any other functions traditionally performed by the IANA well as any other functions traditionally performed by the IANA
functions operator. SAC-067 functions operator. SAC-067
[https://www.icann.org/en/system/files/files/sac-067-en.pdf] [https://www.icann.org/en/system/files/files/sac-067-en.pdf]
provides one description of the many different meanings of the provides one description of the many different meanings of the
term "IANA" and may be useful reading in addition to the term "IANA" and may be useful reading in addition to the
documents constituting the agreement itself. documents constituting the agreement itself.
2. The Formal RFP Response 2. The Formal RFP Response
The entire Request for Proposals, including introduction, can be The entire Request for Proposals, including introduction, can be
found in Appendix C. found in Appendix C.
>>> >>>
>>> 0. Proposal Type >>> 0. Proposal Type
>>> >>>
>>> Identify which category of the IANA functions this >>> Identify which category of the IANA functions this
skipping to change at page 18, line 9 skipping to change at page 17, line 41
>>> Links to announcements, agendas, mailing lists, consultations and >>> Links to announcements, agendas, mailing lists, consultations and
>>> meeting proceedings. >>> meeting proceedings.
>>> >>>
IETF Response: IETF Response:
The following list is not exhaustive, as there have been many open The following list is not exhaustive, as there have been many open
discussions about this transition within the IETF community in the discussions about this transition within the IETF community in the
past few months. past few months.
Creation of an open mailing list to discuss the transition: http://m Creation of an open mailing list to discuss the transition:
ailarchive.ietf.org/arch/msg/ietf-announce/ http://mailarchive.ietf.org/arch/msg/ietf-announce/Ztd2ed9U04qSxI-
Ztd2ed9U04qSxI-k9-Oj80jJLXc k9-Oj80jJLXc
Announcement of a public session on the transition: http://mailarchi Announcement of a public session on the transition:
ve.ietf.org/arch/msg/ietf-announce/M5zVmFFvTbtgVyMB_fjUSW4rJ0c http://mailarchive.ietf.org/arch/msg/ietf-announce/
M5zVmFFvTbtgVyMB_fjUSW4rJ0c
Announcement by the IESG of the intent to form a working group: Announcement by the IESG of the intent to form a working group:
http://mailarchive.ietf.org/arch/msg/ietf-announce/ http://mailarchive.ietf.org/arch/msg/ietf-announce/
QsvU9qX98G2KqB18jy6UfhwKjXk QsvU9qX98G2KqB18jy6UfhwKjXk
The working group discussion http://www.ietf.org/mail-archive/web/ The working group discussion: http://www.ietf.org/mail-
ianaplan/current/maillist.html archive/web/ianaplan/current/maillist.html
2014-10-06 Interim Meeting Agenda, Minutes, and presentations 2014-10-06 Interim Meeting Agenda, Minutes, and presentations:
http://www.ietf.org/proceedings/interim/2014/10/06/ianaplan/ http://www.ietf.org/proceedings/interim/2014/10/06/ianaplan/
proceedings.html proceedings.html
Working group last call http://mailarchive.ietf.org/arch/msg/ Working group last call: http://mailarchive.ietf.org/arch/msg/ianapl
ianaplan/EGF9rfJxn5QpQnRXmS2QxYKYR8k an/EGF9rfJxn5QpQnRXmS2QxYKYR8k
Agenda from IETF 91 IANAPLAN WG meeting https://tools.ietf.org/wg/ Agenda from IETF 91 IANAPLAN WG meeting:
ianaplan/agenda http://www.ietf.org/proceedings/91/agenda/agenda-91-ianaplan
Minutes of IETF 91 IANAPLAN WG meeting https://tools.ietf.org/wg/ Minutes of IETF 91 IANAPLAN WG meeting:
ianaplan/minutes http://www.ietf.org/proceedings/91/minutes/minutes-91-ianaplan
Shepherd write-up http://datatracker.ietf.org/doc/draft-ietf- Shepherd write-up: http://datatracker.ietf.org/doc/draft-ietf-
ianaplan-icg-response/shepherdwriteup/ ianaplan-icg-response/shepherdwriteup/
IETF last call http://mailarchive.ietf.org/arch/msg/ietf-announce/ IETF last call: http://mailarchive.ietf.org/arch/msg/ietf-announce/
i5rx6PfjJCRax3Lu4qZ_38P8wBg i5rx6PfjJCRax3Lu4qZ_38P8wBg
>>> >>>
>>> An assessment of the level of consensus behind your community's >>> An assessment of the level of consensus behind your community's
>>> proposal, including a description of areas of contention or >>> proposal, including a description of areas of contention or
>>> disagreement. >>> disagreement.
>>> >>>
IETF Response: IETF Response:
This document has attained rough consensus of the IETF working group This document has attained rough consensus of the IETF Working Group
and of the IETF community as a whole, as judged by the IESG in and of the IETF community as a whole, as judged first by the chairs
accordance with [RFC2026]. Several suggestions were raised that did and then by the sponsoring Area Director, and then by the IESG in
not enjoy sufficient support to be included. Specifically: accordance with [RFC2026] during the 18 December 2014 IESG telechat.
The IESG has approved the draft, pending insertion of this answer in
this section and the IAB approval note. The IAB approved a statement
for inclusion in the document on 19 December 2014.
Over the course of the development of the document, several
suggestions were raised that did not enjoy sufficient support to be
included. Two general areas of suggestion that generated much
discussion were
o A suggestion for a stronger statement over what terms the IAOC o A suggestion for a stronger statement over what terms the IAOC
should negotiate. should negotiate.
o A suggestion that "iana.org" and other associated marks be o A suggestion that "iana.org" and other associated marks be
transferred to the IETF trust. transferred to the IETF trust.
o A suggestion that IAOC consider some form of arbitration. At the end of the working group process, although there was not
unanimous support for the results, the working group chairs concluded
that rough consensus existed in the working group. The document
shepherd's summary of the WG consensus for this document can be found
here:
At the end, three individuals in the community made clear that they https://datatracker.ietf.org/doc/draft-ietf-ianaplan-icg-response/
did not support the results, while many others did. The chairs shepherdwriteup/
concluded that rough consensus existed in the working group.
During IETF last call, additional people voiced support for the During IETF last call, additional people voiced support for the
group, and no additional people raised objections. document. There were several editorial comments that resulted in
changes, as well as some discussion of more substantial comments some
of which resulted in text changes. There was some discussion of
comments already discussed earlier in the process, and but no new
objections were raised during the IETF last call. A summary of the
last call comments can be found from here:
http://www.ietf.org/mail-archive/web/ianaplan/current/msg01477.html
New draft versions were prepared that took into account all the
agreed changes from the last call. The final version was then
approved by the IESG.
3. IANA Considerations 3. IANA Considerations
This memo is a response to a request for proposals. No parameter This memo is a response to a request for proposals. No parameter
allocations or changes are sought. allocations or changes are sought.
4. Security Considerations 4. Security Considerations
While the agreement, supplements, policies, and procedures around the While the agreement, supplements, policies, and procedures around the
IANA function have shown strong resiliency, the IETF will continue to IANA function have shown strong resiliency, the IETF will continue to
work with all relevant parties to facilitate improvements while work with all relevant parties to facilitate improvements while
maintaining availability of the IANA registries. maintaining availability of the IANA registries.
5. IAB Note 5. IAB Note
This section to be filled in by the IAB. The IAB supports the response in this document.
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, Marc Blanchet, Brian Carpenter, Alissa Cooper, John Jari Arkko, Marc Blanchet, Brian Carpenter, Alissa Cooper, John
Curran, Leslie Daigle, Heather Flanagan, Christer Holmberg, John Curran, Leslie Daigle, Heather Flanagan, Christer Holmberg, John
Klensin, Barry Leiba, Milton Mueller, Andrei Robachevsky, Andrew Klensin, Barry Leiba, Milton Mueller, Andrei Robachevsky, Andrew
skipping to change at page 20, line 4 skipping to change at page 20, line 8
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, Marc Blanchet, Brian Carpenter, Alissa Cooper, John Jari Arkko, Marc Blanchet, Brian Carpenter, Alissa Cooper, John
Curran, Leslie Daigle, Heather Flanagan, Christer Holmberg, John Curran, Leslie Daigle, Heather Flanagan, Christer Holmberg, John
Klensin, Barry Leiba, Milton Mueller, Andrei Robachevsky, Andrew Klensin, Barry Leiba, Milton Mueller, Andrei Robachevsky, Andrew
Sullivan, Dave Thaler, Greg Wood, and Suzanne Woolf. Sullivan, Dave Thaler, Greg Wood, and Suzanne Woolf.
7. References 7. References
7.1. Normative References 7.1. Normative References
[BCP9info] [BCP9info]
, "Information on "The Internet Standards Process -- "Information on "The Internet Standards Process --
Revision 3" ", , <http://www.rfc-editor.org/info/rfc2026>. Revision 3"", <http://www.rfc-editor.org/info/rfc2026>.
[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
Understanding between the IETF and ICANN)", , between the IETF and ICANN)",
<http://iaoc.ietf.org/contracts.html>. <http://iaoc.ietf.org/contracts.html>.
[NTIA-Announce] [NTIA-Announce]
, "NTIA Announcement of Intent to Transition Key Internet "NTIA Announcement of Intent to Transition Key Internet
Domain Name Functions", March 2014, <http:// Domain Name Functions", March 2014,
www.ntia.doc.gov/press-release/2014/ntia-announces-intent- <http://www.ntia.doc.gov/press-release/2014/ntia-
transition-key-internet-domain-name-functions>. announces-intent-transition-key-internet-domain-name-
functions>.
[NTIA-Contract] [NTIA-Contract]
, "The NTIA Contract with ICANN", , <http:// "The NTIA Contract with ICANN",
www.ntia.doc.gov/files/ntia/publications/ <http://www.ntia.doc.gov/files/ntia/publications/
sf_26_pg_1-2-final_award_and_sacs.pdf>. sf_26_pg_1-2-final_award_and_sacs.pdf>.
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision [RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, October 1996. 3", BCP 9, RFC 2026, October 1996.
[RFC2418] Bradner, S., "IETF Working Group Guidelines and [RFC2418] Bradner, S., "IETF Working Group Guidelines and
Procedures", BCP 25, RFC 2418, September 1998. Procedures", BCP 25, RFC 2418, September 1998.
[RFC2850] Internet Architecture Board and B. Carpenter, "Charter of [RFC2850] Internet Architecture Board and B. Carpenter, "Charter of
the Internet Architecture Board (IAB)", BCP 39, RFC 2850, the Internet Architecture Board (IAB)", BCP 39, RFC 2850,
skipping to change at page 21, line 17 skipping to change at page 21, line 24
4071, April 2005. 4071, April 2005.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
[RFC5771] Cotton, M., Vegoda, L., and D. Meyer, "IANA Guidelines for [RFC5771] Cotton, M., Vegoda, L., and D. Meyer, "IANA Guidelines for
IPv4 Multicast Address Assignments", BCP 51, RFC 5771, IPv4 Multicast Address Assignments", BCP 51, RFC 5771,
March 2010. March 2010.
[RFC6220] McPherson, D., Kolkman, O., Klensin, J., Huston, G., [RFC6220] McPherson, D., Kolkman, O., Klensin, J., Huston, G., and
Internet Architecture Board, "Defining the Role and Internet Architecture Board, "Defining the Role and
Function of IETF Protocol Parameter Registry Operators", Function of IETF Protocol Parameter Registry Operators",
RFC 6220, April 2011. RFC 6220, April 2011.
[RFC6761] Cheshire, S. and M. Krochmal, "Special-Use Domain Names", [RFC6761] Cheshire, S. and M. Krochmal, "Special-Use Domain Names",
RFC 6761, February 2013. RFC 6761, February 2013.
[RFC6890] Cotton, M., Vegoda, L., Bonica, R., and B. Haberman, [RFC6890] Cotton, M., Vegoda, L., Bonica, R., and B. Haberman,
"Special-Purpose IP Address Registries", BCP 153, RFC "Special-Purpose IP Address Registries", BCP 153, RFC
6890, April 2013. 6890, April 2013.
skipping to change at page 21, line 41 skipping to change at page 21, line 48
7.2. Informative References 7.2. Informative References
[I-D.leiba-cotton-iana-5226bis] [I-D.leiba-cotton-iana-5226bis]
Cotton, M., Leiba, B., and T. Narten, "Guidelines for Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", draft- Writing an IANA Considerations Section in RFCs", draft-
leiba-cotton-iana-5226bis-11 (work in progress), November leiba-cotton-iana-5226bis-11 (work in progress), November
2014. 2014.
[ProtoParamEvo14] [ProtoParamEvo14]
, "IAB statement on Guiding the Evolution of the IANA "IAB statement on Guiding the Evolution of the IANA
Protocol Parameter Registries ", March 2014, <http:// Protocol Parameter Registries", March 2014,
mailarchive.ietf.org/arch/msg/internetgovtech/ <http://mailarchive.ietf.org/arch/msg/
4EQ4bnEfE5ZkrPAtSAO2OBZM03k>. internetgovtech/4EQ4bnEfE5ZkrPAtSAO2OBZM03k>.
[RFC-INDEX] [RFC-INDEX]
RFC Editor, , "Index of all Requests for Comments", RFC RFC Editor, , "Index of all Requests for Comments", RFC
Index, August 2014. Index, August 2014.
[RFC2014] Weinrib, A. and J. Postel, "IRTF Research Group Guidelines [RFC2014] Weinrib, A. and J. Postel, "IRTF Research Group Guidelines
and Procedures", BCP 8, RFC 2014, October 1996. and Procedures", BCP 8, RFC 2014, October 1996.
[RFC2870] Bush, R., Karrenberg, D., Kosters, M., and R. Plzak, "Root [RFC2870] Bush, R., Karrenberg, D., Kosters, M., and R. Plzak, "Root
Name Server Operational Requirements", BCP 40, RFC 2870, Name Server Operational Requirements", BCP 40, RFC 2870,
skipping to change at page 22, line 34 skipping to change at page 22, line 41
[RFC7020] Housley, R., Curran, J., Huston, G., and D. Conrad, "The [RFC7020] Housley, R., Curran, J., Huston, G., and D. Conrad, "The
Internet Numbers Registry System", RFC 7020, August 2013. Internet Numbers Registry System", RFC 7020, August 2013.
[RFC7249] Housley, R., "Internet Numbers Registries", RFC 7249, May [RFC7249] Housley, R., "Internet Numbers Registries", RFC 7249, May
2014. 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 -06 to -07 A.1. Changes from -07 to -08
o Update text describing the consensus process.
o Insert IAB approval text.
o Point to the proceedings of IETF 91 for IANAPLAN WG agenda and
minutes.
A.2. Changes from -06 to -07
o Merge "No new changes are needed" with "No new organizations or o Merge "No new changes are needed" with "No new organizations or
structures are required". Fewer words to say the same thing. structures are required". Fewer words to say the same thing.
o consult to consult and coordinate. o consult to consult and coordinate.
o RFC Editor comments. o RFC Editor comments.
o Edits resulting from Security Area review by Sean Turner. o Edits resulting from Security Area review by Sean Turner.
o Edits resulting from AD comments. o Edits resulting from AD comments.
A.2. Changes from -05 to -06 A.3. Changes from -05 to -06
o Inclusion of agreed substantial comments from the AD. o Inclusion of agreed substantial comments from the AD.
o Editorial changes. o Editorial changes.
A.3. Changes from -04 to -05 A.4. Changes from -04 to -05
o Change to simpler text for answer about stability and security. o Change to simpler text for answer about stability and security.
o Mention of RFC 5226bis. o Mention of RFC 5226bis.
A.4. Changes from -03 to -04 A.5. Changes from -03 to -04
o Additional text regarding what is needed in Section III. o Additional text regarding what is needed in Section III.
o Appropriate language modifications in section IV to match the o Appropriate language modifications in section IV to match the
above changes in III. above changes in III.
o Acknowledgments edits. o Acknowledgments edits.
A.5. Changes from -02 to -03 A.6. 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 23, line 43 skipping to change at page 24, line 13
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.6. Changes from -01 to -02 A.7. 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.7. Changes from -00 to -01 A.8. 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.
skipping to change at page 27, line 39 skipping to change at page 28, line 5
Introduction Introduction
Under the IANA Stewardship Transition Coordination Group (ICG) Under the IANA Stewardship Transition Coordination Group (ICG)
Charter, the ICG has four main tasks: Charter, the ICG has four main tasks:
(i) Act as liaison to all interested parties in the IANA (i) Act as liaison to all interested parties in the IANA
stewardship transition, including the three "operational stewardship transition, including the three "operational
communities" (i.e., those with direct operational or service communities" (i.e., those with direct operational or service
relationships with the IANA functions operator; namely names, relationships with the IANA functions operator; namely names,
numbers, protocol parameters). This task consists of: &#8232; numbers, protocol parameters). This task consists of:
a. Soliciting proposals from the operational communities a. Soliciting proposals from the operational communities
b. Soliciting the input of the broad group of communities b. Soliciting the input of the broad group of communities
affected by the&#8232;IANA functions affected by the IANA functions
(ii) Assess the outputs of the three operational communities for (ii) Assess the outputs of the three operational communities for
compatibility and interoperability compatibility and interoperability
(iii) Assemble a complete (iii) Assemble a complete
proposal for the transition proposal for the transition
(iv) Information sharing and public communication (iv) Information sharing and public communication
This Request for Proposals (RFP) addresses task (i) of the ICG This Request for Proposals (RFP) addresses task (i) of the ICG
Charter. This RFP does not preclude any form of input from the Charter. This RFP does not preclude any form of input from the
non-operational communities. non-operational communities.
0. Complete Formal Responses 0. Complete Formal Responses
The IANA Stewardship Transition Coordination Group (ICG) seeks The IANA Stewardship Transition Coordination Group (ICG) seeks
complete formal responses to this RFP through processes which are to complete formal responses to this RFP through processes which are to
be convened by each of the "operational communities" of IANA (i.e., be convened by each of the "operational communities" of IANA (i.e.,
those with direct operational or service relationships with the IANA those with direct operational or service relationships with the IANA
skipping to change at page 33, line 20 skipping to change at page 33, line 32
Eliot Lear (editor) Eliot Lear (editor)
Richtistrasse 7 Richtistrasse 7
Wallisellen, ZH CH-8304 Wallisellen, ZH CH-8304
Switzerland Switzerland
Phone: +41 44 878 9200 Phone: +41 44 878 9200
Email: lear@cisco.com Email: lear@cisco.com
Russ Housley (editor) Russ Housley (editor)
918 Spring Noll Drive 918 Spring Knoll Drive
Herndon, VA 20170 Herndon, VA 20170
USA USA
Email: housley@vigilsec.com Email: housley@vigilsec.com
 End of changes. 40 change blocks. 
75 lines changed or deleted 112 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/