X-Mozilla-Keys: 
Received: from rcdn-iport-5.cisco.com (173.37.86.76) by mail.cisco.com
 (173.36.12.89) with Microsoft SMTP Server (TLS) id 14.3.195.1; Wed, 26 Nov
 2014 11:37:16 -0600
Received: from rcdn-core-8.cisco.com ([173.37.93.144])  by
 rcdn-iport-5.cisco.com with ESMTP; 26 Nov 2014 17:37:16 +0000
Received: from alln-inbound-d.cisco.com (alln-inbound-d.cisco.com
 [173.37.147.234])	by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id
 sAQHbFvm000499;	Wed, 26 Nov 2014 17:37:16 GMT
Received-SPF: Pass (alln-inbound-d.cisco.com: domain of
  ianaplan-bounces@ietf.org designates 2001:1900:3001:11::2c as
  permitted sender) identity=mailfrom;
  client-ip=2001:1900:3001:11::2c;
  receiver=alln-inbound-d.cisco.com;
  envelope-from="ianaplan-bounces@ietf.org";
  x-sender="ianaplan-bounces@ietf.org"; x-conformance=spf_only;
  x-record-type="v=spf1"
Received-SPF: None (alln-inbound-d.cisco.com: no sender
  authenticity information available from domain of
  postmaster@mail.ietf.org) identity=helo;
  client-ip=2001:1900:3001:11::2c;
  receiver=alln-inbound-d.cisco.com;
  envelope-from="ianaplan-bounces@ietf.org";
  x-sender="postmaster@mail.ietf.org"; x-conformance=spf_only
Authentication-Results:
 alln-inbound-d.cisco.com; dkim=pass (signature verified) header.i=@ietf.org
X-from-outside-Cisco: 2001:1900:3001:11::2c
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?utf-8?q?A8AdAQBRD3ZUnAAZASCDgISAEQAsW4JkdUwLx?=
 =?utf-8?q?3QiDIV2gWIWAQEBAQEBAg4BAQEBAQgUCUKCJhMLKAgEHQI+EgEcAgQBATcGAQEECh?=
 =?utf-8?q?4LAQIDAQIGAkAFAwgDARsIHxcTBQ+ILQIKu0iFcgEFgXUFjzcBAQEBAQEBAQEBAQE?=
 =?utf-8?q?BAQEBAQEBAQERBoZfjFoPRIFDjCiGRYRghzMBgTU/gxqURYFmC0uCSgEBAQ?=
X-IPAS-Result: =?utf-8?q?A8AdAQBRD3ZUnAAZASCDgISAEQAsW4JkdUwLx3QiDIV2gWIWAQE?=
 =?utf-8?q?BAQEBAg4BAQEBAQgUCUKCJhMLKAgEHQI+EgEcAgQBATcGAQEECh4LAQIDAQIGAkAF?=
 =?utf-8?q?AwgDARsIHxcTBQ+ILQIKu0iFcgEFgXUFjzcBAQEBAQEBAQEBAQEBAQEBAQEBAQERB?=
 =?utf-8?q?oZfjFoPRIFDjCiGRYRghzMBgTU/gxqURYFmC0uCSgEBAQ?=
X-IronPort-AV: E=Sophos;i="5.07,463,1413244800";
   d="scan'208";a="36758620"
X-Amp-Result: Clean
X-Amp-File-Uploaded: False
X-IronPort-Outbreak-Status: No, level 0, Unknown - Unknown
Received: from mail.ietf.org ([IPv6:2001:1900:3001:11::2c])  by
 alln-inbound-d.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 26 Nov 2014
 17:37:11 +0000
Received: from ietfa.amsl.com (localhost [IPv6:::1])	by ietfa.amsl.com
 (Postfix) with ESMTP id 367A51A1A74;	Wed, 26 Nov 2014 09:37:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
	t=1417023430; bh=id80gRnIwyUNNWYQQ6YL5umYPmjAcJz/X0V10c99kqg=;
	h=MIME-Version:From:To:Message-ID:Date:Cc:Subject:Reply-To:List-Id:
	 List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe:
	 Content-Type:Content-Transfer-Encoding:Sender;
	b=EJaJ/sKketqIBLrBjs6EGu5+4U3zOrklq13/PHvjVFb8oEzhKR1AfiwAjOxMEJcJ+
	 2rlYEaAn5JyyJwlig+R7s/IjIFL2IOIcYO5XHahDzEnmtXxmpjaMO2HRlfsvZHw9j0
	 ZB593vxyLRXCftHThY+Usw3nUJvsNj8c/EerLqPk=
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 93ED91A1A72; Wed, 26 Nov 2014 09:37:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9] 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 zfExawPXQHgY; Wed, 26
 Nov 2014 09:37:06 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com
 (Postfix) with ESMTP id 6B8E31A0203; Wed, 26 Nov 2014 09:37:06 -0800 (PST)
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141126173706.6042.70918.idtracker@ietfa.amsl.com>
Date: Wed, 26 Nov 2014 09:37:06 -0800
Archived-At:
 http://mailarchive.ietf.org/arch/msg/ianaplan/X7x5iqh4l25bx_fHnnu2tRmpGOU
CC: <ianaplan@ietf.org>
Subject: [Ianaplan] Last Call: <draft-ietf-ianaplan-icg-response-06.txt>
 (Draft Response to the Internet Coordination Group Request for Proposals on
 the IANA protocol parameters registries) to Informational RFC
X-BeenThere: ianaplan@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: <ietf@ietf.org>
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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ianaplan-bounces@ietf.org
Sender: Ianaplan <ianaplan-bounces@ietf.org>
Return-Path: ianaplan-bounces@ietf.org
X-MS-Exchange-Organization-AuthSource: xhc-aln-x15.cisco.com
X-MS-Exchange-Organization-AuthAs: Internal
X-MS-Exchange-Organization-AuthMechanism: 10
MIME-Version: 1.0


The IESG has received a request from the Planning for the IANA/NTIA
Transition WG (ianaplan) to consider the following document:
- 'Draft Response to the Internet Coordination Group Request for
   Proposals on the IANA protocol parameters registries'
  <draft-ietf-ianaplan-icg-response-06.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2014-12-15. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This document contains the IETF response to a request for proposals
   from the IANA Stewardship Transition Coordination Group regarding the
   protocol parameters registries.  It is meant to be included in an
   aggregate proposal that also includes contributions covering domain
   names and numbering resources that will be submitted from their
   respective operational communities.  The IETF community is invited to
   comment and propose changes to this document.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-ianaplan-icg-response/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-ianaplan-icg-response/ballot/


No IPR declarations have been submitted directly on this I-D.


_______________________________________________
Ianaplan mailing list
Ianaplan@ietf.org
https://www.ietf.org/mailman/listinfo/ianaplan


