[nvo3] Why said L3 "overlay" network
Xuxiaohu <xuxiaohu@huawei.com> Fri, 30 September 2011 03:03 UTC
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E60B121F8C8C for <nvo3@ietfa.amsl.com>; Thu, 29 Sep 2011 20:03:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.503
X-Spam-Level:
X-Spam-Status: No, score=-4.503 tagged_above=-999 required=5 tests=[AWL=2.096, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6ZfYp3MmPs4v for <nvo3@ietfa.amsl.com>; Thu, 29 Sep 2011 20:03:08 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 3DB5B21F8C68 for <nvo3@ietf.org>; Thu, 29 Sep 2011 20:02:49 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSB004P0F7S67@szxga05-in.huawei.com> for nvo3@ietf.org; Fri, 30 Sep 2011 11:04:41 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LSB00CK4F7S74@szxga05-in.huawei.com> for nvo3@ietf.org; Fri, 30 Sep 2011 11:04:40 +0800 (CST)
Received: from szxeml202-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id ADZ93077; Fri, 30 Sep 2011 11:04:40 +0800
Received: from SZXEML404-HUB.china.huawei.com (10.82.67.59) by szxeml202-edg.china.huawei.com (172.24.2.42) with Microsoft SMTP Server (TLS) id 14.1.270.1; Fri, 30 Sep 2011 11:04:28 +0800
Received: from SZXEML525-MBS.china.huawei.com ([169.254.8.181]) by szxeml404-hub.china.huawei.com ([::1]) with mapi id 14.01.0270.001; Fri, 30 Sep 2011 11:04:32 +0800
Date: Fri, 30 Sep 2011 03:04:31 +0000
From: Xuxiaohu <xuxiaohu@huawei.com>
X-Originating-IP: [10.108.4.115]
To: "nvo3@ietf.org" <nvo3@ietf.org>
Message-id: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE736EA7@szxeml525-mbs.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset="us-ascii"
Content-language: zh-CN
Content-transfer-encoding: 7bit
Accept-Language: zh-CN, en-US
Thread-topic: Why said L3 "overlay" network
Thread-index: Acx/H31u3u0ZgPffT8S7tWKR92bznA==
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-CFilter-Loop: Reflected
Subject: [nvo3] Why said L3 "overlay" network
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "L2 \"Network Virtualization Over l3\" overlay discussion list \(nvo3\)" <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: Fri, 30 Sep 2011 03:03:09 -0000
It's good to see such a mailing-list. It would be better to have a associated BoF/WG session at future IETF meetings. By the way, why said L3 "overlay" network in the following mailing-list purpose description? Why not L2 overlay over L3 network? +++++++++++++++++++++++++++++++++++++++++++++++ A new IETF non-working group email list has been created. List address: nvo3 at ietf.org Archive: http://www.ietf.org/mail-archive/web/nvo3/current/maillist.html To subscribe: https://www.ietf.org/mailman/listinfo/nvo3 Purpose: This list is to discuss potential IETF work related to providing L2 network virtualization service over an L3 overlay network. ++++++++++++++++++++++++++++++++++++++++++++++++ Best regards, Xiaohu
- [nvo3] Why said L3 "overlay" network Xuxiaohu