[bess] Some questions regarding draft-ietf-bess-evpn-inter-subnet-forwarding-05

[Zhuangshunwan <[e-mail]>]

Dear authors,

I have some questions regarding draft-ietf-bess-evpn-inter-subnet-forwarding-05.

The last paragraph of https://tools.ietf.org/html/draft-ietf-bess-evpn-inter-subnet-forwarding-05#section-4.1.2 (Page 21) said:
   If EVPN-IRB NVEs are configured not to advertise MAC-only routes,
   then upon receiving the first data packet, it learns the MAC address
   of the TS and updates the MAC entry in the corresponding MAC-VRF
   table with the local adjacency information (e.g., local interface).
   It also realizes that there has been a MAC move because the same MAC
   address has been learned remotely from the source NVE. It then sends
   an unicast ARP request to the host and when receiving an ARP
   response, it follows the procedure outlined in section 4.1.1<https://tools.ietf.org/html/draft-ietf-bess-evpn-inter-subnet-forwarding-05#section-4.1.1>.

Question 1:
“… it follows the procedure outlined in section 4.1.1<https://tools.ietf.org/html/draft-ietf-bess-evpn-inter-subnet-forwarding-05#section-4.1.1>.”,
Which specific paragraph of section 4.1.1 is followed?
IMO, It follows the procedure that starts from the second paragraph of the section 4.1.1:
“
   The target NVE upon receiving this ARP request, updates its MAC-VRF,
   IP-VRF, and ARP table with the host MAC, IP, and local adjacency
   information (e.g., local interface).
…
“
Is my understanding correct?

Question 2:
“It then sends an unicast ARP request to the host and when receiving an ARP response”.
I think this sentence means： The target NVE sends an unicast ARP request to the moved host (TS) and the target NVE receives an ARP response from the moved host (TS). Then, per the ARP response, the target NVE can recognize that the moved host (TS) has been migrated to the target NVE.
Is my understanding correct?


Thanks,
Shunwan