< draft-ietf-bier-ospf-bier-extensions-14.txt		draft-ietf-bier-ospf-bier-extensions-15.txt >
	OSPF P. Psenak, Ed.		OSPF P. Psenak, Ed.
	Internet-Draft N. Kumar		Internet-Draft N. Kumar
	Intended status: Standards Track IJ. Wijnands		Intended status: Standards Track IJ. Wijnands
	Expires: August 26, 2018 Cisco		Expires: August 27, 2018 Cisco
	A. Dolganow		A. Dolganow
	Nokia		Nokia
	T. Przygienda		T. Przygienda
	J. Zhang		J. Zhang
	Juniper Networks, Inc.		Juniper Networks, Inc.
	S. Aldrin		S. Aldrin
	Google, Inc.		Google, Inc.
	February 22, 2018		February 23, 2018
	OSPF Extensions for BIER		OSPF Extensions for BIER
	draft-ietf-bier-ospf-bier-extensions-14.txt		draft-ietf-bier-ospf-bier-extensions-15.txt
	Abstract		Abstract
	Bit Index Explicit Replication (BIER) is an architecture that		Bit Index Explicit Replication (BIER) is an architecture that
	provides multicast forwarding through a "BIER domain" without		provides multicast forwarding through a "BIER domain" without
	requiring intermediate routers to maintain multicast related per-flow		requiring intermediate routers to maintain multicast related per-flow
	state. Neither does BIER require an explicit tree-building protocol		state. Neither does BIER require an explicit tree-building protocol
	for its operation. A multicast data packet enters a BIER domain at a		for its operation. A multicast data packet enters a BIER domain at a
	"Bit-Forwarding Ingress Router" (BFIR), and leaves the BIER domain at		"Bit-Forwarding Ingress Router" (BFIR), and leaves the BIER domain at
	one or more "Bit-Forwarding Egress Routers" (BFERs). The BFIR router		one or more "Bit-Forwarding Egress Routers" (BFERs). The BFIR router
	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 August 26, 2018.		This Internet-Draft will expire on August 27, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2018 IETF Trust and the persons identified as the		Copyright (c) 2018 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 4, line 16 ¶		skipping to change at page 4, line 16 ¶
	Length: Variable, dependent on sub-TLVs.		Length: Variable, dependent on sub-TLVs.
	Sub-domain-ID: Unique value identifying the BIER sub-domain within		Sub-domain-ID: Unique value identifying the BIER sub-domain within
	the BIER domain, as described in section 1 of [RFC8279].		the BIER domain, as described in section 1 of [RFC8279].
	MT-ID: Multi-Topology ID (as defined in [RFC4915]) that identifies		MT-ID: Multi-Topology ID (as defined in [RFC4915]) that identifies
	the topology that is associated with the BIER sub-domain.		the topology that is associated with the BIER sub-domain.
	BFR-id: A 2 octet field encoding the BFR-id, as documented in		BFR-id: A 2 octet field encoding the BFR-id, as documented in
	section 2 of [RFC8279]. If the BFR is not locally configured with		section 2 of [RFC8279]. If the BFR is not locally configured with
	a valid BFR-id, the value of this field is set to invalid BFR-id		a valid BFR-id, the value of this field is set to 0, which is
	per [RFC8279].		defined as illegal in [RFC8279].
	BAR: Single octet BIER specific algorithm used to calculate		BAR: Single octet BIER specific algorithm used to calculate
	underlay paths to reach other BFRs. Values are allocated from the		underlay paths to reach other BFRs. Values are allocated from the
	"BIER Algorithm Registry" which is defined in		"BIER Algorithm Registry" which is defined in
	[I-D.ietf-bier-isis-extensions].		[I-D.ietf-bier-isis-extensions].
	IPA: Single octet IGP algorithm to either modify, enhance or		IPA: Single octet IGP algorithm to either modify, enhance or
	replace the calculation of underlay paths to reach other BFRs as		replace the calculation of underlay paths to reach other BFRs as
	defined by the BAR value. Values are defined in the "IGP		defined by the BAR value. Values are defined in the "IGP
	Algorithm Types" registry.		Algorithm Types" registry.
	Each BFR sub-domain MUST be associated with one and only one OSPF		Each BFR sub-domain MUST be associated with one and only one OSPF
	topology that is identified by the MT-ID. If the association between		topology that is identified by the MT-ID. If the association between
	BIER sub-domain and OSPF topology advertised in the BIER sub-TLV by		BIER sub-domain and OSPF topology advertised in the BIER sub-TLV by
	other BFRs is in conflict with the association locally configured on		other BFRs is in conflict with the association locally configured on
	the receiving router, the BIER Sub-TLV MUST be ignored.		the receiving router, the BIER Sub-TLV MUST be ignored.
			If the MT-ID value is outside of the values specified in [RFC4915],
			the BIER Sub-TLV MUST be ignored.
	If a BFR advertises the same Sub-domain-ID in multiple BIER sub-TLVs,		If a BFR advertises the same Sub-domain-ID in multiple BIER sub-TLVs,
	the BRF MUST be treated as if it did not advertise a BIER sub-TLV for		the BRF MUST be treated as if it did not advertise a BIER sub-TLV for
	such sub-domain.		such sub-domain.
	All BFRs MUST detect advertisement of duplicate valid BFR-IDs for a		All BFRs MUST detect advertisement of duplicate valid BFR-IDs for a
	given MT-ID and Sub-domain-ID. When such duplication is detected all		given MT-ID and Sub-domain-ID. When such duplication is detected by
	BFRs advertising duplicates MUST be treated as if they did not		the BFR, it MUST behave as described in section 5 of [RFC8279].
	advertise a valid BFR-id.
	The supported BAR and IPA algorithms MUST be consistent for all		The supported BAR and IPA algorithms MUST be consistent for all
	routers supporting a given BFR sub-domain. A router receiving BIER		routers supporting a given BFR sub-domain. A router receiving BIER
	Sub-TLV advertisement with a value in BAR or IPA fields which does		Sub-TLV advertisement with a value in BAR or IPA fields which does
	not match the locally configured value for a given BFR sub-domain,		not match the locally configured value for a given BFR sub-domain,
	MUST report a misconfiguration for such BIER sub-domain and MUST		MUST report a misconfiguration for such BIER sub-domain and MUST
	ignore such BIER sub-TLV.		ignore such BIER sub-TLV.
	The use of non-zero values in either the BAR field or the IPA field		The use of non-zero values in either the BAR field or the IPA field
	is outside the scope of this document.		is outside the scope of this document.
	skipping to change at page 6, line 5 ¶		skipping to change at page 6, line 5 ¶
	and ending with (Label + (Max SI)). A unique label range is		and ending with (Label + (Max SI)). A unique label range is
	allocated for each BitStream length and Sub-domain-ID. These		allocated for each BitStream length and Sub-domain-ID. These
	labels are used for BIER forwarding as described in [RFC8279] and		labels are used for BIER forwarding as described in [RFC8279] and
	[RFC8296].		[RFC8296].
	The size of the label range is determined by the number of Set		The size of the label range is determined by the number of Set
	Identifiers (SI) (section 1 of [RFC8279]) that are used in the		Identifiers (SI) (section 1 of [RFC8279]) that are used in the
	network. Each SI maps to a single label in the label range. The		network. Each SI maps to a single label in the label range. The
	first label is for SI=0, the second label is for SI=1, etc.		first label is for SI=0, the second label is for SI=1, etc.
			If the BS length is set to a value that does not match any of the
			allowed values specified in [RFC8296], the BIER MPLS Encapsulation
			Sub-TLV MUST be ignored.
	If same BS length is repeated in multiple BIER MPLS Encapsulation		If same BS length is repeated in multiple BIER MPLS Encapsulation
	Sub-TLV inside the same BIER Sub-TLV, the BIER sub-TLV MUST be		Sub-TLV inside the same BIER Sub-TLV, the BIER sub-TLV MUST be
	ignored.		ignored.
	Label ranges within all BIER MPLS Encapsulation Sub-TLVs advertised		Label ranges within all BIER MPLS Encapsulation Sub-TLVs advertised
	by the same BFR MUST NOT overlap. If the overlap is detected, the		by the same BFR MUST NOT overlap. If the overlap is detected, the
	advertising router MUST be treated as if it did not advertise any		advertising router MUST be treated as if it did not advertise any
	BIER sub-TLVs.		BIER sub-TLVs.
	All advertised labels MUST be valid, otherwise the BIER sub-TLV MUST
	be ignored.
	2.3. Flooding scope of BIER Information		2.3. Flooding scope of BIER Information
	The flooding scope of the OSPF Extended Prefix Opaque LSA [RFC7684]		The flooding scope of the OSPF Extended Prefix Opaque LSA [RFC7684]
	that is used for advertising the BIER Sub-TLV is set to area-local.		that is used for advertising the BIER Sub-TLV is set to area-local.
	To allow BIER deployment in a multi-area environment, OSPF must		To allow BIER deployment in a multi-area environment, OSPF must
	propagate BIER information between areas.		propagate BIER information between areas.
	( ) ( ) ( )		( ) ( ) ( )
	( ) ( ) ( )		( ) ( ) ( )
	R1 Area 1 R2 Area 0 R3 Area 2 R4		R1 Area 1 R2 Area 0 R3 Area 2 R4
	skipping to change at page 8, line 15 ¶		skipping to change at page 8, line 15 ¶
	5. Acknowledgments		5. Acknowledgments
	The authors would like to thank Rajiv Asati, Christian Martin, Greg		The authors would like to thank Rajiv Asati, Christian Martin, Greg
	Shepherd and Eric Rosen for their contribution.		Shepherd and Eric Rosen for their contribution.
	6. Normative References		6. Normative References
	[I-D.ietf-bier-isis-extensions]		[I-D.ietf-bier-isis-extensions]
	Ginsberg, L., Przygienda, T., Aldrin, S., and Z. Zhang,		Ginsberg, L., Przygienda, T., Aldrin, S., and Z. Zhang,
	"BIER support via ISIS", draft-ietf-bier-isis-		"BIER support via ISIS", draft-ietf-bier-isis-
	extensions-07 (work in progress), February 2018.		extensions-08 (work in progress), February 2018.
	[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>.
	[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328,		[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328,
	DOI 10.17487/RFC2328, April 1998,		DOI 10.17487/RFC2328, April 1998,
	<https://www.rfc-editor.org/info/rfc2328>.		<https://www.rfc-editor.org/info/rfc2328>.
End of changes. 10 change blocks.
	13 lines changed or deleted		16 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/