[Ianaplan] RFC 7979 on Response to the IANA Stewardship Transition Coordination Group (ICG) Request for Proposals on the IANA Protocol Parameters Registries
rfc-editor@rfc-editor.org Tue, 30 August 2016 00:46 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ianaplan@ietfa.amsl.com
Delivered-To: ianaplan@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9347E12D8C8; Mon, 29 Aug 2016 17:46:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.17
X-Spam-Level:
X-Spam-Status: No, score=-103.17 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
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 dJe2LaWEA7XU; Mon, 29 Aug 2016 17:46:01 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C681912D8BF; Mon, 29 Aug 2016 17:45:35 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id AF5D2B80C6F; Mon, 29 Aug 2016 17:45:35 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160830004535.AF5D2B80C6F@rfc-editor.org>
Date: Mon, 29 Aug 2016 17:45:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ianaplan/SWSmN9sArj4kM-X3HRxxW-ajkuo>
Cc: drafts-update-ref@iana.org, ianaplan@ietf.org, rfc-editor@rfc-editor.org
Subject: [Ianaplan] RFC 7979 on Response to the IANA Stewardship Transition Coordination Group (ICG) Request for Proposals on the IANA Protocol Parameters Registries
X-BeenThere: ianaplan@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 30 Aug 2016 00:46:12 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7979
Title: Response to the IANA Stewardship
Transition Coordination Group (ICG) Request for
Proposals on the IANA Protocol Parameters
Registries
Author: E. Lear, Ed.,
R. Housley, Ed.
Status: Informational
Stream: IETF
Date: August 2016
Mailbox: lear@cisco.com,
housley@vigilsec.com
Pages: 37
Characters: 81587
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ianaplan-icg-response-10.txt
URL: https://www.rfc-editor.org/info/rfc7979
DOI: http://dx.doi.org/10.17487/RFC7979
The U.S. National Telecommunications and Information Administration
(NTIA) solicited a request from the Internet Corporation for Assigned
Names and Numbers (ICANN) to propose how the NTIA should end its
oversight of the Internet Assigned Numbers Authority (IANA)
functions. After broad consultations, ICANN in turn created the IANA
Stewardship Transition Coordination Group. That group solicited
proposals for the three major IANA functions: names, numbers, and
protocol parameters. This document contains the IETF response to
that solicitation for protocol parameters. It was included in an
aggregate response to the NTIA alongside those for names and
numbering resources that are being developed by their respective
operational communities. A reference to that response may be found
in the introduction, and additional correspondence is included in the
Appendix.
This document is a product of the Planning for the IANA/NTIA Transition Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC