draft-ietf-ospf-te-metric-extensions-08.txt   draft-ietf-ospf-te-metric-extensions-09.txt 
skipping to change at page 1, line 17 skipping to change at page 1, line 17
J. Drake J. Drake
Juniper Networks Juniper Networks
A. Atlas A. Atlas
Juniper Networks Juniper Networks
S. Previdi S. Previdi
Cisco Systems Cisco Systems
December 01, 2014 December 27, 2014
OSPF Traffic Engineering (TE) Metric Extensions OSPF Traffic Engineering (TE) Metric Extensions
draft-ietf-ospf-te-metric-extensions-08.txt draft-ietf-ospf-te-metric-extensions-09.txt
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 RFC 3630 'Traffic Engineering This document describes extensions to RFC 3630 'Traffic Engineering
(TE) Extensions to OSPF Version 2' such that network performance (TE) Extensions to OSPF Version 2' such that network performance
skipping to change at page 2, line 21 skipping to change at page 2, line 21
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on June 1, 2015. This Internet-Draft will expire on June 27, 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 13 skipping to change at page 3, line 13
4.1.2. Length...............................................7 4.1.2. Length...............................................7
4.1.3. A bit................................................7 4.1.3. A bit................................................7
4.1.4. Reserved.............................................7 4.1.4. Reserved.............................................7
4.1.5. Delay Value..........................................8 4.1.5. Delay Value..........................................8
4.2. Min/Max Unidirectional Link Delay Sub-TLV.................8 4.2. Min/Max Unidirectional Link Delay Sub-TLV.................8
4.2.1. Type.................................................8 4.2.1. Type.................................................8
4.2.2. Length...............................................8 4.2.2. Length...............................................8
4.2.3. A bit................................................8 4.2.3. A bit................................................8
4.2.4. Reserved.............................................9 4.2.4. Reserved.............................................9
4.2.5. Min Delay............................................9 4.2.5. Min Delay............................................9
4.2.6. Max Delay............................................9 4.2.6. Reserved.............................................9
4.2.7. Reserved.............................................9 4.2.7 Max Delay.............................................9
4.3. Unidirectional Delay Variation Sub-TLV....................9 4.3. Unidirectional Delay Variation Sub-TLV....................9
4.3.1. Type................................................10 4.3.1. Type................................................10
4.3.2. Length..............................................10 4.3.2. Length..............................................10
4.3.3. Reserved............................................10 4.3.3. Reserved............................................10
4.3.4. Delay Variation.....................................10 4.3.4. Delay Variation.....................................10
4.4. Unidirectional Link Loss Sub-TLV.........................10 4.4. Unidirectional Link Loss Sub-TLV.........................10
4.4.1. Type................................................11 4.4.1. Type................................................11
4.4.2. Length..............................................11 4.4.2. Length..............................................11
4.4.3. A bit...............................................11 4.4.3. A bit...............................................11
4.4.4. Reserved............................................11 4.4.4. Reserved............................................11
4.4.5. Link Loss...........................................11 4.4.5. Link Loss...........................................11
4.5. Unidirectional Residual Bandwidth Sub-TLV................11 4.5. Unidirectional Residual Bandwidth Sub-TLV................11
4.5.1. Type................................................12 4.5.1. Type................................................12
4.5.2. Length..............................................12 4.5.2. Length..............................................12
4.5.3. Residual Bandwidth..................................12 4.5.3. Residual Bandwidth..................................12
4.6. Unidirectional Available Bandwidth Sub-TLV...............13 4.6. Unidirectional Available Bandwidth Sub-TLV...............12
4.6.1. Type................................................13 4.6.1. Type................................................13
4.6.2. Length..............................................13 4.6.2. Length..............................................13
4.6.3. Available Bandwidth.................................13 4.6.3. Available Bandwidth.................................13
4.7. Unidirectional Utilized Bandwidth Sub-TLV................13 4.7. Unidirectional Utilized Bandwidth Sub-TLV................13
4.7.1. Type................................................14 4.7.1. Type................................................14
4.7.2. Length..............................................14 4.7.2. Length..............................................14
4.7.3. Utilized Bandwidth..................................14 4.7.3. Utilized Bandwidth..................................14
5. Announcement Thresholds and Filters...........................14 5. Announcement Thresholds and Filters...........................14
6. Announcement Suppression......................................15 6. Announcement Suppression......................................15
7. Network Stability and Announcement Periodicity................15 7. Network Stability and Announcement Periodicity................15
8. Enabling and Disabling Sub-TLVs...............................16 8. Enabling and Disabling Sub-TLVs...............................16
9. Static Metric Override........................................16 9. Static Metric Override........................................16
10. Compatibility................................................16 10. Compatibility................................................16
11. Security Considerations......................................17 11. Security Considerations......................................16
12. IANA Considerations..........................................17 12. IANA Considerations..........................................17
13. References...................................................17 13. References...................................................17
13.1. Normative References....................................17 13.1. Normative References....................................17
13.2. Informative References..................................18 13.2. Informative References..................................18
14. Acknowledgments..............................................18 14. Acknowledgments..............................................18
15. Author's Addresses...........................................19 15. Author's Addresses...........................................19
1. Introduction 1. Introduction
In certain networks, such as, but not limited to, financial In certain networks, such as, but not limited to, financial
skipping to change at page 5, line 19 skipping to change at page 5, line 19
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
document are to be interpreted as described in RFC-2119 [RFC2119]. document are to be interpreted as described in RFC-2119 [RFC2119].
In this document, these words will appear with that interpretation In this document, these words will appear with that interpretation
only when in ALL CAPS. Lower case uses of these words are not to be only when in ALL CAPS. Lower case uses of these words are not to be
interpreted as carrying RFC-2119 significance. interpreted as carrying RFC-2119 significance.
3. TE Metric Extensions to OSPF TE 3. TE Metric Extensions to OSPF TE
This document proposes new OSPF TE sub-TLVs that can be announced in This document defines new OSPF TE sub-TLVs that can be announced in
OSPF TE LSAs to distribute network performance information. The OSPF TE LSAs to distribute network performance information. The
extensions in this document build on the ones provided in OSPF TE extensions in this document build on the ones provided in OSPF TE
[RFC3630] and GMPLS [RFC4203]. [RFC3630] and GMPLS [RFC4203].
OSPF TE LSAs [RFC3630] are opaque LSAs [RFC5250] with area flooding OSPF TE LSAs [RFC3630] are opaque LSAs [RFC5250] with area flooding
scope. Each consists of a single TLV with one or more nested sub- scope. Each consists of a single TLV with one or more nested sub-
TLVs, permitting the TE LSA to be readily extended. There are two TLVs, permitting the TE LSA to be readily extended. There are two
OSPF TE LSA TLVs, the Router Address and the Link TLV. Like the OSPF TE LSA TLVs, the Router Address and the Link TLV. Like the
extensions in GMPLS (RFC4203), this document proposes several extensions in GMPLS (RFC4203), this document defines several
additional sub-TLVs for the Link TLV: additional sub-TLVs for the Link TLV:
Type Length Value Type Length Value
TBD1 4 Unidirectional Link Delay TBD1 4 Unidirectional Link Delay
TBD2 8 Min/Max Unidirectional Link Delay TBD2 8 Min/Max Unidirectional Link Delay
TBD3 4 Unidirectional Delay Variation TBD3 4 Unidirectional Delay Variation
skipping to change at page 6, line 44 skipping to change at page 6, line 44
do (including nothing). do (including nothing).
Note that when a sub-TLV does not include the A bit, that sub-TLV Note that when a sub-TLV does not include the A bit, that sub-TLV
cannot be used for failover purposes. The A bit was intentionally cannot be used for failover purposes. The A bit was intentionally
omitted from some sub-TLVs to help mitigate oscillations. See section omitted from some sub-TLVs to help mitigate oscillations. See section
7. 1. for more information. 7. 1. for more information.
Link delay, delay variation, and link loss MUST be encoded as Link delay, delay variation, and link loss MUST be encoded as
integers. Consistent with existing OSPF TE specifications [RFC3630], integers. Consistent with existing OSPF TE specifications [RFC3630],
residual, available, and utilized bandwidth MUST be encoded in IEEE residual, available, and utilized bandwidth MUST be encoded in IEEE
floating point. Link delay and delay variation MUST be in units of floating point [IEEE754]. Link delay and delay variation MUST be in
microseconds, link loss MUST be a percentage, and bandwidth MUST be units of microseconds, link loss MUST be a percentage, and bandwidth
in units of bytes per second. All values (except residual bandwidth) MUST be in units of bytes per second. All values (except residual
MUST be calculated as rolling averages where the averaging period bandwidth) MUST be calculated as rolling averages where the averaging
MUST be a configurable period of time. See section 5. for more period MUST be a configurable period of time. See section 5. for more
information. information.
4. Sub-TLV Details 4. Sub-TLV Details
4.1. Unidirectional Link Delay Sub-TLV 4.1. Unidirectional Link Delay Sub-TLV
This sub-TLV advertises the average link delay between two directly This sub-TLV advertises the average link delay between two directly
connected OSPF neighbors. The delay advertised by this sub-TLV MUST connected OSPF neighbors. The delay advertised by this sub-TLV MUST
be the delay from the advertising node to its neighbor (i.e., the be the delay from the advertising node to its neighbor (i.e., the
forward path delay). The format of this sub-TLV is shown in the forward path delay). The format of this sub-TLV is shown in the
skipping to change at page 9, line 16 skipping to change at page 9, line 16
This field is reserved for future use. It MUST be set to 0 when sent This field is reserved for future use. It MUST be set to 0 when sent
and MUST be ignored when received. and MUST be ignored when received.
4.2.5. Min Delay 4.2.5. Min Delay
This 24-bit field carries minimum measured link delay value (in This 24-bit field carries minimum measured link delay value (in
microseconds) over a configurable interval, encoded as an integer microseconds) over a configurable interval, encoded as an integer
value. value.
Implementations MAY also permit the configuration of a static (non Implementations MAY also permit the configuration of an offset value
dynamic) offset value (in microseconds) to be added to the measured (in microseconds) to be added to the measured delay value to
delay value, to facilitate the communication of operator specific advertise operator specific delay constraints.
delay constraints.
When set to the maximum value 16,777,215 (16.777215 sec), then the When set to the maximum value 16,777,215 (16.777215 sec), then the
delay is at least that value and may be larger. delay is at least that value and may be larger.
4.2.6. Max Delay 4.2.6. Reserved
This field is reserved for future use. It MUST be set to 0 when sent
and MUST be ignored when received.
4.2.7 Max Delay
This 24-bit field carries the maximum measured link delay value (in This 24-bit field carries the maximum measured link delay value (in
microseconds) over a configurable interval, encoded as an integer microseconds) over a configurable interval, encoded as an integer
value. value.
Implementations MAY also permit the configuration of a static (non Implementations MAY also permit the configuration of an offset value
dynamic) offset value (in microseconds) to be added to the measured (in microseconds) to be added to the measured delay value to
delay value, to facilitate the communication of operator specific advertise operator specific delay constraints.
delay constraints.
It is possible for min delay and max delay to be the same value. It is possible for min delay and max delay to be the same value.
When the delay value is set to maximum value 16,777,215 (16.777215 When the delay value is set to maximum value 16,777,215 (16.777215
sec), then the delay is at least that value and may be larger. sec), then the delay is at least that value and may be larger.
4.2.7. Reserved
This field is reserved for future use. It MUST be set to 0 when sent
and MUST be ignored when received.
4.3. Unidirectional Delay Variation Sub-TLV 4.3. Unidirectional Delay Variation Sub-TLV
This sub-TLV advertises the average link delay variation between two This sub-TLV advertises the average link delay variation between two
directly connected OSPF neighbors. The delay variation advertised by directly connected OSPF neighbors. The delay variation advertised by
this sub-TLV MUST be the delay from the advertising node to its this sub-TLV MUST be the delay from the advertising node to its
neighbor (i.e., the forward path delay variation). The format of this neighbor (i.e., the forward path delay variation). The format of this
sub-TLV is shown in the following diagram: sub-TLV is shown in the following diagram:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
skipping to change at page 15, line 34 skipping to change at page 15, line 31
both. both.
Additionally, once outside of the bounds of the threshold, any re- Additionally, once outside of the bounds of the threshold, any re-
advertisement of a measurement within the bounds would remain advertisement of a measurement within the bounds would remain
governed solely by the measurement interval for that sub-TLV. governed solely by the measurement interval for that sub-TLV.
6. Announcement Suppression 6. Announcement Suppression
When link performance values change by small amounts that fall under When link performance values change by small amounts that fall under
thresholds that would cause the announcement of a sub-TLV, thresholds that would cause the announcement of a sub-TLV,
implementations SHOULD suppress sub-TLV readvertisement and/or implementations SHOULD suppress sub-TLV re-advertisement and/or
lengthen the period within which they are refreshed. lengthen the period within which they are refreshed.
Only the accelerated advertisement threshold mechanism described in Only the accelerated advertisement threshold mechanism described in
section 6 may shorten the re-advertisement interval. section 5 may shorten the re-advertisement interval.
All suppression and re-advertisement interval back-off timer features All suppression and re-advertisement interval back-off timer features
SHOULD be configurable. SHOULD be configurable.
7. Network Stability and Announcement Periodicity 7. Network Stability and Announcement Periodicity
Sections 6 and 7 provide configurable mechanisms to bound the number Sections 5 and 6 provide configurable mechanisms to bound the number
of re-advertisements. Instability might occur in very large networks of re-advertisements. Instability might occur in very large networks
if measurement intervals are set low enough to overwhelm the if measurement intervals are set low enough to overwhelm the
processing of flooded information at some of the routers in the processing of flooded information at some of the routers in the
topology. Therefore care SHOULD be taken in setting these values. topology. Therefore care SHOULD be taken in setting these values.
Additionally, the default measurement interval for all sub-TLVs Additionally, the default measurement interval for all sub-TLVs
SHOULD be 30 seconds. SHOULD be 30 seconds.
Announcements MUST also be able to be throttled using configurable Announcements MUST also be able to be throttled using configurable
inter-update throttle timers. The minimum announcement periodicity is inter-update throttle timers. The minimum announcement periodicity is
1 announcement per second. The default value SHOULD be set to 120 1 announcement per second. The default value SHOULD be set to 120
seconds. seconds.
skipping to change at page 18, line 5 skipping to change at page 17, line 38
13.1. Normative References 13.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, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3630] Katz, D., Kompella, K., Yeung, D., "Traffic [RFC3630] Katz, D., Kompella, K., Yeung, D., "Traffic
Engineering (TE) Extensions to OSPF Version 2", RFC 3630, Engineering (TE) Extensions to OSPF Version 2", RFC 3630,
September 2003. September 2003.
[RFC4203] Kompella, K., Rekhter, Y., "OSPF Extensions in Support of
Generalized Multi-Protocol Label Switching (GMPLS)", RFC
4203, October 2005.
[IEEE754] Institute of Electrical and Electronics Engineers,
"Standard for Floating-Point Arithmetic", IEEE Standard
754, August 2008.
13.2. Informative References 13.2. Informative References
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan,
V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
Tunnels", RFC 3209, December 2001. Tunnels", RFC 3209, December 2001.
[RFC4203] Kompella, K., Rekhter, Y., "OSPF Extensions in Support of
Generalized Multi-Protocol Label Switching (GMPLS)", RFC
4203, October 2005.
[RFC4206] Kompella, K., Rekhter, Y., "Label Switched Paths (LSP) [RFC4206] Kompella, K., Rekhter, Y., "Label Switched Paths (LSP)
Hierarchy with Generalized Multi-Protocol Label Switching Hierarchy with Generalized Multi-Protocol Label Switching
(GMPLS) Traffic Engineering (TE)", RFC 4206, October 2005. (GMPLS) Traffic Engineering (TE)", RFC 4206, October 2005.
[RFC4655] Farrel, A., Vasseur, J.-P., and J. Ash, "A Path [RFC4655] Farrel, A., Vasseur, J.-P., and J. Ash, "A Path
Computation Element (PCE)-Based Architecture", RFC 4655, Computation Element (PCE)-Based Architecture", RFC 4655,
August 2006. August 2006.
[RFC5250] Berger, L., Bryskin I., Zinin, A., Coltun, R., "The OSPF [RFC5250] Berger, L., Bryskin I., Zinin, A., Coltun, R., "The OSPF
Opaque LSA Option", RFC 5250, July 2008. Opaque LSA Option", RFC 5250, July 2008.
 End of changes. 19 change blocks. 
36 lines changed or deleted 38 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/