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

Versions: 00 01 02 03 draft-ietf-ccamp-lsp-attribute-ro

CCAMP                                                   C. Margaria, Ed.
Internet-Draft                                    Nokia Siemens Networks
Intended status: Standards Track                           D. Schroetter
Expires: October 20, 2012
                                                           G. Martinelli
                                                                   Cisco
                                                          April 18, 2012


                          LSP Attribute in ERO
               draft-margaria-ccamp-lsp-attribute-ero-00

Abstract

   LSP attributes can be specified or recorded for whole path, but they
   cannot be specified as part of an Explicit Route Object (ERO).  This
   document extend the semantic for RSVP ERO object with a new subobject
   to carry LSP attributes.

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 October 20, 2012.

Copyright Notice

   Copyright (c) 2012 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



Margaria, et al.        Expires October 20, 2012                [Page 1]


Internet-Draft         General ERO LSP parameters             April 2012


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


Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Contributing Authors . . . . . . . . . . . . . . . . . . .  3
     1.2.  Requirements Language  . . . . . . . . . . . . . . . . . .  3
   2.  Recording Attributes Per LSP . . . . . . . . . . . . . . . . .  4
     2.1.  Requirements . . . . . . . . . . . . . . . . . . . . . . .  4
     2.2.  ERO LSP Attribute Subobject  . . . . . . . . . . . . . . .  4
     2.3.  Procedures . . . . . . . . . . . . . . . . . . . . . . . .  5
   3.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  6
     3.1.  LSP Attribute ERO subobject  . . . . . . . . . . . . . . .  6
     3.2.  Existing LSP Attribute TLVs  . . . . . . . . . . . . . . .  6
       3.2.1.  Attribute Flags  . . . . . . . . . . . . . . . . . . .  6
       3.2.2.  Service ID TLV . . . . . . . . . . . . . . . . . . . .  6
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . .  8
   5.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . .  9
   6.  Normative References . . . . . . . . . . . . . . . . . . . . . 10
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11





























Margaria, et al.        Expires October 20, 2012                [Page 2]


Internet-Draft         General ERO LSP parameters             April 2012


1.  Introduction

   Generalized MPLS (GMPLS) Traffic Engineering (TE) Label Switched
   Paths (LSPs) can be route-constrained by making use of the Explicit
   Route (ERO) object and related sub-objects as defined in [RFC3209],
   [RFC3473], [RFC3477], [RFC4873], [RFC4874], [RFC5520] and [RFC5553].
   This document introduce a new ERO subobject to carry LSP_ATTRIBUTES
   defined in [RFC5420] within the EXPLICIT_ROUTE.

1.1.  Contributing Authors

1.2.  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.



































Margaria, et al.        Expires October 20, 2012                [Page 3]


Internet-Draft         General ERO LSP parameters             April 2012


2.  Recording Attributes Per LSP

2.1.  Requirements

   LSP attribute defined [RFC5420] should be expressed in ERO and SERO
   objects.

2.2.  ERO LSP Attribute Subobject

   The ERO LSP Attributes subobject may be carried in the ERO or SERO
   object if they are present.  The subobject uses the standard format
   of an ERO subobject.

   The length is variable and content MUST be the same as for the
   LSP_ATTRIBUTE object with Attributes TLVs.

   The ERO LSP attribute subobject is defined as follows:

      0                   1                   2                   3
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |L|    Type     |     Length    |    Reserved                 |R|
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                                                               |
      //                      Attributes TLVs                        //
      |                                                               |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


   See [RFC3209] for a description of L parameters.  The attributes TLV
   are encoded as defined in [RFC5420] section 3.

   Type  x TBD by IANA.

   Length  The Length contains the total length of the subobject in
      bytes, including the Type and Length fields.  The Length MUST be
      always divisible by 4.

   Reserved  Reserved, must be set to 0 when the subobject is inserted
      in the ERO, MUST NOT be changed when a node process the ERO and
      must be ignored on the node addressed by the preceding ERO
      subobjects

   R  This bit reflects the LSP_REQUIRED_ATTRIBUTE and LSP_ATTRIBUTE
      semantic.  When set indicates required LSP attributes to be
      processed by the node, when cleared the LSP attributes are not
      required as described in Section 2.3.




Margaria, et al.        Expires October 20, 2012                [Page 4]


Internet-Draft         General ERO LSP parameters             April 2012


   Attributes TLVs  as defined in [RFC5420] section 3.

2.3.  Procedures

   As described in [RFC3209] and [RFC3473] the ERO is managed as a list
   where each hop information starts with a subobject identifying an
   abstract node or link.  The LSP attribute subobject must be appended
   after the existing subobjects defined in [RFC3209], [RFC3473],
   [RFC3477], [RFC4873], [RFC4874], [RFC5520] and [RFC5553].  Several
   LSP attribute subobject MAY be present.

   If a node is processing an LSP attribute subobject and does not
   support handling of the subobject it will behave as described in
   [RFC3209] when an unrecognized ERO subobject is encountered.  This
   node will return a PathErr with error code "Routing Error" and error
   value "Bad EXPLICIT_ROUTE object" with the EXPLICIT_ROUTE object
   included, truncated (on the left) to the offending unrecognized
   subobject.

   When the R bit is set a node MUST examine the attribute TLV present
   in the subobject following the rules described in [RFC5420] section
   5.2.  When the R bit is not set a node MUST examine the attribute TLV
   present in the subobject following the rules described in [RFC5420]
   section 4.2.  If more than one ERO LSP attribute subobject having the
   R bit set is present, only the first one MUST be processed and the
   others SHOULD be ignored.  If more than one ERO LSP attribute subject
   having the R bit cleared is present, only the first one MUST be
   processed and the others SHOULD be ignored.























Margaria, et al.        Expires October 20, 2012                [Page 5]


Internet-Draft         General ERO LSP parameters             April 2012


3.  IANA Considerations

3.1.  LSP Attribute ERO subobject

   IANA is requested to make the following subobject allocations from
   the "EXPLICIT_ROUTE Subobject Type" registry.


                       Sub-object type TBA

                       Name            LSP attribute

                       Reference       This document

3.2.  Existing LSP Attribute TLVs

   IANA is request to add the following information for each TLV in the
   RSVP TLV type identifier registry.

   o  Whether allowed on LSP attribute ERO subobject

   The existing registry is modified for existing TLVs.

3.2.1.  Attribute Flags

   The new TLV type definition is as follow

   o  TLV Type = 1

   o  TLV Name = Attribute Flags TLV

   o  Allowed on LSP_ATTRIBUTES object

   o  Allowed on LSP_REQUIRED_ATTRIBUTES object

   o  Allowed on LSP attribute ERO subobject

3.2.2.  Service ID TLV

   The new TLV type definition is as follow

   o  TLV Type = 2

   o  TLV Name = Attribute Flags TLV

   o  Allowed on LSP_ATTRIBUTES object





Margaria, et al.        Expires October 20, 2012                [Page 6]


Internet-Draft         General ERO LSP parameters             April 2012


   o  Not allowed on LSP_REQUIRED_ATTRIBUTES object

   o  ? on LSP attribute ERO subobject
















































Margaria, et al.        Expires October 20, 2012                [Page 7]


Internet-Draft         General ERO LSP parameters             April 2012


4.  Security Considerations

   None.
















































Margaria, et al.        Expires October 20, 2012                [Page 8]


Internet-Draft         General ERO LSP parameters             April 2012


5.  Acknowledgments

   The authors would like to thanks Lou Berger for his directions and
   Attila Takacs for inspiring this.















































Margaria, et al.        Expires October 20, 2012                [Page 9]


Internet-Draft         General ERO LSP parameters             April 2012


6.  Normative References

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

   [RFC3209]  Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
              and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
              Tunnels", RFC 3209, December 2001.

   [RFC3473]  Berger, L., "Generalized Multi-Protocol Label Switching
              (GMPLS) Signaling Resource ReserVation Protocol-Traffic
              Engineering (RSVP-TE) Extensions", RFC 3473, January 2003.

   [RFC3477]  Kompella, K. and Y. Rekhter, "Signalling Unnumbered Links
              in Resource ReSerVation Protocol - Traffic Engineering
              (RSVP-TE)", RFC 3477, January 2003.

   [RFC4873]  Berger, L., Bryskin, I., Papadimitriou, D., and A. Farrel,
              "GMPLS Segment Recovery", RFC 4873, May 2007.

   [RFC4874]  Lee, CY., Farrel, A., and S. De Cnodder, "Exclude Routes -
              Extension to Resource ReserVation Protocol-Traffic
              Engineering (RSVP-TE)", RFC 4874, April 2007.

   [RFC5420]  Farrel, A., Papadimitriou, D., Vasseur, JP., and A.
              Ayyangarps, "Encoding of Attributes for MPLS LSP
              Establishment Using Resource Reservation Protocol Traffic
              Engineering (RSVP-TE)", RFC 5420, February 2009.

   [RFC5520]  Bradford, R., Vasseur, JP., and A. Farrel, "Preserving
              Topology Confidentiality in Inter-Domain Path Computation
              Using a Path-Key-Based Mechanism", RFC 5520, April 2009.

   [RFC5553]  Farrel, A., Bradford, R., and JP. Vasseur, "Resource
              Reservation Protocol (RSVP) Extensions for Path Key
              Support", RFC 5553, May 2009.















Margaria, et al.        Expires October 20, 2012               [Page 10]


Internet-Draft         General ERO LSP parameters             April 2012


Authors' Addresses

   Cyril Margaria (editor)
   Nokia Siemens Networks
   St Martin Strasse 76
   Munich,   81541
   Germany

   Phone: +49 89 5159 16934
   Email: cyril.margaria@nsn.com


   Dirk Schroetter
   Moritzstrasse 18
   Wiesbaden,   65185
   DE

   Phone: +49 611 18179920
   Email: dschroetter@googlemail.com


   Giovanni Martinelli
   Cisco
   via Philips 12
   Monza  20900
   IT

   Phone: +39 039 209 2044
   Email: giomarti@cisco.com






















Margaria, et al.        Expires October 20, 2012               [Page 11]


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