RFC 3212 (rfc3212) - Page 1 of 42

Constraint-Based LSP Setup using LDP

Alternative Format: Original Text Document
Next >
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
Next >