draft-ietf-lsr-flex-algo-bw-con-00.txt   draft-ietf-lsr-flex-algo-bw-con-01.txt 
SPRING S. Hegde SPRING S. Hegde
Internet-Draft W. Britto Internet-Draft W. Britto
Intended status: Standards Track R. Shetty Intended status: Standards Track R. Shetty
Expires: December 1, 2021 Juniper Networks Inc. Expires: January 13, 2022 Juniper Networks Inc.
B. Decraene B. Decraene
Orange Orange
P. Psenak P. Psenak
Cisco Systems Cisco Systems
T. Li T. Li
Arista Networks Arista Networks
May 30, 2021 July 12, 2021
Flexible Algorithms: Bandwidth, Delay, Metrics and Constraints Flexible Algorithms: Bandwidth, Delay, Metrics and Constraints
draft-ietf-lsr-flex-algo-bw-con-00 draft-ietf-lsr-flex-algo-bw-con-01
Abstract Abstract
Many networks configure the link metric relative to the link Many networks configure the link metric relative to the link
capacity. High bandwidth traffic gets routed as per the link capacity. High bandwidth traffic gets routed as per the link
capacity. Flexible algorithms provides mechanisms to create capacity. Flexible algorithms provides mechanisms to create
constraint based paths in IGP. This draft documents a generic metric constraint based paths in IGP. This draft documents a generic metric
type and set of bandwidth related constraints to be used in Flexible type and set of bandwidth related constraints to be used in Flexible
Algorithms. Algorithms.
skipping to change at page 1, line 48 skipping to change at page 1, line 48
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 December 1, 2021. This Internet-Draft will expire on January 13, 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 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 2, line 26 skipping to change at page 2, line 26
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Generic Metric Advertisement . . . . . . . . . . . . . . . . 4 2. Generic Metric Advertisement . . . . . . . . . . . . . . . . 4
2.1. ISIS Generic Metric sub-TLV . . . . . . . . . . . . . . . 5 2.1. ISIS Generic Metric sub-TLV . . . . . . . . . . . . . . . 5
2.2. OSPF Generic Metric sub-TLV . . . . . . . . . . . . . . . 6 2.2. OSPF Generic Metric sub-TLV . . . . . . . . . . . . . . . 6
2.3. Generic Metric applicability to Flexible Algorithms
Multi-domain/Multi-area networks . . . . . . . . . . . . 7
3. FAD constraint sub-TLVs . . . . . . . . . . . . . . . . . . . 7 3. FAD constraint sub-TLVs . . . . . . . . . . . . . . . . . . . 7
3.1. ISIS FAD constraint sub-TLVs . . . . . . . . . . . . . . 7 3.1. ISIS FAD constraint sub-TLVs . . . . . . . . . . . . . . 8
3.1.1. ISIS Exclude Minimum Bandwidth sub-TLV . . . . . . . 7 3.1.1. ISIS Exclude Minimum Bandwidth sub-TLV . . . . . . . 8
3.1.2. ISIS Exclude Maximum Delay sub-TLV . . . . . . . . . 8 3.1.2. ISIS Exclude Maximum Delay sub-TLV . . . . . . . . . 8
3.2. OSPF FAD constraint sub-TLVs . . . . . . . . . . . . . . 9 3.2. OSPF FAD constraint sub-TLVs . . . . . . . . . . . . . . 9
3.2.1. OSPF Exclude Minimum Bandwidth sub-TLV . . . . . . . 9 3.2.1. OSPF Exclude Minimum Bandwidth sub-TLV . . . . . . . 9
3.2.2. OSPF Exclude Maximum Delay sub-TLV . . . . . . . . . 10 3.2.2. OSPF Exclude Maximum Delay sub-TLV . . . . . . . . . 10
4. Bandwidth Metric Advertisement . . . . . . . . . . . . . . . 11 4. Bandwidth Metric Advertisement . . . . . . . . . . . . . . . 11
4.1. Automatic Metric Calculation . . . . . . . . . . . . . . 12 4.1. Automatic Metric Calculation . . . . . . . . . . . . . . 12
4.1.1. Automatic Metric Calculation Modes . . . . . . . . . 12 4.1.1. Automatic Metric Calculation Modes . . . . . . . . . 12
4.1.2. Automatic Metric Calculation Methods . . . . . . . . 13 4.1.2. Automatic Metric Calculation Methods . . . . . . . . 13
4.1.3. ISIS FAD constraint sub-TLVs for automatic metric 4.1.3. ISIS FAD constraint sub-TLVs for automatic metric
calculation . . . . . . . . . . . . . . . . . . . . . 14 calculation . . . . . . . . . . . . . . . . . . . . . 14
skipping to change at page 2, line 51 skipping to change at page 3, line 4
5. Bandwidth metric considerations . . . . . . . . . . . . . . . 22 5. Bandwidth metric considerations . . . . . . . . . . . . . . . 22
6. Calculation of Flex-Algorithm paths . . . . . . . . . . . . . 22 6. Calculation of Flex-Algorithm paths . . . . . . . . . . . . . 22
7. Backward Compatibility . . . . . . . . . . . . . . . . . . . 23 7. Backward Compatibility . . . . . . . . . . . . . . . . . . . 23
8. Security Considerations . . . . . . . . . . . . . . . . . . . 23 8. Security Considerations . . . . . . . . . . . . . . . . . . . 23
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23
9.1. IGP Metric-Type Registry . . . . . . . . . . . . . . . . 23 9.1. IGP Metric-Type Registry . . . . . . . . . . . . . . . . 23
9.2. ISIS Sub-Sub-TLVs for Flexible Algorithm Definition Sub- 9.2. ISIS Sub-Sub-TLVs for Flexible Algorithm Definition Sub-
TLV . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 TLV . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
9.3. OSPF Sub-TLVs for Flexible Algorithm Definition Sub-TLV . 24 9.3. OSPF Sub-TLVs for Flexible Algorithm Definition Sub-TLV . 24
9.4. Sub-TLVs for TLVs 22, 23, 25, 141, 222, and 223 . . . . . 24 9.4. Sub-TLVs for TLVs 22, 23, 25, 141, 222, and 223 . . . . . 24
9.5. Sub-sub-TLV Codepoints for Application-Specific Link 9.5. OSPFv2 Extended Link TLV Sub-TLVs . . . . . . . . . . . . 24
Attributes . . . . . . . . . . . . . . . . . . . . . . . 24 9.6. Types for sub-TLVs of TE Link TLV (Value 2) . . . . . . . 25
9.7. OSPFv3 Extended-LSA Sub-TLVs . . . . . . . . . . . . . . 25
9.6. OSPFv2 Extended Link TLV Sub-TLVs . . . . . . . . . . . . 25
9.7. Types for sub-TLVs of TE Link TLV (Value 2) . . . . . . . 25
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25
11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 25 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 25
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 25 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 25
12.1. Normative References . . . . . . . . . . . . . . . . . . 25 12.1. Normative References . . . . . . . . . . . . . . . . . . 25
12.2. Informative References . . . . . . . . . . . . . . . . . 26 12.2. Informative References . . . . . . . . . . . . . . . . . 26
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26
1. Introduction 1. Introduction
High bandwidth traffic such as residential internet traffic and High bandwidth traffic such as residential internet traffic and
skipping to change at page 5, line 9 skipping to change at page 5, line 9
and a value for the metric. The metric type field is assigned by the and a value for the metric. The metric type field is assigned by the
"IGP metric type" IANA registry. Metric types 0-127 are standard "IGP metric type" IANA registry. Metric types 0-127 are standard
metric types as assigned by IANA. This document further specifies a metric types as assigned by IANA. This document further specifies a
user defined metric type space of metric types 128-255. These are user defined metric type space of metric types 128-255. These are
user defined and can be assigned by an operator for local use. user defined and can be assigned by an operator for local use.
2.1. ISIS Generic Metric sub-TLV 2.1. ISIS Generic Metric sub-TLV
The ISIS Generic Metric sub-TLV specifies the link metric for a given The ISIS Generic Metric sub-TLV specifies the link metric for a given
metric type. Typically, this metric is assigned by a network metric type. Typically, this metric is assigned by a network
administrator. The Generic Metric sub-TLV is advertised in the TLVs/ administrator. Generic metric is application-independent attribute
sub-TLVs below: similar to igp-metric. The Generic Metric sub-TLV is advertised in
the TLVs/sub-TLVs below:
TLV-22 (Extended IS reachability) [RFC5305] TLV-22 (Extended IS reachability) [RFC5305]
TLV-222 (MT-ISN) [RFC5120] TLV-222 (MT-ISN) [RFC5120]
TLV-23 (IS Neighbor Attribute) [RFC5311] TLV-23 (IS Neighbor Attribute) [RFC5311]
TLV-223 (MT IS Neighbor Attribute) [RFC5311] TLV-223 (MT IS Neighbor Attribute) [RFC5311]
TLV-141 (inter-AS reachability information) [RFC5316] TLV-141 (inter-AS reachability information) [RFC5316]
sub-TLV 16 (Application-Specific Link Attributes) of TLV
22/222/23/223/141 [RFC8919]
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | metric-type | | Type | Length | metric-type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value | | Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type : TBD (To be assigned by IANA) Type : TBD (To be assigned by IANA)
Length: 4 octets Length: 4 octets
metric-type: A value from the IGP metric-type registry metric-type: A value from the IGP metric-type registry
Value : metric value range (1 - 16,777,215) Value : metric value range (1 - 16,777,215)
Figure 1: ISIS Generic Metric sub-TLV Figure 1: ISIS Generic Metric sub-TLV
The Generic Metric sub-TLV MAY be advertised multiple times. For a The Generic Metric sub-TLV MAY be advertised multiple times. For a
particular metric type, the Generic Metric sub-TLV MUST be advertised particular metric type, the Generic Metric sub-TLV MUST be advertised
only once for a link when advertised in TLV 22,222,23,223 and 141. only once for a link when advertised in TLV 22,222,23,223 and 141.
When Generic metric sub-TLV is advertised in ASLA, each metric type If there are multiple Generic Metric sub-TLVs advertised for a link
MUST be advertised only once per-application for a link. If there for same metric type in one or more received LSPDUs, advertisement in
are multiple Generic Metric sub-TLVs advertised for a link for same the lowest numbered fragment MUST be used and the subsequent ones
metric type (and same application in case of ASLA) in one or more
received LSPDUs, the first one MUST be used and the subsequent ones
MUST be ignored.If the metric type indicates a standard metric type MUST be ignored.If the metric type indicates a standard metric type
for which there are other advertisement mechanisms (e.g., the IGP for which there are other advertisement mechanisms (e.g., the IGP
metric, the Min Unidirectional Link Delay, or the Traffic Engineering metric, the Min Unidirectional Link Delay, or the Traffic Engineering
Default Metric, as of this writing), the Generic Metric advertisement Default Metric, as of this writing), the Generic Metric advertisement
MUST be ignored. MUST be ignored.
2.2. OSPF Generic Metric sub-TLV 2.2. OSPF Generic Metric sub-TLV
The OSPF Generic Metric sub-TLV specifies the link metric for a given The OSPF Generic Metric sub-TLV specifies the link metric for a given
metric type. Typically, this metric is assigned by a network metric type. Typically, this metric is assigned by a network
administrator. The Generic Metric sub-TLV is advertised in the TLVs administrator.Generic metric is application-independent attribute
below: similar to igp-metric. The Generic Metric sub-TLV is advertised in
the TLVs below:
sub-TLV of the OSPF Link TLV of OSPF extended Link LSA [RFC7684]. sub-TLV of the OSPF Link TLV of OSPF extended Link LSA [RFC7684].
sub-TLV of TE Link TLV (2) of OSPF TE LSA [RFC3630]. sub-TLV of TE Link TLV (2) of OSPF TE LSA [RFC3630].
sub-sub-TLV of Application-Specific Link Attributes sub-TLV [RFC sub-TLV of the Router-Link TLV in the E-Router-LSA in OSPFv3
8920] [RFC8362].
The Generic Metric sub-TLV is TLV type TBD (IANA), and is eight The Generic Metric sub-TLV is TLV type TBD (IANA), and is eight
octets in length. octets in length.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| metric-type | Reserved | | metric-type | Reserved |
skipping to change at page 6, line 45 skipping to change at page 6, line 44
Length: 8 octets Length: 8 octets
metric-type = A value from the IGP metric type registry metric-type = A value from the IGP metric type registry
Value : metric value (1- 4,294,967,295) Value : metric value (1- 4,294,967,295)
Figure 2: OSPF Generic Metric sub-TLV Figure 2: OSPF Generic Metric sub-TLV
The Generic Metric sub-TLV MAY be advertised multiple times. For a The Generic Metric sub-TLV MAY be advertised multiple times. For a
particular metric type, the Genreric Metric sub-TLV MUST be particular metric type, the Genreric Metric sub-TLV MUST be
advertised only once for a link when advertised in OSPF Link TLV of advertised only once for a link when advertised in OSPF Link TLV of
Extended Link LSA and Link TLV of TE LSA. When Genreric Metric sub- Extended Link LSA, Link TLV of TE LSA and sub-TLV of the Router-Link
TLV is advertised as sub-sub-TLV of ASLA, it MUST be advertised only TLV in the E-Router-LSA Router-Link TLV in OSPFv3. If there are
once per-application for a link. If there are multiple Genreric multiple Genreric Metric sub-TLVs advertised for a link for the same
Metric sub-TLVs advertised for a link for the same metric type and metric type in a received LSA, the first one MUST be used and the
for same application in one or more received LSPDUs, the first one subsequent ones MUST be ignored.If the metric type indicates a
MUST be used and the subsequent ones MUST be ignored.If the metric standard metric type for which there are other advertisement
type indicates a standard metric type for which there are other mechanisms (e.g., the IGP metric, the Min Unidirectional Link Delay,
advertisement mechanisms (e.g., the IGP metric, the Min or the Traffic Engineering Default Metric, as of this writing), the
Unidirectional Link Delay, or the Traffic Engineering Default Metric, Generic Metric advertisement MUST be ignored.
as of this writing), the Generic Metric advertisement MUST be
ignored. 2.3. Generic Metric applicability to Flexible Algorithms Multi-domain/
Multi-area networks
Generic Metric can be used by Flex-Algorithms by specifying the
metric type in the Flexible Algorithm Definitions. When Flex-
Algorithms is used in a multi-area network, [I-D.ietf-lsr-flex-algo]
defines FAPM sub-TLV that carries the Flexible Algorithm specific
metric. Metric carried in FAPM will be equal to the metric to reach
the prefix for that Flex-Algorithm in its source area or domain.
When Flex-Algorithm uses Generic metric, the same procedures as
described in section 13 of [I-D.ietf-lsr-flex-algo] are used to send
and process FAPM sub-TLV.
3. FAD constraint sub-TLVs 3. FAD constraint sub-TLVs
In networks that carry elephant flows, directing an elephant flow In networks that carry elephant flows, directing an elephant flow
down a low-bandwidth link would be catastrophic. Thus, in the down a low-bandwidth link would be catastrophic. Thus, in the
context of Flex-Algorithm, it would be useful to be able to constrain context of Flex-Algorithm, it would be useful to be able to constrain
the topology to only those links capable of supporting a minimum the topology to only those links capable of supporting a minimum
amount of bandwidth. amount of bandwidth.
If the capacity of a link is constant, this can already be achived If the capacity of a link is constant, this can already be achived
skipping to change at page 8, line 38 skipping to change at page 8, line 45
with Maximum Link Bandwidth advertised in sub-sub-TLV 9 of ASLA sub- with Maximum Link Bandwidth advertised in sub-sub-TLV 9 of ASLA sub-
TLV [RFC 8919]. If L-Flag is set in the ASLA sub-TLV, the Minimum TLV [RFC 8919]. If L-Flag is set in the ASLA sub-TLV, the Minimum
bandwidth advertised in FAEMB sub-TLV MUST be compared with Maximum bandwidth advertised in FAEMB sub-TLV MUST be compared with Maximum
Link Bandwidth as advertised by the sub-TLV 9 of the TLV Link Bandwidth as advertised by the sub-TLV 9 of the TLV
22/222/23/223/141 [RFC 5305] as defined in [RFC8919] Section 4.2. 22/222/23/223/141 [RFC 5305] as defined in [RFC8919] Section 4.2.
If the Maximum Link Bandwidth is lower than the Minimum link If the Maximum Link Bandwidth is lower than the Minimum link
bandwidth advertised in FAEMB sub-TLV, the link MUST be excluded from bandwidth advertised in FAEMB sub-TLV, the link MUST be excluded from
the Flex-Algorithm topology. If a link does not have the Maximum the Flex-Algorithm topology. If a link does not have the Maximum
Link Bandwidth advertised but the FAD contains this sub-TLV, then Link Bandwidth advertised but the FAD contains this sub-TLV, then
that link then the link MUST NOT be excluded from the topology based that link MUST NOT be excluded from the topology based on the Minimum
on the Minimum Bandwidth constraint. Bandwidth constraint.
3.1.2. ISIS Exclude Maximum Delay sub-TLV 3.1.2. ISIS Exclude Maximum Delay sub-TLV
ISIS Flex-Algorithm Exclude Maximum Delay sub-TLV (FAEMD) is a sub- ISIS Flex-Algorithm Exclude Maximum Delay sub-TLV (FAEMD) is a sub-
TLV of the ISIS FAD sub-TLV. It has the following format. TLV of the ISIS FAD sub-TLV. It has the following format.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
skipping to change at page 10, line 25 skipping to change at page 10, line 25
Length: 4 octets. Length: 4 octets.
Min Bandwidth: link bandwidth is encoded in 32 bits in IEEE Min Bandwidth: link bandwidth is encoded in 32 bits in IEEE
floating point format. The units are bytes per second. floating point format. The units are bytes per second.
Figure 5: OSPF FAEMB sub-TLV Figure 5: OSPF FAEMB sub-TLV
The FAEMB sub-TLV MUST appear only once in the FAD sub-TLV. If it The FAEMB sub-TLV MUST appear only once in the FAD sub-TLV. If it
appears more than once, the OSPF FAD TLV MUST be ignored by the appears more than once, the OSPF FAD TLV MUST be ignored by the
receiver. The Maximum Link Bandwidth as advertised by the sub-sub- receiver. The Maximum Link Bandwidth as advertised in Extended Link
TLV 23 of ASLA [RFC 8920] MUST be compared against the Minimum TLV in the Extended Link Opaque LSA in OSPFv2 [RFC7684] or as a sub-
bandwidth advertised in FAEMB sub-TLV. If the link bandwidth is TLV of the Router-Link TLV in the E-Router-LSA Router-Link TLV in
lower than the Minimum bandwidth advertised in FAEMB sub-TLV, the OSPFv3 [RFC8362] MUST be compared against the Minimum bandwidth
link MUST be excluded from the Flex-Algorithm topology. If a link advertised in FAEMB sub-TLV. If the link bandwidth is lower than the
does not have the Maximum Link Bandwidth advertised but the FAD Minimum bandwidth advertised in FAEMB sub-TLV, the link MUST be
contains this sub-TLV, then that link MUST be included in the excluded from the Flex-Algorithm topology. If a link does not have
topology and proceed to apply further pruning rules for the link. the Maximum Link Bandwidth advertised but the FAD contains this sub-
TLV, then that link MUST be included in the topology and proceed to
apply further pruning rules for the link.
3.2.2. OSPF Exclude Maximum Delay sub-TLV 3.2.2. OSPF Exclude Maximum Delay sub-TLV
OSPF Flex-Algorithm Exclude Maximum Delay sub-TLV (FAEMD) is a sub- OSPF Flex-Algorithm Exclude Maximum Delay sub-TLV (FAEMD) is a sub-
TLV of the OSPF FAD TLV. It has the following format. TLV of the OSPF FAD TLV. It has the following format.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
skipping to change at page 20, line 43 skipping to change at page 20, line 43
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bandwidth Threshold n | | Bandwidth Threshold n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Threshold Metric n | | Threshold Metric n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
where: where:
Type: TBD Type: TBD
Length: 2 + n*8 octets. Here n is equal to number of Threshold Metrics specified. Length: 2 + n*8 octets. Here n is equal to number of
Threshold Metrics specified.
n MUST be greater than or equal to 1. n MUST be greater than or equal to 1.
Flags: Flags:
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|G| | | | |G| | | |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
G-flag: when set, interface group Mode MUST be used to derive total link bandwidth. G-flag: when set, interface group Mode MUST be used to derive total link bandwidth.
skipping to change at page 24, line 44 skipping to change at page 24, line 44
Reference: This document Section 4.1.4.2 Reference: This document Section 4.1.4.2
9.4. Sub-TLVs for TLVs 22, 23, 25, 141, 222, and 223 9.4. Sub-TLVs for TLVs 22, 23, 25, 141, 222, and 223
Type: Suggested 45 (TBA) Type: Suggested 45 (TBA)
Description: Generic metric Description: Generic metric
Reference: This document Section 2.1 Reference: This document Section 2.1
9.5. Sub-sub-TLV Codepoints for Application-Specific Link Attributes 9.5. OSPFv2 Extended Link TLV Sub-TLVs
Type: Suggested 45 (TBA) Type: Suggested 45 (TBA)
Description: Generic metric Description: Generic metric
Reference: This document Section 2.1 Reference: This document Section 2.2
9.6. OSPFv2 Extended Link TLV Sub-TLVs 9.6. Types for sub-TLVs of TE Link TLV (Value 2)
Type: Suggested 45 (TBA) Type: Suggested 45 (TBA)
Description: Generic metric Description: Generic metric
Reference: This document Section 2.2 Reference: This document Section 2.2
9.7. Types for sub-TLVs of TE Link TLV (Value 2) 9.7. OSPFv3 Extended-LSA Sub-TLVs
Type: Suggested 45 (TBA) Type: Suggested 45 (TBA)
Description: Generic metric Description: Generic metric
Reference: This document Section 2.2 Reference: This document Section 2.2
10. Acknowledgements 10. Acknowledgements
Many thanks to Chris Bowers, Krzysztof Szarcowitz, Julian Lucek, Ram Many thanks to Chris Bowers, Krzysztof Szarcowitz, Julian Lucek, Ram
Santhanakrishnan for discussions and inputs. Santhanakrishnan, Ketan Talaulikar for discussions and inputs.
11. Contributors 11. Contributors
1. Salih K A 1. Salih K A
Juniper Networks Juniper Networks
salih@juniper.net salih@juniper.net
12. References 12. References
 End of changes. 21 change blocks. 
52 lines changed or deleted 63 lines changed or added

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