draft-ietf-idr-te-pm-bgp-01.txt   draft-ietf-idr-te-pm-bgp-02.txt 
IDR Working Group Q. Wu IDR Working Group Q. Wu
Internet-Draft Huawei Internet-Draft Huawei
Intended status: Standards Track S. Previdi Intended status: Standards Track S. Previdi
Expires: January 5, 2015 Cisco Expires: July 8, 2015 Cisco
H. Gredler H. Gredler
Juniper Juniper
S. Ray S. Ray
Cisco Cisco
J. Tantsura J. Tantsura
Ericsson Ericsson
July 4, 2014 January 4, 2015
BGP attribute for North-Bound Distribution of Traffic Engineering (TE) BGP attribute for North-Bound Distribution of Traffic Engineering (TE)
performance Metrics performance Metrics
draft-ietf-idr-te-pm-bgp-01 draft-ietf-idr-te-pm-bgp-02
Abstract Abstract
In order to populate network performance information like link In order to populate network performance information like link
latency, latency variation, packet loss and bandwidth into Traffic latency, latency variation, packet loss and bandwidth into Traffic
Engineering Database(TED) and ALTO server, this document describes Engineering Database(TED) and ALTO server, this document describes
extensions to BGP protocol, that can be used to distribute network extensions to BGP protocol, that can be used to distribute network
performance information (such as link delay, delay variation, packet performance information (such as link delay, delay variation, packet
loss, residual bandwidth, available bandwidth and utilized bandwidth loss, residual bandwidth, available bandwidth and utilized bandwidth
). ).
skipping to change at page 1, line 44 skipping to change at page 1, line 44
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." 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 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. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 29 skipping to change at page 2, line 29
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions used in this document . . . . . . . . . . . . . . 3 2. Conventions used in this document . . . . . . . . . . . . . . 3
3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. MPLS-TE with H-PCE . . . . . . . . . . . . . . . . . . . 3 3.1. MPLS-TE with H-PCE . . . . . . . . . . . . . . . . . . . 3
3.2. ALTO Server Network API . . . . . . . . . . . . . . . . . 4 3.2. ALTO Server Network API . . . . . . . . . . . . . . . . . 4
4. Carrying TE Performance information in BGP . . . . . . . . . 5 4. Carrying TE Performance information in BGP . . . . . . . . . 5
5. Attribute TLV Details . . . . . . . . . . . . . . . . . . . . 6 5. Attribute TLV Details . . . . . . . . . . . . . . . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . 7 6. Manageability Considerations . . . . . . . . . . . . . . . . 7
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 7. Security Considerations . . . . . . . . . . . . . . . . . . . 7
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
8.1. Normative References . . . . . . . . . . . . . . . . . . 7 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . 8 9.1. Normative References . . . . . . . . . . . . . . . . . . 8
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 8 9.2. Informative References . . . . . . . . . . . . . . . . . 8
A.1. draft-ietf-idr-te-pm-bgp-00 . . . . . . . . . . . . . . . 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 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
As specified in [RFC4655],a Path Computation Element (PCE) is an As specified in [RFC4655],a Path Computation Element (PCE) is an
entity that is capable of computing a network path or route based on entity that is capable of computing a network path or route based on
a network graph, and of applying computational constraints during the a network graph, and of applying computational constraints during the
computation. In order to compute an end to end path, the PCE needs 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- 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 service-aware]. [I.D-ietf-idr-ls-distribution] describes a mechanism
skipping to change at page 7, line 33 skipping to change at page 7, line 33
| | | | | | | | | |
| xxxx | Unidirectional | 22/xx | [ISIS-TE- | | xxxx | Unidirectional | 22/xx | [ISIS-TE- |
| |Available Bandwidth | | METRIC]/4.6 | | |Available Bandwidth | | METRIC]/4.6 |
| | | | | | | | | |
| xxxx | Unidirectional | 22/xx | [ISIS-TE- | | xxxx | Unidirectional | 22/xx | [ISIS-TE- |
| |Utilized Bandwidth | | METRIC]/4.7 | | |Utilized Bandwidth | | METRIC]/4.7 |
+------------+---------------------+--------------+-----------------+ +------------+---------------------+--------------+-----------------+
Table 1: Link Attribute TLVs 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 This document does not introduce security issues beyond those
discussed in [I.D-ietf-idr-ls-distribution] and [RFC4271]. 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 IANA maintains the registry for the TLVs. BGP TE Performance TLV
will require one new type code per TLV defined in this document. 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] [I-D.ietf-idr-ls-distribution]
Gredler, H., "North-Bound Distribution of Link-State and Gredler, H., "North-Bound Distribution of Link-State and
TE Information using BGP", ID draft-ietf-idr-ls- TE Information using BGP", ID draft-ietf-idr-ls-
distribution-03, May 2013. distribution-07, November 2014.
[I-D.ietf-pce-pcep-service-aware] [I-D.ietf-pce-pcep-service-aware]
Dhruv, D., "Extensions to the Path Computation Element Dhruv, D., "Extensions to the Path Computation Element
Communication Protocol (PCEP) to compute service aware Communication Protocol (PCEP) to compute service aware
Label Switched Path (LSP)", ID draft-ietf-pce-pcep- Label Switched Path (LSP)", ID draft-ietf-pce-pcep-
service-aware-01, July 2013. service-aware-06, December 2014.
[ISIS-TE-METRIC] [ISIS-TE-METRIC]
Giacalone, S., "ISIS Traffic Engineering (TE) Metric Giacalone, S., "ISIS Traffic Engineering (TE) Metric
Extensions", ID draft-ietf-isis-te-metric-extensions-00, Extensions", ID draft-ietf-isis-te-metric-extensions-04,
June 2013. October 2014.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", March 1997. Requirement Levels", March 1997.
[RFC4271] Rekhter, Y., "A Border Gateway Protocol 4 (BGP-4)", RFC [RFC4271] Rekhter, Y., "A Border Gateway Protocol 4 (BGP-4)", RFC
4271, January 2006. 4271, January 2006.
[RFC5305] Li, T., "IS-IS Extensions for Traffic Engineering", RFC [RFC5305] Li, T., "IS-IS Extensions for Traffic Engineering", RFC
5305, October 2008. 5305, October 2008.
8.2. Informative References 9.2. Informative References
[ALTO] Yang, Y., "ALTO Protocol", ID [ALTO] Yang, Y., "ALTO Protocol", ID
http://tools.ietf.org/html/draft-ietf-alto-protocol-16, http://tools.ietf.org/html/draft-ietf-alto-protocol-16,
May 2013. May 2013.
[I.D-ietf-pce-hierarchy-extensions] [I.D-ietf-pce-hierarchy-extensions]
Zhang, F., Zhao, Q., Gonzalez de Dios, O., Casellas, R., Zhang, F., Zhao, Q., Gonzalez de Dios, O., Casellas, R.,
and D. King, "Extensions to Path Computation Element and D. King, "Extensions to Path Computation Element
Communication Protocol (PCEP) for Hierarchical Path Communication Protocol (PCEP) for Hierarchical Path
Computation Elements (PCE)", ID draft-ietf-pce-hierarchy- 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 [RFC4655] Farrel, A., "A Path Computation Element (PCE)-Based
Architecture", RFC 4655, August 2006. Architecture", RFC 4655, August 2006.
Appendix A. Change Log Appendix A. Change Log
Note to the RFC-Editor: please remove this section prior to Note to the RFC-Editor: please remove this section prior to
publication as an RFC. publication as an RFC.
A.1. draft-ietf-idr-te-pm-bgp-00 A.1. draft-ietf-idr-te-pm-bgp-00
The following are the major changes compared to previous version The following are the major changes compared to previous version
draft-wu-idr-te-pm-bgp-03: draft-wu-idr-te-pm-bgp-03:
o Update PCE case in section 3.1. o Update PCE case in section 3.1.
o Add some texts in section 1 and section 4 to clarify from where to o Add some texts in section 1 and section 4 to clarify from where to
distribute pm info and measurement interval and method. 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 Authors' Addresses
Qin Wu Qin Wu
Huawei Huawei
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012 Nanjing, Jiangsu 210012
China China
Email: bill.wu@huawei.com Email: bill.wu@huawei.com
 End of changes. 16 change blocks. 
22 lines changed or deleted 37 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/