Re: [bess] [Gen-art] Genart telechat review of draft-ietf-bess-mvpn-expl-track-12

Brian, thanks for your reviews. Eric, thanks for your responses. I entered a No Objection ballot. Alissa > On Oct 12, 2018, at 7:10 AM, Brian Carpenter > wrote: > > Reviewer: Brian Carpenter > Review result: Ready > > Gen-ART telechat review of draft-ietf-bess-mvpn-expl-track-12 > > I am th

Re: [bess] A question regarding draft-wang-bess-evepn-control-word

Hi Sasha, I am also thinking of this recently but haven’t talked with author yet. What was in my mind the solution is actually simple: directly tear down (part of) the mac-VRF or EVI directly if CW capabilities not consistent, considering behavior in one EVI should keep consistent (personally bel

Re: [bess] A question regarding draft-wang-bess-evepn-control-word

Dear Haibo, Again, Lots of thanks for a prompt response. My reading of your response is as following: 1. All egress PEs can receive EVPN-encapsulated packets without the CW 2. All ingress PEs can sent EVPN-encapsulated packets without the CW 3. An egress PE that can receive EV

Re: [bess] A question regarding draft-wang-bess-evepn-control-word

Hi Alexander, The solution here is to carry the next hop capability attribute when the route is advertised. The capability carried here is the control word capability. The specific format of the next hop capability can be referred to the draft.: +---

Re: [bess] A question regarding draft-wang-bess-evepn-control-word

Dear Haibo, Lots of thanks for an extra-prompt response to my question. There may be some misunderstanding here. The draft says (the important text is highlighted): There are two methods to specified the control word indicator label: The first method is to apply for a reserved label

[bess] 答复: A question regarding draft-wang-bess-evepn-control-word

Hi Alexander, The number of routes advertised by the Sender router in our solution will not change, but only carries a next hop capability attribute with control word capability The Receiver router determines whether to carry the control word when forwarding packets according to its own capabil

[bess] A question regarding draft-wang-bess-evepn-control-word

Dear authors of draft-wang-bess-evpn-control-word, I have doubts regarding at least one of the approaches for negotiating the CW usage in the EVPN encapsulation between egress and ingress PE that is defined in the draft. In the c

Re: [bess] CW in EVPN: Was Signaling Control Word in EVPN

James, I am adding PALS WG to the list of addressees because, AFAIK, the PW CW is defined in this WG. I think that the really observed problem with incorrect ECMP behavior exists, but it is different from your description in your earlier email: Any LSR on the path between ingress and egres

[bess] CW in EVPN: Was Signaling Control Word in EVPN

Hi All, I've removed all the individual contacts as per mod request and changed the subject as this conversation was diverging away from the OPs original query (sorry if any of that was my fault). On Tue, 9 Oct 2018 at 15:54, Andrew G. Malis wrote: > > James, > > Agreed. We touched on that in s