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

The information below is for an old version of the document
Document Type Active Internet-Draft (ccamp WG)
Last updated 2014-02-13
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                                                   Juniper
Intended status: Standards Track                           G. Martinelli
Expires: August 17, 2014                                           Cisco
                                                                S. Balls
                                                               B. Wright
                                                              Metaswitch
                                                       February 13, 2014

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

Abstract

   RFC5420 extends RSVP-TE to specify or record generic attributes which
   apply to the whole of the path of an LSP.  This document proposes an
   extension to the RSVP ERO and RRO objects to allow it to specify or
   record generic attributes which apply to a given 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 17, 2014.

Copyright Notice

   Copyright (c) 2014 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 17, 2014                [Page 1]
Internet-Draft         General ERO LSP parameters          February 2014

   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
     1.1.  Contributing Authors  . . . . . . . . . . . . . . . . . .   3
     1.2.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Specifying Hop Attribute  . . . . . . . . . . . . . . . . . .   3
     3.1.  ERO_HOP_ATTRIBUTE subobject . . . . . . . . . . . . . . .   3
     3.2.  HOP Attributes TLVs . . . . . . . . . . . . . . . . . . .   4
     3.3.  Procedures  . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Recording Hop attribute . . . . . . . . . . . . . . . . . . .   5
     4.1.  RRO_HOP_ATTRIBUTE subobject . . . . . . . . . . . . . . .   5
     4.2.  Procedures  . . . . . . . . . . . . . . . . . . . . . . .   6
       4.2.1.  Subobject presence rule . . . . . . . . . . . . . . .   6
       4.2.2.  Reporting Compliance with ERO Hop Attributes  . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   7
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

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].
   Several documents have identified the need for attributes that can be
   targeted at specific hops in the path of an LSP, including [RFC6163],
   [I-D.ietf-ccamp-wson-signaling],
   [I-D.dong-ccamp-rsvp-te-mpls-tp-li-lb] or
   [I-D.ali-ccamp-rc-objective-function-metric-bound],. This document
   provides a generic mechanism for use by these other documents.

   RSVP already supports generic extension of LSP attributes in
   [RFC5420].  In order to support current and future ERO constraint
   extensions this document defines a mechanism to define per-Hop
   attributes.

Margaria, et al.         Expires August 17, 2014                [Page 2]
Internet-Draft         General ERO LSP parameters          February 2014
Show full document text