datatracker.ietf.org
Sign in
Version 5.9.0, 2014-12-18
Report a bug

Link Bundling in MPLS Traffic Engineering (TE)
RFC 4201

Document type: RFC - Proposed Standard (October 2005; No errata)
Document stream: IETF
Last updated: 2013-03-02
Other versions: plain text, pdf, html

IETF State: WG Document
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: RFC 4201 (Proposed Standard)
Responsible AD: Alex Zinin
Send notices to: <swallow@cisco.com>, <loa@pi.se>

Network Working Group                                        K. Kompella
Request for Comments: 4201                                    Y. Rekhter
Updates: 3471, 3472, 3473                               Juniper Networks
Category: Standards Track                                      L. Berger
                                                          Movaz Networks
                                                            October 2005

             Link Bundling in MPLS Traffic Engineering (TE)

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 (2005).

Abstract

   For the purpose of Generalized Multi-Protocol Label Switching (GMPLS)
   signaling, in certain cases a combination of <link identifier, label>
   is not sufficient to unambiguously identify the appropriate resource
   used by a Label Switched Path (LSP).  Such cases are handled by using
   the link bundling construct, which is described in this document.
   This document updates the interface identification TLVs, which are
   defined in the GMPLS Signaling Functional Description.

Kompella, et al.            Standards Track                     [Page 1]
RFC 4201                Link Bundling in MPLS-TE            October 2005

Table of Contents

   1.  Introduction .................................................  2
       1.1.  Specification of Requirements ..........................  2
   2.  Link Bundling ................................................  3
       2.1.  Restrictions on Bundling ...............................  4
       2.2.  Routing Considerations .................................  4
       2.3.  Signaling Considerations ...............................  5
             2.3.1.  Interface Identification TLV Format ............  6
             2.3.2.  Errored Component Identification ...............  7
   3.  Traffic Engineering Parameters for Bundled Links .............  7
       3.1.  OSPF Link Type .........................................  7
       3.2.  OSPF Link ID ...........................................  7
       3.3.  Local and Remote Interface IP Address ..................  7
       3.4.  Local and Remote Identifiers ...........................  8
       3.5.  Traffic Engineering Metric .............................  8
       3.6.  Maximum Bandwidth ......................................  8
       3.7.  Maximum Reservable Bandwidth ...........................  8
       3.8.  Unreserved Bandwidth ...................................  8
       3.9.  Resource Classes (Administrative Groups) ...............  8
       3.10.  Maximum LSP Bandwidth .................................  8
   4.  Bandwidth Accounting .........................................  9
   5.  Security Considerations ......................................  9
   6.  IANA Considerations ..........................................  9
   7.  References ................................................... 10
       7.1.  Normative References ................................... 10
       7.2.  Informative References ................................. 11

1.  Introduction

   For the purpose of Generalized Multi-Protocol Label Switching (GMPLS)
   signaling, in certain cases a combination of <link identifier, label>
   is not sufficient to unambiguously identify the appropriate resource
   used by a Label Switched Path (LSP).  Such cases are handled by using
   the link bundling construct, which is described in this document.
   This document updates the interface identification TLVs, which are
   defined in the GMPLS Signaling Functional Description.

1.1.  Specification of Requirements

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

Kompella, et al.            Standards Track                     [Page 2]
RFC 4201                Link Bundling in MPLS-TE            October 2005

2.  Link Bundling

   As defined in [GMPLS-ROUTING], a traffic engineering (TE) link is a
   logical construct that represents a way to group/map information
   about certain physical resources (and their properties) that
   interconnect LSRs with information that is used by Constrained SPF

[include full document text]