draft-ietf-lsr-isis-rfc7810bis-02.txt   draft-ietf-lsr-isis-rfc7810bis-03.txt 
Link State Routing L. Ginsberg, Ed. Link State Routing L. Ginsberg, Ed.
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Obsoletes: 7810 (if approved) S. Previdi, Ed. Obsoletes: 7810 (if approved) S. Previdi, Ed.
Intended status: Standards Track Huawei Intended status: Standards Track Huawei
Expires: March 6, 2019 S. Giacolone Expires: June 2, 2019 S. Giacolone
Microsoft Microsoft
D. Ward D. Ward
Cisco Systems, Inc. Cisco Systems, Inc.
J. Drake J. Drake
Juniper Networks Juniper Networks
Q. Wu Q. Wu
Huawei Huawei
September 2, 2018 November 29, 2018
IS-IS Traffic Engineering (TE) Metric Extensions IS-IS Traffic Engineering (TE) Metric Extensions
draft-ietf-lsr-isis-rfc7810bis-02 draft-ietf-lsr-isis-rfc7810bis-03
Abstract Abstract
In certain networks, such as, but not limited to, financial In certain networks, such as, but not limited to, financial
information networks (e.g., stock market data providers), network- information networks (e.g., stock market data providers), network-
performance criteria (e.g., latency) are becoming as critical to performance criteria (e.g., latency) are becoming as critical to
data-path selection as other metrics. data-path selection as other metrics.
This document describes extensions to IS-IS Traffic Engineering This document describes extensions to IS-IS Traffic Engineering
Extensions (RFC 5305) such that network-performance information can Extensions (RFC 5305) such that network-performance information can
skipping to change at page 2, line 20 skipping to change at page 2, line 20
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 March 6, 2019. This Internet-Draft will expire on June 2, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 3, line 4 skipping to change at page 3, line 4
4.1. Unidirectional Link Delay Sub-TLV . . . . . . . . . . . . 6 4.1. Unidirectional Link Delay Sub-TLV . . . . . . . . . . . . 6
4.2. Min/Max Unidirectional Link Delay Sub-TLV . . . . . . . . 6 4.2. Min/Max Unidirectional Link Delay Sub-TLV . . . . . . . . 6
4.3. Unidirectional Delay Variation Sub-TLV . . . . . . . . . 8 4.3. Unidirectional Delay Variation Sub-TLV . . . . . . . . . 8
4.4. Unidirectional Link Loss Sub-TLV . . . . . . . . . . . . 8 4.4. Unidirectional Link Loss Sub-TLV . . . . . . . . . . . . 8
4.5. Unidirectional Residual Bandwidth Sub-TLV . . . . . . . . 9 4.5. Unidirectional Residual Bandwidth Sub-TLV . . . . . . . . 9
4.6. Unidirectional Available Bandwidth Sub-TLV . . . . . . . 10 4.6. Unidirectional Available Bandwidth Sub-TLV . . . . . . . 10
4.7. Unidirectional Utilized Bandwidth Sub-TLV . . . . . . . . 11 4.7. Unidirectional Utilized Bandwidth Sub-TLV . . . . . . . . 11
5. Announcement Thresholds and Filters . . . . . . . . . . . . . 12 5. Announcement Thresholds and Filters . . . . . . . . . . . . . 12
6. Announcement Suppression . . . . . . . . . . . . . . . . . . 13 6. Announcement Suppression . . . . . . . . . . . . . . . . . . 13
7. Network Stability and Announcement Periodicity . . . . . . . 13 7. Network Stability and Announcement Periodicity . . . . . . . 13
8. Enabling and Disabling Sub-TLVs . . . . . . . . . . . . . . . 14 8. Enabling and Disabling Sub-TLVs . . . . . . . . . . . . . . . 13
9. Static Metric Override . . . . . . . . . . . . . . . . . . . 14 9. Static Metric Override . . . . . . . . . . . . . . . . . . . 14
10. Compatibility . . . . . . . . . . . . . . . . . . . . . . . . 14 10. Compatibility . . . . . . . . . . . . . . . . . . . . . . . . 14
11. Security Considerations . . . . . . . . . . . . . . . . . . . 14 11. Security Considerations . . . . . . . . . . . . . . . . . . . 14
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15
14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 15 14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 15
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
15.1. Normative References . . . . . . . . . . . . . . . . . . 16 15.1. Normative References . . . . . . . . . . . . . . . . . . 16
15.2. Informative References . . . . . . . . . . . . . . . . . 17 15.2. Informative References . . . . . . . . . . . . . . . . . 17
Appendix A. Changes from RFC 7810 . . . . . . . . . . . . . . . 17 Appendix A. Changes from RFC 7810 . . . . . . . . . . . . . . . 17
skipping to change at page 11, line 28 skipping to change at page 11, line 28
Length: 4 Length: 4
Available Bandwidth: This field carries the available bandwidth on a Available Bandwidth: This field carries the available bandwidth on a
link, forwarding adjacency, or bundled link in IEEE floating-point link, forwarding adjacency, or bundled link in IEEE floating-point
format with units of bytes per second. For a link or forwarding format with units of bytes per second. For a link or forwarding
adjacency, available bandwidth is defined to be residual bandwidth adjacency, available bandwidth is defined to be residual bandwidth
(see Section 4.5) minus the measured bandwidth used for the actual (see Section 4.5) minus the measured bandwidth used for the actual
forwarding of non-RSVP-TE label switched path packets. For a bundled forwarding of non-RSVP-TE label switched path packets. For a bundled
link, available bandwidth is defined to be the sum of the component link, available bandwidth is defined to be the sum of the component
link residual bandwidths (see Section 4.5) minus the sum of the link available bandwidths.
measured bandwidth used for the actual forwarding of non-RSVP-TE
label switched path packets on all component links.
4.7. Unidirectional Utilized Bandwidth Sub-TLV 4.7. Unidirectional Utilized Bandwidth Sub-TLV
This sub-TLV advertises the bandwidth utilization between two This sub-TLV advertises the bandwidth utilization between two
directly connected IS-IS neighbors. The bandwidth utilization directly connected IS-IS neighbors. The bandwidth utilization
advertised by this sub-TLV MUST be the bandwidth from the system advertised by this sub-TLV MUST be the bandwidth from the system
originating this sub-TLV. The format of this sub-TLV is shown in the originating this sub-TLV. The format of this sub-TLV is shown in the
following diagram: following diagram:
0 1 2 3 0 1 2 3
skipping to change at page 12, line 4 skipping to change at page 11, line 51
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Utilized Bandwidth | | Utilized Bandwidth |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 7 Figure 7
where: where:
Type: 39 Type: 39
Length: 4
Length: 4
Utilized Bandwidth: This field carries the bandwidth utilization on a Utilized Bandwidth: This field carries the bandwidth utilization on a
link, forwarding adjacency, or bundled link in IEEE floating-point link, forwarding adjacency, or bundled link in IEEE floating-point
format with units of bytes per second. For a link or forwarding format with units of bytes per second. For a link or forwarding
adjacency, bandwidth utilization represents the actual utilization of adjacency, bandwidth utilization represents the actual utilization of
the link (i.e., as measured by the advertising node). For a bundled the link (i.e., as measured by the advertising node). For a bundled
link, bandwidth utilization is defined to be the sum of the component link, bandwidth utilization is defined to be the sum of the component
link bandwidth utilizations. link bandwidth utilizations.
5. Announcement Thresholds and Filters 5. Announcement Thresholds and Filters
skipping to change at page 17, line 15 skipping to change at page 17, line 15
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
15.2. Informative References 15.2. Informative References
[I-D.ietf-idr-te-pm-bgp] [I-D.ietf-idr-te-pm-bgp]
Ginsberg, L., Previdi, S., Wu, Q., Tantsura, J., and C. Ginsberg, L., Previdi, S., Wu, Q., Tantsura, J., and C.
Filsfils, "BGP-LS Advertisement of IGP Traffic Engineering Filsfils, "BGP-LS Advertisement of IGP Traffic Engineering
Performance Metric Extensions", draft-ietf-idr-te-pm- Performance Metric Extensions", draft-ietf-idr-te-pm-
bgp-10 (work in progress), March 2018. bgp-14 (work in progress), October 2018.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001, Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001,
<https://www.rfc-editor.org/info/rfc3209>. <https://www.rfc-editor.org/info/rfc3209>.
[RFC4203] Kompella, K., Ed. and Y. Rekhter, Ed., "OSPF Extensions in [RFC4203] Kompella, K., Ed. and Y. Rekhter, Ed., "OSPF Extensions in
Support of Generalized Multi-Protocol Label Switching Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 4203, DOI 10.17487/RFC4203, October 2005, (GMPLS)", RFC 4203, DOI 10.17487/RFC4203, October 2005,
<https://www.rfc-editor.org/info/rfc4203>. <https://www.rfc-editor.org/info/rfc4203>.
 End of changes. 9 change blocks. 
10 lines changed or deleted 8 lines changed or added

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