< draft-ietf-ospf-two-part-metric-04.txt   draft-ietf-ospf-two-part-metric-05.txt >
Open Shortest Path First Z. Zhang Open Shortest Path First Z. Zhang
Internet-Draft L. Wang Internet-Draft L. Wang
Updates: 2328, 5340 (if approved) Juniper Networks, Inc. Updates: 2328, 5340 (if approved) Juniper Networks, Inc.
Intended status: Standards Track A. Lindem Intended status: Standards Track A. Lindem
Expires: November 5, 2016 Cisco Systems Expires: November 6, 2016 Cisco Systems
D. Dubois D. Dubois
General Dynamics C4S General Dynamics C4S
V. Julka V. Julka
T. McMillan T. McMillan
L3 Communications, Linkabit L3 Communications, Linkabit
May 4, 2016 May 5, 2016
OSPF Two-part Metric OSPF Two-part Metric
draft-ietf-ospf-two-part-metric-04.txt draft-ietf-ospf-two-part-metric-05.txt
Abstract Abstract
This document specifies an optional extension to the OSPF protocol, This document specifies an optional extension to the OSPF protocol,
to represent the metric on a multi-access network as two parts: the to represent the metric on a multi-access network as two parts: the
metric from a router to the network, and the metric from the network metric from a router to the network, and the metric from the network
to the router. The router to router metric would be the sum of the to the router. The router to router metric would be the sum of the
two. This document updates RFC 2328 and RFC 5340. two. This document updates RFC 2328 and RFC 5340.
Requirements Language Requirements Language
skipping to change at page 1, line 47 skipping to change at page 1, line 47
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 November 5, 2016. This Internet-Draft will expire on November 6, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
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.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Proposed Enhancement . . . . . . . . . . . . . . . . . . . . 3 2. Proposed Enhancement . . . . . . . . . . . . . . . . . . . . 3
3. Speficications . . . . . . . . . . . . . . . . . . . . . . . 4 3. Speficications . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Router Interface Parameters . . . . . . . . . . . . . . . 4 3.1. Router Interface Parameters . . . . . . . . . . . . . . . 4
3.2. Advertising Network-to-Router Metric in OSPFv2 . . . . . 4 3.2. Advertising Network-to-Router Metric in OSPFv2 . . . . . 5
3.3. Advertising Network-to-Router Metric in OSPFv3 . . . . . 5 3.3. Advertising Network-to-Router Metric in OSPFv3 . . . . . 5
3.4. Advertising Network-to-Router TE Metric . . . . . . . . . 5 3.4. Advertising Network-to-Router TE Metric . . . . . . . . . 5
3.5. OSPF Stub Router Behavior . . . . . . . . . . . . . . . . 5 3.5. OSPF Stub Router Behavior . . . . . . . . . . . . . . . . 6
3.6. SPF Calculation . . . . . . . . . . . . . . . . . . . . . 6 3.6. SPF Calculation . . . . . . . . . . . . . . . . . . . . . 6
3.7. Backward Compatibility . . . . . . . . . . . . . . . . . 6 3.7. Backward Compatibility . . . . . . . . . . . . . . . . . 6
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
5. Security Considerations . . . . . . . . . . . . . . . . . . . 7 5. Security Considerations . . . . . . . . . . . . . . . . . . . 7
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
7.1. Normative References . . . . . . . . . . . . . . . . . . 7 7.1. Normative References . . . . . . . . . . . . . . . . . . 7
7.2. Informative References . . . . . . . . . . . . . . . . . 8 7.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
With Open Shortest Path First (OSPF, [RFC2328, RFC5340]) protocol, With Open Shortest Path First (OSPF, [RFC2328], [RFC5340]) protocol,
for a broadcast network, a Network-LSA is advertised to list all for a broadcast network, a Network-LSA is advertised to list all
routers on the network, and each router on the network includes a routers on the network, and each router on the network includes a
link in its Router-LSA to describe its connection to the network. link in its Router-LSA to describe its connection to the network.
The link in the Router-LSA includes a metric but the listed routers The link in the Router-LSA includes a metric but the listed routers
in the Network LSA do not include a metric. This is based on the in the Network LSA do not include a metric. This is based on the
assumption that from a particular router, all others on the same assumption that from a particular router, all others on the same
network can be reached with the same metric. network can be reached with the same metric.
With some broadcast networks, different routers can be reached with With some broadcast networks, different routers can be reached with
different metrics. [RFC6845] extends the OSPF protocol with a hybrid different metrics. [RFC6845] extends the OSPF protocol with a hybrid
skipping to change at page 5, line 5 skipping to change at page 5, line 13
"Interface output cost". "Interface output cost".
3.2. Advertising Network-to-Router Metric in OSPFv2 3.2. Advertising Network-to-Router Metric in OSPFv2
For OSPFv2, the Network-to-Router metric is encoded in an OSPF For OSPFv2, the Network-to-Router metric is encoded in an OSPF
Extended Link TLV Sub-TLV [RFC7684], defined in this document as the Extended Link TLV Sub-TLV [RFC7684], defined in this document as the
Network-to-Router Metric Sub-TLV. The type of the Sub-TLV is TBD. Network-to-Router Metric Sub-TLV. The type of the Sub-TLV is TBD.
The length of the Sub-TLV is 4 (for the value part only). The value The length of the Sub-TLV is 4 (for the value part only). The value
part of the Sub-TLV is defined as follows: part of the Sub-TLV is defined as follows:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MT | 0 | MT metric | | MT | 0 | MT metric |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Multiple such Sub-TLVs can exist in a single OSPF Extended Link TLV, Multiple such Sub-TLVs can exist in a single OSPF Extended Link TLV,
one for each topology [RFC4915]. The OSPF Extended Link TLV one for each topology [RFC4915]. The OSPF Extended Link TLV
identifies the transit link to the network, and is part of an OSPFv2 identifies the transit link to the network, and is part of an OSPFv2
Extended-Link Opaque LSA. The Sub-TLV MUST ONLY appear in Extended- Extended-Link Opaque LSA. The Sub-TLV MUST ONLY appear in Extended-
Link TLVs for Link Type 2 (link to transit network), and MUST be Link TLVs for Link Type 2 (link to transit network), and MUST be
ignored if received for other link types. ignored if received for other link types.
3.3. Advertising Network-to-Router Metric in OSPFv3 3.3. Advertising Network-to-Router Metric in OSPFv3
For OSPFv3, the same Network-to-Router Metric Sub-TLV definition is For OSPFv3, the same Network-to-Router Metric Sub-TLV definition is
used, though it is part of the Router-Link TLV of E-Router-LSA [I- used, though it is part of the Router-Link TLV of E-Router-LSA
D.ietf-ospf-ospfv3-lsa-extend]. Currently OSPFv3 Multi-Toplogy is [I-D.ietf-ospf-ospfv3-lsa-extend]. Currently OSPFv3 Multi-Toplogy is
not defined so the only valid value for the MT field is 0 and only not defined so the only valid value for the MT field is 0 and only
one such Sub-TLV SHOULD be included in the Router-Link TLV. Received one such Sub-TLV SHOULD be included in the Router-Link TLV. Received
Sub-TLVs with non-zero MT field MUST be ignored. Sub-TLVs with non-zero MT field MUST be ignored.
Similarly, the Sub-TLV MUST ONLY appear in Router-Link TLVs for Link Similarly, the Sub-TLV MUST ONLY appear in Router-Link TLVs for Link
Type 2 (connection to a transit network) and MUST be ignored if Type 2 (connection to a transit network) and MUST be ignored if
received for other link types. received for other link types.
3.4. Advertising Network-to-Router TE Metric 3.4. Advertising Network-to-Router TE Metric
skipping to change at page 6, line 31 skipping to change at page 6, line 39
has a Network-to-Router Metric Sub-TLV, then the cost from V to W has a Network-to-Router Metric Sub-TLV, then the cost from V to W
is the metric in the Sub-TLV. If not, the cost is 0. is the metric in the Sub-TLV. If not, the cost is 0.
3.7. Backward Compatibility 3.7. Backward Compatibility
Due to the change of procedures in the SPF calculation, all routers Due to the change of procedures in the SPF calculation, all routers
in an area that includes one or more two-part metric networks must in an area that includes one or more two-part metric networks must
support the changes specified in this document. To ensure that, if support the changes specified in this document. To ensure that, if
an area is provisioned to support two-part metric networks, all an area is provisioned to support two-part metric networks, all
routers supporting this capability must advertise a Router routers supporting this capability must advertise a Router
Information (RI) LSA with a Router Functional Capabilities TLV [I- Information (RI) LSA with a Router Functional Capabilities TLV
D.acee-ospf-rfc4970bis] that includes the following Router Functional [RFC7770] that includes the following Router Functional Capability
Capability Bit: Bit:
Bit Capabilities Bit Capabilities
0 OSPF Two-part Metric [TPM] 0 OSPF Two-part Metric [TPM]
Upon detecting the presence of a reachable Router-LSA without a Upon detecting the presence of a reachable Router-LSA without a
companion RI LSA that has the bit set, all routers MUST recalculate companion RI LSA that has the bit set, all routers MUST recalculate
routes w/o considering any network-to-router costs. routes w/o considering any network-to-router costs.
4. IANA Considerations 4. IANA Considerations
skipping to change at page 7, line 24 skipping to change at page 7, line 34
6. Acknowledgements 6. Acknowledgements
The authors would like to thank Abhay Roy, Hannes Gredler, Peter The authors would like to thank Abhay Roy, Hannes Gredler, Peter
Psenak and Eric Wu for their comments and suggestions. Psenak and Eric Wu for their comments and suggestions.
7. References 7. References
7.1. Normative References 7.1. Normative References
[I-D.acee-ospf-rfc4970bis]
Lindem, A., Shen, N., Vasseur, J., Aggarwal, R., and S.
Shaffer, "Extensions to OSPF for Advertising Optional
Router Capabilities", draft-acee-ospf-rfc4970bis-00 (work
in progress), July 2014.
[I-D.ietf-ospf-ospfv3-lsa-extend] [I-D.ietf-ospf-ospfv3-lsa-extend]
Lindem, A., Mirtorabi, S., Roy, A., and F. Baker, "OSPFv3 Lindem, A., Mirtorabi, S., Roy, A., and F. Baker, "OSPFv3
LSA Extendibility", draft-ietf-ospf-ospfv3-lsa-extend-09 LSA Extendibility", draft-ietf-ospf-ospfv3-lsa-extend-09
(work in progress), November 2015. (work in progress), November 2015.
[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, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
skipping to change at page 8, line 19 skipping to change at page 8, line 24
[RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF [RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF
for IPv6", RFC 5340, DOI 10.17487/RFC5340, July 2008, for IPv6", RFC 5340, DOI 10.17487/RFC5340, July 2008,
<http://www.rfc-editor.org/info/rfc5340>. <http://www.rfc-editor.org/info/rfc5340>.
[RFC7684] Psenak, P., Gredler, H., Shakir, R., Henderickx, W., [RFC7684] Psenak, P., Gredler, H., Shakir, R., Henderickx, W.,
Tantsura, J., and A. Lindem, "OSPFv2 Prefix/Link Attribute Tantsura, J., and A. Lindem, "OSPFv2 Prefix/Link Attribute
Advertisement", RFC 7684, DOI 10.17487/RFC7684, November Advertisement", RFC 7684, DOI 10.17487/RFC7684, November
2015, <http://www.rfc-editor.org/info/rfc7684>. 2015, <http://www.rfc-editor.org/info/rfc7684>.
[RFC7770] Lindem, A., Ed., Shen, N., Vasseur, JP., Aggarwal, R., and
S. Shaffer, "Extensions to OSPF for Advertising Optional
Router Capabilities", RFC 7770, DOI 10.17487/RFC7770,
February 2016, <http://www.rfc-editor.org/info/rfc7770>.
7.2. Informative References 7.2. Informative References
[RFC6845] Sheth, N., Wang, L., and J. Zhang, "OSPF Hybrid Broadcast [RFC6845] Sheth, N., Wang, L., and J. Zhang, "OSPF Hybrid Broadcast
and Point-to-Multipoint Interface Type", RFC 6845, and Point-to-Multipoint Interface Type", RFC 6845,
DOI 10.17487/RFC6845, January 2013, DOI 10.17487/RFC6845, January 2013,
<http://www.rfc-editor.org/info/rfc6845>. <http://www.rfc-editor.org/info/rfc6845>.
[RFC6987] Retana, A., Nguyen, L., Zinin, A., White, R., and D. [RFC6987] Retana, A., Nguyen, L., Zinin, A., White, R., and D.
McPherson, "OSPF Stub Router Advertisement", RFC 6987, McPherson, "OSPF Stub Router Advertisement", RFC 6987,
DOI 10.17487/RFC6987, September 2013, DOI 10.17487/RFC6987, September 2013,
 End of changes. 15 change blocks. 
25 lines changed or deleted 36 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/