Re: [bess] Hub-and-spoke support in EVPN: RFC 8317vs.draft-wang-bess-evpn-context-label-04

2020-08-21 Thread wang.yubao2
Hi Jeffrey, Maybe I was confused by the last mail. Let's discuss it on the basis of the text of the [EVPN Virtual Hub] draft. In section 7.1, it says that: In case of IR with MPLS unicast tunnels, VH1 must advertise different labels to different PEs, so

[bess] I-D Action: draft-ietf-bess-nsh-bgp-control-plane-18.txt

2020-08-21 Thread internet-drafts
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the BGP Enabled ServiceS WG of the IETF. Title : BGP Control Plane for the Network Service Header in Service Function Chaining Authors : Adrian Farrel

[bess] I-D Action: draft-ietf-bess-nsh-bgp-control-plane-17.txt

2020-08-21 Thread internet-drafts
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the BGP Enabled ServiceS WG of the IETF. Title : BGP Control Plane for the Network Service Header in Service Function Chaining Authors : Adrian Farrel

Re: [bess] Hub-and-spoke support in EVPN: RFC 8317 vs.draft-wang-bess-evpn-context-label-04

2020-08-21 Thread Jeffrey (Zhaohui) Zhang
Hi Bob, * *If* the AR REPLICATOR behaviors are removed from that draft,I think the hub/spoke scenario can't be well supported because that the RRs are widely used. What do you mean by *if* in the above statement? It is the designed behavior with hub and spoke scenario – with that do you

Re: [bess] Last Call: (Propagation of ARP/ND Flags in EVPN) to Proposed Standard

2020-08-21 Thread Rabadan, Jorge (Nokia - US/Mountain View)
Hi Luc, Thanks for your email. I think having similar text in the abstract and beginning of the introduction is not uncommon, especially if it helps people to get the gist of the document just by reading the abstract. Nevertheless we can make all the changes that help the readability during the