Hi, I’d like to see the community formally being transitive (not just as an implementation knob), in a multi-stage leaf-spine network, some stages might not have HW/SW to support UCMP, basic propagation of the community (rather than regeneration) would still work (use case – super-spines generate
John Scudder has entered the following ballot position for
draft-ietf-bess-evpn-inter-subnet-forwarding-14: Discuss
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Dear all
We just published a new piece of work that provides a secure declarative
interface for the server to push its address mappings to the leaf. The draft
enables a zeroconf/zerotrust stateful address autoconfiguration based on RFC
8505/RFC 8928 that leverages the eVPN infra to distribute
Hi Satya
Welcome.
As Jeff and Arie pointed out the distinct difference between the dmz link
bandwidth extended community and cumulative link bandwidth is that the
original link bandwidth extended community is non transitive and only
supports 2 octet AS, where the cumulative link bandwidth is an
+bess working group
Juniper Business Use Only
From: spring On Behalf Of Rajesh M
Sent: Thursday, July 8, 2021 12:38 PM
To: dh...@cisco.com; swaag...@cisco.com; cfils...@cisco.com; ket...@cisco.com
Cc: spr...@ietf.org
Subject: [spring] draft-dskc-bess-bgp-car-02
[External Email. Be cautious of
