Hi Jeffrey,

Please see my replies inline.

From: Jeffrey (Zhaohui) Zhang <zzhang=40juniper....@dmarc.ietf.org>
Date: Wednesday, May 28, 2025 at 1:45 PM
To: bess@ietf.org <bess@ietf.org>
Subject: [bess] label scheme in EVPN A-D per EVI routes
Hi,

This is another question coming out of the shepherd review of RFC7432bis.

In the following text, what does "disposition" mean exactly? Just "forwarding"?

Ali> It means forwarding in the disposition direction – i.e., from core to 
access

   Note that the above allows the Ethernet A-D per EVI route to be
   advertised with one of the following granularities:

   *  One Ethernet A-D route per <ESI, Ethernet Tag ID> tuple per
      MAC-VRF.  This is applicable when the PE uses MPLS-based
      disposition with VID translation or may be applicable when the PE
      uses MAC-based disposition with VID translation.

Is it that the label alone will identify the outgoing AC w/o a MAC lookup, and 
it can also identify bridge table in which a MAC lookup is done?

Ali> That’s correct.


   *  One Ethernet A-D route for each <ESI> per MAC-VRF (where the
      Ethernet Tag ID is set to 0).  This is applicable when the PE uses
      MAC-based disposition or MPLS-based disposition without VID
      translation.

Is it that the VID in the packet plus the label will determine the outgoing AC 
or the bridge table in which a MAC lookup is done?

Ali> In case of MAC-based disposition (i.e., using MAC lookup), the received 
MPLS label identifies the bridge table, and the MAC lookup is performed there. 
In case of MPLS-based disposition, the received MPLS label identifies, egress 
port; however, no VID translation can be done for that port. I will change “or” 
or “or,” in the above sentence.


Thanks.
Jeffrey


Juniper Business Use Only

_______________________________________________
BESS mailing list -- bess@ietf.org
To unsubscribe send an email to bess-le...@ietf.org
_______________________________________________
BESS mailing list -- bess@ietf.org
To unsubscribe send an email to bess-le...@ietf.org

Reply via email to