< draft-ietf-lsr-isis-rfc7810bis-00.txt | draft-ietf-lsr-isis-rfc7810bis-01.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: October 27, 2018 S. Giacolone | Expires: January 18, 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 | |||
April 25, 2018 | July 17, 2018 | |||
IS-IS Traffic Engineering (TE) Metric Extensions | IS-IS Traffic Engineering (TE) Metric Extensions | |||
draft-ietf-lsr-isis-rfc7810bis-00 | draft-ietf-lsr-isis-rfc7810bis-01 | |||
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 October 27, 2018. | This Internet-Draft will expire on January 18, 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 18, line 29 ¶ | skipping to change at page 18, line 29 ¶ | |||
the ambiguity. | the ambiguity. | |||
The choice made here is to omit the unused RESERVED field from these | The choice made here is to omit the unused RESERVED field from these | |||
sub-TLVs and use the length of 4. This matches the corresponding | sub-TLVs and use the length of 4. This matches the corresponding | |||
advertisements specified in the equivalent OSPF specification | advertisements specified in the equivalent OSPF specification | |||
[RFC7471] and the corresponding BGP-LS specification | [RFC7471] and the corresponding BGP-LS specification | |||
[I-D.ietf-idr-te-pm-bgp]. | [I-D.ietf-idr-te-pm-bgp]. | |||
Some minor editorial corrections have also been made. | Some minor editorial corrections have also been made. | |||
Implementations may wish to consider temporarily supporting sending/ | ||||
receiving the form of the sub-TLVs using a length of 5 and including | ||||
the RESERVED field as a means of interoperating with the legacy | ||||
implementations. However, the intent of this revision is to specify | ||||
one and only one normative behavior. Any existing implementations | ||||
which encode the sub-TLVs using a length of 5 are expected to be | ||||
revised to conform to the normative behavior specified in this | ||||
document. | ||||
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 | |||
End of changes. 5 change blocks. | ||||
4 lines changed or deleted | 13 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/ |