draft-ietf-isis-te-metric-extensions-03.txt   draft-ietf-isis-te-metric-extensions-04.txt 
Networking Working Group S. Previdi, Ed. Networking Working Group S. Previdi, Ed.
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Intended status: Standards Track S. Giacalone Intended status: Standards Track S. Giacalone
Expires: October 27, 2014 Thomson Reuters Expires: April 25, 2015 Thomson Reuters
D. Ward D. Ward
Cisco Systems, Inc. Cisco Systems, Inc.
J. Drake J. Drake
A. Atlas A. Atlas
Juniper Networks Juniper Networks
C. Filsfils C. Filsfils
Cisco Systems, Inc. Cisco Systems, Inc.
Q. Wu Q. Wu
Huawei Huawei
April 25, 2014 October 22, 2014
IS-IS Traffic Engineering (TE) Metric Extensions IS-IS Traffic Engineering (TE) Metric Extensions
draft-ietf-isis-te-metric-extensions-03 draft-ietf-isis-te-metric-extensions-04
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 data performance criteria (e.g. latency) are becoming as critical to data
path selection as other metrics. path selection as other metrics.
This document describes extensions to IS-IS Traffic Engineering This document describes extensions to IS-IS Traffic Engineering
Extensions (RFC5305) such that network performance information can be Extensions (RFC5305) such that network performance information can be
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 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 October 27, 2014. This Internet-Draft will expire on April 25, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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 3, line 41 skipping to change at page 3, line 41
defined in [RFC5305] (hereafter called "IS-IS TE Metric Extensions"), defined in [RFC5305] (hereafter called "IS-IS TE Metric Extensions"),
that can be used to distribute network performance information (such that can be used to distribute network performance information (such
as link delay, delay variation, packet loss, residual bandwidth, and as link delay, delay variation, packet loss, residual bandwidth, and
available bandwidth). available bandwidth).
The data distributed by the TE Metric Extensions proposed in this The data distributed by the TE Metric Extensions proposed in this
document is meant to be used as part of the operation of the routing document is meant to be used as part of the operation of the routing
protocol (e.g. by replacing cost with latency or considering protocol (e.g. by replacing cost with latency or considering
bandwidth as well as cost), by enhancing Constrained-SPF (CSPF), or bandwidth as well as cost), by enhancing Constrained-SPF (CSPF), or
for other uses such as supplementing the data used by an ALTO server for other uses such as supplementing the data used by an ALTO server
[I-D.ietf-alto-protocol]. With respect to CSPF, the data distributed [RFC7285]. With respect to CSPF, the data distributed by ISIS TE
by ISIS TE Metric Extensions can be used to setup, fail over, and Metric Extensions can be used to setup, fail over, and fail back data
fail back data paths using protocols such as RSVP-TE [RFC3209]; paths using protocols such as RSVP-TE [RFC3209];
[I-D.atlas-mpls-te-express-path] describes some methods for using [I-D.atlas-mpls-te-express-path] describes some methods for using
this information to compute Label Switched Paths (LSPs) at the LSP this information to compute Label Switched Paths (LSPs) at the LSP
ingress. ingress.
Note that the mechanisms described in this document only disseminate Note that the mechanisms described in this document only disseminate
performance information. The methods for initially gathering that performance information. The methods for initially gathering that
performance information, such as [RFC6375], or acting on it once it performance information, such as [RFC6375], or acting on it once it
is distributed are outside the scope of this document. Example is distributed are outside the scope of this document. Example
mechanisms to measure latency, delay variation, and loss in an MPLS mechanisms to measure latency, delay variation, and loss in an MPLS
network are given in [RFC6374]. While this document does not specify network are given in [RFC6374]. While this document does not specify
skipping to change at page 16, line 35 skipping to change at page 16, line 35
14.2. Informative References 14.2. Informative References
[I-D.atlas-mpls-te-express-path] [I-D.atlas-mpls-te-express-path]
Atlas, A., Drake, J., Giacalone, S., Ward, D., Previdi, Atlas, A., Drake, J., Giacalone, S., Ward, D., Previdi,
S., and C. Filsfils, "Performance-based Path Selection for S., and C. Filsfils, "Performance-based Path Selection for
Explicitly Routed LSPs using TE Metric Extensions", draft- Explicitly Routed LSPs using TE Metric Extensions", draft-
atlas-mpls-te-express-path-04 (work in progress), atlas-mpls-te-express-path-04 (work in progress),
September 2013. September 2013.
[I-D.ietf-alto-protocol]
Alimi, R., Penno, R., and Y. Yang, "ALTO Protocol", draft-
ietf-alto-protocol-27 (work in progress), March 2014.
[RFC6375] Frost, D. and S. Bryant, "A Packet Loss and Delay [RFC6375] Frost, D. and S. Bryant, "A Packet Loss and Delay
Measurement Profile for MPLS-Based Transport Networks", Measurement Profile for MPLS-Based Transport Networks",
RFC 6375, September 2011. RFC 6375, September 2011.
[RFC7285] Alimi, R., Penno, R., Yang, Y., Kiesel, S., Previdi, S.,
Roome, W., Shalunov, S., and R. Woundy, "Application-Layer
Traffic Optimization (ALTO) Protocol", RFC 7285, September
2014.
Authors' Addresses Authors' Addresses
Stefano Previdi (editor) Stefano Previdi (editor)
Cisco Systems, Inc. Cisco Systems, Inc.
Via Del Serafico 200 Via Del Serafico 200
Rome 00191 Rome 00191
IT IT
Email: sprevidi@cisco.com Email: sprevidi@cisco.com
Spencer Giacalone Spencer Giacalone
 End of changes. 7 change blocks. 
11 lines changed or deleted 12 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/