Constraint-Based LSP Setup using LDP
RFC 3212

Document Type RFC - Proposed Standard (January 2002; No errata)
Updated by RFC 7358, RFC 3468
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state RFC 3212 (Proposed Standard)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group               B. Jamoussi, Editor, Nortel Networks
Request for Comments: 3212                       L. Andersson, Utfors AB
Category: Standards Track                    R. Callon, Juniper Networks
                                           R. Dantu, Netrake Corporation
                                                    L. Wu, Cisco Systems
                                         P. Doolan, OTB Consulting Corp.
                                                              T. Worster
                                                   N. Feldman, IBM Corp.
                                             A. Fredette, ANF Consulting
                                                M. Girish, Atoga Systems
                                                      E. Gray, Sandburst
                                        J. Heinanen, Song Networks, Inc.
                                      T. Kilty, Newbridge Networks, Inc.
                                               A. Malis, Vivace Networks
                                                            January 2002

                 Constraint-Based LSP Setup using LDP

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2002).  All Rights Reserved.

Abstract

   This document specifies mechanisms and TLVs (Type/Length/Value) for
   support of CR-LSPs (constraint-based routed Label Switched Path)
   using LDP (Label Distribution Protocol).

   This specification proposes an end-to-end setup mechanism of a CR-LSP
   initiated by the ingress LSR (Label Switching Router).  We also
   specify mechanisms to provide means for reservation of resources
   using LDP.

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

Jamoussi, et al.            Standards Track                     [Page 1]
RFC 3212          Constraint-Based LSP Setup using LDP      January 2002

Table of Contents

   1. Introduction....................................................3
   2. Constraint-based Routing Overview...............................4
   2.1 Strict and Loose Explicit Routes...............................5
   2.2 Traffic Characteristics........................................5
   2.3 Preemption.....................................................5
   2.4 Route Pinning..................................................6
   2.5 Resource Class.................................................6
   3. Solution Overview...............................................6
   3.1 Required Messages and TLVs.....................................7
   3.2 Label Request Message..........................................7
   3.3 Label Mapping Message..........................................9
   3.4 Notification Message..........................................10
   3.5 Release , Withdraw, and Abort Messages........................11
   4. Protocol Specification.........................................11
   4.1 Explicit Route TLV (ER-TLV)...................................11
   4.2 Explicit Route Hop TLV (ER-Hop TLV)...........................12
   4.3 Traffic Parameters TLV........................................13
   4.3.1 Semantics...................................................15
   4.3.1.1 Frequency.................................................15
   4.3.1.2 Peak Rate.................................................16
   4.3.1.3 Committed Rate............................................16
   4.3.1.4 Excess Burst Size.........................................16
   4.3.1.5 Peak Rate Token Bucket....................................16
   4.3.1.6 Committed Data Rate Token Bucket..........................17
   4.3.1.7 Weight....................................................18
   4.3.2 Procedures..................................................18
   4.3.2.1 Label Request Message.....................................18
   4.3.2.2 Label Mapping Message.....................................18
   4.3.2.3 Notification Message......................................19
   4.4 Preemption TLV................................................19
   4.5 LSPID TLV.....................................................20
   4.6 Resource Class (Color) TLV....................................21
   4.7 ER-Hop semantics..............................................22
Show full document text