Re: [dcrg-interest] IP over IP solution for data center interconnect

Xuxiaohu <xuxiaohu@huawei.com> Fri, 23 December 2011 06:39 UTC

Return-Path: <xuxiaohu@huawei.com>
X-Original-To: dcrg-interest@ietfa.amsl.com
Delivered-To: dcrg-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7664311E8096 for <dcrg-interest@ietfa.amsl.com>; Thu, 22 Dec 2011 22:39:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.817
X-Spam-Level:
X-Spam-Status: No, score=-1.817 tagged_above=-999 required=5 tests=[AWL=0.240, BAYES_00=-2.599, CN_BODY_35=0.339, 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 tWJXjhpBuhfW for <dcrg-interest@ietfa.amsl.com>; Thu, 22 Dec 2011 22:39:05 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 0E11321F8AB0 for <dcrg-interest@irtf.org>; Thu, 22 Dec 2011 22:39:05 -0800 (PST)
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 <0LWN0004994TDQ@szxga04-in.huawei.com> for dcrg-interest@irtf.org; Fri, 23 Dec 2011 14:38:53 +0800 (CST)
Received: from szxrg02-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 <0LWN00FZW94LO9@szxga04-in.huawei.com> for dcrg-interest@irtf.org; Fri, 23 Dec 2011 14:38:53 +0800 (CST)
Received: from szxeml207-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AFW98823; Fri, 23 Dec 2011 14:38:43 +0800
Received: from SZXEML402-HUB.china.huawei.com (10.82.67.32) by szxeml207-edg.china.huawei.com (172.24.2.59) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 23 Dec 2011 14:38:41 +0800
Received: from SZXEML525-MBS.china.huawei.com ([169.254.8.55]) by szxeml402-hub.china.huawei.com ([10.82.67.32]) with mapi id 14.01.0323.003; Fri, 23 Dec 2011 14:38:41 +0800
Date: Fri, 23 Dec 2011 06:38:40 +0000
From: Xuxiaohu <xuxiaohu@huawei.com>
X-Originating-IP: [10.108.4.80]
To: "Eggert, Lars" <lars@netapp.com>, "dc@ietf.org" <dc@ietf.org>, "dcrg-interest@irtf.org" <dcrg-interest@irtf.org>
Message-id: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE762EB4@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: IP over IP solution for data center interconnect
Thread-index: AQHMwT2CzwDYBIw29UGeVkQ77HSrWQ==
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-CFilter-Loop: Reflected
References: <AFA7E5B6-4ABE-46FA-95B2-80BC5D3F62DA@netapp.com>
Cc: "armd@ietf.org" <armd@ietf.org>
Subject: Re: [dcrg-interest] IP over IP solution for data center interconnect
X-BeenThere: dcrg-interest@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <dcrg-interest.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/dcrg-interest>, <mailto:dcrg-interest-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/dcrg-interest>
List-Post: <mailto:dcrg-interest@irtf.org>
List-Help: <mailto:dcrg-interest-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/dcrg-interest>, <mailto:dcrg-interest-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Dec 2011 06:39:06 -0000

> -----邮件原件-----
> 发件人: Xuxiaohu
> 发送时间: 2011年12月22日 16:28
> 收件人: 'Eggert, Lars'; dc@ietf.org; 'dcrg-interest@irtf.org.'
> 主题: IP over IP solution for data center interconnect
> 
> Hi all,
> 
> There has been a lot of L2 over L3 solutions or proposals for data center
> network and data center interconnect till now. However, it seems recently
> there are increasing interests on L3 over L3 (e.g., IP over IP) solutions for data
> center network and data center interconnect, please see the following text
> quoted from IETF82 L2VPN minutes
> ( https://www.ietf.org/proceedings/82/minutes/l2vpn.txt). It's a general belief
> that L3 is more scalable than L2. Especially when considering the data center
> interconnection case, the L3 over L3 solutions can bring DC operators more
> benefits compared to the L2 over L3 solutions, such as path optimization,
> active-active data centers, MAC table reduction on DC switches and broadcast
> flood suppression etc .

By the way, the ARP table scaling issue on DC gateways, which is deemed by the ARMD WG as the only worthy ARP problem in data center networks, could also be solved with the IP over IP solution.

Best regards,
Xiaohu
 
> 
> Although Layer 2 connectivity is still required for some high-availability clusters
> which use non-IP and link-local multicast for communication, more and more
> cluster vendors are either already able to support cluster services at Layer3 or
> will support it in the near future. In addition, the GSLB mechanism (e.g., DNS
> based GSLB) works very well in most cases, is geo-cluster service still a
> common requirement for data center interconnect? If not, could we spend any
> time on exploring the possibility of using L3 over L3 solution for the most data
> center interconnection scenarios where geo-clustering, especially non-IP based
> geo-clustering is not needed?
> 
> Best regards,
> Xiaohu
> 
> ****************************************************************
> **********************************************************
> Kireeti: I keep seeing ISID, PBB, VLANs.  We have to stop conceding to layer 2
> and start moving to layer 3 (applause) and lots of problems will go away.
> 
> Florin: We should put VPN on the same page to modify the priorities. You need
> to expand so can look at L3 over L3 as well as L2 over L3. For item number 2 we
> need to look at L3 transport as well as Ethernet and MPLS.  And for number 3
> we need to work on this as there's a lot of expertise in L2, L3 and other WGs.
> 
> 
> Marc: The problem statement needs to include more of the L3 issues around
> sending L2 over L3, as the L2 traffic already contains L3.  Issue is just framing.
> 
> Eric Nordmark; "Yes, Yes and Yes".  We need to focus from the DC prospective
> and not from the VPN view.  don't just think about Ethernet over IP, but also IP
> over IP.  Hypervisor may get decoupled over time.
> ****************************************************************
> **********************************************************
> > -----邮件原件-----
> > 发件人: dc-bounces@ietf.org [mailto:dc-bounces@ietf.org] 代表 Eggert,
> Lars
> > 发送时间: 2011年12月16日 16:24
> > 收件人: dc@ietf.org
> > 主题: [dc] IRTF datacenter research group discussion list
> >
> > Hi,
> >
> > I wanted to make you all aware of the IRTF's dcrg-interest mailing list, which
> > was set up following a face-to-face meeting at SIGCOMM this year to discuss
> a
> > possible IRTF research group on datacenter networking:
> > http://irtf.org/mailman/listinfo/dcrg-interest
> >
> > There has not been much activity towards the formation of an IRTF RG since
> > SIGCOMM, but I am hopeful that the high energy level demonstrated in the
> > various Taipei meetings on the topic will inject some energy here - several of
> > the topics that may be too early for the IETF to standardize around would fit
> an
> > IRTF RG very well. I'm certainly supportive of this.
> >
> > Lars
> > IRTF Chair
> >
> >
> > --
> > Mobile number during December:    +358 46 5215582
> > Mobile number starting January:  +49 151 12055791