datatracker.ietf.org
Sign in
Version 5.6.3, 2014-09-19
Report a bug

BGP Traffic Engineering Attribute
RFC 5543

Network Working Group                                     H. Ould-Brahim
Request for Comments: 5543                               Nortel Networks
Category: Standards Track                                       D. Fedyk
                                                          Alcatel-Lucent
                                                              Y. Rekhter
                                                        Juniper Networks
                                                                May 2009

                   BGP Traffic Engineering Attribute

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) 2009 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 in effect on the date of
   publication of this document (http://trustee.ietf.org/license-info).
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.

Abstract

   This document defines a new BGP attribute, the Traffic Engineering
   attribute, that enables BGP to carry Traffic Engineering information.

   The scope and applicability of this attribute currently excludes its
   use for non-VPN reachability information.

Ould-Brahim, et al.         Standards Track                     [Page 1]
RFC 5543                    BGP TE Attribute                    May 2009

1.  Introduction

   In certain cases (e.g., Layer-1 VPNs (L1VPNs) [RFC5195]), it may be
   useful to augment the VPN reachability information carried in BGP
   with Traffic Engineering information.

   This document defines a new BGP attribute, the Traffic Engineering
   attribute, that enables BGP [RFC4271] to carry Traffic Engineering
   information.

   Section 4 of [RFC5195] describes one possible usage of this
   attribute.

   The scope and applicability of this attribute currently excludes its
   use for non-VPN reachability information.

   Procedures for modifying the Traffic Engineering attribute, when
   re-advertising a route that carries such an attribute, are outside
   the scope of this document.

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

3.  Traffic Engineering Attribute

   The Traffic Engineering attribute is an optional, non-transitive BGP
   attribute.

   The information carried in this attribute is identical to what is
   carried in the Interface Switching Capability Descriptor, as
   specified in [RFC4203] and [RFC5307].

   The attribute contains one or more of the following:

Ould-Brahim, et al.         Standards Track                     [Page 2]
RFC 5543                    BGP TE Attribute                    May 2009

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      | Switching Cap |   Encoding    |           Reserved            |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                  Max LSP Bandwidth at priority 0              |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                  Max LSP Bandwidth at priority 1              |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                  Max LSP Bandwidth at priority 2              |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                  Max LSP Bandwidth at priority 3              |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                  Max LSP Bandwidth at priority 4              |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                  Max LSP Bandwidth at priority 5              |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                  Max LSP Bandwidth at priority 6              |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

[include full document text]