BGP-LS Advertisement of IGP Traffic Engineering Performance Metric Extensions
draft-ietf-idr-te-pm-bgp-06

Document Type Active Internet-Draft (idr WG)
Last updated 2017-06-25
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Networking Working Group                                 S. Previdi, Ed.
Internet-Draft                                       Cisco Systems, Inc.
Intended status: Standards Track                                   Q. Wu
Expires: December 27, 2017                                        Huawei
                                                              H. Gredler
                                                                  S. Ray
                                                             J. Tantsura
                                                              Individual
                                                             C. Filsfils
                                                             L. Ginsberg
                                                     Cisco Systems, Inc.
                                                           June 25, 2017

   BGP-LS Advertisement of IGP Traffic Engineering Performance Metric
                               Extensions
                      draft-ietf-idr-te-pm-bgp-06

Abstract

   This document defines new BGP-LS TLVs in order to carry the IGP
   Traffic Engineering Extensions defined in IS-IS and OSPF protocols.

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

   In this document, these words will appear with that interpretation
   only when in ALL CAPS.  Lower case uses of these words are not to be
   interpreted as carrying RFC-2119 significance.

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

Previdi, et al.         Expires December 27, 2017               [Page 1]
Internet-Draft BGP-LS Advertisement of Performance Metric      June 2017

   This Internet-Draft will expire on December 27, 2017.

Copyright Notice

   Copyright (c) 2017 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.  Link Attribute TLVs for TE Metric Extensions  . . . . . . . .   3
   3.  TLV Details . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Unidirectional Link Delay TLV . . . . . . . . . . . . . .   3
     3.2.  Min/Max Unidirectional Link Delay TLV . . . . . . . . . .   4
     3.3.  Unidirectional Delay Variation TLV  . . . . . . . . . . .   4
     3.4.  Unidirectional Link Loss TLV  . . . . . . . . . . . . . .   5
     3.5.  Unidirectional Residual Bandwidth TLV . . . . . . . . . .   5
     3.6.  Unidirectional Available Bandwidth TLV  . . . . . . . . .   5
     3.7.  Unidirectional Utilized Bandwidth TLV . . . . . . . . . .   6
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   BGP-LS ([RFC7752]) defines NLRI and attributes in order to carry
   link-state information.  New BGP-LS Link-Attribute TLVs are required
   in order to carry the Traffic Engineering Metric Extensions defined
   in [RFC7810] and [RFC7471].
Show full document text