Browse Prior Art Database

Early IANA Allocation of Standards Track Code Points (RFC4020)

IP.com Disclosure Number: IPCOM000074146D
Original Publication Date: 2005-Feb-01
Included in the Prior Art Database: 2005-Feb-23
Document File: 8 page(s) / 14K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

K. Kompella: AUTHOR [+2]

Abstract

This memo discusses earlier allocation of code points by IANA as a remedy to the problem created by the "Standards Action" IANA policy for protocols for which, by the IETF process, implementation and deployment experience is desired or required prior to publication.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 20% of the total text.

Network Working Group                                        K. Kompella

Request for Comments: 4020                              Juniper Networks

BCP: 100                                                        A. Zinin

Category: Best Current Practice                                  Alcatel

                                                           February 2005

          Early IANA Allocation of Standards Track Code Points

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.

Copyright Notice

   Copyright (C) The Internet Society (2005).

Abstract

   This memo discusses earlier allocation of code points by IANA as a

   remedy to the problem created by the "Standards Action" IANA policy

   for protocols for which, by the IETF process, implementation and

   deployment experience is desired or required prior to publication.

1.  Introduction

   In Standards Track RFCs, there is often a need to allocate code

   points for various objects, messages, or other protocol entities so

   that implementations can interoperate.  Many of these code point

   spaces have registries handled by the Internet Assigned Number

   Authority (IANA).  Several IANA allocation policies are described in

   RFC 2434 [2434].  Some of them, such as First Come First Served or

   Expert Review, do not require a formal IETF action before the IANA

   performs allocation.  However, in situations where code points are a

   scarce resource and/or the IETF community is willing to retain tight

   control of the protocol, policies such as IESG Approval, IETF

   Consensus, or Standards Action have been used.  The Standards Action

   policy represents a problem in situations where implementation and/or

   deployment experience are desired or required for the Standards

   Action.

   To break the deadlock, "pre-RFC" implementations have sometimes

   simply chosen some "seemingly unused" code points; these may turn out

   to be different from those later assigned by IANA.  To make matters

   worse, these "pre-RFC" implementations are often deployed.  This

   creates several potential interoperability problems between early

Kompella & Zinin         Best Current Practice                  [Page 1]

RFC 4020        Early Allocation of Standard Code Points   February 2005

   implementations and implementations of the final standard, as

   described below:

   1. IANA allocates code points different from those that early

      implementations assumed would be allocated.  Early implementations

      won't int...