Questions about the draft "draft-boutros-l2vpn-vxlan-evpn-04"

Haoweiguo <haoweiguo@huawei.com> Thu, 16 October 2014 02:08 UTC

Return-Path: <haoweiguo@huawei.com>
X-Original-To: l2vpn@ietfa.amsl.com
Delivered-To: l2vpn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07A091ACE96 for <l2vpn@ietfa.amsl.com>; Wed, 15 Oct 2014 19:08:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id srMUIKBVY0Yp for <l2vpn@ietfa.amsl.com>; Wed, 15 Oct 2014 19:08:51 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA7861A008C for <l2vpn@ietf.org>; Wed, 15 Oct 2014 19:08:50 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BNR73963; Thu, 16 Oct 2014 02:08:48 +0000 (GMT)
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 16 Oct 2014 03:08:48 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.21]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Thu, 16 Oct 2014 10:08:44 +0800
From: Haoweiguo <haoweiguo@huawei.com>
To: "l2vpn@ietf.org" <l2vpn@ietf.org>
Subject: Questions about the draft "draft-boutros-l2vpn-vxlan-evpn-04"
Thread-Topic: Questions about the draft "draft-boutros-l2vpn-vxlan-evpn-04"
Thread-Index: Ac/o5hydoDo6Qr6VTEmXQxwbh3g4IA==
Date: Thu, 16 Oct 2014 02:08:43 +0000
Message-ID: <DD5FC8DE455C3348B94340C0AB5517334F808ABD@nkgeml501-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.135.23.94]
Content-Type: multipart/alternative; boundary="_000_DD5FC8DE455C3348B94340C0AB5517334F808ABDnkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/u-wx0YrA6DrWJnsC7meVyPbhWd8
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Layer 2 Virtual Private Networks <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2vpn/>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Oct 2014 02:08:53 -0000

Hi Co-authors,
I have read the draft, it provides an applicable solution for VXLAN/NVGRE network interconnection.
But some details haven't been clearly described, so i have the following questions:
1. How to allocate ESI Label in this scenario?
2. How to achieve mass MAC withdraw/Alias when local network occurs topology change?

If you have considered this question, clarifications are appreciated. If you haven't considered, we can work together for these points.
Thanks

weiguo