--- 1/draft-ietf-idr-te-pm-bgp-01.txt 2015-01-04 22:14:49.833791323 -0800 +++ 2/draft-ietf-idr-te-pm-bgp-02.txt 2015-01-04 22:14:49.857791910 -0800 @@ -1,26 +1,26 @@ IDR Working Group Q. Wu Internet-Draft Huawei Intended status: Standards Track S. Previdi -Expires: January 5, 2015 Cisco +Expires: July 8, 2015 Cisco H. Gredler Juniper S. Ray Cisco J. Tantsura Ericsson - July 4, 2014 + January 4, 2015 BGP attribute for North-Bound Distribution of Traffic Engineering (TE) performance Metrics - draft-ietf-idr-te-pm-bgp-01 + draft-ietf-idr-te-pm-bgp-02 Abstract In order to populate network performance information like link latency, latency variation, packet loss and bandwidth into Traffic Engineering Database(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, available bandwidth and utilized bandwidth ). @@ -33,25 +33,25 @@ 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 5, 2015. + This Internet-Draft will expire on July 8, 2015. Copyright Notice - Copyright (c) 2014 IETF Trust and the persons identified as the + 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 @@ -59,27 +59,29 @@ Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Conventions used in this document . . . . . . . . . . . . . . 3 3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.1. MPLS-TE with H-PCE . . . . . . . . . . . . . . . . . . . 3 3.2. ALTO Server Network API . . . . . . . . . . . . . . . . . 4 4. Carrying TE Performance information in BGP . . . . . . . . . 5 5. Attribute TLV Details . . . . . . . . . . . . . . . . . . . . 6 - 6. Security Considerations . . . . . . . . . . . . . . . . . . . 7 - 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 - 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 - 8.1. Normative References . . . . . . . . . . . . . . . . . . 7 - 8.2. Informative References . . . . . . . . . . . . . . . . . 8 - Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 8 - A.1. draft-ietf-idr-te-pm-bgp-00 . . . . . . . . . . . . . . . 8 + 6. Manageability Considerations . . . . . . . . . . . . . . . . 7 + 7. Security Considerations . . . . . . . . . . . . . . . . . . . 7 + 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 + 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 + 9.1. Normative References . . . . . . . . . . . . . . . . . . 8 + 9.2. Informative References . . . . . . . . . . . . . . . . . 8 + Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 9 + A.1. draft-ietf-idr-te-pm-bgp-00 . . . . . . . . . . . . . . . 9 + A.2. draft-ietf-idr-te-pm-bgp-02 . . . . . . . . . . . . . . . 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-pce-pcep- service-aware]. [I.D-ietf-idr-ls-distribution] describes a mechanism @@ -279,90 +281,103 @@ | | | | | | xxxx | Unidirectional | 22/xx | [ISIS-TE- | | |Available Bandwidth | | METRIC]/4.6 | | | | | | | xxxx | Unidirectional | 22/xx | [ISIS-TE- | | |Utilized Bandwidth | | METRIC]/4.7 | +------------+---------------------+--------------+-----------------+ Table 1: Link Attribute TLVs -6. Security Considerations +6. Manageability Considerations + + Manageability Considerations described in section 6.2 of [I-D.ietf- + idr-ls-distribution] can be applied to Traffic Engineering (TE) + performance Metrics as well. + +7. Security Considerations This document does not introduce security issues beyond those discussed in [I.D-ietf-idr-ls-distribution] and [RFC4271]. -7. IANA Considerations +8. IANA Considerations IANA maintains the registry for the TLVs. BGP TE Performance TLV will require one new type code per TLV defined in this document. -8. References +9. References -8.1. Normative References +9.1. Normative References [I-D.ietf-idr-ls-distribution] Gredler, H., "North-Bound Distribution of Link-State and TE Information using BGP", ID draft-ietf-idr-ls- - distribution-03, May 2013. + distribution-07, November 2014. [I-D.ietf-pce-pcep-service-aware] Dhruv, D., "Extensions to the Path Computation Element Communication Protocol (PCEP) to compute service aware Label Switched Path (LSP)", ID draft-ietf-pce-pcep- - service-aware-01, July 2013. + service-aware-06, December 2014. [ISIS-TE-METRIC] Giacalone, S., "ISIS Traffic Engineering (TE) Metric - Extensions", ID draft-ietf-isis-te-metric-extensions-00, - June 2013. + Extensions", ID draft-ietf-isis-te-metric-extensions-04, + October 2014. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", March 1997. [RFC4271] Rekhter, Y., "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, January 2006. [RFC5305] Li, T., "IS-IS Extensions for Traffic Engineering", RFC 5305, October 2008. -8.2. Informative References +9.2. Informative References [ALTO] Yang, Y., "ALTO Protocol", ID http://tools.ietf.org/html/draft-ietf-alto-protocol-16, May 2013. [I.D-ietf-pce-hierarchy-extensions] Zhang, F., Zhao, Q., Gonzalez de Dios, O., Casellas, R., and D. King, "Extensions to Path Computation Element Communication Protocol (PCEP) for Hierarchical Path Computation Elements (PCE)", ID draft-ietf-pce-hierarchy- - extensions-00, August 2013. + extensions-01, February 2014. [RFC4655] Farrel, A., "A Path Computation Element (PCE)-Based Architecture", RFC 4655, August 2006. Appendix A. Change Log Note to the RFC-Editor: please remove this section prior to publication as an RFC. A.1. draft-ietf-idr-te-pm-bgp-00 The following are the major changes compared to previous version draft-wu-idr-te-pm-bgp-03: o Update PCE case in section 3.1. o Add some texts in section 1 and section 4 to clarify from where to distribute pm info and measurement interval and method. +A.2. draft-ietf-idr-te-pm-bgp-02 + + The following are the major changes compared to previous version + draft-wu-idr-te-pm-bgp-03: + + o Some Editorial changes. + Authors' Addresses Qin Wu Huawei 101 Software Avenue, Yuhua District Nanjing, Jiangsu 210012 China Email: bill.wu@huawei.com