< draft-ietf-ospf-two-part-metric-00.txt   draft-ietf-ospf-two-part-metric-01.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: July 24, 2015 Cisco Systems Expires: January 26, 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
January 20, 2015 July 25, 2015
OSPF Two-part Metric OSPF Two-part Metric
draft-ietf-ospf-two-part-metric-00.txt draft-ietf-ospf-two-part-metric-01.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. two.
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 July 24, 2015. This Internet-Draft will expire on January 26, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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 2, line 36 skipping to change at page 2, line 36
3.2. Advertising Network-to-Router metric in OSPFv2 . . . . . 4 3.2. Advertising Network-to-Router metric in OSPFv2 . . . . . 4
3.3. Advertising Network-to-Router metric in OSPFv3 . . . . . 5 3.3. Advertising Network-to-Router metric in OSPFv3 . . . . . 5
3.4. SPF Calculation . . . . . . . . . . . . . . . . . . . . . 5 3.4. SPF Calculation . . . . . . . . . . . . . . . . . . . . . 5
3.5. Backward Compatibility . . . . . . . . . . . . . . . . . 5 3.5. Backward Compatibility . . . . . . . . . . . . . . . . . 5
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . . 6 5. Security Considerations . . . . . . . . . . . . . . . . . . . 6
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. Normative References . . . . . . . . . . . . . . . . . . 6 7.1. Normative References . . . . . . . . . . . . . . . . . . 6
7.2. Informative References . . . . . . . . . . . . . . . . . 7 7.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
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.
skipping to change at page 7, line 13 skipping to change at page 7, line 13
in progress), July 2014. in progress), July 2014.
[I-D.ietf-ospf-lsa-extend] [I-D.ietf-ospf-lsa-extend]
Psenak, P., Previdi, S., Filsfils, C., Gredler, H., Psenak, P., Previdi, S., Filsfils, C., Gredler, H.,
Shakir, R., Henderickx, W., Tantsura, J., and A. Lindem, Shakir, R., Henderickx, W., Tantsura, J., and A. Lindem,
"OSPFv2 LSA Extendibility", draft-ietf-ospf-lsa-extend-00 "OSPFv2 LSA Extendibility", draft-ietf-ospf-lsa-extend-00
(work in progress), August 2014. (work in progress), August 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-05 LSA Extendibility", draft-ietf-ospf-ospfv3-lsa-extend-06
(work in progress), November 2014. (work in progress), February 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, March 1997. Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328,
DOI 10.17487/RFC2328, April 1998,
<http://www.rfc-editor.org/info/rfc2328>.
[RFC4915] Psenak, P., Mirtorabi, S., Roy, A., Nguyen, L., and P. [RFC4915] Psenak, P., Mirtorabi, S., Roy, A., Nguyen, L., and P.
Pillay-Esnault, "Multi-Topology (MT) Routing in OSPF", RFC Pillay-Esnault, "Multi-Topology (MT) Routing in OSPF",
4915, June 2007. RFC 4915, DOI 10.17487/RFC4915, June 2007,
<http://www.rfc-editor.org/info/rfc4915>.
[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, July 2008. for IPv6", RFC 5340, DOI 10.17487/RFC5340, July 2008,
<http://www.rfc-editor.org/info/rfc5340>.
[RFC5613] Zinin, A., Roy, A., Nguyen, L., Friedman, B., and D. [RFC5613] Zinin, A., Roy, A., Nguyen, L., Friedman, B., and D.
Yeung, "OSPF Link-Local Signaling", RFC 5613, August 2009. Yeung, "OSPF Link-Local Signaling", RFC 5613,
DOI 10.17487/RFC5613, August 2009,
<http://www.rfc-editor.org/info/rfc5613>.
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, January and Point-to-Multipoint Interface Type", RFC 6845,
2013. DOI 10.17487/RFC6845, January 2013,
<http://www.rfc-editor.org/info/rfc6845>.
Authors' Addresses Authors' Addresses
Jeffrey Zhang Jeffrey Zhang
Juniper Networks, Inc. Juniper Networks, Inc.
10 Technology Park Drive 10 Technology Park Drive
Westford, MA 01886 Westford, MA 01886
EMail: zzhang@juniper.net EMail: zzhang@juniper.net
Lili Wang Lili Wang
Juniper Networks, Inc. Juniper Networks, Inc.
10 Technology Park Drive 10 Technology Park Drive
 End of changes. 13 change blocks. 
15 lines changed or deleted 24 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/