datatracker.ietf.org
Sign in
Version 5.6.2.p1, 2014-07-22
Report a bug

IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3)
RFC 4446

Document type: RFC - Best Current Practice (April 2006; Errata)
Also Known As BCP 116
Document stream: IETF
Last updated: 2013-03-02
Other versions: plain text, pdf, html

IETF State: (None)
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: RFC 4446 (Best Current Practice)
Responsible AD: Mark Townsley
Send notices to: stbryant@cisco.com, danny@tcb.net

Network Working Group                                         L. Martini
Request for Comments: 4446                            Cisco Systems Inc.
BCP: 116                                                      April 2006
Category: Best Current Practice

     IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3)

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 (2006).

Abstract

   This document allocates the fixed pseudowire identifier and other
   fixed protocol values for protocols that have been defined in the
   Pseudo Wire Edge to Edge (PWE3) working group.  Detailed IANA
   allocation instructions are also included in this document.

Table of Contents

   1. Introduction ....................................................2
   2. Specification of Requirements ...................................2
   3. IANA Considerations .............................................2
      3.1. Expert Review Directives ...................................2
      3.2. MPLS Pseudowire Type .......................................3
      3.3. Interface Parameters Sub-TLV Type ..........................4
      3.4. Attachment Identifiers .....................................5
           3.4.1. Attachment Individual Identifier Type ...............5
           3.4.2. Attachment Group Identifier (AGI) Type ..............5
      3.5. Pseudowire Status ..........................................6
      3.6. PW Associated Channel Type .................................6
   4. Security Considerations .........................................7
   5. References ......................................................7
      5.1. Normative References .......................................7
      5.2. Informative References .....................................7

Martini                  Best Current Practice                  [Page 1]
RFC 4446               IANA Allocations for PWE3              April 2006

1.  Introduction

   Most of the new IANA registries and respective IANA-allocation
   processes for protocols defined in the PWE3 IETF working group can be
   found in this document.  The IANA registries defined here are in
   general subdivided into three main ranges: a range to be allocated by
   IETF consensus according to [RFC2434], a range to be allocated by the
   expert review process according to [RFC2434], and a range to be
   allocated on a first come, first served basis that is reserved for
   vendor proprietary allocations.  Note that vendor proprietary types
   MUST NOT be registered for IETF standards or extensions thereof,
   whether they are still in development or already completed.

2.  Specification of Requirements

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

3.  IANA Considerations

   IANA has created several registries as described in the following
   paragraphs.  Each of these registries contains numeric values used to
   identify data types.  In each of these registries, the value of 0 is
   reserved and MUST not be used.

3.1.  Expert Review Directives

   Throughout this document, allocation procedures for several
   registries call for an expert review process according to [RFC2434].
   The expert should consider the following points:

      *  Duplication of code point allocations should be avoided.

      *  A brief, clear description of the code point allocation
         requested should be provided.

      *  The type allocation requested should be appropriate for the
         particular requested value range in the registry.

   The expert reviewing the request MUST approve or disapprove the
   request within 10 business days from when he or she received the
   expert review request.

Martini                  Best Current Practice                  [Page 2]
RFC 4446               IANA Allocations for PWE3              April 2006

3.2.  MPLS Pseudowire Type

   IANA has set up the registry of "MPLS Pseudowire Type".  This type
   has 15-bit values.  PW Type values 1 through 30 are specified in this
   document, and PW Type values 31 through 1024 are to be assigned by
   IANA, using the "Expert Review" policy defined in [RFC2434].  PW Type
   values 1025 through 4096 and 32767 are to be allocated using the IETF

[include full document text]