Subject: WG Last Call: draft-ietf-bess-evpn-unequal-lb-26 (Ends 2025-09-24)
This message starts a 2-week WG Last Call for this document.
Abstract:
EVPN enables all-active multi-homing for a CE (Customer Equipment)
device connected to two or more PE (Provider Equipment) devices via a
LAG (Link Aggregation), such that bridged and routed traffic from
remote PEs to hosts attached to the Ethernet Segment can be equally
load balanced (it uses Equal Cost Multi Path) across the multi-homing
PEs. EVPN also enables multi-homing for IP subnets advertised in IP
Prefix routes, so that routed traffic from remote PEs to those IP
subnets can be load balanced. This document defines extensions to
EVPN procedures to optimally handle unequal access bandwidth
distribution across a set of multi-homing PEs in order to:
* provide greater flexibility, with respect to adding or removing
individual multi-homed PE-CE links.
* handle multi-homed PE-CE link failures that can result in unequal
PE-CE access bandwidth across a set of multi-homing PEs.
In order to achieve the above, it specifies signaling extensions and
procedures to:
* Loadbalance bridged and routed traffic across egress PEs in
proportion to PE-CE link bandwidth or a generalized weight
distribution.
* Achieve BUM (Broadcast, UnknownUnicast, Multicast) DF (Designated
Forwarder) election distribution for a given ES (Ethernet Segment)
across the multi-homing PE set in proportion to PE-CE link
bandwidth. Section 6 of this document further updates RFC 8584,
draft-ietf-bess-evpn-per-mcast-flow-df-election and draft-ietf-
bess-evpn-pref-df in order for the DF election extension defined
in this document to work across different DF election algorithms.
File can be retrieved from:
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-unequal-lb/
Please review and indicate your support or objection to proceed with the
publication of this document by replying to this email keeping [email protected]
in copy. Objections should be motivated and suggestions to resolve them are
highly appreciated.
Authors, and WG participants in general, are reminded again of the
Intellectual Property Rights (IPR) disclosure obligations described in BCP 79
[1]. 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/
[2] https://datatracker.ietf.org/doc/bcp79/
[3] https://datatracker.ietf.org/doc/rfc6701/
_______________________________________________
BESS mailing list -- [email protected]
To unsubscribe send an email to [email protected]
