draft-filsfils-spring-sr-recursing-info-03.txt		draft-filsfils-spring-sr-recursing-info-04.txt
	SPRING C. Filsfils		SPRING C. Filsfils
	Internet-Draft S. Previdi		Internet-Draft S. Previdi
	Intended status: Standards Track P. Psenak		Intended status: Standards Track P. Psenak
	Expires: April 20, 2017 L. Ginsberg		Expires: October 13, 2017 L. Ginsberg
	Cisco Systems, Inc.		Cisco Systems, Inc.
	October 17, 2016		April 11, 2017
	Segment Routing Recursive Information		Segment Routing Recursive Information
	draft-filsfils-spring-sr-recursing-info-03		draft-filsfils-spring-sr-recursing-info-04
	Abstract		Abstract
	Segment Routing (SR) allows for a flexible definition of end-to-end		Segment Routing (SR) allows for a flexible definition of end-to-end
	paths within IGP topologies by encoding paths as sequences of		paths within IGP topologies by encoding paths as sequences of
	topological sub-paths, called "segments". These segments are		topological sub-paths, called "segments". These segments are
	advertised by the link-state routing protocols (IS-IS and OSPF).		advertised by the link-state routing protocols (IS-IS and OSPF).
	There are use cases where it is desirable to utilize a SID associated		There are use cases where it is desirable to utilize a SID associated
	with a given node in order to transport traffic destined to different		with a given node in order to transport traffic destined to different
	skipping to change at page 1, line 46 ¶		skipping to change at page 1, line 46 ¶
	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 April 20, 2017.		This Internet-Draft will expire on October 13, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2016 IETF Trust and the persons identified as the		Copyright (c) 2017 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
	skipping to change at page 7, line 31 ¶		skipping to change at page 7, line 31 ¶
	8. Acknowledgements		8. Acknowledgements
	We would like to thank Les Ginsberg and Ahmed Bashandy for their		We would like to thank Les Ginsberg and Ahmed Bashandy for their
	contributions.		contributions.
	9. Normative References		9. Normative References
	[I-D.ietf-spring-segment-routing]		[I-D.ietf-spring-segment-routing]
	Filsfils, C., Previdi, S., Decraene, B., Litkowski, S.,		Filsfils, C., Previdi, S., Decraene, B., Litkowski, S.,
	and R. Shakir, "Segment Routing Architecture", draft-ietf-		and R. Shakir, "Segment Routing Architecture", draft-ietf-
	spring-segment-routing-09 (work in progress), July 2016.		spring-segment-routing-11 (work in progress), February
			2017.
	[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>.
	Authors' Addresses		Authors' Addresses
	Clarence Filsfils		Clarence Filsfils
	Cisco Systems, Inc.		Cisco Systems, Inc.
End of changes. 6 change blocks.
	6 lines changed or deleted		7 lines changed or added
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/