IANA Guidance for Managing the ULE Next-Header Registry
draft-fairhurst-ipdvb-ule-iana-06

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-03-27 (latest revision 2014-03-05)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Consensus Yes
Document shepherd Wesley Eddy
Shepherd write-up Show (last changed 2014-01-30)
IESG IESG state Approved-announcement to be sent::Point Raised - writeup needed
Telechat date
Responsible AD Brian Haberman
Send notices to gorry@erg.abdn.ac.uk, draft-fairhurst-ipdvb-ule-iana@tools.ietf.org, wes@mti-systems.com
IANA IANA review state IANA OK - Actions Needed
IANA action state None
IPDVB Working Group                                         G. Fairhurst
Internet-Draft                                    University of Aberdeen
Updates: 4326 (if approved)                                March 6, 2014
Intended status: Standards Track
Expires: September 7, 2014

        IANA Guidance for Managing the ULE Next-Header Registry
                   draft-fairhurst-ipdvb-ule-iana-06

Abstract

   This document proposes an update to RFC 4326 to clarify and update
   the allocation rules for the Unidirectional Lightweight Encapsulation
   (ULE) Next-Header registry.  This registry is used by ULE and Generic
   Stream Encapsulation (GSE) to record the code points of extension
   headers and protocols supported by these encapsulation protocols.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 7, 2014.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Fairhurst               Expires September 7, 2014               [Page 1]
Internet-Draft             IANA ULE guidelines                March 2014

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  The ULE Next Header Registries  . . . . . . . . . . . . .   3
     2.2.  Informative example of using a value from the optional
           range . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Updated IANA guidance on allocation in the ULE Next Header
       Registry  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  ULE Next-Header Registry  . . . . . . . . . . . . . . . .   4
     3.2.  IANA Guidelines . . . . . . . . . . . . . . . . . . . . .   4
     3.3.  Reservation of Next Header values for Private Use . . . .   5
   4.  Update to registry information  . . . . . . . . . . . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   6
   8.  Revision Notes  . . . . . . . . . . . . . . . . . . . . . . .   6
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   The Unidirectional Lightweight Encapsulation (ULE) [RFC4326]
   specifies an encapsulation for links that employ the MPEG-2 Transport
   Stream, with support over a wide variety of physical-layer bearers
   [RFC4259].  The encapsulation header includes a Type field that
   identifies payload types and extension headers (e.g.[RFC5163]).  The
   ULE specification requested IANA to maintain the ULE next header
   registries to record the allocation of the values used to derive this
   Type field.

   The Digital Video Broadcast (DVB) Project has published an
   encapsulation for second-generation DVB physical layers.  This
   specifies the Generic Stream Encapsulation [GSE].  This encapsulation
   shares many of the network properties of ULE and uses a common format
   for the Type field [RFC5163].  The ULE Next Header registries are
   therefore also applicable to this encapsulation.

   This document updates the IANA rules and guidance defined in section
   11.1 of [RFC4326] in the following way:

   o  The document clarifies use of the ULE Next-Header registry by GSE
Show full document text