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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-04-18
Replaced by draft-ietf-ccamp-lsp-attribute-ro
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
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
Show full document text