[Ianaplan] Fwd: WG Action: Formed Planning for the IANA/NTIA Transition (ianaplan)

Marc Blanchet <marc.blanchet@viagenie.ca> Mon, 08 September 2014 16:21 UTC

Return-Path: <marc.blanchet@viagenie.ca>
X-Original-To: ianaplan@ietfa.amsl.com
Delivered-To: ianaplan@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36C4E1A88C3 for <ianaplan@ietfa.amsl.com>; Mon, 8 Sep 2014 09:21:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.552
X-Spam-Level:
X-Spam-Status: No, score=-3.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001] autolearn=ham
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 HyofqKPI7MtT for <ianaplan@ietfa.amsl.com>; Mon, 8 Sep 2014 09:21:23 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 1DD221A88C2 for <ianaplan@ietf.org>; Mon, 8 Sep 2014 09:21:23 -0700 (PDT)
Received: from h118.viagenie.ca (h118.viagenie.ca [206.123.31.118]) by jazz.viagenie.ca (Postfix) with ESMTPSA id E064341319 for <ianaplan@ietf.org>; Mon, 8 Sep 2014 12:21:21 -0400 (EDT)
From: Marc Blanchet <marc.blanchet@viagenie.ca>
Content-Type: multipart/alternative; boundary="Apple-Mail=_78272E75-51B0-4A6F-8A33-388B4BE9ED8D"
Date: Mon, 8 Sep 2014 12:21:21 -0400
References: <20140908160252.20603.40987.idtracker@ietfa.amsl.com>
To: ianaplan@ietf.org
Message-Id: <71401DA0-6E33-4707-AD25-E2A34E8F66A4@viagenie.ca>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/f7oeR2al87qPFN79bLRBjNnxsEA
Subject: [Ianaplan] Fwd: WG Action: Formed Planning for the IANA/NTIA Transition (ianaplan)
X-BeenThere: ianaplan@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IANA Plan <ianaplan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ianaplan/>
List-Post: <mailto:ianaplan@ietf.org>
List-Help: <mailto:ianaplan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Sep 2014 16:21:26 -0000

FYI,  Marc.

Début du message réexpédié :

> De: The IESG <iesg-secretary@ietf.org>;
> Objet: WG Action: Formed Planning for the IANA/NTIA Transition (ianaplan)
> Date: 8 septembre 2014 12:02:52 UTC−4
> À: IETF-Announce <ietf-announce@ietf.org>;
> Cc: ianaplan WG <ianaplan@ietf.org>;
> Répondre à: ietf@ietf.org
> 
> A new IETF working group has been formed in the General Area. For
> additional information please contact the Area Directors or the WG
> Chairs.
> 
> Planning for the IANA/NTIA Transition (ianaplan)
> ------------------------------------------------
> Current Status: Proposed WG
> 
> Chairs:
>  Marc Blanchet <Marc.Blanchet@viagenie.ca>;
>  Leslie Daigle <ldaigle@thinkingcat.com>;
> 
> Assigned Area Director:
>  Jari Arkko <jari.arkko@piuha.net>;
> 
> Mailing list
>  Address: ianaplan@ietf.org
>  To Subscribe: https://www.ietf.org/mailman/listinfo/ianaplan
>  Archive: http://www.ietf.org/mail-archive/web/ianaplan/
> 
> Charter:
> 
> Background
> ==========
> 
> Registries of parameter values for use in IETF protocols are stored
> and maintainted for the IETF by the Internet Assigned Numbers
> Authority (IANA), and are the subject of the "IANA Considerations"
> section in many RFCs.
> 
> For a number of years, this 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 between the IETF and ICANN 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 had a contract with the US Department of Commerce (DoC) to
> provide the IANA function, undertaken through the National
> Telecommunications and Information Administration (NTIA).  In March of
> 2014, NTIA announced its intention to transition out of its current
> role, 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 elements of the IANA function
> concerning the IETF protocol registries, it is likely that the
> existing well-documented practices will continue and no or little new
> activity will be required.
> 
> Tasks
> =====
> 
> The IANAPLAN working group is chartered to produce an IETF consensus
> document that describes the expected interaction between the IETF and
> the operator of IETF protocol parameters registries.
> 
> The system in place today for oversight of the IETF protocol
> registries component of the IANA function works well. As a result,
> minimal change in the oversight of the IETF protocol parameters
> registries is preferred in all cases and no change is preferred when
> possible. The working group will address the implications of moving
> the NTIA out of its current role with respect to IANA on the IETF
> protocol parameters registry function in a way that focuses on
> continuation of the current arrangements.  The working group will
> assume the following documents continue to be in effect:
> 
> - RFC 2850
> - RFC 3777 and its updates
> - RFC 2860
> - RFC 6220
> - IETF-ICANN-MOU_2000
>   (http://iaoc.ietf.org/documents/IETF-ICANN-MOU_2000.pdf)
> - ICANN-IETF Supplemental Agreements
>   (updated yearly since 2007, the 2014 version is available at
>   http://iaoc.ietf.org/documents/
>   2014-ICANN-IETF-MoU-Supplemental-Agreement-Executed.pdf)
> 
> This working group is chartered solely with respect to the planning
> needed for the transition, and is not meant to cover other topics
> related to IANA. Possible improvements outside that scope will be set
> aside for future consideration. However, the mechanisms required to
> address the removal of the overarching NTIA contract may require
> additional documentation or agreements. The WG will identify, but
> not create, such required agreements.
> 
> Should proposals made by other communities regarding the
> transition of other IANA functions affect the IETF protocol parameter
> registries or the IETF, the WG may also review and comment on them.
> 
> Fully documenting the interaction between the IETF and the operator
> of IETF protocol parameters registries may require detailed terms of
> agreements or other details of procedures that are normally delegated
> to and handled by the IAB or IAOC. The working group will not attempt
> to produce or discuss documentation for these details, but will
> request the IAB or IAOC to provide them separately.
> 
> The WG shall seek the expertise of the IAB IANA Evolution Program to
> formulate its output. It is expected that members of the IAB IANA
> Evolution Program will actively participate in the WG.
> 
> 
> Milestones:
>  Jan 2015 - complete protocol parameters registries document
>  May 2015 - review of other transition proposals, if needed
>  Sep 2015 - close