draft-ietf-lsr-isis-rfc7810bis-01.txt   draft-ietf-lsr-isis-rfc7810bis-02.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: January 18, 2019 S. Giacolone Expires: March 6, 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
July 17, 2018 September 2, 2018
IS-IS Traffic Engineering (TE) Metric Extensions IS-IS Traffic Engineering (TE) Metric Extensions
draft-ietf-lsr-isis-rfc7810bis-01 draft-ietf-lsr-isis-rfc7810bis-02
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 January 18, 2019. This Internet-Draft will expire on March 6, 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 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 available bandwidths minus the measured bandwidth used for the link residual bandwidths (see Section 4.5) minus the sum of the
actual forwarding of non-RSVP-TE label switched path packets. For a measured bandwidth used for the actual forwarding of non-RSVP-TE
bundled link, available bandwidth is defined to be the sum of the label switched path packets on all component links.
component link available bandwidths.
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 18, line 38 skipping to change at page 18, line 38
As a means of interoperating with implementations which do not As a means of interoperating with implementations which do not
conform to the corrections defined in this document, implementers may conform to the corrections defined in this document, implementers may
wish to consider temporarily supporting sending and/or receiving the wish to consider temporarily supporting sending and/or receiving the
form of the sub-TLVs using a length of 5 and including the RESERVED form of the sub-TLVs using a length of 5 and including the RESERVED
field. However, the intent of this revision is to specify one and field. However, the intent of this revision is to specify one and
only one normative behavior. Any existing implementations which only one normative behavior. Any existing implementations which
encode the sub-TLVs using a length of 5 are expected to be revised to encode the sub-TLVs using a length of 5 are expected to be revised to
conform to the normative behavior specified in this document. conform to the normative behavior specified in this document.
Errata ID: 5486 (https://www.rfc-editor.org/errata/eid5486)
identified that in [RFC7810] Section 4.6 the definition of available
bandwidth on bundled links used a circular definition i.e., it used
"sum of the component link available bandwidths" when it should have
used "sum of the component link residual bandwidths". This has been
corrected and clarified.
Authors' Addresses Authors' Addresses
Les Ginsberg (editor) Les Ginsberg (editor)
Cisco Systems, Inc. Cisco Systems, Inc.
Email: ginsberg@cisco.com Email: ginsberg@cisco.com
Stefano Previdi (editor) Stefano Previdi (editor)
Huawei Huawei
Email: stefano@previdi.net Email: stefano@previdi.net
Spencer Giacolone Spencer Giacolone
Microsoft Microsoft
Email: spencer.giacalone@gmail.com Email: spencer.giacalone@gmail.com
Dave Ward Dave Ward
Cisco Systems, Inc. Cisco Systems, Inc.
Email: wardd@cisco.com Email: wardd@cisco.com
 End of changes. 8 change blocks. 
9 lines changed or deleted 15 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/