Hi Gyan, Please see zzh> below.
From: Gyan Mishra <[email protected]> Sent: Monday, January 6, 2020 7:10 PM To: [email protected] Cc: [email protected]; [email protected]; [email protected] Subject: Re: [bess] WG adoption and IPR poll for draft-zzhang-bess-bgp-multicast-03 Authors Would this draft also provide a move towards a stateless core migration of inband signaling provided by mLDP to now be provided by BGP. Zzh> This will still have per-tree state in the core. The only way to do efficient replication w/o per-tree state is BIER, at least so far. Cisco and other vendors may support BGP C-Multicast signaling out of band signaling type 6 and 7 mVPN routes today. Zzh> MVPN type 6/7 routes (RFC 6514) routes are for signaling multicast over a “virtual LAN” (overlaid on top of the provider core). This draft is for signaling multicast through a network (of many hops) using BGP. In some way it is similar to mLDP inband signaling but nowadays in the SR era some people want to remove LDP/RSVP entirely. I thought this was covered in one of the other MVPN RFCs but maybe not. Could BGP also be used for SR SR-MPLS and SRv6 use cases to carry MVPN services out of band via BGP that was traditionally carried over mLDP or PIM. Zzh> Not exactly sure what you’re asking; but this draft is about establishing a multicast tree (native or labeled PIM-like tree or mLDP-like P2MP tunnel), which could be used however/wherever it makes sense – e.g. w/ or w/o MVPN. Zzh> Jeffrey Kind regards, Gyan On Mon, Jan 6, 2020 at 9:15 AM <[email protected]<mailto:[email protected]>> wrote: Hello, This email begins a two-weeks WG adoption poll for and draft-zzhang-bess-bgp-multicast-03 [1] .. For information, it’s companion document (draft-zzhang-bess-bgp-multicast-controller-02) is also polled for WG adoption in a separate email. Please review the draft and post any comments to the BESS working group list. We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as an author or a contributor of this document, please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR, copying the BESS mailing list. The document won't progress without answers from all the authors and contributors. Currently, there are no IPR disclosures against this document. If you are not listed as an author or a contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules. This poll for adoption closes on *** 20th January 2020 *** Regards, Matthew and Stephane [1] https://datatracker.ietf.org/doc/draft-zzhang-bess-bgp-multicast<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-zzhang-bess-bgp-multicast__;!!NEt6yMaO-gk!Q6rFB6ImtuZ93rr2rq9fS3WH3JcBQmWafp3Ng5bn8fDIzx_9HiNIf1DeZ7EDvK3Y$> _______________________________________________ BESS mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/bess<https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/bess__;!!NEt6yMaO-gk!Q6rFB6ImtuZ93rr2rq9fS3WH3JcBQmWafp3Ng5bn8fDIzx_9HiNIf1DeZ6wWVdFQ$> -- Gyan S. Mishra IT Network Engineering & Technology Verizon Communications Inc. (VZ) 13101 Columbia Pike FDC1 3rd Floor Silver Spring, MD 20904 United States Phone: 301 502-1347 Email: [email protected]<mailto:[email protected]> www.linkedin.com/in/networking-technologies-consultant<https://urldefense.com/v3/__http:/www.linkedin.com/in/networking-technologies-consultant__;!!NEt6yMaO-gk!Q6rFB6ImtuZ93rr2rq9fS3WH3JcBQmWafp3Ng5bn8fDIzx_9HiNIf1DeZxMOqhNO$>
_______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
