I support WG Adoption. This draft provides an appropriate BGP mechanism using a new AFI / SAFI and TEA for a BGP controller to distribute BIER information to instantiate the BIER TE path.
This a BGP centralized controller (SDN) mechanism to instantiate a BIER TE path. There is a another draft that provides a similar solution using PCECC centralized SDN controller extension to instantiate the BIER TE path. https://datatracker.ietf.org/doc/html/draft-chen-pce-controller-bier-te-03 Both solutions integrate well into the BIER TE architecture and provides operator flexibility of using PCEP or BGP controller. I agree that this BGP Controller based BIER TE mechanism would integrate well into the BIER TE architecture. BIER MVPN draft below provides a new BIER PTA tunnel ID addition to RFC 6513 & 6514 MVPN procedures. https://datatracker.ietf.org/doc/html/draft-ietf-bier-mvpn This draft is providing a centralized BGP controller based solution versus a distributed solution, however I believe it could be applicable to a distributed solution X-PMSI P-TREE instantiation of MVPN with the new BIER PTA above draft which could use this drafts BGP mechanism in a distributed fashion to instantiate the BIER TE path for the new BIER PTA. As most operators are moving towards If they have not already done so towards a centralized SDN model versus a distributed or hybrid model, I believe this draft will be highly valuable for operators deployment of BIER-TE in an automated fashion. Kind Regards Gyan On Wed, Jun 22, 2022 at 12:17 PM Susan Hares <[email protected]> wrote: > Bess WG: > > > > IDR has begun an adoption call for draft-chen-idr-bier-te-path-04.txt. > > since this document specifies BGP mechanisms > > (an NLRI and additions to the BGP TEA), the adoption call > > Is going on in IDR. > > > > We welcome your comments on this draft on the IDR thread: > > (click below to go directly to the mail thread online) > > https://mailarchive.ietf.org/arch/msg/idr/tKgu_S5_32_l5YzWfO8481hpRRY/ > > > > The IDR Chairs would appreciate feedback on > > how this interacts with existing multicast VPNs specifications > > existing (specified in the bess WG or other WGs). > > > > Another avenue of input is to provide feedback directly to the > > bess chairs. The IDR Chairs will be checking with the bess chairs > > prior to finalizing the adoption of this attribute. > > > > Cheers, > > Sue Hares > > (IDR co-chair, document shepherd) > > > > > > *From:* Susan Hares > *Sent:* Wednesday, June 22, 2022 12:05 PM > *To:* [email protected] > *Subject:* WG adoption call for draft-chen-idr-bier-te-path-04.txt > (6/22/2022 to 7/6/2022 > > > > This begins a 2 week Adoption call (6/22/2022 to 7/6/2022) > > for draft-chen-idr-bier-te-path-04.txt > > (https://datatracker.ietf.org/doc/draft-chen-idr-bier-te-path/). > > > > This draft provides extensions to BGP to distribute BIER > > (bit replication traffic/tree) data via BGP using a > > new NLRI (AFI = IPv4 or IPv6, new SAFI) and > > new options for the Tunnel Encapsulation Attribute (TEA). > > The NLRI includes an RD + Bier Domain tunnel identifier. > > > > In your comments, please consider if this draft: > > > > 1) Does this draft specify appropriate BGP mechanisms for > > a controller to distribute bier information? > > > > 2) Does this mechanism correctly integrates into > > a) the BIER architecture (draft-ietf-bier-te-arch) and > > b) Multicast VPNs (BESS)? > > > > 3) Will this technology aid the deployment of > > Bier multicast forwarding in operational networks? > > > > Cheers, Sue > _______________________________________________ > BESS mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/bess > -- <http://www.verizon.com/> *Gyan Mishra* *Network Solutions A**rchitect * *Email [email protected] <[email protected]>* *M 301 502-1347*
_______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
