[Docs] [txt|pdf] [Tracker] [Email] [Nits]

Versions: 00 draft-lcap-mpls-moving-iana-registries

Network Working Group                                       L. Andersson
Internet-Draft                                                    Huawei
Updates: 6374 (if approved)                                July 14, 2013
Intended status: Standards Track
Expires: January 15, 2014


    Moving Generic Associated Channel registries to a new name space
             draft-andersson-mpls-moving-iana-registries-00

Abstract

   When RFC 6374 "Packet Loss and Delay Measurement for MPLS Networks"
   were developed, the code points allocated by this RFC were mistakenly
   placed within the Multi-Protocol Label Switching (MPLS) Label
   Switched Paths (LSPs) Ping Parameter registry.  This document creates
   a new dedicated name space for Generic Associated Channel code points
   and move them to a name space their own.

Requirements Language

   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 RFC 2119 [RFC2119].

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 January 15, 2014.

Copyright Notice

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





Andersson               Expires January 15, 2014                [Page 1]


Internet-Draft          Creating GACh registries               July 2013


   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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Moving GACh parameters out of LSP Ping parameter registry . .   2
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Moving Loss/Delay registries  . . . . . . . . . . . . . .   3
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   4
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   RFC 6374 [RFC6374] specify protocols for delay and loss measurements.
   The protocols run over the Generic Associated Channel (GACh).  There
   are four registries with code points for these protocols.  These
   registries were mistakenly allocated within the LSP Ping Parameters
   namespace.  This document now creates a new GACh name space and move
   the Loss and Delay parameter registries to the new registry.

2.  Moving GACh parameters out of LSP Ping parameter registry

   In the "Multi-Protocol Label Switching (MPLS) Label Switched Paths
   (LSPs) Ping Parameters" name space there are four registries that are
   for using the MPLS Generic Associated Channel [RFC5586]for MPLS Loss
   and Delay measurements [RFC6374].

   The registries are:

   o  Measurement Timestamp Type

   o  Loss/Delay Measurement Control Code: Query Codes

   o  Loss/Delay Measurement Control Code: Response Codes

   o  MPLS Loss/Delay Measurement TLV Object



Andersson               Expires January 15, 2014                [Page 2]


Internet-Draft          Creating GACh registries               July 2013


   These registries are now moved into a new name space under the
   "Multiprotocol Label Switching Architecture" (MPLS) heading called
   "MPLS Generic Associated Channel Parameters".

   This is an update to RFC6374.

   The sub-section 9.2 in the IANA section of RFC6374 has a sentence
   that read:

   IANA has created a new "Measurement Timestamp Type" registry, with
   format and initial allocations as follows:

   This sentence is now changed to read:

   IANA has created a new "Measurement Timestamp Type" registry in the
   "MPLS Generic Associated Channel Parameters" name space, with format
   and initial allocations as follows:

   The sub-section 9.3 in the IANA section of RFC6374 has a sentence
   that read:

   IANA has created a new "MPLS Loss/Delay Measurement Control Code"
   registry.

   This sentence is now changed to read:

   IANA has created a new "MPLS Loss/Delay Measurement Control Code"
   registry in the "MPLS Generic Associated Channel Parameters" name
   space, with format and initial allocations as follows:

   The sub-section 9.4 in the IANA section of RFC6374 has a sentence
   that read:

   IANA has created a new "MPLS Loss/Delay Measurement TLV Object"
   registry, with format and initial allocations as follows:

   This sentence is now changed to read:

   IANA has created a new "MPLS Loss/Delay Measurement TLV Object"
   registry in the "MPLS Generic Associated Channel Parameters", with
   format and initial allocations as follows:

3.  IANA Considerations

   IANA is requested to take the actions listed below.

3.1.  Moving Loss/Delay registries




Andersson               Expires January 15, 2014                [Page 3]


Internet-Draft          Creating GACh registries               July 2013


   1.  To create a new name space called "MPLS Generic Associated
       Channel Parameters" under the "MPLS Architecture" heasding.

   2.  To move the "Measurement Timestamp Type", the "Loss/Delay
       Measurement Control Code: Query Codes", the "Loss/Delay
       Measurement Control Code: Response Codes" and the "MPLS Loss/
       Delay Measurement TLV Object" to the newly created "MPLS Generic
       Associated Channel Parameters" name space.

   3.  Not to change any of the values previously assigned in the
       registries that are moved.

   4.  The registries should be moved without any traces left in the
       "Multi-Protocol Label Switching (MPLS) Label Switched Paths
       (LSPs) Ping Parameters" name space.

4.  Security Considerations

   This document is about updating the IANA LSP Ping TLV and sub-TLV
   registries and it does not add any new security issues as compared to
   the RFC that specifies the protocol.

5.  Acknowledgements

6.  References

6.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC4379]  Kompella, K. and G. Swallow, "Detecting Multi-Protocol
              Label Switched (MPLS) Data Plane Failures", RFC 4379,
              February 2006.

   [RFC5586]  Bocci, M., Vigoureux, M., and S. Bryant, "MPLS Generic
              Associated Channel", RFC 5586, June 2009.

   [RFC6374]  Frost, D. and S. Bryant, "Packet Loss and Delay
              Measurement for MPLS Networks", RFC 6374, September 2011.

6.2.  Informative References

   [IANA-LSP-Ping]
              , "LSP Ping Parameters", , <http://www.iana.org/
              assignments/mpls-lsp-ping-parameters/mpls-lsp-ping-
              parameters.xml/>.




Andersson               Expires January 15, 2014                [Page 4]


Internet-Draft          Creating GACh registries               July 2013


Author's Address

   Loa Andersson
   Huawei

   Email: loa@mail01.huawei.com













































Andersson               Expires January 15, 2014                [Page 5]


Html markup produced by rfcmarkup 1.114, available from https://tools.ietf.org/tools/rfcmarkup/