draft-ietf-idr-te-pm-bgp-07.txt   draft-ietf-idr-te-pm-bgp-08.txt 
Networking Working Group L. Ginsberg, Ed. Networking Working Group L. Ginsberg, Ed.
Internet-Draft S. Previdi Internet-Draft S. Previdi
Intended status: Standards Track Cisco Systems, Inc. Intended status: Standards Track Cisco Systems, Inc.
Expires: February 3, 2018 Q. Wu Expires: February 19, 2018 Q. Wu
Huawei Huawei
H. Gredler H. Gredler
S. Ray S. Ray
J. Tantsura J. Tantsura
Individual Individual
C. Filsfils C. Filsfils
Cisco Systems, Inc. Cisco Systems, Inc.
August 2, 2017 August 18, 2017
BGP-LS Advertisement of IGP Traffic Engineering Performance Metric BGP-LS Advertisement of IGP Traffic Engineering Performance Metric
Extensions Extensions
draft-ietf-idr-te-pm-bgp-07 draft-ietf-idr-te-pm-bgp-08
Abstract Abstract
This document defines new BGP-LS TLVs in order to carry the IGP This document defines new BGP-LS TLVs in order to carry the IGP
Traffic Engineering Extensions defined in IS-IS and OSPF protocols. Traffic Engineering Extensions defined in IS-IS and OSPF protocols.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
skipping to change at page 2, line 4 skipping to change at page 2, line 4
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 February 3, 2018. This Internet-Draft will expire on February 19, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
skipping to change at page 7, line 13 skipping to change at page 7, line 13
the state and resources availability of the IGP link. The IGP the state and resources availability of the IGP link. The IGP
instances originating these TLVs are assumed to have all the required instances originating these TLVs are assumed to have all the required
security and authentication mechanism (as described in [RFC7810] and security and authentication mechanism (as described in [RFC7810] and
[RFC7471]) in order to prevent any security issue when propagating [RFC7471]) in order to prevent any security issue when propagating
the TLVs into BGP-LS. the TLVs into BGP-LS.
5. IANA Considerations 5. IANA Considerations
This document requests assigning code-points from the registry "BGP- This document requests assigning code-points from the registry "BGP-
LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute
TLVs" for the new Link Attribute TLVs deefined in the table here TLVs" for the new Link Attribute TLVs defined in the table below:
below:
TLV code-point Value TLV code-point Value
-------------------------------------------------------- --------------------------------------------------------
1104 (Suggested) Unidirectional Link Delay 1114 Unidirectional Link Delay
1105 (Suggested) Min/Max Unidirectional Link Delay 1115 Min/Max Unidirectional Link Delay
1106 (Suggested) Unidirectional Delay Variation 1116 Unidirectional Delay Variation
1107 (Suggested) Unidirectional Packet Loss 1117 Unidirectional Packet Loss
1108 (Suggested) Unidirectional Residual Bandwidth 1118 Unidirectional Residual Bandwidth
1109 (Suggested) Unidirectional Available Bandwidth 1119 Unidirectional Available Bandwidth
1110 (Suggested) Unidirectional Bandwidth Utilization 1120 Unidirectional Bandwidth Utilization
6. Acknowledgements 6. Acknowledgements
TBD TBD
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc2119>. editor.org/info/rfc2119>.
[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
Border Gateway Protocol 4 (BGP-4)", RFC 4271, Border Gateway Protocol 4 (BGP-4)", RFC 4271,
DOI 10.17487/RFC4271, January 2006, DOI 10.17487/RFC4271, January 2006, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc4271>. editor.org/info/rfc4271>.
[RFC7471] Giacalone, S., Ward, D., Drake, J., Atlas, A., and S. [RFC7471] Giacalone, S., Ward, D., Drake, J., Atlas, A., and S.
Previdi, "OSPF Traffic Engineering (TE) Metric Previdi, "OSPF Traffic Engineering (TE) Metric
Extensions", RFC 7471, DOI 10.17487/RFC7471, March 2015, Extensions", RFC 7471, DOI 10.17487/RFC7471, March 2015,
<http://www.rfc-editor.org/info/rfc7471>. <https://www.rfc-editor.org/info/rfc7471>.
[RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and [RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and
S. Ray, "North-Bound Distribution of Link-State and S. Ray, "North-Bound Distribution of Link-State and
Traffic Engineering (TE) Information Using BGP", RFC 7752, Traffic Engineering (TE) Information Using BGP", RFC 7752,
DOI 10.17487/RFC7752, March 2016, DOI 10.17487/RFC7752, March 2016, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc7752>. editor.org/info/rfc7752>.
[RFC7810] Previdi, S., Ed., Giacalone, S., Ward, D., Drake, J., and [RFC7810] Previdi, S., Ed., Giacalone, S., Ward, D., Drake, J., and
Q. Wu, "IS-IS Traffic Engineering (TE) Metric Extensions", Q. Wu, "IS-IS Traffic Engineering (TE) Metric Extensions",
RFC 7810, DOI 10.17487/RFC7810, May 2016, RFC 7810, DOI 10.17487/RFC7810, May 2016,
<http://www.rfc-editor.org/info/rfc7810>. <https://www.rfc-editor.org/info/rfc7810>.
7.2. Informative References 7.2. Informative References
[RFC4272] Murphy, S., "BGP Security Vulnerabilities Analysis", [RFC4272] Murphy, S., "BGP Security Vulnerabilities Analysis",
RFC 4272, DOI 10.17487/RFC4272, January 2006, RFC 4272, DOI 10.17487/RFC4272, January 2006,
<http://www.rfc-editor.org/info/rfc4272>. <https://www.rfc-editor.org/info/rfc4272>.
[RFC6952] Jethanandani, M., Patel, K., and L. Zheng, "Analysis of [RFC6952] Jethanandani, M., Patel, K., and L. Zheng, "Analysis of
BGP, LDP, PCEP, and MSDP Issues According to the Keying BGP, LDP, PCEP, and MSDP Issues According to the Keying
and Authentication for Routing Protocols (KARP) Design and Authentication for Routing Protocols (KARP) Design
Guide", RFC 6952, DOI 10.17487/RFC6952, May 2013, Guide", RFC 6952, DOI 10.17487/RFC6952, May 2013,
<http://www.rfc-editor.org/info/rfc6952>. <https://www.rfc-editor.org/info/rfc6952>.
Authors' Addresses Authors' Addresses
Les Ginsberg (editor) Les Ginsberg (editor)
Cisco Systems, Inc. Cisco Systems, Inc.
US US
Email: ginsberg@cisco.com Email: ginsberg@cisco.com
Stefano Previdi Stefano Previdi
 End of changes. 19 change blocks. 
23 lines changed or deleted 22 lines changed or added

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