Dear WG I support publication.
This draft is a very important draft for operators in the case of redundancy with multicast sources and ensuring that the receivers don’t get the duplicate packets using the procedures defined in the draft. It is common to have multiple servers sending the same multicast flow as well as multicast source redundantly connected to FHR and duplicate stream and PIM assert pruning redundant stream. Multicast redundancy is also commonly setup at application layer with a pecking order and not all active simultaneously in a primary with N backup servers. I would like to mention that source redundancy can be done at the application layer which is common with multicast streaming technologies. Thanks Gyan On Wed, May 18, 2022 at 3:23 AM <[email protected]> wrote: > Hello WG, > > > > > > This email starts a two weeks Working Group Last Call on > draft-ietf-bess-evpn-redundant-mcast-source > > [1]. > > > > > > > > This poll runs until * the 1th of June *. > > > > > > 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. The Document won't progress without answers from > > all the Authors and Contributors. > > > > There is currently no IPR disclosed. > > > > > > 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. > > > > > > We are also polling for any existing implementation as per [2]. > > > > > > > > Thank you, > > Stephane & Matthew > > > > > > [1] > > https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-redundant-mcast-source/ > > [2] > > > > https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw > > > _______________________________________________ > 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
