Hi, I support adopting this draft.

Arista has a working implementation of the draft.

Alex

>
>
> ---------- Forwarded message ----------
> From: "Patrice Brissette (pbrisset)" <[email protected]>
> To: Zhaohui Zhang <[email protected]>, "[email protected]" <[email protected]>, "
> [email protected]" <[email protected]>, "
> [email protected]" <
> [email protected]>
> Cc:
> Bcc:
> Date: Sun, 3 May 2026 09:17:24 +0000
> Subject: [bess] Re: Call for adoption:
> draft-rbickhart-evpn-ip-mac-proxy-adv-06  (Ends 2026-05-12)
> Hi,
>
> As co-author, I support WG adoption of this draft. FRRouting already has
> an implementation used by SONiC community when supporting EVPN Multi-homing.
>
> Regards,
>
> Patrice Brissette
> Distinguished Software Engineer
>
>
> *From: *Zhaohui Zhang via Datatracker <[email protected]>
> *Date: *Tuesday, April 28, 2026 at 16:39
> *To: *[email protected] <[email protected]>; [email protected] <
> [email protected]>; [email protected] <
> [email protected]>
> *Subject: *Call for adoption: draft-rbickhart-evpn-ip-mac-proxy-adv-06
> (Ends 2026-05-12)
>
> This message starts a bess WG Call for Adoption of:
> draft-rbickhart-evpn-ip-mac-proxy-adv-06
>
> This Working Group Call for Adoption ends on 2026-05-12
>
> Abstract:
>    This document specifies procedures for EVPN PEs connected to a common
>    multihomed site to generate proxy EVPN MAC-IP advertisements on
>    behalf of other PEs to facilitate preservation of ARP/ND state across
>    link or node failures.
>
> Please reply to this message and indicate whether or not you support
> adoption
> of this Internet-Draft by the bess WG. Comments to explain your preference
> are greatly appreciated. Please reply to all recipients of this message and
> include this message in your response.
>
> 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.
> Jeffrey and BESS co-chairs
>
> [1] https://datatracker.ietf.org/doc/bcp78/
> [2] https://datatracker.ietf.org/doc/bcp79/
> [3] https://datatracker.ietf.org/doc/rfc6701/
>
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-rbickhart-evpn-ip-mac-proxy-adv/
>
> There is also an HTMLized version available at:
>
> https://datatracker.ietf.org/doc/html/draft-rbickhart-evpn-ip-mac-proxy-adv-06
>
> A diff from the previous version is available at:
>
> https://author-tools.ietf.org/iddiff?url2=draft-rbickhart-evpn-ip-mac-proxy-adv-06
> _______________________________________________
> BESS mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>
_______________________________________________
BESS mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to