Tree Engineering for Bit Index Explicit Replication (BIER-TE)
draft-ietf-bier-te-arch-13

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, Xuesong Geng <gengxuesong@huawei.com>, aretana.ietf@gmail.com, bier-chairs@ietf.org, bier@ietf.org, draft-ietf-bier-te-arch@ietf.org, gengxuesong@huawei.com, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'Tree Engineering for Bit Index Explicit Replication (BIER-TE)' to Proposed Standard (draft-ietf-bier-te-arch-13.txt)

The IESG has approved the following document:
- 'Tree Engineering for Bit Index Explicit Replication (BIER-TE)'
  (draft-ietf-bier-te-arch-13.txt) as Proposed Standard

This document is the product of the Bit Indexed Explicit Replication Working
Group.

The IESG contact persons are Alvaro Retana, Andrew Alston and John Scudder.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-bier-te-arch/

Ballot Text

Technical Summary

   This memo describes per-packet stateless strict and loose path
   steered replication and forwarding for Bit Index Explicit Replication
   packets (RFC8279).  It is called BIER Tree Engineering (BIER-TE) and
   is intended to be used as the path steering mechanism for Traffic
   Engineering with BIER.

Working Group Summary

   The name of the mechanism defined in the draft has been 
   discussed during last call, which was changed from “BIER 
   traffic engineering” to “BIER tree engineering”, considering 
   that it only covers the path steering function in the overall 
   solution of traffic engineering. Any BIER traffic engineering 
   mechanism could use this mechanism. 

   After full discussions and multiple revisions, there is solid 
   consensus for this document in WG.

Document Quality

   No implementation was yet announced in the BIER WG. No 
   formal language is used in the document (there is some informal 
   pseudo-code without formal verification tools). No aspects of 
   the document required expert review.

RFC Editor Note