BCP 37, RFC 5237 on IANA Allocation Guidelines for the Protocol Field
rfc-editor@rfc-editor.org Fri, 29 February 2008 00:36 UTC
Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietfarch-ietf-announce-archive@core3.amsl.com
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7BCC528C9CE; Thu, 28 Feb 2008 16:36:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.483
X-Spam-Level:
X-Spam-Status: No, score=-0.483 tagged_above=-999 required=5 tests=[AWL=-0.046, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EZXT+byo4vqB; Thu, 28 Feb 2008 16:36:28 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6F16B28C9DA; Thu, 28 Feb 2008 16:32:21 -0800 (PST)
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8D06D28C9B4 for <ietf-announce@core3.amsl.com>; Thu, 28 Feb 2008 16:32:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jvC0slaOSdmd for <ietf-announce@core3.amsl.com>; Thu, 28 Feb 2008 16:32:14 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 7941028C3AF for <ietf-announce@ietf.org>; Thu, 28 Feb 2008 16:32:09 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id AC9B411744A; Thu, 28 Feb 2008 16:32:02 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 37, RFC 5237 on IANA Allocation Guidelines for the Protocol Field
From: rfc-editor@rfc-editor.org
Message-Id: <20080229003202.AC9B411744A@bosco.isi.edu>
Date: Thu, 28 Feb 2008 16:32:02 -0800
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Announcements <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
A new Request for Comments is now available in online RFC libraries.
BCP 37
RFC 5237
Title: IANA Allocation Guidelines for the
Protocol Field
Author: J. Arkko, S. Bradner
Status: Best Current Practice
Date: February 2008
Mailbox: jari.arkko@piuha.net,
sob@harvard.edu
Pages: 5
Characters: 9303
Updates: RFC2780
See Also: BCP0037
I-D Tag: draft-arkko-rfc2780-proto-update-02.txt
URL: http://www.rfc-editor.org/rfc/rfc5237.txt
This document revises the IANA guidelines for allocating new Protocol
field values in IPv4 header. It modifies the rules specified in RFC
2780 by removing the Expert Review option. The change will also
affect the allocation of Next Header field values in IPv6. This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.
BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
The RFC Editor Team
USC/Information Sciences Institute
...
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce