< draft-ietf-ospf-two-part-metric-05.txt		draft-ietf-ospf-two-part-metric-06.txt >
	Open Shortest Path First Z. Zhang		Network Working Group 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 6, 2016 Cisco Systems		Expires: February 6, 2017 Cisco Systems
	D. Dubois		August 5, 2016
	General Dynamics C4S
	V. Julka
	T. McMillan
	L3 Communications, Linkabit
	May 5, 2016
	OSPF Two-part Metric		OSPF Two-part Metric
	draft-ietf-ospf-two-part-metric-05.txt		draft-ietf-ospf-two-part-metric-06.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 42 ¶
	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 6, 2016.		This Internet-Draft will expire on February 6, 2017.
	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
	skipping to change at page 2, line 34 ¶		skipping to change at page 2, line 29 ¶
	modifications of such material outside the IETF Standards Process.		modifications of such material outside the IETF Standards Process.
	Without obtaining an adequate license from the person(s) controlling		Without obtaining an adequate license from the person(s) controlling
	the copyright in such materials, this document may not be modified		the copyright in such materials, this document may not be modified
	outside the IETF Standards Process, and derivative works of it may		outside the IETF Standards Process, and derivative works of it may
	not be created outside the IETF Standards Process, except to format		not be created outside the IETF Standards Process, except to format
	it for publication as an RFC or to translate it into languages other		it for publication as an RFC or to translate it into languages other
	than English.		than English.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	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 . . . . . 5		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. Advertising Network-to-Router TE Metric . . . . . . . . . 5		3.4. Advertising Network-to-Router TE Metric . . . . . . . . . 5
	3.5. OSPF Stub Router Behavior . . . . . . . . . . . . . . . . 6		3.5. OSPF Stub Router Behavior . . . . . . . . . . . . . . . . 5
	3.6. SPF Calculation . . . . . . . . . . . . . . . . . . . . . 6		3.6. SPF Calculation . . . . . . . . . . . . . . . . . . . . . 6
	3.7. Backward Compatibility . . . . . . . . . . . . . . . . . 6		3.7. Backward Compatibility . . . . . . . . . . . . . . . . . 6
	4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7		4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 7		5. Security Considerations . . . . . . . . . . . . . . . . . . . 7
	6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7		6. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . 7		6.1. Normative References . . . . . . . . . . . . . . . . . . 7
	7.1. Normative References . . . . . . . . . . . . . . . . . . 7		6.2. Informative References . . . . . . . . . . . . . . . . . 8
	7.2. Informative References . . . . . . . . . . . . . . . . . 8		Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 8
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8		Appendix B. Contributors' Addreses . . . . . . . . . . . . . . . 9
			Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
	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
	skipping to change at page 7, line 25 ¶		skipping to change at page 7, line 15 ¶
	o A new Sub-TLV type in OSPFv3 Extended-LSA Sub-TLV registry, for		o A new Sub-TLV type in OSPFv3 Extended-LSA Sub-TLV registry, for
	the Network-to-Router Metric Sub-TLV.		the Network-to-Router Metric Sub-TLV.
	o A new Sub-TLV type in Types for sub-TLVs of TE Link TLV (Value 2)		o A new Sub-TLV type in Types for sub-TLVs of TE Link TLV (Value 2)
	registry, for the Network-to-Router TE Metric Sub-TLV.		registry, for the Network-to-Router TE Metric Sub-TLV.
	5. Security Considerations		5. Security Considerations
	This document does not introduce new security risks.		This document does not introduce new security risks.
	6. Acknowledgements		6. References
	The authors would like to thank Abhay Roy, Hannes Gredler, Peter
	Psenak and Eric Wu for their comments and suggestions.
	7. References
	7.1. Normative References		6.1. Normative References
	[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-10
	(work in progress), November 2015.		(work in progress), May 2016.
	[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>.
	[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328,		[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328,
	DOI 10.17487/RFC2328, April 1998,		DOI 10.17487/RFC2328, April 1998,
	<http://www.rfc-editor.org/info/rfc2328>.		<http://www.rfc-editor.org/info/rfc2328>.
	skipping to change at page 8, line 29 ¶		skipping to change at page 8, line 15 ¶
	[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		[RFC7770] Lindem, A., Ed., Shen, N., Vasseur, JP., Aggarwal, R., and
	S. Shaffer, "Extensions to OSPF for Advertising Optional		S. Shaffer, "Extensions to OSPF for Advertising Optional
	Router Capabilities", RFC 7770, DOI 10.17487/RFC7770,		Router Capabilities", RFC 7770, DOI 10.17487/RFC7770,
	February 2016, <http://www.rfc-editor.org/info/rfc7770>.		February 2016, <http://www.rfc-editor.org/info/rfc7770>.
	7.2. Informative References		6.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,
	<http://www.rfc-editor.org/info/rfc6987>.		<http://www.rfc-editor.org/info/rfc6987>.
	Authors' Addresses		Appendix A. Acknowledgements
	Zhaohui Zhang
	Juniper Networks, Inc.
	10 Technology Park Drive
	Westford, MA 01886
	EMail: zzhang@juniper.net
	Lili Wang
	Juniper Networks, Inc.
	10 Technology Park Drive
	Westford, MA 01886
	EMail: liliw@juniper.net		The authors would like to thank Abhay Roy, Hannes Gredler, Peter
			Psenak and Eric Wu for their comments and suggestions.
	Acee Lindem		The RFC text was produced using Marshall Rose's xml2rfc tool.
	Cisco Systems
	301 Midenhall Way
	Cary, NC 27513
	EMail: acee@cisco.com		Appendix B. Contributors' Addreses
	David Dubois		David Dubois
	General Dynamics C4S		General Dynamics C4S
	400 John Quincy Adams Road		400 John Quincy Adams Road
	Taunton, MA 02780		Taunton, MA 02780
	EMail: dave.dubois@gdc4s.com		EMail: dave.dubois@gd-ms.com
	Vibhor Julka		Vibhor Julka
	L3 Communications, Linkabit		L3 Communications, Linkabit
	9890 Towne Centre Drive		9890 Towne Centre Drive
	San Diego, CA 92121		San Diego, CA 92121
	EMail: vibhor.julka@l-3Com.com		EMail: vjulka1@yahoo.com
	Tom McMillan		Tom McMillan
	L3 Communications, Linkabit		L3 Communications, Linkabit
	9890 Towne Centre Drive		9890 Towne Centre Drive
	San Diego, CA 92121		San Diego, CA 92121
	EMail: tom.mcmillan@l-3com.com		EMail: tom.mcmillan@l-3com.com
			Authors' Addresses
			Zhaohui Zhang
			Juniper Networks, Inc.
			10 Technology Park Drive
			Westford, MA 01886
			Email: zzhang@juniper.net
			Lili Wang
			Juniper Networks, Inc.
			10 Technology Park Drive
			Westford, MA 01886
			Email: liliw@juniper.net
			Acee Lindem
			Cisco Systems
			301 Midenhall Way
			Cary, NC 27513
			Email: acee@cisco.com
End of changes. 20 change blocks.
	49 lines changed or deleted		27 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/