< draft-ietf-idr-te-lsp-distribution-15.txt		draft-ietf-idr-te-lsp-distribution-16.txt >
	Network Working Group S. Previdi		Network Working Group S. Previdi
	Internet-Draft		Internet-Draft
	Intended status: Standards Track K. Talaulikar, Ed.		Intended status: Standards Track K. Talaulikar, Ed.
	Expires: November 6, 2021 Cisco Systems, Inc.		Expires: April 25, 2022 Cisco Systems, Inc.
	J. Dong, Ed.		J. Dong, Ed.
	M. Chen		M. Chen
	Huawei Technologies		Huawei Technologies
	H. Gredler		H. Gredler
	RtBrick Inc.		RtBrick Inc.
	J. Tantsura		J. Tantsura
	Apstra		Apstra
	May 5, 2021		October 22, 2021
	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-15		draft-ietf-idr-te-lsp-distribution-16
	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
	node and advertise it into BGP Link State (BGP-LS) updates. Such		node and advertise it into BGP Link State (BGP-LS) updates. Such
	information can be used by external components for path computation,		information can be used by external components for path computation,
	re-optimization, service placement, network visualization, etc.		re-optimization, service placement, network visualization, etc.
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 42 ¶		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 https://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 November 6, 2021.		This Internet-Draft will expire on April 25, 2022.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 IETF Trust and the persons identified as the		Copyright (c) 2021 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
	(https://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
	skipping to change at page 7, line 19 ¶		skipping to change at page 7, line 19 ¶
	| 551 | LSP ID |		| 551 | LSP ID |
	| 552 | IPv4/6 Tunnel Head-end address |		| 552 | IPv4/6 Tunnel Head-end address |
	| 553 | IPv4/6 Tunnel Tail-end address |		| 553 | IPv4/6 Tunnel Tail-end address |
	| 554 | SR Policy Candidate Path |		| 554 | SR Policy Candidate Path |
	| 555 | Local MPLS Cross Connect |		| 555 | Local MPLS Cross Connect |
	+-----------+----------------------------------+		+-----------+----------------------------------+
	The Local Node Descriptor TLV MUST include the following Node		The Local Node Descriptor TLV MUST include the following Node
	Descriptor TLVs:		Descriptor TLVs:
	o BGP Router-ID (TLV 516) [I-D.ietf-idr-bgpls-segment-routing-epe],		o BGP Router-ID (TLV 516) [RFC9086], which contains a valid BGP
	which contains a valid BGP Identifier of the local node.		Identifier of the local node.
	o Autonomous System Number (TLV 512) [RFC7752], which contains the		o Autonomous System Number (TLV 512) [RFC7752], which contains the
	ASN or AS Confederation Identifier (ASN) [RFC5065], if		ASN or AS Confederation Identifier (ASN) [RFC5065], if
	confederations are used, of the local node.		confederations are used, of the local node.
	The Local Node Descriptor TLV SHOULD include the following Node		The Local Node Descriptor TLV SHOULD include the following Node
	Descriptor TLVs:		Descriptor TLVs:
	o IPv4 Router-ID of Local Node (TLV 1028) [RFC7752], which contains		o IPv4 Router-ID of Local Node (TLV 1028) [RFC7752], which contains
	the IPv4 TE Router-ID of the local node when one is provisioned.		the IPv4 TE Router-ID of the local node when one is provisioned.
	o IPv6 Router-ID of Local Node (TLV 1029) [RFC7752], which contains		o IPv6 Router-ID of Local Node (TLV 1029) [RFC7752], which contains
	the IPv6 TE Router-ID of the local node when one is provisioned.		the IPv6 TE Router-ID of the local node when one is provisioned.
	The Local Node Descriptor TLV MAY include the following Node		The Local Node Descriptor TLV MAY include the following Node
	Descriptor TLVs:		Descriptor TLVs:
	o Member-ASN (TLV 517) [I-D.ietf-idr-bgpls-segment-routing-epe],		o Member-ASN (TLV 517) [RFC9086], which contains the ASN of the
	which contains the ASN of the confederation member (i.e. Member-		confederation member (i.e. Member-AS Number), if BGP
	AS Number), if BGP confederations are used, of the local node.		confederations are used, of the local node.
	o Node Descriptors as defined in [RFC7752].		o Node Descriptors as defined in [RFC7752].
	4. TE Policy Descriptors		4. TE Policy Descriptors
	This sections defines the TE Policy Descriptors TLVs which are used		This sections defines the TE Policy Descriptors TLVs which are used
	to describe the TE Policy being advertised by using the new BGP-LS TE		to describe the TE Policy being advertised by using the new BGP-LS TE
	Policy NLRI type defined in Section 3.		Policy NLRI type defined in Section 3.
	4.1. Tunnel Identifier (Tunnel ID)		4.1. Tunnel Identifier (Tunnel ID)
	skipping to change at page 49, line 24 ¶		skipping to change at page 49, line 24 ¶
	12. Acknowledgements		12. Acknowledgements
	The authors would like to thank Dhruv Dhody, Mohammed Abdul Aziz		The authors would like to thank Dhruv Dhody, Mohammed Abdul Aziz
	Khalid, Lou Berger, Acee Lindem, Siva Sivabalan, Arjun Sreekantiah,		Khalid, Lou Berger, Acee Lindem, Siva Sivabalan, Arjun Sreekantiah,
	and Dhanendra Jain for their review and valuable comments.		and Dhanendra Jain for their review and valuable comments.
	13. References		13. References
	13.1. Normative References		13.1. Normative References
	[I-D.ietf-idr-bgpls-segment-routing-epe]
	Previdi, S., Talaulikar, K., Filsfils, C., Patel, K., Ray,
	S., and J. Dong, "BGP-LS extensions for Segment Routing
	BGP Egress Peer Engineering", draft-ietf-idr-bgpls-
	segment-routing-epe-19 (work in progress), May 2019.
	[I-D.ietf-idr-bgpls-srv6-ext]		[I-D.ietf-idr-bgpls-srv6-ext]
	Dawra, G., Filsfils, C., Talaulikar, K., Chen, M.,		Dawra, G., Filsfils, C., Talaulikar, K., Chen, M.,
	Bernier, D., and B. Decraene, "BGP Link State Extensions		Bernier, D., and B. Decraene, "BGP Link State Extensions
	for SRv6", draft-ietf-idr-bgpls-srv6-ext-07 (work in		for SRv6", draft-ietf-idr-bgpls-srv6-ext-08 (work in
	progress), March 2021.		progress), June 2021.
	[I-D.ietf-spring-segment-routing-policy]		[I-D.ietf-spring-segment-routing-policy]
	Filsfils, C., Talaulikar, K., Voyer, D., Bogdanov, A., and		Filsfils, C., Talaulikar, K., Voyer, D., Bogdanov, A., and
	P. Mattes, "Segment Routing Policy Architecture", draft-		P. Mattes, "Segment Routing Policy Architecture", draft-
	ietf-spring-segment-routing-policy-11 (work in progress),		ietf-spring-segment-routing-policy-13 (work in progress),
	April 2021.		May 2021.
	[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,
	<https://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, <https://www.rfc-editor.org/info/rfc2205>.		September 1997, <https://www.rfc-editor.org/info/rfc2205>.
	skipping to change at page 51, line 21 ¶		skipping to change at page 51, line 15 ¶
	[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC		[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
	2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,		2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
	May 2017, <https://www.rfc-editor.org/info/rfc8174>.		May 2017, <https://www.rfc-editor.org/info/rfc8174>.
	[RFC8986] Filsfils, C., Ed., Camarillo, P., Ed., Leddy, J., Voyer,		[RFC8986] Filsfils, C., Ed., Camarillo, P., Ed., Leddy, J., Voyer,
	D., Matsushima, S., and Z. Li, "Segment Routing over IPv6		D., Matsushima, S., and Z. Li, "Segment Routing over IPv6
	(SRv6) Network Programming", RFC 8986,		(SRv6) Network Programming", RFC 8986,
	DOI 10.17487/RFC8986, February 2021,		DOI 10.17487/RFC8986, February 2021,
	<https://www.rfc-editor.org/info/rfc8986>.		<https://www.rfc-editor.org/info/rfc8986>.
			[RFC9086] Previdi, S., Talaulikar, K., Ed., Filsfils, C., Patel, K.,
			Ray, S., and J. Dong, "Border Gateway Protocol - Link
			State (BGP-LS) Extensions for Segment Routing BGP Egress
			Peer Engineering", RFC 9086, DOI 10.17487/RFC9086, August
			2021, <https://www.rfc-editor.org/info/rfc9086>.
	13.2. Informative References		13.2. Informative References
	[RFC2702] Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M., and J.		[RFC2702] Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M., and J.
	McManus, "Requirements for Traffic Engineering Over MPLS",		McManus, "Requirements for Traffic Engineering Over MPLS",
	RFC 2702, DOI 10.17487/RFC2702, September 1999,		RFC 2702, DOI 10.17487/RFC2702, September 1999,
	<https://www.rfc-editor.org/info/rfc2702>.		<https://www.rfc-editor.org/info/rfc2702>.
	[RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering		[RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering
	(TE) Extensions to OSPF Version 2", RFC 3630,		(TE) Extensions to OSPF Version 2", RFC 3630,
	DOI 10.17487/RFC3630, September 2003,		DOI 10.17487/RFC3630, September 2003,
	skipping to change at page 52, line 31 ¶		skipping to change at page 52, line 31 ¶
	Authors' Addresses		Authors' Addresses
	Stefano Previdi		Stefano Previdi
	Email: stefano@previdi.net		Email: stefano@previdi.net
	Ketan Talaulikar (editor)		Ketan Talaulikar (editor)
	Cisco Systems, Inc.		Cisco Systems, Inc.
	India		India
	Email: ketant@cisco.com		Email: ketant.ietf@gmail.com
	Jie Dong (editor)		Jie Dong (editor)
	Huawei Technologies		Huawei Technologies
	Huawei Campus, No. 156 Beiqing Rd.		Huawei Campus, No. 156 Beiqing Rd.
	Beijing 100095		Beijing 100095
	China		China
	Email: jie.dong@huawei.com		Email: jie.dong@huawei.com
	Mach(Guoyi) Chen		Mach(Guoyi) Chen
End of changes. 11 change blocks.
	20 lines changed or deleted		20 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/