< draft-ietf-idr-bgp-ls-sbfd-extensions-00.txt		draft-ietf-idr-bgp-ls-sbfd-extensions-01.txt >
	Inter-Domain Routing Z. Li		Inter-Domain Routing Z. Li
	Internet-Draft S. Zhuang		Internet-Draft S. Zhuang
	Intended status: Standards Track Huawei		Intended status: Standards Track Huawei
	Expires: December 1, 2019 K. Talaulikar		Expires: May 4, 2020 K. Talaulikar
	Cisco Systems		Cisco Systems
	S. Aldrin		S. Aldrin
	Google, Inc		Google, Inc
	J. Tantsura		J. Tantsura
	Apstra		Apstra
	G. Mirsky		G. Mirsky
	ZTE Corp.		ZTE Corp.
	May 30, 2019		November 1, 2019
	BGP Link-State Extensions for Seamless BFD		BGP Link-State Extensions for Seamless BFD
	draft-ietf-idr-bgp-ls-sbfd-extensions-00		draft-ietf-idr-bgp-ls-sbfd-extensions-01
	Abstract		Abstract
	Seamless Bidirectional Forwarding Detection (S-BFD) defines a		Seamless Bidirectional Forwarding Detection (S-BFD) defines a
	simplified mechanism to use Bidirectional Forwarding Detection (BFD)		simplified mechanism to use Bidirectional Forwarding Detection (BFD)
	with large portions of negotiation aspects eliminated, thus providing		with large portions of negotiation aspects eliminated, thus providing
	benefits such as quick provisioning as well as improved control and		benefits such as quick provisioning as well as improved control and
	flexibility to network nodes initiating the path monitoring. The		flexibility to network nodes initiating the path monitoring. The
	link-state routing protocols (IS-IS and OSPF) have been extended to		link-state routing protocols (IS-IS and OSPF) have been extended to
	advertise the Seamless BFD (S-BFD) Discriminators.		advertise the Seamless BFD (S-BFD) Discriminators.
	skipping to change at page 2, line 10 ¶		skipping to change at page 2, line 10 ¶
	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 December 1, 2019.		This Internet-Draft will expire on May 4, 2020.
	Copyright Notice		Copyright Notice
	Copyright (c) 2019 IETF Trust and the persons identified as the		Copyright (c) 2019 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 2, line 41 ¶		skipping to change at page 2, line 41 ¶
	3. Problem and Requirement . . . . . . . . . . . . . . . . . . . 3		3. Problem and Requirement . . . . . . . . . . . . . . . . . . . 3
	4. BGP-LS Extensions for S-BFD Discriminator . . . . . . . . . . 4		4. BGP-LS Extensions for S-BFD Discriminator . . . . . . . . . . 4
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
	6. Manageability Considerations . . . . . . . . . . . . . . . . 6		6. Manageability Considerations . . . . . . . . . . . . . . . . 6
	6.1. Operational Considerations . . . . . . . . . . . . . . . 6		6.1. Operational Considerations . . . . . . . . . . . . . . . 6
	6.2. Management Considerations . . . . . . . . . . . . . . . . 6		6.2. Management Considerations . . . . . . . . . . . . . . . . 6
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 6		7. Security Considerations . . . . . . . . . . . . . . . . . . . 6
	8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7		8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7		9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
	9.1. Normative References . . . . . . . . . . . . . . . . . . 7		9.1. Normative References . . . . . . . . . . . . . . . . . . 7
	9.2. Informative References . . . . . . . . . . . . . . . . . 7		9.2. Informative References . . . . . . . . . . . . . . . . . 8
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
	1. Introduction		1. Introduction
	Seamless Bidirectional Forwarding Detection (S-BFD) [RFC7880] defines		Seamless Bidirectional Forwarding Detection (S-BFD) [RFC7880] defines
	a simplified mechanism to use Bidirectional Forwarding Detection		a simplified mechanism to use Bidirectional Forwarding Detection
	(BFD) [RFC5880] with large portions of negotiation aspects		(BFD) [RFC5880] with large portions of negotiation aspects
	eliminated, thus providing benefits such as quick provisioning as		eliminated, thus providing benefits such as quick provisioning as
	well as improved control and flexibility to network nodes initiating		well as improved control and flexibility to network nodes initiating
	the path monitoring.		the path monitoring.
	skipping to change at page 5, line 23 ¶		skipping to change at page 5, line 23 ¶
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| ... |		| ... |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Discriminator n (Optional) |		| Discriminator n (Optional) |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 1: S-BFD Discriminators TLV		Figure 1: S-BFD Discriminators TLV
	where:		where:
	o Type: TBD (see IANA Considerations Section 5)		o Type: 1032
	o Length: variable. Minimum of 8 octets and increments of 4 octets		o Length: variable. Minimum of 8 octets and increments of 4 octets
	there on for each additional discriminator		there on for each additional discriminator
	o Discriminators : multiples of 4 octets, each carrying a S-BFD		o Discriminators : multiples of 4 octets, each carrying a S-BFD
	local discriminator value of the node. At least one discriminator		local discriminator value of the node. At least one discriminator
	MUST be included in the TLV.		MUST be included in the TLV.
	The S-BFD Discriminators TLV can only be added to the BGP-LS		The S-BFD Discriminators TLV can only be added to the BGP-LS
	Attribute associated with the Node NLRI that originates the		Attribute associated with the Node NLRI that originates the
	skipping to change at page 6, line 9 ¶		skipping to change at page 6, line 9 ¶
	When the node is not running any of the IGPs but running a protocol		When the node is not running any of the IGPs but running a protocol
	like BGP, then the locally provisioned S-BFD discriminators of the		like BGP, then the locally provisioned S-BFD discriminators of the
	node MAY be originated as part of the BGP-LS attribute within the		node MAY be originated as part of the BGP-LS attribute within the
	Node NLRI corresponding to the local node.		Node NLRI corresponding to the local node.
	5. IANA Considerations		5. IANA Considerations
	This document requests assigning code-points from the registry "BGP-		This document requests assigning code-points from the registry "BGP-
	LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute		LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute
	TLVs" based on table below. The column "IS-IS TLV/Sub-TLV" defined		TLVs" based on table below which reflects the values assigned via the
	in the registry does not require any value and should be left empty.		early allocation process. The column "IS-IS TLV/Sub-TLV" defined in
			the registry does not require any value and should be left empty.
	+---------------+--------------------------+----------+		+---------------+--------------------------+----------+
	| Code Point | Description | Length |		| Code Point | Description | Length |
	+---------------+--------------------------+----------+		+---------------+--------------------------+----------+
	| TBD | S-BFD Discriminators TLV | variable |		| 1032 | S-BFD Discriminators TLV | variable |
	+---------------+--------------------------+----------+		+---------------+--------------------------+----------+
	6. Manageability Considerations		6. Manageability Considerations
	This section is structured as recommended in [RFC5706].		This section is structured as recommended in [RFC5706].
	The new protocol extensions introduced in this document augment the		The new protocol extensions introduced in this document augment the
	existing IGP topology information that was distributed via [RFC7752].		existing IGP topology information that was distributed via [RFC7752].
	Procedures and protocol extensions defined in this document do not		Procedures and protocol extensions defined in this document do not
	affect the BGP protocol operations and management other than as		affect the BGP protocol operations and management other than as
	skipping to change at page 8, line 11 ¶		skipping to change at page 8, line 13 ¶
	May 2017, <https://www.rfc-editor.org/info/rfc8174>.		May 2017, <https://www.rfc-editor.org/info/rfc8174>.
	9.2. Informative References		9.2. Informative References
	[I-D.ietf-mpls-seamless-mpls]		[I-D.ietf-mpls-seamless-mpls]
	Leymann, N., Decraene, B., Filsfils, C., Konstantynowicz,		Leymann, N., Decraene, B., Filsfils, C., Konstantynowicz,
	M., and D. Steinberg, "Seamless MPLS Architecture", draft-		M., and D. Steinberg, "Seamless MPLS Architecture", draft-
	ietf-mpls-seamless-mpls-07 (work in progress), June 2014.		ietf-mpls-seamless-mpls-07 (work in progress), June 2014.
	[I-D.ietf-spring-segment-routing-policy]		[I-D.ietf-spring-segment-routing-policy]
	Filsfils, C., Sivabalan, S., daniel.voyer@bell.ca, d.,		Filsfils, C., Sivabalan, S., Voyer, D., Bogdanov, A., and
	bogdanov@google.com, b., and P. Mattes, "Segment Routing		P. Mattes, "Segment Routing Policy Architecture", draft-
	Policy Architecture", draft-ietf-spring-segment-routing-		ietf-spring-segment-routing-policy-03 (work in progress),
	policy-03 (work in progress), May 2019.		May 2019.
	[RFC5706] Harrington, D., "Guidelines for Considering Operations and		[RFC5706] Harrington, D., "Guidelines for Considering Operations and
	Management of New Protocols and Protocol Extensions",		Management of New Protocols and Protocol Extensions",
	RFC 5706, DOI 10.17487/RFC5706, November 2009,		RFC 5706, DOI 10.17487/RFC5706, November 2009,
	<https://www.rfc-editor.org/info/rfc5706>.		<https://www.rfc-editor.org/info/rfc5706>.
	[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection		[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
	(BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010,		(BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010,
	<https://www.rfc-editor.org/info/rfc5880>.		<https://www.rfc-editor.org/info/rfc5880>.
End of changes. 9 change blocks.
	13 lines changed or deleted		14 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/