< draft-ietf-idr-te-lsp-distribution-07.txt		draft-ietf-idr-te-lsp-distribution-08.txt >
	Network Working Group S. Previdi, Ed.		Network Working Group S. Previdi, Ed.
	Internet-Draft Cisco Systems, Inc.		Internet-Draft Cisco Systems, Inc.
	Intended status: Standards Track J. Dong, Ed.		Intended status: Standards Track J. Dong, Ed.
	Expires: January 2, 2018 M. Chen		Expires: June 29, 2018 M. Chen
	Huawei Technologies		Huawei Technologies
	H. Gredler		H. Gredler
	RtBrick Inc.		RtBrick Inc.
	J. Tantsura		J. Tantsura
	Individual		Individual
	July 1, 2017		December 26, 2017
	Distribution of Traffic Engineering (TE) Policies and State using BGP-LS		Distribution of Traffic Engineering (TE) Policies and State using BGP-LS
	draft-ietf-idr-te-lsp-distribution-07		draft-ietf-idr-te-lsp-distribution-08
	Abstract		Abstract
	This document describes a mechanism to collect the Traffic		This document describes a mechanism to collect the Traffic
	Engineering and Policy information that is locally available in a		Engineering and Policy information that is locally available in a
	router and advertise it into BGP-LS updates. Such information can be		router and advertise it into BGP-LS updates. Such information can be
	used by external components for path computation, re-optimization,		used by external components for path computation, re-optimization,
	service placement, network visualization, etc.		service placement, network visualization, etc.
	Requirements Language		Requirements Language
	skipping to change at page 1, line 39 ¶		skipping to change at page 1, line 39 ¶
	document are to be interpreted as described in RFC 2119 [RFC2119].		document are to be interpreted as described in RFC 2119 [RFC2119].
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	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 https://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 January 2, 2018.		This Internet-Draft will expire on June 29, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 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		(https://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.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	skipping to change at page 25, line 15 ¶		skipping to change at page 25, line 15 ¶
	Cisco Systems		Cisco Systems
	Email: cfilsfil@cisco.com		Email: cfilsfil@cisco.com
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	[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>.		<https://www.rfc-editor.org/info/rfc2119>.
	[RFC2205] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and S.		[RFC2205] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and S.
	Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1		Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1
	Functional Specification", RFC 2205, DOI 10.17487/RFC2205,		Functional Specification", RFC 2205, DOI 10.17487/RFC2205,
	September 1997, <http://www.rfc-editor.org/info/rfc2205>.		September 1997, <https://www.rfc-editor.org/info/rfc2205>.
	[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,		[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
	and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP		and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
	Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001,		Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001,
	<http://www.rfc-editor.org/info/rfc3209>.		<https://www.rfc-editor.org/info/rfc3209>.
	[RFC3473] Berger, L., Ed., "Generalized Multi-Protocol Label		[RFC3473] Berger, L., Ed., "Generalized Multi-Protocol Label
	Switching (GMPLS) Signaling Resource ReserVation Protocol-		Switching (GMPLS) Signaling Resource ReserVation Protocol-
	Traffic Engineering (RSVP-TE) Extensions", RFC 3473,		Traffic Engineering (RSVP-TE) Extensions", RFC 3473,
	DOI 10.17487/RFC3473, January 2003,		DOI 10.17487/RFC3473, January 2003,
	<http://www.rfc-editor.org/info/rfc3473>.		<https://www.rfc-editor.org/info/rfc3473>.
	[RFC4090] Pan, P., Ed., Swallow, G., Ed., and A. Atlas, Ed., "Fast		[RFC4090] Pan, P., Ed., Swallow, G., Ed., and A. Atlas, Ed., "Fast
	Reroute Extensions to RSVP-TE for LSP Tunnels", RFC 4090,		Reroute Extensions to RSVP-TE for LSP Tunnels", RFC 4090,
	DOI 10.17487/RFC4090, May 2005,		DOI 10.17487/RFC4090, May 2005,
	<http://www.rfc-editor.org/info/rfc4090>.		<https://www.rfc-editor.org/info/rfc4090>.
	[RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter,		[RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter,
	"Multiprotocol Extensions for BGP-4", RFC 4760,		"Multiprotocol Extensions for BGP-4", RFC 4760,
	DOI 10.17487/RFC4760, January 2007,		DOI 10.17487/RFC4760, January 2007,
	<http://www.rfc-editor.org/info/rfc4760>.		<https://www.rfc-editor.org/info/rfc4760>.
	[RFC4872] Lang, J., Ed., Rekhter, Y., Ed., and D. Papadimitriou,		[RFC4872] Lang, J., Ed., Rekhter, Y., Ed., and D. Papadimitriou,
	Ed., "RSVP-TE Extensions in Support of End-to-End		Ed., "RSVP-TE Extensions in Support of End-to-End
	Generalized Multi-Protocol Label Switching (GMPLS)		Generalized Multi-Protocol Label Switching (GMPLS)
	Recovery", RFC 4872, DOI 10.17487/RFC4872, May 2007,		Recovery", RFC 4872, DOI 10.17487/RFC4872, May 2007,
	<http://www.rfc-editor.org/info/rfc4872>.		<https://www.rfc-editor.org/info/rfc4872>.
	[RFC4873] Berger, L., Bryskin, I., Papadimitriou, D., and A. Farrel,		[RFC4873] Berger, L., Bryskin, I., Papadimitriou, D., and A. Farrel,
	"GMPLS Segment Recovery", RFC 4873, DOI 10.17487/RFC4873,		"GMPLS Segment Recovery", RFC 4873, DOI 10.17487/RFC4873,
	May 2007, <http://www.rfc-editor.org/info/rfc4873>.		May 2007, <https://www.rfc-editor.org/info/rfc4873>.
	[RFC4874] Lee, CY., Farrel, A., and S. De Cnodder, "Exclude Routes -		[RFC4874] Lee, CY., Farrel, A., and S. De Cnodder, "Exclude Routes -
	Extension to Resource ReserVation Protocol-Traffic		Extension to Resource ReserVation Protocol-Traffic
	Engineering (RSVP-TE)", RFC 4874, DOI 10.17487/RFC4874,		Engineering (RSVP-TE)", RFC 4874, DOI 10.17487/RFC4874,
	April 2007, <http://www.rfc-editor.org/info/rfc4874>.		April 2007, <https://www.rfc-editor.org/info/rfc4874>.
	[RFC5420] Farrel, A., Ed., Papadimitriou, D., Vasseur, JP., and A.		[RFC5420] Farrel, A., Ed., Papadimitriou, D., Vasseur, JP., and A.
	Ayyangarps, "Encoding of Attributes for MPLS LSP		Ayyangarps, "Encoding of Attributes for MPLS LSP
	Establishment Using Resource Reservation Protocol Traffic		Establishment Using Resource Reservation Protocol Traffic
	Engineering (RSVP-TE)", RFC 5420, DOI 10.17487/RFC5420,		Engineering (RSVP-TE)", RFC 5420, DOI 10.17487/RFC5420,
	February 2009, <http://www.rfc-editor.org/info/rfc5420>.		February 2009, <https://www.rfc-editor.org/info/rfc5420>.
	[RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation		[RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation
	Element (PCE) Communication Protocol (PCEP)", RFC 5440,		Element (PCE) Communication Protocol (PCEP)", RFC 5440,
	DOI 10.17487/RFC5440, March 2009,		DOI 10.17487/RFC5440, March 2009,
	<http://www.rfc-editor.org/info/rfc5440>.		<https://www.rfc-editor.org/info/rfc5440>.
	[RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and		[RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and
	S. Ray, "North-Bound Distribution of Link-State and		S. Ray, "North-Bound Distribution of Link-State and
	Traffic Engineering (TE) Information Using BGP", RFC 7752,		Traffic Engineering (TE) Information Using BGP", RFC 7752,
	DOI 10.17487/RFC7752, March 2016,		DOI 10.17487/RFC7752, March 2016,
	<http://www.rfc-editor.org/info/rfc7752>.		<https://www.rfc-editor.org/info/rfc7752>.
	8.2. Informative References		8.2. Informative References
	[I-D.ietf-idr-tunnel-encaps]		[I-D.ietf-idr-tunnel-encaps]
	Rosen, E., Patel, K., and G. Velde, "The BGP Tunnel		Rosen, E., Patel, K., and G. Velde, "The BGP Tunnel
	Encapsulation Attribute", draft-ietf-idr-tunnel-encaps-06		Encapsulation Attribute", draft-ietf-idr-tunnel-encaps-07
	(work in progress), June 2017.		(work in progress), July 2017.
	[I-D.ietf-pce-stateful-pce]		[I-D.ietf-pce-stateful-pce]
	Crabbe, E., Minei, I., Medved, J., and R. Varga, "PCEP		Crabbe, E., Minei, I., Medved, J., and R. Varga, "PCEP
	Extensions for Stateful PCE", draft-ietf-pce-stateful-		Extensions for Stateful PCE", draft-ietf-pce-stateful-
	pce-21 (work in progress), June 2017.		pce-21 (work in progress), June 2017.
	[I-D.previdi-idr-segment-routing-te-policy]		[I-D.previdi-idr-segment-routing-te-policy]
	Previdi, S., Filsfils, C., Mattes, P., Rosen, E., and S.		Previdi, S., Filsfils, C., Mattes, P., Rosen, E., and S.
	Lin, "Advertising Segment Routing Policies in BGP", draft-		Lin, "Advertising Segment Routing Policies in BGP", draft-
	previdi-idr-segment-routing-te-policy-07 (work in		previdi-idr-segment-routing-te-policy-07 (work in
	progress), June 2017.		progress), June 2017.
	[RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation		[RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation
	Element (PCE)-Based Architecture", RFC 4655,		Element (PCE)-Based Architecture", RFC 4655,
	DOI 10.17487/RFC4655, August 2006,		DOI 10.17487/RFC4655, August 2006,
	<http://www.rfc-editor.org/info/rfc4655>.		<https://www.rfc-editor.org/info/rfc4655>.
	[RFC6952] Jethanandani, M., Patel, K., and L. Zheng, "Analysis of		[RFC6952] Jethanandani, M., Patel, K., and L. Zheng, "Analysis of
	BGP, LDP, PCEP, and MSDP Issues According to the Keying		BGP, LDP, PCEP, and MSDP Issues According to the Keying
	and Authentication for Routing Protocols (KARP) Design		and Authentication for Routing Protocols (KARP) Design
	Guide", RFC 6952, DOI 10.17487/RFC6952, May 2013,		Guide", RFC 6952, DOI 10.17487/RFC6952, May 2013,
	<http://www.rfc-editor.org/info/rfc6952>.		<https://www.rfc-editor.org/info/rfc6952>.
	Authors' Addresses		Authors' Addresses
	Stefano Previdi (editor)		Stefano Previdi (editor)
	Cisco Systems, Inc.		Cisco Systems, Inc.
	Email: stefano@previdi.net		Email: stefano@previdi.net
	Jie Dong (editor)		Jie Dong (editor)
	Huawei Technologies		Huawei Technologies
End of changes. 21 change blocks.
	22 lines changed or deleted		22 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/