IETF Logo Mail Archive

Re: [nvo3] unified encapsulation headers for both Layer2 and Layer3 VPN overlays?

Xuxiaohu <xuxiaohu@huawei.com> Wed, 21 November 2012 03:04 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 4535121F8773 for <nvo3@ietfa.amsl.com>; Tue, 20 Nov 2012 19:04:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.662
X-Spam-Level:
X-Spam-Status: No, score=-2.662 tagged_above=-999 required=5 tests=[AWL=-0.267, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p2MwipdLqsKb for <nvo3@ietfa.amsl.com>; Tue, 20 Nov 2012 19:04:37 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id C462821F84CF for <nvo3@ietf.org>; Tue, 20 Nov 2012 19:04:36 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ALT29151; Wed, 21 Nov 2012 03:04:35 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 21 Nov 2012 03:04:06 +0000
Received: from SZXEML402-HUB.china.huawei.com (10.82.67.32) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 21 Nov 2012 03:04:34 +0000
Received: from SZXEML525-MBX.china.huawei.com ([169.254.1.161]) by szxeml402-hub.china.huawei.com ([::1]) with mapi id 14.01.0323.003; Wed, 21 Nov 2012 11:04:26 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "nvo3@ietf.org" <nvo3@ietf.org>
Thread-Topic: [nvo3] unified encapsulation headers for both Layer2 and Layer3 VPN overlays?
Thread-Index: Ac2X4Ugr93knpXh5RySCUK6WDOKxff//tcWA/6BP2aA=
Date: Wed, 21 Nov 2012 03:04:25 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE07572710@szxeml525-mbx.china.huawei.com>
References: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0755BE2F@szxeml525-mbx.china.huawei.com> <CABRz93X5=c6vaD-gPYF1+z16b4_mYdXJswSTNDq=8FDHUC=34g@mail.gmail.com>
In-Reply-To: <CABRz93X5=c6vaD-gPYF1+z16b4_mYdXJswSTNDq=8FDHUC=34g@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.98.130]
Content-Type: multipart/alternative; boundary="_000_1FEE3F8F5CCDE64C9A8E8F4AD27C19EE07572710szxeml525mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [nvo3] unified encapsulation headers for both Layer2 and Layer3 VPN overlays?
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: Wed, 21 Nov 2012 03:04:38 -0000

Hi all,

The following two drafts may be useful for us to further this discussion:

http://tools.ietf.org/html/draft-yong-l3vpn-nvgre-vxlan-encap-00
http://tools.ietf.org/html/draft-drao-bgp-l3vpn-virtual-network-overlays-00

Best regards,
Xiaohu

发件人: Kireeti Kompella [mailto:kireeti.kompella@gmail.com]
发送时间: 2012年9月21日 21:44
收件人: Xuxiaohu
抄送: nvo3@ietf.org
主题: Re: [nvo3] unified encapsulation headers for both Layer2 and Layer3 VPN overlays?

Hi,

For a number of reasons, including the current "vigorous discussion" on multiple encaps for L2-in-L3, I would STRONGLY URGE the group to not go there.
There are more than enough L3-in-L3 encaps already: sufficient unto the day ....

Regards,
Kireeti.

On Fri, Sep 21, 2012 at 3:10 AM, Xuxiaohu <xuxiaohu@huawei.com<mailto:xuxiaohu@huawei.com>> wrote:
Hi all,

It’s well-known that MPLS encapsulation can be used in both Layer2 VPN overlay (e.g., MAC-in-MPLS-in-GRE) and Layer3 VPN overlay (e.g., IP-in-MPLS-in-GRE). Meanwhile, although NVGRE is targeted only for Layer2 VPN overlay (i.e., MAC over IP overlay) scheme at present, the protocol type field in the GRE header however provides a possibility of supporting Layer3 VPN overlay (i.e., IP over IP overlay) if needed in the future. However, as per the encapsulation format described in the current version of VXLAN draft, there is no such protocol type field in the VXLAN header yet. Hence I suggest the VXLAN co-authors could consider using some reserved bits as the protocol type field. In this way, the VXLAN encapsulation header could also be applicable to the Layer3 VPN overlay scheme if needed in the future.

Best regards,
Xiaohu

_______________________________________________
nvo3 mailing list
nvo3@ietf.org<mailto:nvo3@ietf.org>
https://www.ietf.org/mailman/listinfo/nvo3



--
Kireeti

v2.23.0 | Report a Bug | By Email