Skip to main content

Tethering A BIER Router To A BIER incapable Router
draft-ietf-bier-tether-05

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>, andrew-ietf@liquid.tech, bier-chairs@ietf.org, bier@ietf.org, chen.ran@zte.com.cn, draft-ietf-bier-tether@ietf.org, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'Tethering A BIER Router To A BIER incapable Router' to Proposed Standard (draft-ietf-bier-tether-04.txt)

The IESG has approved the following document:
- 'Tethering A BIER Router To A BIER incapable Router'
  (draft-ietf-bier-tether-04.txt) as Proposed Standard

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

The IESG contact persons are Jim Guichard, Andrew Alston and John Scudder.

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


Ballot Text

Technical Summary

   This document specifies optional procedures to optimize the handling
   of Bit Index Explicit Replication (BIER) incapable routers, by
   attaching (tethering) a BIER router to a BIER incapable router.

Working Group Summary

   Was there anything in the WG process that is worth noting?
   For example, was there controversy about particular points 
   or were there decisions where the consensus was
   particularly rough? 

Document Quality

   Are there existing implementations of the protocol?  Have a 
   significant number of vendors indicated their plan to
   implement the specification?  Are there any reviewers that
   merit special mention as having done a thorough review,
   e.g., one that resulted in important changes or a
   conclusion that the document had no substantive issues?  If
   there was a MIB Doctor, Media Type, or other Expert Review,
   what was its course (briefly)?  In the case of a Media Type
   Review, on what date was the request posted?

Personnel

   The Document Shepherd for this document is Ran Chen. The Responsible
   Area Director is Andrew Alston.

IANA Note

  (Insert IANA Note here or remove section)

RFC Editor Note