Re: [nvo3] FW: I-D Action: draft-zhang-nvo3-yang-active-active-cfg-00.txt
hantao 00223943 <billow.han@huawei.com> Mon, 03 November 2014 07:51 UTC
Return-Path: <billow.han@huawei.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8865A1A0410 for <nvo3@ietfa.amsl.com>; Sun, 2 Nov 2014 23:51:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.794
X-Spam-Level:
X-Spam-Status: No, score=-4.794 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001] 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 RucyeY2b48_6 for <nvo3@ietfa.amsl.com>; Sun, 2 Nov 2014 23:51:04 -0800 (PST)
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 331DB1A6FC5 for <nvo3@ietf.org>; Sun, 2 Nov 2014 23:51:04 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BLF41467; Mon, 03 Nov 2014 07:51:02 +0000 (GMT)
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 3 Nov 2014 07:51:00 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.21]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0158.001; Mon, 3 Nov 2014 15:50:54 +0800
From: hantao 00223943 <billow.han@huawei.com>
To: "nvo3@ietf.org" <nvo3@ietf.org>
Thread-Topic: [nvo3] FW: I-D Action: draft-zhang-nvo3-yang-active-active-cfg-00.txt
Thread-Index: AQHP9zrkqqMlWvCNCEK3zw2Wno/KFw==
Date: Mon, 03 Nov 2014 07:50:53 +0000
Message-ID: <A0D2D4E67BB73041AF0ED8A82F309F7B3222A033@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.111.102.175]
Content-Type: multipart/alternative; boundary="_000_A0D2D4E67BB73041AF0ED8A82F309F7B3222A033nkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/nvo3/elvVDvC77t-gmxCG54Zp9DJRGXM
Subject: Re: [nvo3] FW: I-D Action: draft-zhang-nvo3-yang-active-active-cfg-00.txt
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" <nvo3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3>, <mailto:nvo3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nvo3/>
List-Post: <mailto:nvo3@ietf.org>
List-Help: <mailto:nvo3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3>, <mailto:nvo3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Nov 2014 07:51:05 -0000
Hi, This model can be used to realize the configuration of an all-active multi-homing. For the definition in this version, I find the VNI is defined as a leaf item. In this way, there might be as many as O(end-id)*O(vni) groups. How about defining the "vni" as a list. Then all VNIs assigned for this group can be put together. Thanks, Billow
- [nvo3] FW: I-D Action: draft-zhang-nvo3-yang-acti… Mingui Zhang
- Re: [nvo3] FW: I-D Action: draft-zhang-nvo3-yang-… hantao 00223943
- Re: [nvo3] FW: I-D Action: draft-zhang-nvo3-yang-… Mingui Zhang