Re: [Bier] I-D Action: draft-ietf-bier-te-arch-09.txt

[Toerless Eckert <[e-mail]>]

Xuesong found some good textual bugs and lacking explanation wrt. to the difference
in dependencies against the routing underlay in BIER/BIER-TE. Fixed in -09

https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=https://tools.ietf.org/id/draft-ietf-bier-te-arch-08.txt&url2=https://tools.ietf.org/id/draft-ietf-bier-te-arch-09.txt

Don't plan to report on those during 109, unless somebody wants me to,
otherwise i hope we'll quickly get the IHR disclosure statements from the
co-authors, so she can go forward with her shepherd writeup.

Cheers
    Toerless

On Fri, Oct 30, 2020 at 12:15:39PM -0700, [e-mail] wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Bit Indexed Explicit Replication WG of the IETF.
> 
>         Title           : Tree Engineering for Bit Index Explicit Replication (BIER-TE)
>         Authors         : Toerless Eckert
>                           Gregory Cauchie
>                           Michael Menth
> 	Filename        : draft-ietf-bier-te-arch-09.txt
> 	Pages           : 48
> 	Date            : 2020-10-30
> 
> Abstract:
>    This memo introduces per-packet stateless strict and loose path
>    steered replication and forwarding for Bit Index Explicit Replication
>    packets (RFC8279).  This is called BIER Tree Engineering (BIER-TE).
>    BIER-TE can be used as a path steering mechanism in future Traffic
>    Engineering solutions for BIER (BIER-TE).
> 
>    BIER-TE leverages RFC8279 and extends it with a new semantic for bits
>    in the bitstring.  BIER-TE can leverage BIER forwarding engines with
>    little or no changes.
> 
>    In BIER, the BitPositions (BP) of the packets bitstring indicate BIER
>    Forwarding Egress Routers (BFER), and hop-by-hop forwarding uses a
>    Routing Underlay such as an IGP.
> 
>    In BIER-TE, BitPositions indicate adjacencies.  The BIFT of each BFR
>    are only populated with BPs that are adjacent to the BFR in the BIER-
>    TE topology.  The BIER-TE topology can consist of layer 2 or remote
>    (routed) adjacencies.  The BFR then replicates and forwards BIER
>    packets to those adjacencies.  This results in the aforementioned
>    strict and loose path steering and replications.
> 
>    BIER-TE can co-exist with BIER forwarding in the same domain, for
>    example by using separate BIER sub-domains.  In the absence of routed
>    adjacencies, BIER-TE does not require a BIER routing underlay, and
>    can then be operated without requiring an Interior Gateway Routing
>    protocol (IGP).
> 
>    BIER-TE operates without explicit in-network tree-state and carries
>    the multicast distribution tree in the packet header.  It can
>    therefore be a good fit to support multicast path steering in Segment
>    Routing (SR) networks.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-bier-te-arch/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-bier-te-arch-09
> https://datatracker.ietf.org/doc/html/draft-ietf-bier-te-arch-09
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-bier-te-arch-09
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> 
> _______________________________________________
> BIER mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/bier

-- 
---
[e-mail]