Another Questions about the draft "draft-boutros-l2vpn-vxlan-evpn-04"
Haoweiguo <haoweiguo@huawei.com> Fri, 24 October 2014 01:26 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 70A9D1AD5AF for <l2vpn@ietfa.amsl.com>; Thu, 23 Oct 2014 18:26:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.76
X-Spam-Level:
X-Spam-Status: No, score=-1.76 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, 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 NR68rLpaI1eh for <l2vpn@ietfa.amsl.com>; Thu, 23 Oct 2014 18:26:17 -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 18B801AD627 for <l2vpn@ietf.org>; Thu, 23 Oct 2014 18:26:16 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BKW51100; Fri, 24 Oct 2014 01:26:15 +0000 (GMT)
Received: from NKGEML403-HUB.china.huawei.com (10.98.56.34) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 24 Oct 2014 02:26:14 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.21]) by nkgeml403-hub.china.huawei.com ([10.98.56.34]) with mapi id 14.03.0158.001; Fri, 24 Oct 2014 09:26:11 +0800
From: Haoweiguo <haoweiguo@huawei.com>
To: "l2vpn@ietf.org" <l2vpn@ietf.org>
Subject: Another Questions about the draft "draft-boutros-l2vpn-vxlan-evpn-04"
Thread-Topic: Another Questions about the draft "draft-boutros-l2vpn-vxlan-evpn-04"
Thread-Index: AQHP7yl+WpAd0NxLMEGDZiT7vaYZSg==
Date: Fri, 24 Oct 2014 01:26:10 +0000
Message-ID: <DD5FC8DE455C3348B94340C0AB5517334F80B058@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_DD5FC8DE455C3348B94340C0AB5517334F80B058nkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/89UfQyFNzK66fzgTGyPkNvGnOh0
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: Fri, 24 Oct 2014 01:26:19 -0000
Hi Co-authors, Another question: If we want to support VNI aware bundling EVPN, VN ID should be carried in the MPLS encapsulated frames. There carrying method can be: 1. Using extra MPLS Label to carry VN ID. But MPLS Label has only 20 bits, it doesn't match 24bits VN ID. 2. Using Ethernet Tag to carry VN ID. VLAN ID has only 12 bits, it also doesn't match 24bits VN ID. Do you have any other carrying VN ID method? What's your suggestions? Thanks weiguo ________________________________ 发件人: Haoweiguo 发送时间: 2014年10月16日 10:08 收件人: l2vpn@ietf.org 主题: Questions about the draft "draft-boutros-l2vpn-vxlan-evpn-04" 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