re: Application of L3VPN for DCI//re: Preliminary L3VPN/VPN4DC agenda@ IETF82
Xuxiaohu <xuxiaohu@huawei.com> Fri, 04 November 2011 06:01 UTC
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: l3vpn@ietfa.amsl.com
Delivered-To: l3vpn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E10E611E808D for <l3vpn@ietfa.amsl.com>; Thu, 3 Nov 2011 23:01:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.161
X-Spam-Level:
X-Spam-Status: No, score=-2.161 tagged_above=-999 required=5 tests=[AWL=-1.304, BAYES_00=-2.599, CN_BODY_35=0.339, J_CHICKENPOX_13=0.6, J_CHICKENPOX_32=0.6, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, 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 uIaN+xgcSnaL for <l3vpn@ietfa.amsl.com>; Thu, 3 Nov 2011 23:01:42 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 50E1211E8073 for <l3vpn@ietf.org>; Thu, 3 Nov 2011 23:01:42 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LU400AUUGQMPH@szxga04-in.huawei.com> for l3vpn@ietf.org; Fri, 04 Nov 2011 14:01:34 +0800 (CST)
Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LU4006JJGQLVO@szxga04-in.huawei.com> for l3vpn@ietf.org; Fri, 04 Nov 2011 14:01:34 +0800 (CST)
Received: from szxeml208-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AEW24634; Fri, 04 Nov 2011 14:00:53 +0800
Received: from SZXEML401-HUB.china.huawei.com (10.82.67.31) by szxeml208-edg.china.huawei.com (172.24.2.60) with Microsoft SMTP Server (TLS) id 14.1.270.1; Fri, 04 Nov 2011 14:00:47 +0800
Received: from SZXEML525-MBS.china.huawei.com ([169.254.8.181]) by szxeml401-hub.china.huawei.com ([10.82.67.31]) with mapi id 14.01.0270.001; Fri, 04 Nov 2011 14:00:48 +0800
Date: Fri, 04 Nov 2011 06:00:47 +0000
From: Xuxiaohu <xuxiaohu@huawei.com>
Subject: re: Application of L3VPN for DCI//re: Preliminary L3VPN/VPN4DC agenda@ IETF82
In-reply-to: <238542D917511A45B6B8AA806E875E25073CA754@XMB-RCD-201.cisco.com>
X-Originating-IP: [10.108.4.59]
To: "Luyuan Fang (lufang)" <lufang@cisco.com>, Pedro Marques <pedro.r.marques@gmail.com>
Message-id: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE73D053@szxeml525-mbs.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset="gb2312"
Content-language: zh-CN
Content-transfer-encoding: base64
Accept-Language: zh-CN, en-US
Thread-topic: Application of L3VPN for DCI//re: Preliminary L3VPN/VPN4DC agenda@ IETF82
Thread-index: AQHMmrGOILXiFPzge0SLRu2L8lR6TpWcNUOw
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-CFilter-Loop: Reflected
References: <EE622807-97A1-49C4-9398-C51EF7F86677@niven-jenkins.co.uk> <4A95BA014132FF49AE685FAB4B9F17F6120B1CD6@dfweml505-mbx> <238542D917511A45B6B8AA806E875E25073CA33E@XMB-RCD-201.cisco.com> <4A95BA014132FF49AE685FAB4B9F17F6120B1F7A@dfweml505-mbx> <CAMXVrt4aXnTxkygtrusAqwBUD3_2SKnWysQ7offM+MAkV7vy4Q@mail.gmail.com> <4A95BA014132FF49AE685FAB4B9F17F6120B209B@dfweml505-mbx> <CAMXVrt533yfVUq_eMqddoDYprthu=N91tD=UzuTfOFjjwaa2-w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE73D016@szxeml525-mbs.china.huawei.com> <CAMXVrt5LpbOd+DXDmHmvH_77q=ueX0+Uqko2cQsv9jWEYLdaOQ@mail.gmail.com> <238542D917511A45B6B8AA806E875E25073CA754@XMB-RCD-201.cisco.com>
Cc: L3VPN WG mailing list <l3vpn@ietf.org>
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Nov 2011 06:01:44 -0000
Luyuan, > -----邮件原件----- > 发件人: Luyuan Fang (lufang) [mailto:lufang@cisco.com] > 发送时间: 2011年11月4日 13:21 > 收件人: Pedro Marques; Xuxiaohu > 抄送: L3VPN WG mailing list > 主题: RE: Application of L3VPN for DCI//re: Preliminary L3VPN/VPN4DC > agenda@ IETF82 > > Xiaohu, > > VM mobility is certainly in scope for VPN4DC, it would not be much use > otherwise. > There are large modern data centers running l3 only today, VM mobility > goes without say, it works. Oh, sorry, it's my misunderstanding:) > Assume your draft is with l2vpn WG, as you called out "IP only L2VPN > solution". Virtual Subnet is an approach for subnet extension by the use of L3VPN or ARP proxy technologies. To some extension, subnet extension could be understood as an IP-only L2VPN service due to the following two reasons:1) from the perspective of CE hosts, subnet extension makes them act as if they are located within the same L2VPN instance:2) only IP traffic is allowed to be transported in Virtual Subnet. Since it's an application of L3VPN protocol as a data center interconnection solution, I think it should be talked at L3VPN WG. Best regards, Xiaohu > Thanks, > Luyuan > > > -----Original Message----- > > From: l3vpn-bounces@ietf.org [mailto:l3vpn-bounces@ietf.org] On Behalf > > Of Pedro Marques > > Sent: Friday, November 04, 2011 12:14 AM > > To: Xuxiaohu > > Cc: L3VPN WG mailing list > > Subject: Re: Application of L3VPN for DCI//re: Preliminary > L3VPN/VPN4DC > > agenda@ IETF82 > > > > Xiaohu, > > > > On Thu, Nov 3, 2011 at 8:54 PM, Xuxiaohu <xuxiaohu@huawei.com> wrote: > > >> There is a second reason why the data-center network topology is > > >> virtualized which is the need to support VM moves. This implies > that > > >> the IP addresses used for communication between applications may be > > >> anywhere across the data-center. Using a virtual topology is an > > >> attractive way to solve this problem. > > > > > > I guess VM mobility is not the object for VPN4DC. For VM mobility > > across data centers, subnet extension at least is required so as to > > allow the IP addresses used for communication between applications to > > be anywhere across the data-centers. > > > > There is no reason to think in terms of subnets. Given that there is > > no locality the concept of subnet no longer makes any sense. Thus one > > has a collection of host routes spread randomly across a large area. > > > > It is trivial to make all VM to VM communication routed. If you look > > at the details in the l3vpn-end-system proposal, packets are routed > > from the VM to the host-os and by the host-os which encapsulates the > > packets. The latter has a collection of host routes. Thinking in terms > > of subnets is not helpful, the concept is just not applicable. > > > > Using ARP, proxy or otherwise, is simply self inflicted pain and > > suffering. There is no reason to care about the mac address of the > > remote system. > > > > regards, > > Pedro.
- Preliminary L3VPN/VPN4DC agenda @ IETF82 Ben Niven-Jenkins
- RE: Preliminary L3VPN/VPN4DC agenda @ IETF82 Lucy yong
- RE: Preliminary L3VPN/VPN4DC agenda @ IETF82 Linda Dunbar
- RE: Preliminary L3VPN/VPN4DC agenda @ IETF82 Luyuan Fang (lufang)
- RE: Preliminary L3VPN/VPN4DC agenda @ IETF82 Linda Dunbar
- Re: Preliminary L3VPN/VPN4DC agenda @ IETF82 Pedro Marques
- Re: Preliminary L3VPN/VPN4DC agenda @ IETF82 Robert Raszuk
- RE: Preliminary L3VPN/VPN4DC agenda @ IETF82 Linda Dunbar
- RE: Preliminary L3VPN/VPN4DC agenda @ IETF82 Linda Dunbar
- Re: Preliminary L3VPN/VPN4DC agenda @ IETF82 Robert Raszuk
- RE: Preliminary L3VPN/VPN4DC agenda @ IETF82 Luyuan Fang (lufang)
- Re: Preliminary L3VPN/VPN4DC agenda @ IETF82 Pedro Marques
- RE: Preliminary L3VPN/VPN4DC agenda @ IETF82 Linda Dunbar
- RE: Preliminary L3VPN/VPN4DC agenda @ IETF82 Linda Dunbar
- Re: Preliminary L3VPN/VPN4DC agenda @ IETF82 Robert Raszuk
- RE: Preliminary L3VPN/VPN4DC agenda @ IETF82 Luyuan Fang (lufang)
- RE: Preliminary L3VPN/VPN4DC agenda @ IETF82 Linda Dunbar
- RE: Preliminary L3VPN/VPN4DC agenda @ IETF82 Luyuan Fang (lufang)
- Application of L3VPN for DCI//re: Preliminary L3V… Xuxiaohu
- Re: Application of L3VPN for DCI//re: Preliminary… Pedro Marques
- RE: Application of L3VPN for DCI//re: Preliminary… Luyuan Fang (lufang)
- re: Application of L3VPN for DCI//re: Preliminary… Xuxiaohu
- 答复: Application of L3VPN for DCI//re: Preliminary… Xuxiaohu
- 答复: Application of L3VPN for DCI//re: Preliminary… Xuxiaohu
- re: Application of L3VPN for DCI//re: Preliminary… Xuxiaohu
- 答复: Application of L3VPN for DCI//re: Preliminary… Xuxiaohu
- Re: 答复: Application of L3VPN for DCI//re: Prelimi… Pedro Marques
- Re: Preliminary L3VPN/VPN4DC agenda @ IETF82 Bitar, Nabil N
- Re: Preliminary L3VPN/VPN4DC agenda @ IETF82 Derick Winkworth
- Re: Preliminary L3VPN/VPN4DC agenda @ IETF82 Lizhong Jin
- RE: Preliminary L3VPN/VPN4DC agenda @ IETF82 Luyuan Fang (lufang)
- RE: Preliminary L3VPN/VPN4DC agenda @ IETF82 Luyuan Fang (lufang)
- RE: Preliminary L3VPN/VPN4DC agenda @ IETF82 Luyuan Fang (lufang)
- RE: Preliminary L3VPN/VPN4DC agenda @ IETF82 Luyuan Fang (lufang)
- Re: Preliminary L3VPN/VPN4DC agenda @ IETF82 Lizhong Jin
- Re: Preliminary L3VPN/VPN4DC agenda @ IETF82 Bitar, Nabil N
- Re: Preliminary L3VPN/VPN4DC agenda @ IETF82 Derick Winkworth
- re: Application of L3VPN for DCI//re: Preliminary… Xuxiaohu