Scratch proposal: Charter for IANAPLAN WG
version 2014-07-20a

Area: General
Responsible AD: Jari Arkko
Chairs: TBD

Background
==========

The IETF maintains parameters for protocols it defines in registries.
These registries are maintained by the Internet Assigned Numbers
Authority (IANA), and are the subject of the "IANA Considerations"
section in many RFCs.  

For a number of years, the IANA function has been provided by the
Internet Corporation for Assigned Names and Numbers (ICANN).  The
IETF's relationship with IANA was formalized through a Memorandum of
Understanding codified in 2000 with the publication of RFC 2860; over
time processes and role definitions have evolved, and have been
documented in supplemental agreements.

ICANN has historically had a contract with the US Department of
Commerce (DoC), undertaken through the National Telecommunications and
Information Administration (NTIA).  In March of 2014, NTIA announced
its intention to complete the evolution begun in 1997, meaning that
NTIA would not need to renew its contract with ICANN when that
contract expires 30 September 2015.  NTIA requested a transition
proposal be prepared to outline the necessary arrangements. In the
case of the IETF, we expect these arrangements to consist largely of
the existing well-documented practices.

Tasks
=====

The WG will review, comment on, evaluate, and if need be prepare text
for a proposal about protocol parameters registries.  It will begin
with the following documents:

- RFC 2850 (especially section 2(d))
- RFC 2860
- RFC 6220
- IETF-ICANN-MOU_2000
   (http://iaoc.ietf.org/documents/IETF-ICANN-MOU_2000.pdf)
- IETF-ICANN Supplemental Agreement Dec 2007
   (http://iaoc.ietf.org/documents/IETF-ICANN_Supplemental_Agreement.pdf)
- IETF-ICANN Supplemental Agreement March 2008
   (http://iaoc.ietf.org/documents/IETF-IANA_%20MoU_Supplemental_Agreement_2008.pdf)
- ICANN-IETF Supplemental Agreement March 2009
   (http://iaoc.ietf.org/documents/ICANN-IETF-SLA-2009-Executed.pdf)
- ICANN-IETF Supplemental Agreement 2010
   (http://iaoc.ietf.org/documents/ICANN-IETF-SLA-2010-Executed.pdf)
- ICANN-IETF Supplemental Agreement 2011
   (http://iaoc.ietf.org/documents/ICANN-IETF-Agreement-2011-Executed.pdf)
- ICANN-IETF Supplemental Agreement 2012
   (http://iaoc.ietf.org/documents/ICANN-IETF-Agreement-2012-Executed.pdf)
- ICANN-IETF Supplemental Agreement 2013
   (http://iaoc.ietf.org/documents/2013-ICANN-IETF-MoU-Supplemental-Agreement-Executed.pdf)
- ICANN-IETF Supplemental Agreement 2014
   (http://iaoc.ietf.org/documents/2014-ICANN-IETF-MoU-Supplemental-Agreement-Executed.pdf)

It may consider, but is not bound to use,
draft-kolkman-iana-framework-00.  It is likely that RFC 3777 and its
updates are also implicated.

This work is chartered exclusively to propose alterations that are
needed in order to support the transition of stewardship of the IANA
functions.  Other possible improvements will be set aside for future
consideration.

The WG will also review, comment on, and evaluate proposals from other
communities about the NTIA transition, to the extent that those
proposals impinge on the protocol parameters registries.

The results of any WG consensus on protocol parameters registries
will, of necessity, be input but not necessarily firm restrictions on
any contractual terms that are ultimately adopted by the IAB and any
future IANA functions provider, or contractual terms ultimately
adopted by the IAOC and any future IANA functions provider.
Statements of principle and desired outcomes are more important items
to be delivered by the working group than are detailed terms for
future agreements.

Milestones
==========

January 2015  -- complete protocol parameters registries proposal
May 2015 -- review of other transition proposals, if needed
Sept 2015 -- close