Re: [Bier] RFC 8279 on Multicast Using Bit Index Explicit Replication (BIER))

[Toerless Eckert <[e-mail]>]

If you wonder why there is no big hurray !!!!!!,
congratulations for the RFC here on the mailing list,
here are my top guesses:

a) We already had it in Singapore in the BIER WG meeting.
c) We're all still in jet lag koma after flying back from Singapore
b) We're all getting ready for thanksgiving

Nevertheless: hurray!!!!!

Happy thanksgiving (applicable to U.S. residents)
  Toerless

In-Reply-To: <[e-mail]>

On Mon, Nov 20, 2017 at 12:40:27PM -0800, [e-mail] wrote:
> A new Request for Comments is now available in online RFC libraries.
> 
>         
>         RFC 8279
> 
>         Title:      Multicast Using Bit Index Explicit 
>                     Replication (BIER) 
>         Author:     I. Wijnands, Ed.,
>                     E. Rosen, Ed.,
>                     A. Dolganow,
>                     T. Przygienda,
>                     S. Aldrin
>         Status:     Experimental
>         Stream:     IETF
>         Date:       November 2017
>         Mailbox:    [e-mail],
>                     [e-mail],
>                     [e-mail],
>                     [e-mail],
>                     [e-mail]
>         Pages:      43
>         Characters: 97283
>         Updates/Obsoletes/SeeAlso:   None
> 
>         I-D Tag:    draft-ietf-bier-architecture-08.txt
> 
>         URL:        https://www.rfc-editor.org/info/rfc8279
> 
>         DOI:        10.17487/RFC8279
> 
> This document specifies a new architecture for the forwarding of
> multicast data packets.  It provides optimal forwarding of multicast
> packets through a "multicast domain".  However, it does not require a
> protocol for explicitly building multicast distribution trees, nor
> does it require intermediate nodes to maintain any per-flow state.
> This architecture is known as "Bit Index Explicit Replication"
> (BIER).  When a multicast data packet enters the domain, the ingress
> router determines the set of egress routers to which the packet needs
> to be sent.  The ingress router then encapsulates the packet in a
> BIER header.  The BIER header contains a bit string in which each bit
> represents exactly one egress router in the domain; to forward the
> packet to a given set of egress routers, the bits corresponding to
> those routers are set in the BIER header.  The procedures for
> forwarding a packet based on its BIER header are specified in this
> document.  Elimination of the per-flow state and the explicit
> tree-building protocols results in a considerable simplification.
> 
> This document is a product of the Bit Indexed Explicit Replication Working Group of the IETF.
> 
> 
> EXPERIMENTAL: This memo defines an Experimental Protocol for the
> Internet community.  It does not specify an Internet standard of any
> kind. Discussion and suggestions for improvement are requested.
> Distribution of this memo is unlimited.
> 
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>   https://www.ietf.org/mailman/listinfo/ietf-announce
>   https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
> 
> For searching the RFC series, see https://www.rfc-editor.org/search
> For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
> 
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to [e-mail].  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
> 
> 
> The RFC Editor Team
> Association Management Solutions, LLC
> 
> _______________________________________________
> BIER mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/bier

-- 
---
[e-mail]