Browse Prior Art Database

IANA Allocation Guidelines for the Protocol Field (RFC5237)

IP.com Disclosure Number: IPCOM000168079D
Original Publication Date: 2008-Feb-01
Included in the Prior Art Database: 2008-Feb-29
Document File: 6 page(s) / 9K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Arkko: AUTHOR [+2]

Abstract

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 text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 29% of the total text.

Network Working Group                                           J. Arkko Request for Comments: 5237                                      Ericsson BCP: 37                                                       S. Bradner Updates: 2780                                         Harvard University Category: Best Current Practice                            February 2008

            IANA Allocation Guidelines for the Protocol Field

Status of This Memo

   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.

Abstract

   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.

1.  Introduction

   This document revises the IANA guidelines [RFC2780] for allocating    new Protocol field values in IPv4 header [RFC0791].  The change will    also be applicable for IPv6, as the IANA guidelines for IPv6 Next    Header values [RFC2460] allocation refer to the IPv4 guidelines.

   Previously, RFC 2780 allowed such allocations to happen through IESG    Approval, Standards action, or Expert Review processes    [RFC2780][RFC2434].  The Expert Review process was specified to be    used only in the case where a non-disclosure agreement was involved:

      IANA allocates values from the IPv4 Protocol name space following       an Expert Review, IESG Approval or Standards Action process.  The       Expert Review process should only be used in those special cases       where non-disclosure information is involved.  In these cases the       expert(s) should be designated by the IESG.

   The need for the Standards Action rule is obvious as the IETF keeps    developing new protocols.  It is equally obvious that there is a need    to allow experimental allocations in this space; see RFC 4727    [RFC4727] for an example.  Similarly, there are cases when it makes    sense to allocate values out of this space for other non-Standards    Track or non-IETF uses.  However, the size of the field is 256    values, and 55% of these were in use at the time this document was    written.  As a result, a sanity check is needed to ensure that

Arkko & Bradner          Best Current Practice                  [Page 1]
 RFC 5237               Protocol Field IANA Rules           February 2008

    allocations are not made needlessly.  RFC...