BGP attribute for North-Bound Distribution of Traffic Engineering (TE) performance Metric
draft-wu-idr-te-pm-bgp-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-07-12
Replaced by draft-ietf-idr-te-pm-bgp, rfc8571
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Inter-Domain Routing Working Group                                 Q. Wu
Internet-Draft                                                   D. Wang
Intended status: Standards Track                                  Huawei
Expires: January 13, 2014                                  July 12, 2013

 BGP attribute for North-Bound Distribution of Traffic Engineering (TE)
                           performance Metric
                       draft-wu-idr-te-pm-bgp-00

Abstract

   In order to populate network performance information like link
   latency, latency variation and packet loss into TED and ALTO server,
   this document describes extensions to BGP protocol, that can be used
   to distribute network performance information (such as link delay,
   delay variation, packet loss, residual bandwidth, and available
   bandwidth,link utilization, channel throughput).

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 January 13, 2014.

Copyright Notice

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

Wu & Wang               Expires January 13, 2014                [Page 1]
Internet-Draft           BGP for TE performance                July 2013

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions used in this document . . . . . . . . . . . . . .   3
   3.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  MPLS-TE with PCE  . . . . . . . . . . . . . . . . . . . .   3
     3.2.  ALTO Server Network API . . . . . . . . . . . . . . . . .   3
   4.  Carrying TE Performance information in BGP  . . . . . . . . .   4
   5.  Attribute TLV Details . . . . . . . . . . . . . . . . . . . .   5
     5.1.  Link Utilization TLV  . . . . . . . . . . . . . . . . . .   6
     5.2.  Channel Throughput TLV  . . . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   As specified in [RFC4655],a Path Computation Element (PCE) is an
   entity that is capable of computing a network path or route based on
   a network graph, and of applying computational constraints during the
   computation In order to compute an end to end path, the PCE needs to
   have a unified view of the overall topology.  [I.D-ietf-idr-ls-
   distribution] 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
   mechanism can be used by both PCE and ALTO server to gather
   information about the topologies and capabilities of the network.

   With the growth of network virtualization technology, the needs for
   inter-connecting between various overlay technologies (e.g.
   Enterprise BGP/MPLS IP VPNs) in the Wide Area Network (WAN) become
   important.  The Network performance or QoS requirements such as
   latency, limited bandwidth, packet loss, and jitter, are all critical
   factors that must be taken into account in path computation and
   selection to establish segment overlay tunnel between overlay nodes
   and stitch them together to compute end to end path.

Wu & Wang               Expires January 13, 2014                [Page 2]
Internet-Draft           BGP for TE performance                July 2013

   In order to populate network performance information like link
Show full document text