< draft-tantsura-ospf-segment-routing-msd-00.txt		draft-tantsura-ospf-segment-routing-msd-01.txt >
	OSPF Working Group J. Tantsura		OSPF Working Group J. Tantsura
	Internet-Draft U. Chunduri		Internet-Draft U. Chunduri
	Intended status: Standards Track Ericsson		Intended status: Standards Track Individual
	Expires: September 9, 2016 March 8, 2016		Expires: March 30, 2017 September 26, 2016
	Signaling MSD (Maximum SID Depth) using OSPF		Signaling MSD (Maximum SID Depth) using OSPF
	draft-tantsura-ospf-segment-routing-msd-00		draft-tantsura-ospf-segment-routing-msd-01
	Abstract		Abstract
	This document proposes a way to expose Maximum SID Depth (MSD)		This document proposes a way to expose Maximum SID Depth (MSD)
	supported by a node at node and/or link level by an OSPF Router. In		supported by a node at node and/or link level by an OSPF Router. In
	a Segment Routing (SR) enabled network a centralized controller that		a Segment Routing (SR) enabled network a centralized controller that
	programs SR tunnels at the head-end node needs to know the MSD		programs SR tunnels at the head-end node needs to know the MSD
	information at node level and/or link level to push the label stack		information at node level and/or link level to push the label stack
	of an appropriate depth . Here the term OSPF means both OSPFv2 and		of an appropriate depth . Here the term OSPF means both OSPFv2 and
	OSPFv3.		OSPFv3.
	skipping to change at page 1, line 36 ¶		skipping to change at page 1, line 36 ¶
	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 September 9, 2016.		This Internet-Draft will expire on March 30, 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 38 ¶		skipping to change at page 2, line 38 ¶
	SID Depth" of the node or link SR tunnel exits over, so it doesn't		SID Depth" of the node or link SR tunnel exits over, so it doesn't
	download a path with SID (label stack) of a depth more than the node		download a path with SID (label stack) of a depth more than the node
	or link used is capable of imposing. This document describes how to		or link used is capable of imposing. This document describes how to
	use OSPF to expose the MSD of the node or link to a centralized		use OSPF to expose the MSD of the node or link to a centralized
	controller.		controller.
	PCEP SR extensions [I-D.ietf-pce-segment-routing] has defined MSD, to		PCEP SR extensions [I-D.ietf-pce-segment-routing] has defined MSD, to
	signal in SR PCE Capability TLV, METRIC Object. However, If PCEP is		signal in SR PCE Capability TLV, METRIC Object. However, If PCEP is
	not supported by a node (head-end of the SR tunnel) and controller		not supported by a node (head-end of the SR tunnel) and controller
	does not participate in IGP routing it has no way to learn the MSD of		does not participate in IGP routing it has no way to learn the MSD of
	the node or link configured. BGP-LS [I-D.ietf-idr-ls-distribution]		the node or link configured. BGP-LS [RFC7752] defines a way to
	defines a way to expose topology and associated different attributes,		expose topology and associated different attributes, capabilities of
	capabilities of the nodes in that topology to a centralized		the nodes in that topology to a centralized controller and MSD has
	controller and MSD has been defined in		been defined in [I-D.tantsura-bgp-ls-segment-routing-msd]. For this
	[I-D.tantsura-bgp-ls-segment-routing-msd]. For this information to		information to be advertised by BGP for the all nodes and links of
	be advertised by BGP for the all nodes and links of the network,		the network, where this is provisioned, OSPF module should have this
	where this is provisioned, OSPF module should have this information		information in the LSDB.
	in the LSDB.
	[I-D.ietf-ospf-mpls-elc] defines, RLSDC which indicates how many		[I-D.ietf-ospf-mpls-elc] defines, RLSDC which indicates how many
	labels a node can read to take a decision to insert an Entropy Label		labels a node can read to take a decision to insert an Entropy Label
	(EL) and is different than how many labels a node can push as defined		(EL) and is different than how many labels a node can push as defined
	by MSD in this draft.		by MSD in this draft.
	1.1. Conventions used in this document		1.1. Conventions used in this document
	1.1.1. Terminology		1.1.1. Terminology
	skipping to change at page 5, line 21 ¶		skipping to change at page 5, line 21 ¶
	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>.
	[RFC4970] Lindem, A., Ed., Shen, N., Vasseur, JP., Aggarwal, R., and		[RFC4970] 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 4970, DOI 10.17487/RFC4970, July		Router Capabilities", RFC 4970, DOI 10.17487/RFC4970, July
	2007, <http://www.rfc-editor.org/info/rfc4970>.		2007, <http://www.rfc-editor.org/info/rfc4970>.
	8.2. Informative References		8.2. Informative References
	[I-D.ietf-idr-ls-distribution]
	Gredler, H., Medved, J., Previdi, S., Farrel, A., and S.
	Ray, "North-Bound Distribution of Link-State and TE
	Information using BGP", draft-ietf-idr-ls-distribution-13
	(work in progress), October 2015.
	[I-D.ietf-ospf-mpls-elc]		[I-D.ietf-ospf-mpls-elc]
	Xu, X., Kini, S., Sivabalan, S., Filsfils, C., and S.		Xu, X., Kini, S., Sivabalan, S., Filsfils, C., and S.
	Litkowski, "Signaling Entropy Label Capability Using		Litkowski, "Signaling Entropy Label Capability Using
	OSPF", draft-ietf-ospf-mpls-elc-01 (work in progress),		OSPF", draft-ietf-ospf-mpls-elc-02 (work in progress), May
	November 2015.		2016.
	[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.
	[I-D.ietf-pce-segment-routing]		[I-D.ietf-pce-segment-routing]
	Sivabalan, S., Medved, J., Filsfils, C., Crabbe, E.,		Sivabalan, S., Medved, J., Filsfils, C., Crabbe, E.,
	Lopez, V., Tantsura, J., Henderickx, W., and J. Hardwick,		Lopez, V., Tantsura, J., Henderickx, W., and J. Hardwick,
	"PCEP Extensions for Segment Routing", draft-ietf-pce-		"PCEP Extensions for Segment Routing", draft-ietf-pce-
	segment-routing-06 (work in progress), August 2015.		segment-routing-07 (work in progress), March 2016.
	[I-D.tantsura-bgp-ls-segment-routing-msd]		[I-D.tantsura-bgp-ls-segment-routing-msd]
	Tantsura, J., Mirsky, G., Sivabalan, S., and U. Chunduri,		Tantsura, J., Mirsky, G., Sivabalan, S., and U. Chunduri,
	"Signaling Maximum SID Depth using Border Gateway Protocol		"Signaling Maximum SID Depth using Border Gateway Protocol
	Link-State", draft-tantsura-bgp-ls-segment-routing-msd-02		Link-State", draft-tantsura-bgp-ls-segment-routing-msd-02
	(work in progress), January 2016.		(work in progress), January 2016.
	[RFC5838] Lindem, A., Ed., Mirtorabi, S., Roy, A., Barnes, M., and		[RFC5838] Lindem, A., Ed., Mirtorabi, S., Roy, A., Barnes, M., and
	R. Aggarwal, "Support of Address Families in OSPFv3",		R. Aggarwal, "Support of Address Families in OSPFv3",
	RFC 5838, DOI 10.17487/RFC5838, April 2010,		RFC 5838, DOI 10.17487/RFC5838, April 2010,
	<http://www.rfc-editor.org/info/rfc5838>.		<http://www.rfc-editor.org/info/rfc5838>.
	[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>.
			[RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and
			S. Ray, "North-Bound Distribution of Link-State and
			Traffic Engineering (TE) Information Using BGP", RFC 7752,
			DOI 10.17487/RFC7752, March 2016,
			<http://www.rfc-editor.org/info/rfc7752>.
	Authors' Addresses		Authors' Addresses
	Jeff Tantsura		Jeff Tantsura
	Ericsson		Individual
	Email: jeff.tantsura@ericsson.com		Email: jefftant.ietf@gmail.com
	Uma Chunduri		Uma Chunduri
	Ericsson		Individual
	Email: uma.chunduri@ericsson.com		Email: uma.chunduri@gmail.com
End of changes. 13 change blocks.
	26 lines changed or deleted		25 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/