Ok, let me elaborate.
A remote PE sending known unicast traffic to any PE attached to the all-active
Ethernet Segment (non-DF or DF, it’s irrelevant here!), has to use a label that
identifies the Broadcast Domain at the egress PE for a MAC lookup (if MAC-based
forwarding) or a label that
It “sounds” to me that Jaikumar’s question might be related to comparing
MPLS-based vs MAC-based forwarding models.
RFC8388 may help, sections 6-8.
My 2 cents.
Thx
Jorge
From: BESS on behalf of Jide Akintola
Date: Monday, February 18, 2019 at 1:23 PM
To: "bess@ietf.org" , Jaikumar
Hi Jaikumar,
You need to make a distinction between Alias label and several other EVPN
routes labels defined in the RFC7432. Kindly check that RFC for the route
encoding and their different usage/function.
As detailed in my previous email, alias label is a "hint" to the remote PE to
load
Thanks a lot Jide, for the reply.
Please find my response below [Jai]
Thanks & Regards
Jaikumar S
From: Jide Akintola
Sent: Monday, February 18, 2019 5:00 PM
To: bess@ietf.org; Jaikumar Somasundaram
Subject: Re: [bess] A question on using EVPN label and Alias label in load
balancing
Hi
Hi Jaikumar,
As per the rfc, aliasing is define as the ability of a PE to signal that it has
reachability to an EVPN instance on a given ES even when it has learned no MAC
addresses from that EVI/ES. It is advertised with Ethernet A-D per EVI type 1
routes.
Aliasing improves load-balancing by
