Retiring TLVs from the Associated Channel Header of the MPLS Generic Associated Channel

Internet Engineering Task Force (IETF)                         A. Farrel
Request for Comments: 7026                              Juniper Networks
Updates: <a href="./rfc5586">5586</a>                                                  S. Bryant
Category: Standards Track                                  Cisco Systems
ISSN: 2070-1721                                           September 2013


            <span class="h1">Retiring TLVs from the Associated Channel Header</span>
                 <span class="h1">of the MPLS Generic Associated Channel</span>

Abstract

   The MPLS Generic Associated Channel (G-ACh) is a generalization of
   the applicability of the pseudowire (PW) Associated Channel Header
   (ACH).  <a href="./rfc5586">RFC 5586</a> defines the concept of TLV constructs that can be
   carried in messages on the G-ACh by placing them in the ACH between
   the fixed header fields and the G-ACh message.  These TLVs are called
   ACH TLVs

   No Associated Channel Type yet defined uses an ACH TLV.  Furthermore,
   it is believed that handling TLVs in hardware introduces significant
   problems to the fast path, and since G-ACh messages are intended to
   be processed substantially in hardware, the use of ACH TLVs is
   undesirable.

   This document updates <a href="./rfc5586">RFC 5586</a> by retiring ACH TLVs and removing the
   associated registry.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by
   the Internet Engineering Steering Group (IESG).  Further
   information on Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of
   RFC 5741</a>.

   Information about the current status of this document, any
   errata, and how to provide feedback on it may be obtained at
   <a href="https://www.rfc-editor.org/info/rfc7026">http://www.rfc-editor.org/info/rfc7026</a>.









<span class="grey">Farrel & Bryant              Standards Track                    [Page 1]</span>

<span id="page-2" ></span>
<span class="grey"><a href="./rfc7026">RFC 7026</a>                    Retiring ACH TLVs             September 2013</span>


Copyright Notice

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

   This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction and Scope</span>

   <a href="./rfc4385">RFC 4385</a> [<a href="./rfc4385" title=""Pseudowire Emulation Edge-to-Edge (PWE3) Control Word for Use over an MPLS PSN"">RFC4385</a>] says that if the first nibble of a PW packet
   carried over an MPLS network has a value of 1, then the packet starts
   with a specific header format called the Pseudowire Associated
   Channel Header (PWACH) or more generally known as the ACH.  This
   mechanism creates an Associated Channel that is a message channel
   associated with a specific pseudowire (PW).

   The applicability of the ACH is generalized in <a href="./rfc5586">RFC 5586</a> [<a href="./rfc5586" title=""MPLS Generic Associated Channel"">RFC5586</a>] to
   define the MPLS Generic Associated Channel (G-ACh).  This creates a
   common encapsulation header for control channel messages associated
   with MPLS Sections, Label Switching Paths (LSPs), and PWs.

   As part of making the ACH fully generic, <a href="./rfc5586">RFC 5586</a> defines ACH TLV
   constructs.  According to <a href="./rfc5586">RFC 5586</a>:

     In some applications of the generalized associated control channel,
     it is necessary to include one or more ACH TLVs to provide
     additional context information to the G-ACh packet.

   <a href="./rfc5586">RFC 5586</a> goes on to say:

     If the G-ACh message MAY be preceded by one or more ACH TLVs, then
     this MUST be explicitly specified in the definition of an ACH
     Channel Type.

   However, at the time of writing, of the 18 ACH Channel Types defined,
   none allows the use of ACH TLVs [<a href="#ref-IANA-ACH" title=""Pseudowire Associated Channel Types"">IANA-ACH</a>].  At the time of writing,
   there are no unexpired Internet-Drafts that utilize ACH TLVs.






<span class="grey">Farrel & Bryant              Standards Track                    [Page 2]</span>

<span id="page-3" ></span>
<span class="grey"><a href="./rfc7026">RFC 7026</a>                    Retiring ACH TLVs             September 2013</span>


   Furthermore, G-ACh packets are intended to be substantially processed
   in hardware; however, processing TLVs in hardware can be difficult
   because of the unpredictable formats and lengths that they introduce
   to the normal ACH format.

   This document states that ACH TLVs, as specified in <a href="./rfc5586">RFC 5586</a>, are not
   useful and might be harmful.  It updates <a href="./rfc5586">RFC 5586</a> by deprecating the
   ACH TLV and updating the associated IANA registries as described in
   <a href="#section-4">Section 4</a> of this document.  This document makes no comment about the
   use of TLVs in other places.  In particular, proposals to use TLVs
   within ACH messages or as an appendage to ACH messages, are not in
   scope of this document.

<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>.  Specification of Requirements</span>

   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 [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Update to <a href="./rfc5586">RFC 5586</a></span>

   <a href="./rfc5586#section-3">Section 3 of RFC 5586</a> is deleted.

   References to ACH TLVs in <a href="./rfc5586#section-4">Section 4 of RFC 5586</a> should also be
   disregarded.  Note that the text in <a href="#section-4">Section 4</a> currently uses phrases
   like "ACH TLV(s), if present" so, with the removal of <a href="#section-3">Section 3</a> that
   used to define ACH TLVs, they will not be present.

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  Implication for the ACH</span>

   A G-ACh message MUST NOT be preceded by an ACH TLV.

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  IANA Considerations</span>

   This document details two changes to the IANA registries.

<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>.  Associated Channel Header TLV Registry</span>

   The "Pseudowire Name Spaces (PWE3)" registry has a subregistry called
   the "Associated Channel Header TLV Registry".  IANA has entirely
   deleted this subregistry but has left a tombstone record in the top-
   level list of registries that says:

     Associated Channel Header TLV Registry (DELETED)

     Reference
     [<a href="./rfc5586" title=""MPLS Generic Associated Channel"">RFC5586</a>] [<a href="./rfc7026">RFC7026</a>]




<span class="grey">Farrel & Bryant              Standards Track                    [Page 3]</span>

<span id="page-4" ></span>
<span class="grey"><a href="./rfc7026">RFC 7026</a>                    Retiring ACH TLVs             September 2013</span>


<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>.  Pseudowire Associated Channel Types Registry</span>

     The "Pseudowire Name Spaces (PWE3)" registry has a subregistry
     called the "Pseudowire Associated Channel Types" registry.  This
     subregistry previously included a column marked "TLV Follows".
     IANA has entirely deleted this column leaving no record.

<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  Manageability Considerations</span>

     This document will have no impact on network or device
     manageability because there are no ACH Types that allow the use of
     TLVs.  The document removes a feature that might have been used to
     enhance management messages, and especially Operations, Management,
     and Administration (OAM) messages.  However, given the considerable
     experience in defining MPLS OAM messages in the last few years, it
     would appear that this feature is not useful.

     It is possible that packet sniffers that have already been
     implemented will look for ACH TLVs.  The deletion of the construct
     will not have a negative impact.

<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>.  Security Considerations</span>

     Deleting the ACH TLV has a marginal positive effect on security
     because it removes a feature that might have been used as an attack
     vector to carry false information or to bloat G-ACh messages.

     On the other hand, it had been suggested that the ACH TLV could
     have been used to carry security parameters to secure the messages
     on the G-ACh in a generic way.  However, no mechanisms have been
     proposed at the time of writing, and it has generally been
     considered that it is the responsibility of the specification that
     defines G-ACh messages to consider the security requirements of
     those messages that may be different for the different
     applications.

     Otherwise, this document has no implications for security.

<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>.  Acknowledgements</span>

     Thanks to Eric Osborne, Thomas Morin, Lizhong Jin, Greg Mirsky, Jia
     He, and Pearl Liang for suggestions to improve the text.









<span class="grey">Farrel & Bryant              Standards Track                    [Page 4]</span>

<span id="page-5" ></span>
<span class="grey"><a href="./rfc7026">RFC 7026</a>                    Retiring ACH TLVs             September 2013</span>


<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>.  References</span>

<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>.  Normative References</span>

   [<a id="ref-RFC2119">RFC2119</a>]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.

   [<a id="ref-RFC4385">RFC4385</a>]   Bryant, S., Swallow, G., Martini, L., and D. McPherson,
              "Pseudowire Emulation Edge-to-Edge (PWE3) Control Word for
              Use over an MPLS PSN", <a href="./rfc4385">RFC 4385</a>, February 2006.

   [<a id="ref-RFC5586">RFC5586</a>]   Bocci, M., Ed., Vigoureux, M., Ed., and S. Bryant, Ed.,
              "MPLS Generic Associated Channel", <a href="./rfc5586">RFC 5586</a>, June 2009.

<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>.  Informative References</span>

   [<a id="ref-IANA-ACH">IANA-ACH</a>] "Pseudowire Associated Channel Types", IANA,
              <<a href="http://www.iana.org/assignments/pwe3-parameters">http://www.iana.org/assignments/pwe3-parameters</a>>

Authors' Addresses

   Adrian Farrel
   Juniper Networks
   EMail: [email protected]

   Stewart Bryant
   Cisco Systems
   EMail: [email protected]























Farrel & Bryant              Standards Track                    [Page 5]