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

Zhuangshunwan <zhuangshunwan@huawei.com> Thu, 13 September 2018 08:01 UTC

Return-Path: <zhuangshunwan@huawei.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 0BB19130FF9; Thu, 13 Sep 2018 01:01:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id EBIrZEE_SavL; Thu, 13 Sep 2018 01:01:10 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C37CB130FB4; Thu, 13 Sep 2018 01:01:09 -0700 (PDT)
Received: from lhreml707-cah.china.huawei.com (unknown []) by Forcepoint Email with ESMTP id 31F00316837B4; Thu, 13 Sep 2018 09:01:05 +0100 (IST)
Received: from NKGEML414-HUB.china.huawei.com ( by lhreml707-cah.china.huawei.com ( with Microsoft SMTP Server (TLS) id 14.3.399.0; Thu, 13 Sep 2018 09:00:33 +0100
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml414-hub.china.huawei.com ([]) with mapi id 14.03.0399.000; Thu, 13 Sep 2018 16:00:23 +0800
From: Zhuangshunwan <zhuangshunwan@huawei.com>
To: "draft-ietf-bess-evpn-inter-subnet-forwarding@ietf.org" <draft-ietf-bess-evpn-inter-subnet-forwarding@ietf.org>
CC: "bess@ietf.org" <bess@ietf.org>
Thread-Topic: Some questions regarding draft-ietf-bess-evpn-inter-subnet-forwarding-05
Thread-Index: AdRLE1r05LwM8t65TICwjrNrzm4wmg==
Date: Thu, 13 Sep 2018 08:00:22 +0000
Message-ID: <19AB2A007F56DB4E8257F949A2FB9858DC471752@NKGEML515-MBX.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_19AB2A007F56DB4E8257F949A2FB9858DC471752NKGEML515MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/x3G_E0BQiiKkM_d3t5QhfKoWgjE>
Subject: [bess] Some questions regarding draft-ietf-bess-evpn-inter-subnet-forwarding-05
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Sep 2018 08:01:22 -0000

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?