LSP Attribute in ERO
draft-ietf-ccamp-lsp-attribute-ro-00

The information below is for an old version of the document
Document Type Active Internet-Draft (ccamp WG)
Last updated 2013-02-12
Replaces draft-margaria-ccamp-lsp-attribute-ero
Replaced by draft-ietf-teas-lsp-attribute-ro, rfc7570
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
CCAMP                                                   C. Margaria, Ed.
Internet-Draft                                    Nokia Siemens Networks
Intended status: Standards Track                           G. Martinelli
Expires: August 11, 2013                                           Cisco
                                                                S. Balls
                                                               B. Wright
                                                              Metaswitch
                                                       February 07, 2013

                          LSP Attribute in ERO
                  draft-ietf-ccamp-lsp-attribute-ro-00

Abstract

   LSP attributes can be specified or recorded for whole path, but they
   cannot be targeted to a specific hop.  This document proposes
   alternative ways to extend the semantic for RSVP ERO object to target
   LSP attributes to a specific hop.

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 August 11, 2013.

Copyright Notice

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

Margaria, et al.         Expires August 11, 2013                [Page 1]
Internet-Draft         General ERO LSP parameters          February 2013

   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 . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Contributing Authors . . . . . . . . . . . . . . . . . . .  3
     1.2.  Requirements Language  . . . . . . . . . . . . . . . . . .  3
   2.  Requirements . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Solutions  . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     3.1.  Non solution . . . . . . . . . . . . . . . . . . . . . . .  5
     3.2.  Extended ERO Object  . . . . . . . . . . . . . . . . . . .  5
       3.2.1.  Semantic of the Extended ERO object  . . . . . . . . .  5
       3.2.2.  Procedures . . . . . . . . . . . . . . . . . . . . . .  5
       3.2.3.  Subobjects . . . . . . . . . . . . . . . . . . . . . .  6
       3.2.4.  Processing . . . . . . . . . . . . . . . . . . . . . .  9
   4.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 11
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . . 12
   6.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 13
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
     7.1.  Normative References . . . . . . . . . . . . . . . . . . . 14
     7.2.  Informative References . . . . . . . . . . . . . . . . . . 14
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15

Margaria, et al.         Expires August 11, 2013                [Page 2]
Internet-Draft         General ERO LSP parameters          February 2013

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 proposes mechanisms to target LSP attributes at a
   specific hop.  This document presents several solutions for
   discussion, final document will contains only one document after WG
   consensus.

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

Margaria, et al.         Expires August 11, 2013                [Page 3]
Internet-Draft         General ERO LSP parameters          February 2013

2.  Requirements
Show full document text