Distribution of MPLS Traffic Engineering (TE) LSP State using BGP
draft-ietf-idr-te-lsp-distribution-02

The information below is for an old version of the document
Document Type Active Internet-Draft (idr WG)
Last updated 2015-01-05
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd Jie Dong
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                            J. Dong
Internet-Draft                                                   M. Chen
Intended status: Standards Track                     Huawei Technologies
Expires: July 9, 2015                                         H. Gredler
                                                  Juniper Networks, Inc.
                                                              S. Previdi
                                                     Cisco Systems, Inc.
                                                             J. Tantsura
                                                                Ericsson
                                                         January 5, 2015

   Distribution of MPLS Traffic Engineering (TE) LSP State using BGP
                 draft-ietf-idr-te-lsp-distribution-02

Abstract

   This document describes a mechanism to collect the Traffic
   Engineering (TE) LSP information using BGP.  Such information can be
   used by external components for path reoptimization, service
   placement and network visualization.

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

   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 July 9, 2015.

Dong, et al.              Expires July 9, 2015                  [Page 1]
Internet-Draft  MPLS TE LSP State Distribution using BGP    January 2015

Copyright Notice

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Carrying LSP State Information in BGP . . . . . . . . . . . .   4
     2.1.  LSP Identifier Information  . . . . . . . . . . . . . . .   4
     2.2.  LSP State Information . . . . . . . . . . . . . . . . . .   5
   3.  Operational Considerations  . . . . . . . . . . . . . . . . .   7
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   In some network environments, the states of established Multi-
   Protocol Label Switching (MPLS) Traffic Engineering (TE) Label
   Switched Paths (LSPs) in the network are required by some components
   external to the network domain.  Usually this information is directly
   maintained by the ingress Label Edge Routers (LERs) of the MPLS TE
   LSPs.

   One example of using the LSP information is stateful Path Computation
   Element (PCE) [I-D.ietf-pce-stateful-pce], which could provide
   benefits in path reoptimization . While some extensions are proposed
   in Path Computation Element Communication Protocol (PCEP) for the
   Path Computation Clients (PCCs) to report the LSP states to the PCE,
   this mechanism may not be applicable in a management-based PCE
   architecture as specified in section 5.5 of [RFC4655].  As
   illustrated in the figure below, the PCC is not an LSR in the routing
   domain, thus the head-end nodes of the TE-LSP may not implement the

Dong, et al.              Expires July 9, 2015                  [Page 2]
Internet-Draft  MPLS TE LSP State Distribution using BGP    January 2015

   PCEP protocol.  In this case some general mechanism to collect the
Show full document text