[bess] Re: Call for adoption: draft-mackenzie-bess-evpn-l3mh-proto-07 (Ends 2025-11-04)

[Wen Lin <[e-mail]>]

As a co-author, I support WG adoption of this draft.

Thanks,
Wen



Cisco Confidential


Juniper Business Use Only

From: Zhaohui Zhang via Datatracker <[e-mail]>
Date: Tuesday, October 21, 2025 at 4:51 PM
To: [e-mail] <[e-mail]>, [e-mail] <[e-mail]>, [e-mail] <[e-mail]>
Subject: [bess] Call for adoption: draft-mackenzie-bess-evpn-l3mh-proto-07 (Ends 2025-11-04)


Subject: Call for adoption: draft-mackenzie-bess-evpn-l3mh-proto-07  (Ends
2025-11-04)

This message starts a 2-week Call for Adoption for this document.

Abstract:
   This document describes the use of EVPN Multi-Chassis Link
   Aggregation Group (MC-LAG) technology to improve network availability
   and load balancing for Layer 3 (L3) services with EVPN.  In this
   approach, all synchronized routes ensure the correct L3 state within
   Virtual Routing and Forwarding (VRF) instances.  Unlike traditional
   deployments, these L3 services operate entirely at Layer 3 and do not
   require Layer 2 constructs such as Ethernet Virtual Instances (EVIs),
   MAC-VRFs, Bridge Domains (BDs), or Integrated Routing and Bridging
   (IRB) interfaces.

File can be retrieved from:
https://datatracker.ietf.org/doc/draft-mackenzie-bess-evpn-l3mh-proto/<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-mackenzie-bess-evpn-l3mh-proto/__;!!NEt6yMaO-gk!E25ktslg-V5iKeFUQ8d33qerybOf4P_7vD2AonhtV_L3afhs-naNBhMRFxazgd0mmgIz7zDdxt6jKiAuZhJoW4C_SfD8_Q$>

Please reply to this message keeping [e-mail] in copy by indicating
whether you support or not the adoption of this draft as a WG document.
Comments to motivate your preference are highly appreciated.

Authors, and WG participants in general, are reminded of the Intellectual
Property Rights (IPR) disclosure obligations described in BCP 79 [2].
Appropriate IPR disclosures required for full conformance with the provisions
of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
Sanctions available for application to violators of IETF IPR Policy can be
found at [3].

Thank you.
[1] https://datatracker.ietf.org/doc/bcp78/<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/bcp78/__;!!NEt6yMaO-gk!E25ktslg-V5iKeFUQ8d33qerybOf4P_7vD2AonhtV_L3afhs-naNBhMRFxazgd0mmgIz7zDdxt6jKiAuZhJoW4CRF5_DQQ$>
[2] https://datatracker.ietf.org/doc/bcp79/<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/bcp79/__;!!NEt6yMaO-gk!E25ktslg-V5iKeFUQ8d33qerybOf4P_7vD2AonhtV_L3afhs-naNBhMRFxazgd0mmgIz7zDdxt6jKiAuZhJoW4DQFAUFwQ$>
[3] https://datatracker.ietf.org/doc/rfc6701/<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/rfc6701/__;!!NEt6yMaO-gk!E25ktslg-V5iKeFUQ8d33qerybOf4P_7vD2AonhtV_L3afhs-naNBhMRFxazgd0mmgIz7zDdxt6jKiAuZhJoW4AeW7NFXQ$>



_______________________________________________
BESS mailing list -- [e-mail]
To unsubscribe send an email to [e-mail]