Hi Patrice Makes sense. That is a very important use case for for operators for SHD, SHN scenario for more granular per flow versus per VLAN DF election and load balancing.
So this draft is an optimization for SHD, SHN per flow load balancing updating RFC 7432, similar to RFC 8584 MHD, MHN optimization per flow load balancing which updates RFC 7432. Kind Regards Gyan On Mon, Apr 12, 2021 at 11:09 AM Patrice Brissette (pbrisset) < pbris...@cisco.com> wrote: > Hi Gyan, > > > > RFC8584 talks about all-active which sometime is referred as active-active > per flow where a host is reachable via both MH PE. > > The L2GW protocol draft is completely different. It is about single-active > per flow load balancing where a host is reachable via a single MH PE at a > time. > > > > Regards, > > Patrice Brissette, Principal Engineer > > Cisco Systems > > > > *http://e-vpn.io <http://e-vpn.io>* > > *http://go2.cisco.com/evpn <http://go2.cisco.com/evpn>* > > > > > > > > > > *From: *Gyan Mishra <hayabusa...@gmail.com> > *Date: *Thursday, April 8, 2021 at 13:59 > *To: *Patrice Brissette <pbris...@cisco.com> > *Cc: *"bess@ietf.org" <bess@ietf.org>, "slitkows.i...@gmail.com" < > slitkows.i...@gmail.com> > *Subject: *Re: [bess] WG adoption and IPR poll for > draft-brissette-bess-evpn-l2gw-proto > > > > I support WG adoption. > > > > I had one question for the authors. > > > > Does RFC 8584 DF election optimized per flow load balancing algorithm for > SHD MHD scenarios which updates RFC 7432 address the problem and solution > described in this draft. > > > > Kind Regards > > > > Gyan > > > > On Thu, Apr 8, 2021 at 11:20 AM Patrice Brissette (pbrisset) <pbrisset= > 40cisco....@dmarc.ietf.org> wrote: > > As co-author I support adoption. > > I am aware of an IPR which is in process of being disclosed. > > > > That is yet another important draft. > > There are implementations of that draft and customers are already using > them. > > > > Regards, > > Patrice Brissette, Principal Engineer > > Cisco Systems > > > > *http://e-vpn.io <http://e-vpn.io>* > > *http://go2.cisco.com/evpn <http://go2.cisco.com/evpn>* > > > > > > > > > > *From: *BESS <bess-boun...@ietf.org> on behalf of "slitkows.i...@gmail.com" > <slitkows.i...@gmail.com> > *Date: *Monday, March 29, 2021 at 03:13 > *To: *"bess@ietf.org" <bess@ietf.org> > *Subject: *[bess] WG adoption and IPR poll for > draft-brissette-bess-evpn-l2gw-proto > > > > Hello, > > > > This email begins a two-weeks WG adoption poll for > draft-brissette-bess-evpn-l2gw-proto > [1]. > > > > 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 will > not progress without answers from all of 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 April 12th 2021. > > > > Regards, > > Matthew and Stephane > > > > > > [1] https://datatracker.ietf.org/doc/draft-brissette-bess-evpn-l2gw-proto/ > > > > _______________________________________________ > BESS mailing list > BESS@ietf.org > https://www.ietf.org/mailman/listinfo/bess > > -- > > <http://www.verizon.com/> > > *Gyan Mishra* > > *Network Solutions Architect * > > *Email gyan.s.mis...@verizon.com <gyan.s.mis...@verizon.com>* > > *M 301 502-1347* > > > -- <http://www.verizon.com/> *Gyan Mishra* *Network Solutions A**rchitect * *Email gyan.s.mis...@verizon.com <gyan.s.mis...@verizon.com>* *M 301 502-1347*
_______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
