Re: [nvo3] Why not use L3VPN for data center interconnect? (was //re: Request a WG adoption poll for draft-xu-virtual-subnet-10)
"Luyuan Fang (lufang)" <lufang@cisco.com> Tue, 02 July 2013 14:44 UTC
Return-Path: <lufang@cisco.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 6992A21F9C8C; Tue, 2 Jul 2013 07:44:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.457
X-Spam-Level:
X-Spam-Status: No, score=-5.457 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CN_BODY_35=0.339, J_CHICKENPOX_13=0.6, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_HI=-8]
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 nn2Pvpx0R8kI; Tue, 2 Jul 2013 07:44:38 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 73FAD21F9A05; Tue, 2 Jul 2013 07:44:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6434; q=dns/txt; s=iport; t=1372776268; x=1373985868; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=HvDQaoyRd4L2wRl4AvICXP87stccYa5hfKSzWprIXYw=; b=Vp6ZD9IW8e5Gzm+y/Kh+pHTtbIdx1I9Uch8t1K6vIHQ2oWhkmnfbGQiJ TEJ8WxHjDFXJ1H3yCYMUWV1quJi+l3GPEox+hIsOeIYeDBE7rgnoMiO1u WZuceEmaLD2+x58PbNhJ4jSTLPFTbABYzcE7lNHxT6NpM3TLtZJjEHvr6 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiUFAKDl0lGtJV2Y/2dsb2JhbABagwkySYMHvEYNdBZ0giMBAQEDATRFBQcGAQYCEQMBAgUGGQQFBDAUCQgCBAENBQiIAQYMjyKbOQiRN4EijHaBDwIWGwcGgkc3ZwOYcpAcgViBOYFxNw
X-IronPort-AV: E=Sophos;i="4.87,980,1363132800"; d="scan'208";a="229763109"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-1.cisco.com with ESMTP; 02 Jul 2013 14:44:27 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r62EiRnd031805 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 2 Jul 2013 14:44:27 GMT
Received: from xmb-rcd-x03.cisco.com ([169.254.7.100]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.02.0318.004; Tue, 2 Jul 2013 09:44:26 -0500
From: "Luyuan Fang (lufang)" <lufang@cisco.com>
To: Xuxiaohu <xuxiaohu@huawei.com>, L3VPN <l3vpn@ietf.org>
Thread-Topic: Why not use L3VPN for data center interconnect? (was //re: Request a WG adoption poll for draft-xu-virtual-subnet-10)
Thread-Index: AQHOdzKmbHVswEhesE6gJNHDWf6d9Q==
Date: Tue, 02 Jul 2013 14:44:26 +0000
Message-ID: <0DB8F45437AB844CBB5102F807A0AD9310438A42@xmb-rcd-x03.cisco.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE081CB31D@NKGEML512-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.5.130515
x-originating-ip: [10.21.115.117]
Content-Type: text/plain; charset="gb2312"
Content-ID: <BB333A801293EA4C8715E2734279693B@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "nvo3@ietf.org" <nvo3@ietf.org>
Subject: Re: [nvo3] Why not use L3VPN for data center interconnect? (was //re: Request a WG adoption poll for draft-xu-virtual-subnet-10)
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 02 Jul 2013 14:44:43 -0000
> why not try to use the proven L3VPN technology for data center >interconnect... We presented draft-fang-l3vpn-data-center-interconnect in Orlando, IETF 86. http://tools.ietf.org/html/draft-fang-l3vpn-data-center-interconnect-01 Comments from WGs are welcome. Thanks, Luyuan -----Original Message----- From: Xuxiaohu <xuxiaohu@huawei.com> Date: Tuesday, July 2, 2013 2:52 AM To: L3VPN <l3vpn@ietf.org> Cc: "nvo3@ietf.org" <nvo3@ietf.org> Subject: Why not use L3VPN for data center interconnect?//re: Request a WG adoption poll for draft-xu-virtual-subnet-10 >Hi all, > >Till now, it seems that too much attention has been paid to the use of >L2VPN for data center interconnect. Although there are still a few >clustering applications which rely on non-IP or non-routable IP >communications (e.g., heartbeat messages between cluster nodes), more and >more cluster vendors are offering clustering applications based on Layer >3 interconnection. In addition, geographical high-availability clusters >is not a must in many data center interconnect cases. > >As L3VPN has many distinct advantages over L2VPN for data center >interconnect such as: scaling forwarding tables of data center switches, >path optimization, unknown unicast and ARP suppression... why not try to >use the proven L3VPN technology for data center interconnect in the >scenario where the limitations as mentioned above don't exist? > >Best regards, >Xiaohu > >> -----邮件原件----- >> 发件人: thomas.morin@orange.com [mailto:thomas.morin@orange.com] >> 发送时间: 2013年7月1日 21:14 >> 收件人: Xuxiaohu >> 抄送: l3vpn-chairs@tools.ietf.org; martin.vigoureux@alcatel-lucent.com; >> L3VPN >> 主题: Re: Request a WG adoption poll for draft-xu-virtual-subnet-10 >> >> Hello Xuxiaohu, >> >> Before eventually starting a discussion on the adoption on this >> document, we chairs would like to see more discussion and have the >> feedback from more readers (during the 2 previous meetings, only 5 to 10 >> people raised their hand when the room was polled on having read the >> document). >> >> Regards, >> >> -Thomas and Martin, >> l3vpn co-chairs >> >> >> 2013-07-01, Xuxiaohu: >> > Hi Thomas and Martin, >> > >> > I haven't received any response from any of you. Hence I resend it. >> > >> > Best regards, >> > Xiaohu >> > >> >> -----邮件原件----- >> >> 发件人: Xuxiaohu >> >> 发送时间: 2013年6月20日 15:07 >> >> 收件人: 'l3vpn-chairs@tools.ietf.org'; 'thomas.morin@orange.com'; >> >> 'martin.vigoureux@alcatel-lucent.com' >> >> 抄送: L3VPN >> >> 主题: Request a WG adoption poll for draft-xu-virtual-subnet-10 >> >> >> >> Hi WG co-chairs, >> >> >> >> As mentioned before, this draft >> >> (http://tools.ietf.org/html/draft-xu-virtual-subnet-10) describes >>how to >> reuse >> >> the proven L3VPN technology to realize subnet extension for data >>center >> >> interconnect, with the aid of many concrete experiments and >>verifications. >> >> >> >> We co-authors believe the information contained in this draft would >>be >> valuable >> >> for cloud service providers to evaluate the feasibility of adopting >>the proven >> >> L3VPN technology for data center interconnection (by the way, some >>people >> >> had shown their interests on the scheme described in this draft when >> visiting >> >> our implementation demo of this scheme at the Bits-N-Bites event of >> IETF86). >> >> Hence we would like co-chairs to start a WG adoption poll for this >>draft. >> >> >> >> Best regards, >> >> Xiaohu (on behalf of all co-authors) >> >> ________________________________________________________________ >> _________________________________________________________ >> >> Ce message et ses pieces jointes peuvent contenir des informations >> confidentielles ou privilegiees et ne doivent donc >> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez >>recu ce >> message par erreur, veuillez le signaler >> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages >> electroniques etant susceptibles d'alteration, >> Orange decline toute responsabilite si ce message a ete altere, deforme >>ou >> falsifie. Merci. >> >> This message and its attachments may contain confidential or privileged >> information that may be protected by law; >> they should not be distributed, used or copied without authorisation. >> If you have received this email in error, please notify the sender and >>delete this >> message and its attachments. >> As emails may be altered, Orange is not liable for messages that have >>been >> modified, changed or falsified. >> Thank you. >
- [nvo3] Why not use L3VPN for data center intercon… Xuxiaohu
- Re: [nvo3] Why not use L3VPN for data center inte… Eric Osborne (eosborne)
- Re: [nvo3] Why not use L3VPN for data center inte… Luyuan Fang (lufang)
- Re: [nvo3] Why not use L3VPN for data center inte… Xuxiaohu
- Re: [nvo3] Why not use L3VPN for data center inte… Xuxiaohu
- Re: [nvo3] Why not use L3VPN for data center inte… Xuxiaohu
- Re: [nvo3] Why not use L3VPN for data center inte… Xuxiaohu
- Re: [nvo3] Why not use L3VPN for data center inte… Xuxiaohu