Guiding the Evolution of the IANA Protocol Parameter Registries

IAB Chair <iab-chair@iab.org> Mon, 24 February 2014 17:28 UTC

Return-Path: <iab-chair@iab.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23E701A0193 for <ietf-announce@ietfa.amsl.com>; Mon, 24 Feb 2014 09:28:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KsC3UWQ1dCtE for <ietf-announce@ietfa.amsl.com>; Mon, 24 Feb 2014 09:28:49 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.21]) by ietfa.amsl.com (Postfix) with ESMTP id 0AB0D1A022C for <ietf-announce@ietf.org>; Mon, 24 Feb 2014 09:28:48 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id A9CE9A02F1; Mon, 24 Feb 2014 09:27:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5PvFjcNXCBjs; Mon, 24 Feb 2014 09:27:40 -0800 (PST)
Received: from [192.168.2.100] (pool-173-79-206-43.washdc.fios.verizon.net [173.79.206.43]) by c9a.amsl.com (Postfix) with ESMTPSA id 1C47AA02E7; Mon, 24 Feb 2014 09:27:40 -0800 (PST)
Subject: Guiding the Evolution of the IANA Protocol Parameter Registries
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: IAB Chair <iab-chair@iab.org>
In-Reply-To: <530921E3.7060005@cisco.com>
Date: Mon, 24 Feb 2014 12:28:45 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <DFC22E37-7FA1-4973-A804-73C00685419C@iab.org>
References: <53066F72.6080809@cisco.com> <CF2CB88C.1B2CA%alissa@cooperw.in> <53078600.3090104@cisco.com> <CF2CCDF6.1B3E7%alissa@cooperw.in> <53086568.7050707@cisco.com> <3FFD6830-DC12-4707-AE2B-0FE1F251B198@vigilsec.com> <530921E3.7060005@cisco.com>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1085)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/rRn3N89AuGFcarSE7dL4o-Wvxao
Cc: internetgovtech@iab.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Feb 2014 17:28:51 -0000

Existing IETF and IAB consensus concerning Internet registry functions
and IANA are documented in a variety of RFCs and IAB communications
[RFC2860,RFC6220,IAB1,IAB2].  Since registry functions and IANA are
likely to be the subject of discussion in a number of venues outside the
IETF over the coming months and years, the IAB is seeking community
feedback about operating principles to use when they find themselves
involved in those discussions.

While dealing with these issues the IAB has consistently approached the
issues from a set of (implicit) principles.  Since the registry functions
are subject of discussion in various fora, the IAB has tried to make
these operating principles explicit and seeks to confirm these with the
community.

The IAB are planning to use part of the time in the IGOVUPDATE session at
IETF 89 (6 March 2014, 17:00-18:30 GMT) for a discussion of such operating
principles.  But we wanted to kick-start that discussion with a few
thoughts about principles that the IAB and IETF have articulated in
various documents already and some that have emerged over time but may
not have been written down.  What we are interested in is an articulation
of what the IETF community values.  What other parties (ICANN, RIRs,
governments, etc.) value when they think about registry functions is
interesting, but we want to focus this discussion on the IETF and not
those other parties.

This is a first cut of making the principles more explicit for which we
seek your views.

Some of these might seem a bit generic, but it is difficult to predict
the nature of future discussions in which IETF and IAB leaders might find
themselves, so generality helps in that regard.

On behalf of the IAB,
  Russ Housley
  IAB Chair

= = = = = = = =

Principles Guiding the Evolution of the IANA Protocol Parameter Registries

1. The IETF protocol parameters function has been and continues to be
capably provided by the Internet community.

The strength and stability of the function and its foundation within the
Internet community are both important given how critical protocol
parameters are to the proper functioning of IETF protocols.

We think the structures that sustain the protocol parameters function
needs be strong enough that they can be offered independently by the
Internet community, without the need for backing from external parties.
And we believe we largely are there already, although the system can be
strengthened further, and continuous improvements are being made.

2. The administration of the protocol parameters function by ICANN is
working well for the Internet and the IETF.

We are pleased with the publication and maintenance of the protocol
parameter function and the coordination of the evaluation of
registration requests through the IANA function provided by ICANN.

3. The IETF protocol parameters function requires openness,
transparency, and accountability.

Existing documentation of how the function is administered and overseen
is good [RFC2860,RFC6220], but further articulation and clarity may be
beneficial. It is important that the whole Internet community can
understand how the function works, and that the processes for
registering parameters and holding those who oversee the protocol
parameter function accountable for following those processes are
understood by all interested parties. We are committed to making
improvements here if necessary.

4. Any contemplated changes to the protocol parameters function should
use the current RFCs and model as the starting point.

The protocol parameters function is working well, and as a result
wholesale changes to the role of the IETF vis a vis the function are not
warranted. The IETF/IANA Memorandum of Understanding [RFC2860] is a good
model to work from in the event that other parties do want to contemplate
changes. Put quite simply: evolution, not revolution.

5. The Internet architecture requires and receives capable service by 
Internet registries.

The stability of the Internet depends on capable provision of not just
IETF protocol parameters, but IP numbers, domain names, and other
registries. Furthermore, DNS and IPv4/IPv6 are IETF-defined protocols.
Thus we expect the role of the IETF in standards development, architectural
guidance, and allocation of certain name/number parameters to continue.
IP multicast addresses and special-use DNS names are two examples where
close coordination is needed.  The IETF will continue to coordinate with
ICANN, the RIRs, and other parties that are mutually invested in the
continued smooth operation of the Internet registries. We fully
understand the need to work together.

6.  The IETF will continue its direction and stewardship of the protocol
parameters function as an integral component of the IETF standards
process and the use of resulting protocols.

RFC 6220 specifies the role and function of the protocol parameters
registry, which is critical to IETF standards processes and IETF
protocols.  We see no need to revisit or reconsider our current approach
with regard to protocol parameters, including the ability to delegate
operational responsibility for registries to other organizations.

[RFC2860] http://www.rfc-editor.org/rfc/rfc2860.txt
[RFC6220]  http://www.rfc-editor.org/rfc/rfc6220.txt
[IAB1] http://www.iab.org/wp-content/IAB-uploads/2011/03/2009-06-08-IAB-NTIA-NOI-final.pdf
[IAB2] http://www.iab.org/wp-content/IAB-uploads/2011/07/IANA-IAB-FNOI-2011.pdf