Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

gt; Sent: Wednesday, June 08, 2016 6:13 AM >> To: Ali Sajassi (sajassi); Jeffrey (Zhaohui) Zhang; BESS; >> draft-ietf-bess-evpn- >> et...@tools.ietf.org >> Subject: Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree >> >> Hi Ali, >> >> I haven

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

t;> > >>>>>> For the regular EVPN, section 3.3.2 talks about a situation where > >>>>>> the only traffic is BUM. There is no need for mac learning in > >>>>>> that situation. > >>>>>> > >>>>>> For P

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

gt;>>> One more question about PBB-EVPN. >>>>>>> >>>>>>> For the regular EVPN, section 3.3.2 talks about a situation where >>>>>>>the >>>>>>> only traffic is BUM. There is no need for mac learning in that >&g

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

; EXT - thomas.mo...@orange.com ; BESS ; draft-ietf-bess-evpn-et...@tools.ietf.org Subject: Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree Hi Jeffrey, Thanks for the review. Your comments helps tighten the draft some more. I have updated the draft and will publish it next (rev04). Majority o

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

;>>root/leaf >>>>> B-mac addresses are enough. >>>>> >>>>> Perhaps this can be mentioned for parity/completeness. Of course, >>>>>this >>>>>is >>>>> not a big deal and either way it's fine - but I do want to ask to

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

gt;>>>is >>>> not a big deal and either way it's fine - but I do want to ask to >>>>confirm >>>> my understanding. >>> >>> We’ll do. >>> >>> Cheers, >>> Ali >>> >>>> >>>> Jeffrey

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

ess. Of course, this >>>is >>> not a big deal and either way it's fine - but I do want to ask to >>>confirm >>> my understanding. >> >> We’ll do. >> >> Cheers, >> Ali >> >>> >>> Jeffrey >>> >>

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

riginal Message- From: Ali Sajassi (sajassi) [mailto:saja...@cisco.com] Sent: Monday, February 01, 2016 2:04 AM To: Jeffrey (Zhaohui) Zhang ; EXT - thomas.mo...@orange.com ; BESS ; draft-ietf-bess-evpn-et...@tools.ietf.org Subject: Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree Hi Jeffr

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

g ; EXT - >> thomas.mo...@orange.com ; BESS ; >> draft-ietf-bess-evpn-et...@tools.ietf.org >> Subject: Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree >> >> Hi Jeffrey, >> >> Thanks for the review. Your comments helps tighten the draft some m

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

Same here and I am not aware of any ipr beyond what was already disclosed Sami Sent from my iPhone > On Feb 3, 2016, at 6:55 AM, Aldrin Isaac wrote: > > I support as co-author. Not aware of any related IPR. > Cheers, > Aldrin > >> On Tue, Jan 19, 2016 at 12:51 AM Thomas Morin >> wrote: >>

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

I support as co-author. Not aware of any related IPR. Cheers, Aldrin On Tue, Jan 19, 2016 at 12:51 AM Thomas Morin wrote: > Hello Working Group, > > This email starts a Working Group Last Call on > draft-ietf-bess-evpn-etree [1] which is considered mature and ready for > a final working group re

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

Ali Sajassi (sajassi) [mailto:saja...@cisco.com] > Sent: Monday, February 01, 2016 2:04 AM > To: Jeffrey (Zhaohui) Zhang ; EXT - > thomas.mo...@orange.com ; BESS ; > draft-ietf-bess-evpn-et...@tools.ietf.org > Subject: Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree > > Hi Jef

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

Hi, Support, very much needed to complete definition of MEF services over EVPN. Cheers, Jeff On 1/19/16, 09:51, "BESS on behalf of Thomas Morin" wrote: >Hello Working Group, > >This email starts a Working Group Last Call on >draft-ietf-bess-evpn-etree [1] which is considered mature and

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

Folks, I¹m supporting this document. It does provide a right etree solution for EVPN. Regards, Patrice Patrice Brissette TECHNICAL LEADER.ENGINEERING pbris...@cisco.com Phone: +1 613 254 3336 Cisco Systems Canada Co. / Les Systemes Cisco Canada CIE Canada Cisco.com

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

, the leaf flag SHOULD be >set to 0 but ignored by the receiving routers. Therefore, why not set it >to 1 to be consistent the MAC/IP route case? Because the flag is used for known unicast traffic and Leaf label for BUM traffic. We don¹t want to mix the two. Cheers, Ali > >Thanks. &g

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

SS [mailto:bess-boun...@ietf.org] On Behalf Of Thomas Morin >>>Sent: Tuesday, January 19, 2016 2:51 AM >>>To: BESS; draft-ietf-bess-evpn-et...@tools.ietf.org >>>Subject: [bess] WG Last Call on draft-ietf-bess-evpn-etree >>> >>>Hello Working Group, >>

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

Support publication of this draft. It is a good document for the Etree framework to EVPN. Thanks, ―Satya On 1/24/16, 9:40 PM, "BESS on behalf of Ali Sajassi (sajassi)" wrote: > >Support publication of this document as a co-author and I am not aware of >any IPR that hasn¹t been disclosed. > >Che

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

be consistent the MAC/IP route case? Thanks. Jeffrey > -Original Message- > From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Thomas Morin > Sent: Tuesday, January 19, 2016 3:51 AM > To: BESS ; draft-ietf-bess-evpn-et...@tools.ietf.org > Subject: [bess] WG Last Call on draft-

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

ehalf Of Thomas Morin >>Sent: Tuesday, January 19, 2016 2:51 AM >>To: BESS; draft-ietf-bess-evpn-et...@tools.ietf.org >>Subject: [bess] WG Last Call on draft-ietf-bess-evpn-etree >> >>Hello Working Group, >> >>This email starts a Working Group Last Call on draf

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

Support as co-author. I'm not aware of any IPR beyond what has already been disclosed. Thanks, Samer > >On 1/19/16, 12:51 AM, "BESS on behalf of thomas.mo...@orange.com" > wrote: > >>Hello Working Group, >> >>This email starts a Working Group Last Call on >>draft-ietf-bess-evpn-etree [1] which i

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

s.ietf.org Subject: Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree Fully support as a co-author. I am not aware of any un-disclosed IPR. Thanks, Wen > >-Original Message- >From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Thomas Morin >Sent: Tuesday, January 19,

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

Subject: [bess] WG Last Call on draft-ietf-bess-evpn-etree > >Hello Working Group, > >This email starts a Working Group Last Call on draft-ietf-bess-evpn-etree >[1] which is considered mature and ready for a final working group review. > >Please read the document if you haven&#

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

Support Thanks, Luay -Original Message- From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Thomas Morin Sent: Tuesday, January 19, 2016 2:51 AM To: BESS; draft-ietf-bess-evpn-et...@tools.ietf.org Subject: [bess] WG Last Call on draft-ietf-bess-evpn-etree Hello Working Group, This

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

Support publication of this document as a co-author and I am not aware of any IPR that hasn¹t been disclosed. Cheers, Ali On 1/19/16, 12:51 AM, "BESS on behalf of thomas.mo...@orange.com" wrote: >Hello Working Group, > >This email starts a Working Group Last Call on >draft-ietf-bess-evpn-etree

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

As co-author, I fully support this document for publication. Not aware of any relevant IPR. Thank you. Jorge On 1/19/16, 12:51 AM, "BESS on behalf of Thomas Morin" wrote: >Hello Working Group, > >This email starts a Working Group Last Call on >draft-ietf-bess-evpn-etree [1] which is consid

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

ject: [bess] WG Last Call on draft-ietf-bess-evpn-etree > > Hello Working Group, > > This email starts a Working Group Last Call on draft-ietf-bess-evpn-etree [1] > which is considered mature and ready for a final working group review. > > Please read the document if you

Re: [bess] WG Last Call on draft-ietf-bess-evpn-etree

As a co-author I believe this doc is mature and stable for final WG review. Not aware of IPR related to the draft On 19/01/16 00:51, "BESS on behalf of Thomas Morin" wrote: >Hello Working Group, > >This email starts a Working Group Last Call on >draft-ietf-bess-evpn-etree [1] which is consid

[bess] WG Last Call on draft-ietf-bess-evpn-etree

Hello Working Group, This email starts a Working Group Last Call on draft-ietf-bess-evpn-etree [1] which is considered mature and ready for a final working group review. Please read the document if you haven't read the most recent version yet (-03), and send your comments to the list, no lat