North-Bound Distribution of Link-State and TE Information using BGP
draft-ietf-idr-ls-distribution-01

The information below is for an old version of the document
Document Type Active Internet-Draft (idr WG)
Last updated 2012-10-22
Replaces draft-gredler-idr-ls-distribution
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Inter-Domain Routing                                          H. Gredler
Internet-Draft                                    Juniper Networks, Inc.
Intended status: Standards Track                               J. Medved
Expires: April 25, 2013                                       S. Previdi
                                                     Cisco Systems, Inc.
                                                               A. Farrel
                                                  Juniper Networks, Inc.
                                                                  S. Ray
                                                     Cisco Systems, Inc.
                                                        October 22, 2012

  North-Bound Distribution of Link-State and TE Information using BGP
                   draft-ietf-idr-ls-distribution-01

Abstract

   In a number of environments, a component external to a network is
   called upon to perform computations based on the network topology and
   current state of the connections within the network, including
   traffic engineering information.  This is information typically
   distributed by IGP routing protocols within the network

   This document describes a mechanism by which links state and traffic
   engineering information can be collected from networks and shared
   with external components using the BGP routing protocol.  This is
   achieved using a new BGP Network Layer Reachability Information
   (NLRI) encoding format.  The mechanism is applicable to physical and
   virtual links.  The mechanism described is subject to policy control.

   Applications of this technique include Application Layer Traffic
   Optimization (ALTO) servers, and Path Computation Elements (PCEs).

Requirements Language

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

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

Gredler, et al.          Expires April 25, 2013                 [Page 1]
Internet-Draft   Link-State Info Distribution using BGP     October 2012

   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 April 25, 2013.

Copyright Notice

   Copyright (c) 2012 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
   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.

Gredler, et al.          Expires April 25, 2013                 [Page 2]
Internet-Draft   Link-State Info Distribution using BGP     October 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Motivation and Applicability . . . . . . . . . . . . . . . . .  5
     2.1.  MPLS-TE with PCE . . . . . . . . . . . . . . . . . . . . .  5
     2.2.  ALTO Server Network API  . . . . . . . . . . . . . . . . .  7
   3.  Carrying Link State Information in BGP . . . . . . . . . . . .  8
     3.1.  TLV Format . . . . . . . . . . . . . . . . . . . . . . . .  8
     3.2.  The Link State NLRI  . . . . . . . . . . . . . . . . . . .  9
       3.2.1.  Node Descriptors . . . . . . . . . . . . . . . . . . . 11
       3.2.2.  Link Descriptors . . . . . . . . . . . . . . . . . . . 15
       3.2.3.  The Prefix NLRI  . . . . . . . . . . . . . . . . . . . 16
     3.3.  The LINK_STATE Attribute . . . . . . . . . . . . . . . . . 16
       3.3.1.  Link Attribute TLVs  . . . . . . . . . . . . . . . . . 16
       3.3.2.  Node Attribute TLVs  . . . . . . . . . . . . . . . . . 20
       3.3.3.  Prefix Attributes TLVs . . . . . . . . . . . . . . . . 23
Show full document text