< draft-ietf-bier-ospf-bier-extensions-15.txt		draft-ietf-bier-ospf-bier-extensions-16.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 27, 2018 Cisco		Expires: September 13, 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 23, 2018		March 12, 2018
	OSPF Extensions for BIER		OSPFv2 Extensions for BIER
	draft-ietf-bier-ospf-bier-extensions-15.txt		draft-ietf-bier-ospf-bier-extensions-16.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 27, 2018.		This Internet-Draft will expire on September 13, 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 2, line 35 ¶		skipping to change at page 2, line 35 ¶
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Flooding of the BIER Information in OSPF . . . . . . . . . . 3		2. Flooding of the BIER Information in OSPF . . . . . . . . . . 3
	2.1. BIER Sub-TLV . . . . . . . . . . . . . . . . . . . . . . 3		2.1. BIER Sub-TLV . . . . . . . . . . . . . . . . . . . . . . 3
	2.2. BIER MPLS Encapsulation Sub-TLV . . . . . . . . . . . . . 5		2.2. BIER MPLS Encapsulation Sub-TLV . . . . . . . . . . . . . 5
	2.3. Flooding scope of BIER Information . . . . . . . . . . . 6		2.3. Flooding scope of BIER Information . . . . . . . . . . . 6
	3. Security Considerations . . . . . . . . . . . . . . . . . . . 7		3. Security Considerations . . . . . . . . . . . . . . . . . . . 7
	4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7		4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
	5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8		5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
	6. Normative References . . . . . . . . . . . . . . . . . . . . 8		6. Normative References . . . . . . . . . . . . . . . . . . . . 8
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
	1. Introduction		1. Introduction
	Bit Index Explicit Replication (BIER) is an architecture that		Bit Index Explicit Replication (BIER) is an architecture that
	provides optimal multicast forwarding through a "BIER domain" without		provides optimal multicast forwarding through a "BIER domain" without
	requiring intermediate routers to maintain any multicast related per-		requiring intermediate routers to maintain any multicast related per-
	flow state. Neither does BIER explicitly require a tree-building		flow state. Neither does BIER explicitly require a tree-building
	protocol for its operation. A multicast data packet enters a BIER		protocol for its operation. A multicast data packet enters a BIER
	domain at a "Bit-Forwarding Ingress Router" (BFIR), and leaves the		domain at a "Bit-Forwarding Ingress Router" (BFIR), and leaves the
	BIER domain at one or more "Bit-Forwarding Egress Routers" (BFERs).		BIER domain at one or more "Bit-Forwarding Egress Routers" (BFERs).
	skipping to change at page 4, line 39 ¶		skipping to change at page 4, line 39 ¶
	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],		If the MT-ID value is outside of the values specified in [RFC4915],
	the BIER Sub-TLV MUST be ignored.		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 BFR 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 by		given MT-ID and Sub-domain-ID. When such duplication is detected by
	the BFR, it MUST behave as described in section 5 of [RFC8279].		the BFR, it MUST behave as described in section 5 of [RFC8279].
	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,
	skipping to change at page 5, line 29 ¶		skipping to change at page 5, line 29 ¶
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Type | Length |		| Type | Length |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Max SI | Label |		| Max SI | Label |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|BS Len | Reserved |		|BS Len | Reserved |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Type: 10		Type: 10
	Length: 4 octets		Length: 8 octets
	Max SI : A 1 octet field encoding the Maximum Set Identifier		Max SI : A 1 octet field encoding the maximum Set Identifier
	(section 1 of [RFC8296]), used in the encapsulation for this BIER		(section 1 of [RFC8279]), used in the encapsulation for this BIER
	sub-domain for this bitstring length.		sub-domain for this bitstring length.
	Label: A 3 octet field, where the 20 rightmost bits represent the		Label: A 3 octet field, where the 20 rightmost bits represent the
	first label in the label range. The 4 leftmost bits MUST be		first label in the label range. The 4 leftmost bits MUST be
	ignored.		ignored.
	Bit String Length: A 4 bits field encoding the supported BitString		Bit String Length: A 4 bits field encoding the supported BitString
	length associated with this BFR-prefix. The values allowed in		length associated with this BFR-prefix. The values allowed in
	this field are specified in section 2 of [RFC8296].		this field are specified in section 2 of [RFC8296].
			Reserved: SHOULD be set to 0 on transmission and MUST be ignored
			on reception.
	The "label range" is the set of labels beginning with the Label		The "label range" is the set of labels beginning with the Label
	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 label associated with the Maximum Set Identifier exceeds the
			20 bit range, the BIER MPLS Encapsulation Sub-TLV MUST be ignored.
	If the BS length is set to a value that does not match any of the		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		allowed values specified in [RFC8296], the BIER MPLS Encapsulation
	Sub-TLV MUST be ignored.		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
	skipping to change at page 8, line 15 ¶		skipping to change at page 8, line 24 ¶
	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-08 (work in progress), February 2018.		extensions-09 (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. 12 change blocks.
	12 lines changed or deleted		18 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/