< draft-ietf-bier-te-arch-01.txt		draft-ietf-bier-te-arch-02.txt >
	Network Working Group T. Eckert, Ed.		Network Working Group T. Eckert, Ed.
	Internet-Draft Huawei		Internet-Draft Huawei
	Intended status: Experimental G. Cauchie		Intended status: Standards Track G. Cauchie
	Expires: April 26, 2019 Bouygues Telecom		Expires: November 15, 2019 Bouygues Telecom
	W. Braun		W. Braun
	M. Menth		M. Menth
	University of Tuebingen		University of Tuebingen
	October 23, 2018		May 14, 2019
	Traffic Engineering for Bit Index Explicit Replication (BIER-TE)		Traffic Engineering for Bit Index Explicit Replication (BIER-TE)
	draft-ietf-bier-te-arch-01		draft-ietf-bier-te-arch-02
	Abstract		Abstract
	This document proposes an architecture for BIER-TE: Traffic		This document proposes an architecture for BIER-TE: Traffic
	Engineering for Bit Index Explicit Replication (BIER).		Engineering for Bit Index Explicit Replication (BIER).
	BIER-TE shares part of its architecture with BIER as described in		BIER-TE shares part of its architecture with BIER as described in
	[RFC8279]. It also proposes to share the packet format with BIER.		[RFC8279]. It also proposes to share the packet format with BIER.
	BIER-TE forwards and replicates packets like BIER based on a		BIER-TE forwards and replicates packets like BIER based on a
	skipping to change at page 1, line 47 ¶		skipping to change at page 1, line 47 ¶
	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 April 26, 2019.		This Internet-Draft will expire on November 15, 2019.
	Copyright Notice		Copyright Notice
	Copyright (c) 2018 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
	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
	skipping to change at page 3, line 26 ¶		skipping to change at page 3, line 26 ¶
	7.4. Assigning BFR-ids for BIER-TE . . . . . . . . . . . . . . 26		7.4. Assigning BFR-ids for BIER-TE . . . . . . . . . . . . . . 26
	7.5. Example bit allocations . . . . . . . . . . . . . . . . . 27		7.5. Example bit allocations . . . . . . . . . . . . . . . . . 27
	7.5.1. With BIER . . . . . . . . . . . . . . . . . . . . . . 27		7.5.1. With BIER . . . . . . . . . . . . . . . . . . . . . . 27
	7.5.2. With BIER-TE . . . . . . . . . . . . . . . . . . . . 28		7.5.2. With BIER-TE . . . . . . . . . . . . . . . . . . . . 28
	7.6. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 29		7.6. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 29
	8. BIER-TE and Segment Routing . . . . . . . . . . . . . . . . . 29		8. BIER-TE and Segment Routing . . . . . . . . . . . . . . . . . 29
	9. Security Considerations . . . . . . . . . . . . . . . . . . . 30		9. Security Considerations . . . . . . . . . . . . . . . . . . . 30
	10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30		10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30
	11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 30		11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 30
	12. Change log [RFC Editor: Please remove] . . . . . . . . . . . 30		12. Change log [RFC Editor: Please remove] . . . . . . . . . . . 30
	13. References . . . . . . . . . . . . . . . . . . . . . . . . . 32		13. References . . . . . . . . . . . . . . . . . . . . . . . . . 33
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33
	1. Introduction		1. Introduction
	1.1. Overview		1.1. Overview
	This document specifies the architecture for BIER-TE: traffic		This document specifies the architecture for BIER-TE: traffic
	engineering for Bit Index Explicit Replication BIER.		engineering for Bit Index Explicit Replication BIER.
	BIER-TE shares architecture and packet formats with BIER as described		BIER-TE shares architecture and packet formats with BIER as described
	skipping to change at page 30, line 40 ¶		skipping to change at page 30, line 40 ¶
	11. Acknowledgements		11. Acknowledgements
	The authors would like to thank Greg Shepherd, Ijsbrand Wijnands and		The authors would like to thank Greg Shepherd, Ijsbrand Wijnands and
	Neale Ranns for their extensive review and suggestions.		Neale Ranns for their extensive review and suggestions.
	12. Change log [RFC Editor: Please remove]		12. Change log [RFC Editor: Please remove]
	draft-ietf-bier-te-arch:		draft-ietf-bier-te-arch:
			02: Refresh after IETF104 discussion: changed intended status back
			to standard. Reasoning:
			Tighter review of standards document == ensures arch will be
			better prepared for possible adoption by other WGs (e.g.: DetNet)
			or std. bodies.
			Requirement against the degree of existing implementations is self
			defined by the WG. BIER WG seems to think it is not necessary to
			apply multiple interoperating implementions against an
			architecture level document at this time to make it qualify to go
			to standards track. Also, the levels of support introduced in -01
			rev. should allow all BIER forwarding engines to also be able to
			support the base level BIER-TE forwarding.
	01: Added note comparing BIER and SR to also hopefully clarify		01: Added note comparing BIER and SR to also hopefully clarify
	BIER-TE vs. BIER comparison re. SR.		BIER-TE vs. BIER comparison re. SR.
	- added requirements section mandating only most basic BIER-TE		- added requirements section mandating only most basic BIER-TE
	forwarding features as MUST.		forwarding features as MUST.
	- reworked comparison with BIER forwarding section to only		- reworked comparison with BIER forwarding section to only
	summarize and point to pseudocode section.		summarize and point to pseudocode section.
	- reworked pseudocode section to have one pseodcode that mirrors		- reworked pseudocode section to have one pseodcode that mirrors
End of changes. 7 change blocks.
	7 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/