
From nobody Thu Apr  3 08:30:06 2014
Return-Path: <mkonstan@cisco.com>
X-Original-To: l2tpext@ietfa.amsl.com
Delivered-To: l2tpext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E45251A0204 for <l2tpext@ietfa.amsl.com>; Thu,  3 Apr 2014 08:30:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.51
X-Spam-Level: 
X-Spam-Status: No, score=-9.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aeZ0cv0KZDyG for <l2tpext@ietfa.amsl.com>; Thu,  3 Apr 2014 08:29:58 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) by ietfa.amsl.com (Postfix) with ESMTP id 1EEBB1A0207 for <l2tpext@ietf.org>; Thu,  3 Apr 2014 08:29:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9039; q=dns/txt; s=iport; t=1396538993; x=1397748593; h=from:to:cc:subject:date:message-id:references: in-reply-to:reply-to:mime-version; bh=Ggg6ynRjJ7q0Ziieitl84Ynt264mbAB9bQF4Jq9msWk=; b=ftnmno0nHbBt3KZy7qFcGfsccId0VPRxducsXafiON0mkI1pkEx1UuOo jm2DBmFIxFCAZ1UquGsRCQe86CZmB+iUYnmdXwqAJbmoVybLpJvXaqZ+n vvK75p66fTI38b0/X0/FUYjGTMNdmKcPap2f/uQWDXt3xc/2TUb9boGg2 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ar0FAAR+PVOtJV2Y/2dsb2JhbABYgkJEO0sMuwCBP4ZmUYEfFnSCJgEBBAEBARpRCxACAQg/BycLDgYRAgQOBYd5DbF3nSEXjg8RAVAGAYMkgRQEmFuBNJAmZIFxgT+Bcjk
X-IronPort-AV: E=Sophos; i="4.97,787,1389744000"; d="scan'208,217"; a="32626645"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-8.cisco.com with ESMTP; 03 Apr 2014 15:29:52 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s33FTqx3017286 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 3 Apr 2014 15:29:52 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.22]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.03.0123.003; Thu, 3 Apr 2014 10:29:52 -0500
From: "Maciek Konstantynowicz (mkonstan)" <mkonstan@cisco.com>
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Thread-Topic: [L2tpext] WG Adoption of Keyed IPv6 Tunnel [draft-mkonstan-l2tpext-keyed-ipv6-tunnel]
Thread-Index: AQHPT1GOOg1LIICLMUWuqlzfjT/XxQ==
Date: Thu, 3 Apr 2014 15:29:51 +0000
Message-ID: <561D1D06-F492-42D3-8739-A9B2DA3097B9@cisco.com>
References: <D3A58613-B4F3-4E6C-A90E-BE2732D8A6B9@cisco.com> <2C4B7689-549E-4302-A23F-DD7FEED10EFD@cisco.com>
In-Reply-To: <2C4B7689-549E-4302-A23F-DD7FEED10EFD@cisco.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.244.162]
Content-Type: multipart/alternative; boundary="_000_561D1D06F49242D38739A9B2DA3097B9ciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/l2tpext/KdME4mhwEQNH7FVgwZxAUw2lJtE
Cc: "draft-mkonstan-l2tpext-keyed-ipv6-tunnel@tools.ietf.org" <draft-mkonstan-l2tpext-keyed-ipv6-tunnel@tools.ietf.org>, "l2tpext@ietf.org" <l2tpext@ietf.org>
Subject: Re: [L2tpext] WG Adoption of Keyed IPv6 Tunnel [draft-mkonstan-l2tpext-keyed-ipv6-tunnel]
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "maciek@cisco.com" <maciek@cisco.com>
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2tpext/>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 15:30:03 -0000

--_000_561D1D06F49242D38739A9B2DA3097B9ciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Updated rev posted.

/maciek

On 24 Mar 2014, at 17:41, Carlos Pignataro (cpignata) <cpignata@cisco.com<m=
ailto:cpignata@cisco.com>> wrote:

L2TPExt,

This email concludes the call for adoption on this draft.

This document received good support on the list and is hereby adopted as an=
 L2TPExt WG document.

Authors, please post a new revision of the document as draft-ietf-l2tpext-k=
eyed-ipv6-tunnel-00.

Thanks!

Carlos and Ignacio, l2tpext co-chairs.

Thumb typed by Carlos Pignataro.
Excuze typofraphicak errows

On Mar 3, 2014, at 3:33 PM, "Carlos Pignataro (cpignata)" <cpignata@cisco.c=
om<mailto:cpignata@cisco.com>> wrote:

WG,

The authors of 'Keyed IPv6 Tunnel' have requested that L2TPEXT adopts this =
draft as a WG document. The draft received discussion and comments on the l=
ist, and was updated twice based on list feedback.

http://tools.ietf.org/html/draft-mkonstan-l2tpext-keyed-ipv6-tunnel-00

This message starts a three-week Call for WG Adoption for draft-mkonstan-l2=
tpext-keyed-ipv6-tunnel-00. Given that IETF89 is going on right now, we are=
 adding an extra week to this adoption call. The call for adoption will end=
 on Monday, March 24th.

Please share your thoughts on this adoption call on the list -- we will not=
 be taking silence as support. Bonus points supporting a yes/no email with =
a technical explanation as to why.

Thanks!

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


--_000_561D1D06F49242D38739A9B2DA3097B9ciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <192C1A2CF39D404E8694064469C5CB68@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;">
Updated rev posted.
<div><br>
<div>
<div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; t=
ext-align: start; text-indent: 0px; text-transform: none; white-space: norm=
al; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-w=
rap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-=
space;">
<div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; t=
ext-align: start; text-indent: 0px; text-transform: none; white-space: norm=
al; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-w=
rap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-=
space;">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; color:=
 rgb(0, 0, 0); font-family: 'Lucida Grande'; font-style: normal; font-varia=
nt: normal; font-weight: normal; letter-spacing: normal; line-height: norma=
l; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0p=
x; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px=
;">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space;">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; color:=
 rgb(0, 0, 0); font-family: 'Lucida Grande'; font-style: normal; font-varia=
nt: normal; font-weight: normal; letter-spacing: normal; line-height: norma=
l; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0p=
x; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px=
;">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space;">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; color:=
 rgb(0, 0, 0); font-family: 'Lucida Grande'; font-style: normal; font-varia=
nt: normal; font-weight: normal; letter-spacing: normal; line-height: norma=
l; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0p=
x; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px=
;">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space;">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; color:=
 rgb(0, 0, 0); font-family: 'Lucida Grande'; font-style: normal; font-varia=
nt: normal; font-weight: normal; letter-spacing: normal; line-height: norma=
l; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0p=
x; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px=
;">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space;">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; color:=
 rgb(0, 0, 0); font-family: 'Lucida Grande'; font-style: normal; font-varia=
nt: normal; font-weight: normal; letter-spacing: normal; line-height: norma=
l; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0p=
x; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px=
;">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space;">
/maciek</div>
</span></div>
</span></div>
</span></div>
</span></div>
</span></div>
</div>
</div>
<br>
<div>
<div>On 24 Mar 2014, at 17:41, Carlos Pignataro (cpignata) &lt;<a href=3D"m=
ailto:cpignata@cisco.com">cpignata@cisco.com</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div dir=3D"auto">
<div><span></span></div>
<div><span>L2TPExt,</span><br>
<span></span><br>
<span>This email concludes the call for adoption on this draft.</span></div=
>
<div><br>
</div>
<div>This document received good support on the list and is hereby adopted =
as an L2TPExt WG document.</div>
<div><br>
</div>
<div>Authors, please post a new revision of the document as&nbsp;<span styl=
e=3D"font-size: 12pt; font-family: Helvetica;"><b>draft-ietf-l2tpext-keyed-=
ipv6-tunnel-00</b>.&nbsp;</span><br>
<br>
Thanks!</div>
<div><br>
</div>
<div>Carlos and Ignacio, l2tpext co-chairs.&nbsp;<br>
<span></span><br>
<span>Thumb typed by Carlos Pignataro.</span><br>
<span>Excuze typofraphicak errows</span><br>
<span></span><br>
<blockquote type=3D"cite"><span>On Mar 3, 2014, at 3:33 PM, &quot;Carlos Pi=
gnataro (cpignata)&quot; &lt;<a href=3D"mailto:cpignata@cisco.com">cpignata=
@cisco.com</a>&gt; wrote:</span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>WG,</span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>The authors of 'Keyed IPv6 Tunnel' have req=
uested that L2TPEXT adopts this draft as a WG document. The draft received =
discussion and comments on the list, and was updated twice based on list fe=
edback.</span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span><a href=3D"http://tools.ietf.org/html/draft=
-mkonstan-l2tpext-keyed-ipv6-tunnel-00">http://tools.ietf.org/html/draft-mk=
onstan-l2tpext-keyed-ipv6-tunnel-00</a></span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>This message starts a three-week Call for W=
G Adoption for draft-mkonstan-l2tpext-keyed-ipv6-tunnel-00. Given that IETF=
89 is going on right now, we are adding an extra week to this adoption call=
. The call for adoption will end on
 Monday, March 24th.</span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>Please share your thoughts on this adoption=
 call on the list -- we will not be taking silence as support. Bonus points=
 supporting a yes/no email with a technical explanation as to why.</span><b=
r>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>Thanks!</span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>Carlos.</span><br>
</blockquote>
</div>
</div>
_______________________________________________<br>
L2tpext mailing list<br>
<a href=3D"mailto:L2tpext@ietf.org">L2tpext@ietf.org</a><br>
https://www.ietf.org/mailman/listinfo/l2tpext<br>
</blockquote>
</div>
<br>
</div>
</body>
</html>

--_000_561D1D06F49242D38739A9B2DA3097B9ciscocom_--


From nobody Thu Apr  3 08:39:44 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: l2tpext@ietfa.amsl.com
Delivered-To: l2tpext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A8F31A0212; Thu,  3 Apr 2014 08:39:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4JaAEpy9h_s3; Thu,  3 Apr 2014 08:39:34 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 78CC41A0214; Thu,  3 Apr 2014 08:39:32 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.2.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140403153932.32721.3531.idtracker@ietfa.amsl.com>
Date: Thu, 03 Apr 2014 08:39:32 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/l2tpext/klILeZrrAaDhSK9aRgFzELqT28U
Cc: l2tpext@ietf.org
Subject: [L2tpext] I-D Action: draft-ietf-l2tpext-keyed-ipv6-tunnel-00.txt
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2tpext/>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 15:39:39 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Layer Two Tunneling Protocol Extensions Working Group of the IETF.

        Title           : Keyed IPv6 Tunnel
        Authors         : Maciek Konstantynowicz
                          Giles Heron
                          Rainer Schatzmayr
                          Wim Henderickx
	Filename        : draft-ietf-l2tpext-keyed-ipv6-tunnel-00.txt
	Pages           : 11
	Date            : 2014-04-03

Abstract:
   This document describes a simple L2 Ethernet over IPv6 tunnel
   encapsulation with mandatory 64-bit key for connecting L2 Ethernet
   attachment circuits identified by IPv6 addresses.  The encapsulation
   is based on L2TPv3 over IP.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-l2tpext-keyed-ipv6-tunnel/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-l2tpext-keyed-ipv6-tunnel-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Apr  9 20:37:37 2014
Return-Path: <frank.xialiang@huawei.com>
X-Original-To: l2tpext@ietfa.amsl.com
Delivered-To: l2tpext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 975DD1A0041; Wed,  9 Apr 2014 20:37:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.473
X-Spam-Level: 
X-Spam-Status: No, score=-4.473 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bc0dUvPHdcUh; Wed,  9 Apr 2014 20:37:32 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id AA9F31A006B; Wed,  9 Apr 2014 20:37:30 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BCY07208; Thu, 10 Apr 2014 03:37:28 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 10 Apr 2014 04:36:07 +0100
Received: from SZXEMA404-HUB.china.huawei.com (10.82.72.36) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 10 Apr 2014 04:37:24 +0100
Received: from SZXEMA502-MBS.china.huawei.com ([169.254.4.203]) by SZXEMA404-HUB.china.huawei.com ([10.82.72.36]) with mapi id 14.03.0158.001; Thu, 10 Apr 2014 11:37:16 +0800
From: "Xialiang (Frank)" <frank.xialiang@huawei.com>
To: "l2tpext@ietf.org" <l2tpext@ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>
Thread-Topic: New Version Notification for draft-fan-l2tp-vp-01.txt
Thread-Index: AQHPVGwUioKZm7B370uoJbPkmsBi+JsKMc1A
Date: Thu, 10 Apr 2014 03:37:15 +0000
Message-ID: <C02846B1344F344EB4FAA6FA7AF481F10F3E29D0@SZXEMA502-MBS.china.huawei.com>
References: <20140410032205.30725.83163.idtracker@ietfa.amsl.com>
In-Reply-To: <20140410032205.30725.83163.idtracker@ietfa.amsl.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.135.42.220]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/l2tpext/5dOvhQHQumWZbRIfpD3hmdhBWNk
Cc: Fanduoliang <fanduoliang@huawei.com>, Zehn Cao <zehn.cao@gmail.com>, Namgon Kim <ng.kim@kt.com>
Subject: Re: [L2tpext] New Version Notification for draft-fan-l2tp-vp-01.txt
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2tpext/>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 03:37:33 -0000

SGkgZm9sa3MsDQpXZSBoYXZlIHVwZGF0ZWQgdGhlIEwyVFAtVlAgdmVyc2lvbiAtMDEgZHJhZnQu
IA0KSW4gdGhlIG5ldyB2ZXJzaW9uIGRyYWZ0LCB3ZSBhZGQgdGhlIG1vdGl2YXRpb24gb2YgdGhp
cyBkcmFmdCBhbmQgbW9kaWZpY2F0aW9uIHRvIHRoZSBmb3JtYXQgb2YgTDJUUC1WUCBoZWFkZXIu
DQpXZWxjb21lIHlvdXIgY29tbWVudHMgYW5kIHN1Z2dlc3Rpb25zIQ0KDQpCLlIuDQpGcmFuaw0K
DQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IGludGVybmV0LWRyYWZ0c0Bp
ZXRmLm9yZyBbbWFpbHRvOmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZ10NCj4gU2VudDogVGh1cnNk
YXksIEFwcmlsIDEwLCAyMDE0IDExOjIyIEFNDQo+IFRvOiBYaWFsaWFuZyAoRnJhbmspOyBaaGVu
IENhbzsgRmFuZHVvbGlhbmc7IFplaG4gQ2FvOyBOYW1nb24gS2ltOyBOYW1nb24NCj4gS2ltOyBG
YW5kdW9saWFuZzsgWGlhbGlhbmcgKEZyYW5rKQ0KPiBTdWJqZWN0OiBOZXcgVmVyc2lvbiBOb3Rp
ZmljYXRpb24gZm9yIGRyYWZ0LWZhbi1sMnRwLXZwLTAxLnR4dA0KPiANCj4gDQo+IEEgbmV3IHZl
cnNpb24gb2YgSS1ELCBkcmFmdC1mYW4tbDJ0cC12cC0wMS50eHQgaGFzIGJlZW4gc3VjY2Vzc2Z1
bGx5IHN1Ym1pdHRlZA0KPiBieSBMaWFuZyBYaWEgYW5kIHBvc3RlZCB0byB0aGUgSUVURiByZXBv
c2l0b3J5Lg0KPiANCj4gTmFtZToJCWRyYWZ0LWZhbi1sMnRwLXZwDQo+IFJldmlzaW9uOgkwMQ0K
PiBUaXRsZToJCUwyVFAtVlA6IExheWVyIFR3byBUdW5uZWxpbmcgUHJvdG9jb2wgLSBWaXJ0dWFs
aXphdGlvbiBQcm9maWxlDQo+IERvY3VtZW50IGRhdGU6CTIwMTQtMDQtMTANCj4gR3JvdXA6CQlJ
bmRpdmlkdWFsIFN1Ym1pc3Npb24NCj4gUGFnZXM6CQk5DQo+IFVSTDoNCj4gaHR0cDovL3d3dy5p
ZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtZmFuLWwydHAtdnAtMDEudHh0DQo+IFN0YXR1
czogICAgICAgICBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1mYW4tbDJ0
cC12cC8NCj4gSHRtbGl6ZWQ6ICAgICAgIGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0
LWZhbi1sMnRwLXZwLTAxDQo+IERpZmY6ICAgICAgICAgICBodHRwOi8vd3d3LmlldGYub3JnL3Jm
Y2RpZmY/dXJsMj1kcmFmdC1mYW4tbDJ0cC12cC0wMQ0KPiANCj4gQWJzdHJhY3Q6DQo+ICAgIFRo
aXMgZG9jdW1lbnQgZGVzY3JpYmVzIExheWVyIFR3byBUdW5uZWxpbmcgUHJvdG9jb2wgKEwyVFAp
J3MNCj4gICAgdmlydHVhbGl6YXRpb24gcHJvZmlsZSAoTDJUUC1WUCksIHdoaWNoIHJldXNlcyBz
ZXNzaW9uIGhlYWRlciBvZiBMMlRQDQo+ICAgIGRhdGEgbWVzc2FnZSB0byBzZWN1cmVseSBzdXBw
b3J0IG92ZXJsYXkgbmV0d29ya3MgZm9yIG11bHRpcGxlDQo+ICAgIHRlbmFudHMsIGFuZCBzaW1w
bGlmaWVzIHR1bm5lbCBzZXR1cCBieSBkaXNhYmxpbmcgYWxsIGtpbmRzIG9mIEwyVFANCj4gICAg
Y29udHJvbCBtZXNzYWdlcy4NCj4gDQo+IA0KPiANCj4gDQo+IFBsZWFzZSBub3RlIHRoYXQgaXQg
bWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mIHN1Ym1pc3Npb24N
Cj4gdW50aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0
b29scy5pZXRmLm9yZy4NCj4gDQo+IFRoZSBJRVRGIFNlY3JldGFyaWF0DQoNCg==


From nobody Thu Apr 10 08:58:45 2014
Return-Path: <therbert@google.com>
X-Original-To: l2tpext@ietfa.amsl.com
Delivered-To: l2tpext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B67B1A028D for <l2tpext@ietfa.amsl.com>; Thu, 10 Apr 2014 08:46:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.651
X-Spam-Level: 
X-Spam-Status: No, score=-1.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bk3awwS74rKg for <l2tpext@ietfa.amsl.com>; Thu, 10 Apr 2014 08:46:57 -0700 (PDT)
Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001:c05::233]) by ietfa.amsl.com (Postfix) with ESMTP id 07D8A1A0285 for <l2tpext@ietf.org>; Thu, 10 Apr 2014 08:46:56 -0700 (PDT)
Received: by mail-ig0-f179.google.com with SMTP id hl10so3943537igb.0 for <l2tpext@ietf.org>; Thu, 10 Apr 2014 08:46:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Y0shcQgreCWWZqC7dMC17mcRwVotqVyybALIM+1Ma0k=; b=EHo3wAQ/VajVvnoZADmrdgyTHziTGyG+UECqgyFS1/RynC5OZlGr24cHcGOPueiL4y LaokPncyont5FBd04DlAm4E7Q6qpoLc6DgNCWX4FxFmIHQTs/nCTHow02kTIc9mHDden 5ykopjSBdfJMsuYVFHmDnWGiHYY/2AzUq2vjOsnJO3fLCkyqfrWLGOmIjmDlIfzq8dh8 +yrzWN0DCCDU6AZG2S4iWNCe4WB+s0OCKGuqWINDzVKxOibu2ICODEC2xE7A1pHd08Wx VRtAplE6YtWjPg2W4RT3YcDAhOVHeMHFKixejEsCXNtXC8+bMTnVrrpIfxc4EPQzVP/w AlRA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Y0shcQgreCWWZqC7dMC17mcRwVotqVyybALIM+1Ma0k=; b=TJwoex0RzUxfDdTxp8xn67XmZ6U1vc91haqZetba/tVIJJomEkBVaM82lZadfuXYyP pSrc5PMQXapCfwR+P7YQzubAa4nkTNlk6yVjIAH8wYpHiggHFXpqYyFr+nxcMP6fJ25j Vw+Un6h2jvMANFd2yoyUr7wJSynLA3n9Jav3Uy3sBAKna6uvQ60msTWtrIHE6ICMc3qq 3fD3IjPhPBKHrXauwWYVj1xPZtBew0vi2PJ3mWRJr1dx/6Uu61ELecXWM3grrpPcUes/ BNMcBHVL3hteY6p2hw4OB5Mm92tpt7UWUKkiPsAwnyQe0cei1jEfV1uDVR26r1GB7qsR nI1A==
X-Gm-Message-State: ALoCoQk6W4nihD9dXHkZldhnlQS2r4HfrmYNB59TaWqpmekichH9NXI/l5fwG/fxw667BWx0r5nmGkgF1I03d+ViqevBmJj+bdTqlVeL7DPfrGQI0fLsR48N8qXXLaIQ7ETnKC2ouhN74+B9qTKJKaFZVrt2XWOxQ4eYofyrl4XI9lEqtRu4YII0faNRjYAAuAQLddEWRALh
MIME-Version: 1.0
X-Received: by 10.50.152.105 with SMTP id ux9mr11621829igb.28.1397144815741; Thu, 10 Apr 2014 08:46:55 -0700 (PDT)
Received: by 10.64.148.98 with HTTP; Thu, 10 Apr 2014 08:46:55 -0700 (PDT)
In-Reply-To: <C02846B1344F344EB4FAA6FA7AF481F10F3E29D0@SZXEMA502-MBS.china.huawei.com>
References: <20140410032205.30725.83163.idtracker@ietfa.amsl.com> <C02846B1344F344EB4FAA6FA7AF481F10F3E29D0@SZXEMA502-MBS.china.huawei.com>
Date: Thu, 10 Apr 2014 08:46:55 -0700
Message-ID: <CA+mtBx9r75d3bkk4FeHWXjPMwfetr97rBuxWoubDsx=_Y_RZ0g@mail.gmail.com>
From: Tom Herbert <therbert@google.com>
To: "Xialiang (Frank)" <frank.xialiang@huawei.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/l2tpext/9f_pTYHSicytbqL31YcLaIL2IKM
X-Mailman-Approved-At: Thu, 10 Apr 2014 08:58:43 -0700
Cc: Fanduoliang <fanduoliang@huawei.com>, Zehn Cao <zehn.cao@gmail.com>, "nvo3@ietf.org" <nvo3@ietf.org>, "l2tpext@ietf.org" <l2tpext@ietf.org>, Namgon Kim <ng.kim@kt.com>
Subject: Re: [L2tpext] [nvo3] New Version Notification for draft-fan-l2tp-vp-01.txt
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2tpext/>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 15:46:58 -0000

On Wed, Apr 9, 2014 at 8:37 PM, Xialiang (Frank)
<frank.xialiang@huawei.com> wrote:
> Hi folks,
> We have updated the L2TP-VP version -01 draft.
> In the new version draft, we add the motivation of this draft and modification to the format of L2TP-VP header.
> Welcome your comments and suggestions!
>
Hi Frank,

Thanks for posting. A few comments:

- This is so dramatically different from L2TP I wonder if it can still
honestly be called L2TP. Have you implemented this? How much of L2TP
stack can be leveraged?
- "Session ID is changed to a 31-bit field"-- doesn't this break L2TP then?
- "Type field"-- I suspect this is meant to be an EtherType value.
Please be explicit about this.
- To get hashing (for ECMP, RSS, etc.) in the network we'd almost
certainly use L2TP over UDP, so L2TP-VP should probably have a format
defined for use with UDP.
- Even with Type field, this still suffers from the same problem L2TP
has that network devices won't be able to parse the packet beyond the
L2TP header (the cookie field makes the header variable length). This
eliminates the ability to implement the protocol with LRO for
instance. I suggest you take four or five bits from reserved section
for header length to resolve this (see example in GUE).
- Cookie mechanism is an advantage over VXLAN and nvgre I believe, but
why limit it to 32 bits? 64 bits is much stronger, and at some point
we might even want 128 bits to do strong authentication.

Some more general questions applicable to this and some other proposals.

- "TNI field"-- this seems to use the same 24 bit left shifted format
of nvgre and VXLAN. I still don't see the rationale for this! Why
can't the full 32 bit field be allocated for vni? A large deployment
will be using various levels of hierarchical allocation and possibly
obfuscation of vni (TNI). The nvo3 requirements on this are vague
("100's of thousands of virtual networks"), but they clearly don't
expect this the VNI to be a simple flat space either.
- "Outer Ethernet Header"-- showing the outer Ethernet header in L3
encapsulations examples is not necessary, use of Ethernet is not a
requirement, and this is potentially very misleading. For instance,
the outer Ethernet FCS does *not* protect the packet end to end in an
L3 routed network. Personally, I think it would be more illustrative
to show the IP packet in the inner Ethernet frame instead to see how
its alignment is affected.

Thanks,
Tom

> B.R.
> Frank
>
>> -----Original Message-----
>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>> Sent: Thursday, April 10, 2014 11:22 AM
>> To: Xialiang (Frank); Zhen Cao; Fanduoliang; Zehn Cao; Namgon Kim; Namgon
>> Kim; Fanduoliang; Xialiang (Frank)
>> Subject: New Version Notification for draft-fan-l2tp-vp-01.txt
>>
>>
>> A new version of I-D, draft-fan-l2tp-vp-01.txt has been successfully submitted
>> by Liang Xia and posted to the IETF repository.
>>
>> Name:         draft-fan-l2tp-vp
>> Revision:     01
>> Title:                L2TP-VP: Layer Two Tunneling Protocol - Virtualization Profile
>> Document date:        2014-04-10
>> Group:                Individual Submission
>> Pages:                9
>> URL:
>> http://www.ietf.org/internet-drafts/draft-fan-l2tp-vp-01.txt
>> Status:         https://datatracker.ietf.org/doc/draft-fan-l2tp-vp/
>> Htmlized:       http://tools.ietf.org/html/draft-fan-l2tp-vp-01
>> Diff:           http://www.ietf.org/rfcdiff?url2=draft-fan-l2tp-vp-01
>>
>> Abstract:
>>    This document describes Layer Two Tunneling Protocol (L2TP)'s
>>    virtualization profile (L2TP-VP), which reuses session header of L2TP
>>    data message to securely support overlay networks for multiple
>>    tenants, and simplifies tunnel setup by disabling all kinds of L2TP
>>    control messages.
>>
>>
>>
>>
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> The IETF Secretariat
>
> _______________________________________________
> nvo3 mailing list
> nvo3@ietf.org
> https://www.ietf.org/mailman/listinfo/nvo3


From nobody Thu Apr 10 10:08:52 2014
Return-Path: <cpignata@cisco.com>
X-Original-To: l2tpext@ietfa.amsl.com
Delivered-To: l2tpext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD7751A01FF; Thu, 10 Apr 2014 10:08:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.772
X-Spam-Level: 
X-Spam-Status: No, score=-9.772 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c2mrb4JYoKP4; Thu, 10 Apr 2014 10:08:38 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) by ietfa.amsl.com (Postfix) with ESMTP id 6809B1A01DD; Thu, 10 Apr 2014 10:08:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14364; q=dns/txt; s=iport; t=1397149717; x=1398359317; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=SHg+aigfhgEXofSf/S+USB7RkxUI0hdJV7VGrp/GmkM=; b=aw4mK62M7N0fWwxHPD9cnPcQBCCADABHb6XpDHB8M9J1ZmMLVm+gWLa2 0c/ZQE5iiFVe7iANSW0h2kKijSj3ENgxkibkMSe5cELimx1kH99uJ4bLd dwU2hRWGsZwfw4Llc0pbHtv+6MRLgyx1ZzKyP8ELwwpfC52hJPptMkOfy 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkYFAM7ORlOtJA2K/2dsb2JhbABagkJEO1EGvHGHNYEjFnSCJQEBAQQBAQFrCQIMBAIBCA4DBAEBKAcnCxQJCAIEDgUJh3MIBc08F44VUwQHBgODG4EUBJRxg22BNZENgzCBakE
X-IronPort-AV: E=Sophos; i="4.97,835,1389744000"; d="scan'208,217"; a="34720988"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-2.cisco.com with ESMTP; 10 Apr 2014 17:08:36 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s3AH8aWB008806 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 10 Apr 2014 17:08:36 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.99]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0123.003; Thu, 10 Apr 2014 12:08:35 -0500
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Tom Herbert <therbert@google.com>
Thread-Topic: [nvo3] New Version Notification for draft-fan-l2tp-vp-01.txt
Thread-Index: AQHPVGwUioKZm7B370uoJbPkmsBi+JsKMc1AgAEhXoCAABbWgA==
Date: Thu, 10 Apr 2014 17:08:35 +0000
Message-ID: <1045434E-F6BE-444E-8E28-B2DCCE1B0A35@cisco.com>
References: <20140410032205.30725.83163.idtracker@ietfa.amsl.com> <C02846B1344F344EB4FAA6FA7AF481F10F3E29D0@SZXEMA502-MBS.china.huawei.com> <CA+mtBx9r75d3bkk4FeHWXjPMwfetr97rBuxWoubDsx=_Y_RZ0g@mail.gmail.com>
In-Reply-To: <CA+mtBx9r75d3bkk4FeHWXjPMwfetr97rBuxWoubDsx=_Y_RZ0g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.229.74]
Content-Type: multipart/alternative; boundary="_000_1045434EF6BE444E8E28B2DCCE1B0A35ciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/l2tpext/qzhVx-HCkCcrb662F_2Ls1hw9Qg
Cc: "l2tpext@ietf.org" <l2tpext@ietf.org>, Namgon Kim <ng.kim@kt.com>, Fanduoliang <fanduoliang@huawei.com>, "nvo3@ietf.org" <nvo3@ietf.org>, Zehn Cao <zehn.cao@gmail.com>
Subject: Re: [L2tpext] [nvo3] New Version Notification for draft-fan-l2tp-vp-01.txt
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2tpext/>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 17:08:43 -0000

--_000_1045434EF6BE444E8E28B2DCCE1B0A35ciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Frank, Tom,

Please find some additional comments inline, L2TPExt chair hat off.

On Apr 10, 2014, at 11:46 AM, Tom Herbert <therbert@google.com<mailto:therb=
ert@google.com>> wrote:

On Wed, Apr 9, 2014 at 8:37 PM, Xialiang (Frank)
<frank.xialiang@huawei.com<mailto:frank.xialiang@huawei.com>> wrote:
Hi folks,
We have updated the L2TP-VP version -01 draft.
In the new version draft, we add the motivation of this draft and modificat=
ion to the format of L2TP-VP header.
Welcome your comments and suggestions!

Hi Frank,

Thanks for posting. A few comments:

- This is so dramatically different from L2TP I wonder if it can still
honestly be called L2TP. Have you implemented this? How much of L2TP
stack can be leveraged?
- "Session ID is changed to a 31-bit field"-- doesn't this break L2TP then?

These two bullet points are critical. A "profile" of protocol is a constrai=
ned subset of it, within an applicability context. What this document shows=
 is not a profile.

The most-significant bit of the Session ID being used for something else ("=
Modified bit") has two implications:

  1.  This is not a profile, it's an attempt to redefine L2TPv3.
  2.  This non-profile draft describes a non-backwards compatible protocol.=
 Meaning, L2TPv3's Session ID allows for Session IDs with the MSB set. Cons=
equently, a packet cannot be differentiated between L2TPv3 and this other p=
rotocol (which is not a profile).
  3.  It breaks L2TPv3.

OK, I lied, three (or possibly more) implications :-)

The remaining points are subordinate to this high-order bit (no pun intende=
d).

- "Type field"-- I suspect this is meant to be an EtherType value.
Please be explicit about this.
- To get hashing (for ECMP, RSS, etc.) in the network we'd almost
certainly use L2TP over UDP, so L2TP-VP should probably have a format
defined for use with UDP.

There's also hashing for L2TPv3 directly over IP (e.g., RFC 5640)

Thanks,

Carlos.

- Even with Type field, this still suffers from the same problem L2TP
has that network devices won't be able to parse the packet beyond the
L2TP header (the cookie field makes the header variable length). This
eliminates the ability to implement the protocol with LRO for
instance. I suggest you take four or five bits from reserved section
for header length to resolve this (see example in GUE).
- Cookie mechanism is an advantage over VXLAN and nvgre I believe, but
why limit it to 32 bits? 64 bits is much stronger, and at some point
we might even want 128 bits to do strong authentication.

Some more general questions applicable to this and some other proposals.

- "TNI field"-- this seems to use the same 24 bit left shifted format
of nvgre and VXLAN. I still don't see the rationale for this! Why
can't the full 32 bit field be allocated for vni? A large deployment
will be using various levels of hierarchical allocation and possibly
obfuscation of vni (TNI). The nvo3 requirements on this are vague
("100's of thousands of virtual networks"), but they clearly don't
expect this the VNI to be a simple flat space either.
- "Outer Ethernet Header"-- showing the outer Ethernet header in L3
encapsulations examples is not necessary, use of Ethernet is not a
requirement, and this is potentially very misleading. For instance,
the outer Ethernet FCS does *not* protect the packet end to end in an
L3 routed network. Personally, I think it would be more illustrative
to show the IP packet in the inner Ethernet frame instead to see how
its alignment is affected.

Thanks,
Tom

B.R.
Frank

-----Original Message-----
From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> [mailto:int=
ernet-drafts@ietf.org]
Sent: Thursday, April 10, 2014 11:22 AM
To: Xialiang (Frank); Zhen Cao; Fanduoliang; Zehn Cao; Namgon Kim; Namgon
Kim; Fanduoliang; Xialiang (Frank)
Subject: New Version Notification for draft-fan-l2tp-vp-01.txt


A new version of I-D, draft-fan-l2tp-vp-01.txt has been successfully submit=
ted
by Liang Xia and posted to the IETF repository.

Name:         draft-fan-l2tp-vp
Revision:     01
Title:                L2TP-VP: Layer Two Tunneling Protocol - Virtualizatio=
n Profile
Document date:        2014-04-10
Group:                Individual Submission
Pages:                9
URL:
http://www.ietf.org/internet-drafts/draft-fan-l2tp-vp-01.txt
Status:         https://datatracker.ietf.org/doc/draft-fan-l2tp-vp/
Htmlized:       http://tools.ietf.org/html/draft-fan-l2tp-vp-01
Diff:           http://www.ietf.org/rfcdiff?url2=3Ddraft-fan-l2tp-vp-01

Abstract:
  This document describes Layer Two Tunneling Protocol (L2TP)'s
  virtualization profile (L2TP-VP), which reuses session header of L2TP
  data message to securely support overlay networks for multiple
  tenants, and simplifies tunnel setup by disabling all kinds of L2TP
  control messages.




Please note that it may take a couple of minutes from the time of submissio=
n
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

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

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


--_000_1045434EF6BE444E8E28B2DCCE1B0A35ciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <2FA0CDE0E014D640A5B60B9B7B2144F8@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;">
Frank, Tom,
<div><br>
</div>
<div>Please find some additional comments inline, L2TPExt chair hat off.
<div><br>
<div>
<div>On Apr 10, 2014, at 11:46 AM, Tom Herbert &lt;<a href=3D"mailto:therbe=
rt@google.com">therbert@google.com</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div style=3D"font-size: 12px; font-style: normal; font-variant: normal; fo=
nt-weight: normal; letter-spacing: normal; line-height: normal; orphans: au=
to; text-align: start; text-indent: 0px; text-transform: none; white-space:=
 normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
On Wed, Apr 9, 2014 at 8:37 PM, Xialiang (Frank)<br>
&lt;<a href=3D"mailto:frank.xialiang@huawei.com">frank.xialiang@huawei.com<=
/a>&gt; wrote:<br>
<blockquote type=3D"cite">Hi folks,<br>
We have updated the L2TP-VP version -01 draft.<br>
In the new version draft, we add the motivation of this draft and modificat=
ion to the format of L2TP-VP header.<br>
Welcome your comments and suggestions!<br>
<br>
</blockquote>
Hi Frank,<br>
<br>
Thanks for posting. A few comments:<br>
<br>
- This is so dramatically different from L2TP I wonder if it can still<br>
honestly be called L2TP. Have you implemented this? How much of L2TP<br>
stack can be leveraged?<br>
- &quot;Session ID is changed to a 31-bit field&quot;-- doesn't this break =
L2TP then?<br>
</div>
</blockquote>
<div><br>
</div>
<div>These two bullet points are critical. A &quot;profile&quot; of protoco=
l is a constrained subset of it, within an applicability context. What this=
 document shows is not a profile.&nbsp;</div>
<div><br>
</div>
<div>The most-significant bit of the Session ID being used for something el=
se (&quot;Modified bit&quot;) has two implications:</div>
<div>
<ol>
<li>This is not a profile, it's an attempt to redefine L2TPv3.</li><li>This=
 non-profile draft describes a non-backwards compatible protocol. Meaning, =
L2TPv3's Session ID allows for Session IDs with the MSB set. Consequently, =
a packet cannot be differentiated between L2TPv3 and this other protocol (w=
hich is not a profile).</li><li>It breaks L2TPv3.</li></ol>
</div>
<div>OK, I lied, three (or possibly more) implications :-)</div>
<div><br>
</div>
<div>The remaining points are subordinate to this high-order bit (no pun in=
tended).</div>
<br>
<blockquote type=3D"cite">
<div style=3D"font-size: 12px; font-style: normal; font-variant: normal; fo=
nt-weight: normal; letter-spacing: normal; line-height: normal; orphans: au=
to; text-align: start; text-indent: 0px; text-transform: none; white-space:=
 normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
- &quot;Type field&quot;-- I suspect this is meant to be an EtherType value=
.<br>
Please be explicit about this.<br>
- To get hashing (for ECMP, RSS, etc.) in the network we'd almost<br>
certainly use L2TP over UDP, so L2TP-VP should probably have a format<br>
defined for use with UDP.<br>
</div>
</blockquote>
<div><br>
</div>
<div>There's also hashing for L2TPv3 directly over IP (e.g., RFC&nbsp;5640)=
</div>
<div><br>
</div>
<div>Thanks,</div>
<div><br>
</div>
<div>Carlos.</div>
<br>
<blockquote type=3D"cite">
<div style=3D"font-size: 12px; font-style: normal; font-variant: normal; fo=
nt-weight: normal; letter-spacing: normal; line-height: normal; orphans: au=
to; text-align: start; text-indent: 0px; text-transform: none; white-space:=
 normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
- Even with Type field, this still suffers from the same problem L2TP<br>
has that network devices won't be able to parse the packet beyond the<br>
L2TP header (the cookie field makes the header variable length). This<br>
eliminates the ability to implement the protocol with LRO for<br>
instance. I suggest you take four or five bits from reserved section<br>
for header length to resolve this (see example in GUE).<br>
- Cookie mechanism is an advantage over VXLAN and nvgre I believe, but<br>
why limit it to 32 bits? 64 bits is much stronger, and at some point<br>
we might even want 128 bits to do strong authentication.<br>
<br>
Some more general questions applicable to this and some other proposals.<br=
>
<br>
- &quot;TNI field&quot;-- this seems to use the same 24 bit left shifted fo=
rmat<br>
of nvgre and VXLAN. I still don't see the rationale for this! Why<br>
can't the full 32 bit field be allocated for vni? A large deployment<br>
will be using various levels of hierarchical allocation and possibly<br>
obfuscation of vni (TNI). The nvo3 requirements on this are vague<br>
(&quot;100's of thousands of virtual networks&quot;), but they clearly don'=
t<br>
expect this the VNI to be a simple flat space either.<br>
- &quot;Outer Ethernet Header&quot;-- showing the outer Ethernet header in =
L3<br>
encapsulations examples is not necessary, use of Ethernet is not a<br>
requirement, and this is potentially very misleading. For instance,<br>
the outer Ethernet FCS does *not* protect the packet end to end in an<br>
L3 routed network. Personally, I think it would be more illustrative<br>
to show the IP packet in the inner Ethernet frame instead to see how<br>
its alignment is affected.<br>
<br>
Thanks,<br>
Tom<br>
<br>
<blockquote type=3D"cite">B.R.<br>
Frank<br>
<br>
<blockquote type=3D"cite">-----Original Message-----<br>
From: <a href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org<=
/a> [<a href=3D"mailto:internet-drafts@ietf.org">mailto:internet-drafts@iet=
f.org</a>]<br>
Sent: Thursday, April 10, 2014 11:22 AM<br>
To: Xialiang (Frank); Zhen Cao; Fanduoliang; Zehn Cao; Namgon Kim; Namgon<b=
r>
Kim; Fanduoliang; Xialiang (Frank)<br>
Subject: New Version Notification for draft-fan-l2tp-vp-01.txt<br>
<br>
<br>
A new version of I-D, draft-fan-l2tp-vp-01.txt has been successfully submit=
ted<br>
by Liang Xia and posted to the IETF repository.<br>
<br>
Name: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;draft-fan-l2tp-vp<br>
Revision: &nbsp;&nbsp;&nbsp;&nbsp;01<br>
Title: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;L2TP-VP: Layer Two Tunneling Protocol - Virtualizatio=
n Profile<br>
Document date: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2014-04-10<br>
Group: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;Individual Submission<br>
Pages: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;9<br>
URL:<br>
<a href=3D"http://www.ietf.org/internet-drafts/draft-fan-l2tp-vp-01.txt">ht=
tp://www.ietf.org/internet-drafts/draft-fan-l2tp-vp-01.txt</a><br>
Status: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;https://datatracker=
.ietf.org/doc/draft-fan-l2tp-vp/<br>
Htmlized: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;http://tools.ietf.org/html/dr=
aft-fan-l2tp-vp-01<br>
Diff: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;http://ww=
w.ietf.org/rfcdiff?url2=3Ddraft-fan-l2tp-vp-01<br>
<br>
Abstract:<br>
&nbsp;&nbsp;This document describes Layer Two Tunneling Protocol (L2TP)'s<b=
r>
&nbsp;&nbsp;virtualization profile (L2TP-VP), which reuses session header o=
f L2TP<br>
&nbsp;&nbsp;data message to securely support overlay networks for multiple<=
br>
&nbsp;&nbsp;tenants, and simplifies tunnel setup by disabling all kinds of =
L2TP<br>
&nbsp;&nbsp;control messages.<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at tools.ietf.org.<br>
<br>
The IETF Secretariat<br>
</blockquote>
<br>
_______________________________________________<br>
nvo3 mailing list<br>
<a href=3D"mailto:nvo3@ietf.org">nvo3@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/nvo3">https://www.ietf.org=
/mailman/listinfo/nvo3</a><br>
</blockquote>
<br>
_______________________________________________<br>
nvo3 mailing list<br>
<a href=3D"mailto:nvo3@ietf.org">nvo3@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/nvo3">https://www.ietf.org=
/mailman/listinfo/nvo3</a></div>
</blockquote>
</div>
<br>
</div>
</div>
</body>
</html>

--_000_1045434EF6BE444E8E28B2DCCE1B0A35ciscocom_--


From nobody Thu Apr 10 11:23:25 2014
Return-Path: <therbert@google.com>
X-Original-To: l2tpext@ietfa.amsl.com
Delivered-To: l2tpext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF5F71A02BE for <l2tpext@ietfa.amsl.com>; Thu, 10 Apr 2014 11:23:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.651
X-Spam-Level: 
X-Spam-Status: No, score=-1.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0zxf-SpbmtUh for <l2tpext@ietfa.amsl.com>; Thu, 10 Apr 2014 11:23:21 -0700 (PDT)
Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 4A7C81A02BC for <l2tpext@ietf.org>; Thu, 10 Apr 2014 11:23:21 -0700 (PDT)
Received: by mail-ie0-f178.google.com with SMTP id lx4so4162817iec.23 for <l2tpext@ietf.org>; Thu, 10 Apr 2014 11:23:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MaVrkqOdUawXk4QQ0Zi8mVTR9PhsBowOwg0N+LD+5qM=; b=Tu8us2r9YllrtG70x4kkPStmhG1aLTzkGbgmR/jYGnNP7xh66bHXJEaowtLCAvz3qX JHB/DQ4UmhKc1esu4Ud8eE3DEG14gV/DN5BF0OWQ7JFJGeM2t0Uv0bTpukNEr7D+9KDm QC6x1zDn+2M4fH07jg8mJMmWv4OnGR4L0BXEk8iTVA+hjw0n/b4SCpriqkbIPShiaGsB mJfmAQ7ZnMafcxa/a0oiKTQcmd6yS0qL5TJacNea+1QKHhzzktKcRXgwFOhrzE5IA9KA YQR1Es1+PwZqOaSzrCDARGyJNHeQKNQ+nxHxmWE8PWOn5UNzUGv0RsJM4/ooN3ithkhW euXA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=MaVrkqOdUawXk4QQ0Zi8mVTR9PhsBowOwg0N+LD+5qM=; b=ALMe2R2QYjt1Xx1eFQF/cAxomi77I9VAeUvU2gESF589aS2cTZkWtnuSlq4q3MrUf3 ATgsVl8V8CvDJxfkcSHoWgLv0ApRP3e2xcocbAF5UPhpV/8yRYTLLJ38BwaReGysV+Tk fPV+skHd5Z91+xRrSM7pj7S29M8CG08xele+OB2oQZ2n2UQhc1eCesRFUlEmLh043xJ8 X8mXKYgR7rwfu+dpiBmUAZQvAkNhCYUbdU+Te9eBaFIr9IPw2zlAI5B0oMYrTEmcXrWE 9KRhbo5nUma5YSJwfGRUd9sY6DEWQdsiun28d1HN4lMzDbCQaU77R7yeKSpX5b+2qFTN eXEg==
X-Gm-Message-State: ALoCoQnRTYxGWJa6HH3ZHKjIxduKRCM1QWou2T55RPA9LHnt7n2wEplYtx/TDezS9ZFvWE6mBAXf2vQhkY5h4m019z/fmceyIQqF4DKMAqZoEdAYq0reA7KSH3D2a5bxYFw+bwoSRo18ow1ogYuGqjaiTqwQhLNnYJR84gFCxHFPft37VoU/1OB3t1c3cm8FnkHRzKQIvpCm
MIME-Version: 1.0
X-Received: by 10.43.151.7 with SMTP id kq7mr2723246icc.78.1397154200155; Thu, 10 Apr 2014 11:23:20 -0700 (PDT)
Received: by 10.64.148.98 with HTTP; Thu, 10 Apr 2014 11:23:20 -0700 (PDT)
In-Reply-To: <1045434E-F6BE-444E-8E28-B2DCCE1B0A35@cisco.com>
References: <20140410032205.30725.83163.idtracker@ietfa.amsl.com> <C02846B1344F344EB4FAA6FA7AF481F10F3E29D0@SZXEMA502-MBS.china.huawei.com> <CA+mtBx9r75d3bkk4FeHWXjPMwfetr97rBuxWoubDsx=_Y_RZ0g@mail.gmail.com> <1045434E-F6BE-444E-8E28-B2DCCE1B0A35@cisco.com>
Date: Thu, 10 Apr 2014 11:23:20 -0700
Message-ID: <CA+mtBx9480QZV-+FByVi2yF9dnGQDAFau8-Xak-vD+wuZjmTOQ@mail.gmail.com>
From: Tom Herbert <therbert@google.com>
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/l2tpext/syN0fdTwsu2qTdUa-QoXrotQbf4
Cc: "l2tpext@ietf.org" <l2tpext@ietf.org>, Namgon Kim <ng.kim@kt.com>, Fanduoliang <fanduoliang@huawei.com>, "nvo3@ietf.org" <nvo3@ietf.org>, Zehn Cao <zehn.cao@gmail.com>
Subject: Re: [L2tpext] [nvo3] New Version Notification for draft-fan-l2tp-vp-01.txt
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2tpext/>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 18:23:23 -0000

> - To get hashing (for ECMP, RSS, etc.) in the network we'd almost
> certainly use L2TP over UDP, so L2TP-VP should probably have a format
> defined for use with UDP.
>
>
> There's also hashing for L2TPv3 directly over IP (e.g., RFC 5640)
>
Unfortunately to use that I'd need to replace all my hardware to
support it, and even if we did that the second we start putting L2TP
in IPsec we're right back to not having the hash. Same thinking
applies to GRE and it's use of key field for hash. I suppose it's not
by design, but UDP encap will likely be the de facto standard in the
data center-- it's not really that bad just a few bytes of overhead
buys us compatibility with a lot of devices. There's some pesky issues
to resolve, like whether UDP checksum is worthwhile and how to
interact with NAT, but if we do this right we should be a able to
provide a solution for all IP protocols (e.g.
http://tools.ietf.org/html/draft-herbert-gue-01 :-) )

Tom

> Thanks,
>
> Carlos.
>
> - Even with Type field, this still suffers from the same problem L2TP
> has that network devices won't be able to parse the packet beyond the
> L2TP header (the cookie field makes the header variable length). This
> eliminates the ability to implement the protocol with LRO for
> instance. I suggest you take four or five bits from reserved section
> for header length to resolve this (see example in GUE).
> - Cookie mechanism is an advantage over VXLAN and nvgre I believe, but
> why limit it to 32 bits? 64 bits is much stronger, and at some point
> we might even want 128 bits to do strong authentication.
>
> Some more general questions applicable to this and some other proposals.
>
> - "TNI field"-- this seems to use the same 24 bit left shifted format
> of nvgre and VXLAN. I still don't see the rationale for this! Why
> can't the full 32 bit field be allocated for vni? A large deployment
> will be using various levels of hierarchical allocation and possibly
> obfuscation of vni (TNI). The nvo3 requirements on this are vague
> ("100's of thousands of virtual networks"), but they clearly don't
> expect this the VNI to be a simple flat space either.
> - "Outer Ethernet Header"-- showing the outer Ethernet header in L3
> encapsulations examples is not necessary, use of Ethernet is not a
> requirement, and this is potentially very misleading. For instance,
> the outer Ethernet FCS does *not* protect the packet end to end in an
> L3 routed network. Personally, I think it would be more illustrative
> to show the IP packet in the inner Ethernet frame instead to see how
> its alignment is affected.
>
> Thanks,
> Tom
>
> B.R.
> Frank
>
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Thursday, April 10, 2014 11:22 AM
> To: Xialiang (Frank); Zhen Cao; Fanduoliang; Zehn Cao; Namgon Kim; Namgon
> Kim; Fanduoliang; Xialiang (Frank)
> Subject: New Version Notification for draft-fan-l2tp-vp-01.txt
>
>
> A new version of I-D, draft-fan-l2tp-vp-01.txt has been successfully
> submitted
> by Liang Xia and posted to the IETF repository.
>
> Name:         draft-fan-l2tp-vp
> Revision:     01
> Title:                L2TP-VP: Layer Two Tunneling Protocol - Virtualization
> Profile
> Document date:        2014-04-10
> Group:                Individual Submission
> Pages:                9
> URL:
> http://www.ietf.org/internet-drafts/draft-fan-l2tp-vp-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-fan-l2tp-vp/
> Htmlized:       http://tools.ietf.org/html/draft-fan-l2tp-vp-01
> Diff:           http://www.ietf.org/rfcdiff?url2=draft-fan-l2tp-vp-01
>
> Abstract:
>   This document describes Layer Two Tunneling Protocol (L2TP)'s
>   virtualization profile (L2TP-VP), which reuses session header of L2TP
>   data message to securely support overlay networks for multiple
>   tenants, and simplifies tunnel setup by disabling all kinds of L2TP
>   control messages.
>
>
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>
> _______________________________________________
> nvo3 mailing list
> nvo3@ietf.org
> https://www.ietf.org/mailman/listinfo/nvo3
>
>
> _______________________________________________
> nvo3 mailing list
> nvo3@ietf.org
> https://www.ietf.org/mailman/listinfo/nvo3
>
>


From nobody Thu Apr 10 11:34:53 2014
Return-Path: <cpignata@cisco.com>
X-Original-To: l2tpext@ietfa.amsl.com
Delivered-To: l2tpext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B29351A0414; Thu, 10 Apr 2014 11:34:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.773
X-Spam-Level: 
X-Spam-Status: No, score=-9.773 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hdDAGoFZ7xng; Thu, 10 Apr 2014 11:34:46 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) by ietfa.amsl.com (Postfix) with ESMTP id 0B3451A02EB; Thu, 10 Apr 2014 11:34:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5515; q=dns/txt; s=iport; t=1397154878; x=1398364478; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=f7tlGT4YB3myYK3D3i7JVmx/h44PkkX+MFfZay2FPi8=; b=gSs0FWc7rmNL3HLLlImrHdyWvw99c6wJ6RM2on+QCgtBAUfn8miFxhDP Sw0/uc5c81Ab0f4//Vnbx08uQcHCKf/svE4XhNEoVj9jwc3wwN0QbULtA keBbt6KqozmNcGcO7tviBZ52JakyuIKCH4FdnuwniyUGRZB8rsqfDqtFz w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkYFALDjRlOtJA2G/2dsb2JhbABagwY7UQa8c4ZkUYEkFnSCJQEBAQQBAQFrCQIMBAIBCA4DAwEBASgHIQYLFAkIAgQOBQkSh00DEQgFxioNhmMXjFOBQlcHBoQyBJZwgW6BNYs+hU+DMIFqQQ
X-IronPort-AV: E=Sophos;i="4.97,835,1389744000"; d="scan'208";a="34750840"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-7.cisco.com with ESMTP; 10 Apr 2014 18:34:37 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id s3AIYbZC026506 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 10 Apr 2014 18:34:37 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.99]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.03.0123.003; Thu, 10 Apr 2014 13:34:37 -0500
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Tom Herbert <therbert@google.com>
Thread-Topic: [L2tpext] [nvo3] New Version Notification for draft-fan-l2tp-vp-01.txt
Thread-Index: AQHPVOuGHQ6nAlR090S5GdtDr4vZ5A==
Date: Thu, 10 Apr 2014 18:34:37 +0000
Message-ID: <CF6C5B3D.52433%cpignata@cisco.com>
References: <20140410032205.30725.83163.idtracker@ietfa.amsl.com> <C02846B1344F344EB4FAA6FA7AF481F10F3E29D0@SZXEMA502-MBS.china.huawei.com> <CA+mtBx9r75d3bkk4FeHWXjPMwfetr97rBuxWoubDsx=_Y_RZ0g@mail.gmail.com> <1045434E-F6BE-444E-8E28-B2DCCE1B0A35@cisco.com> <CA+mtBx9480QZV-+FByVi2yF9dnGQDAFau8-Xak-vD+wuZjmTOQ@mail.gmail.com>
In-Reply-To: <CA+mtBx9480QZV-+FByVi2yF9dnGQDAFau8-Xak-vD+wuZjmTOQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.1.140326
x-originating-ip: [10.82.229.74]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <968640D2C5013A4CA8B2BDCAD5422D50@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/l2tpext/9n5Y6CdVk6sQpgzXe4DYhAiymqs
Cc: Fanduoliang <fanduoliang@huawei.com>, Zehn Cao <zehn.cao@gmail.com>, "nvo3@ietf.org" <nvo3@ietf.org>, "l2tpext@ietf.org" <l2tpext@ietf.org>, Namgon Kim <ng.kim@kt.com>
Subject: Re: [L2tpext] [nvo3] New Version Notification for draft-fan-l2tp-vp-01.txt
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2tpext/>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 18:34:50 -0000

Hi, Tom,

-----Original Message-----
From: Tom Herbert <therbert@google.com>
Date: Thursday, April 10, 2014 at 2:23 PM
To: Carlos Pignataro <cpignata@cisco.com>
Cc: "l2tpext@ietf.org" <l2tpext@ietf.org>, Namgon Kim <ng.kim@kt.com>,
Fanduoliang <fanduoliang@huawei.com>, "nvo3@ietf.org" <nvo3@ietf.org>,
Zehn Cao <zehn.cao@gmail.com>
Subject: Re: [L2tpext] [nvo3] New Version Notification
for	draft-fan-l2tp-vp-01.txt

>> - To get hashing (for ECMP, RSS, etc.) in the network we'd almost
>> certainly use L2TP over UDP, so L2TP-VP should probably have a format
>> defined for use with UDP.
>>
>>
>> There's also hashing for L2TPv3 directly over IP (e.g., RFC 5640)
>>
>Unfortunately to use that I'd need to replace all my hardware to
>support it, and even if we did that the second we start putting L2TP
>in IPsec we're right back to not having the hash. Same thinking
>applies to GRE and it's use of key field for hash. I suppose it's not
>by design, but UDP encap will likely be the de facto standard in the
>data center-- it's not really that bad just a few bytes of overhead
>buys us compatibility with a lot of devices. There's some pesky issues
>to resolve, like whether UDP checksum is worthwhile and how to
>interact with NAT, but if we do this right we should be a able to
>provide a solution for all IP protocols (e.g.
>http://tools.ietf.org/html/draft-herbert-gue-01 :-) )

This is a larger topic, and certainly there have been many Foo-over-UDP
and generic-UDP-tunnel/encap proposals out there.

Without rat-holing, my point was only that there=B9s specs for ECMP for
L2TPv3/GRE directly over IP, and also (agreeing with you here) you can run
L2TPv3 over UDP.

Thanks,

=8B Carlos.

>
>Tom
>
>> Thanks,
>>
>> Carlos.
>>
>> - Even with Type field, this still suffers from the same problem L2TP
>> has that network devices won't be able to parse the packet beyond the
>> L2TP header (the cookie field makes the header variable length). This
>> eliminates the ability to implement the protocol with LRO for
>> instance. I suggest you take four or five bits from reserved section
>> for header length to resolve this (see example in GUE).
>> - Cookie mechanism is an advantage over VXLAN and nvgre I believe, but
>> why limit it to 32 bits? 64 bits is much stronger, and at some point
>> we might even want 128 bits to do strong authentication.
>>
>> Some more general questions applicable to this and some other proposals.
>>
>> - "TNI field"-- this seems to use the same 24 bit left shifted format
>> of nvgre and VXLAN. I still don't see the rationale for this! Why
>> can't the full 32 bit field be allocated for vni? A large deployment
>> will be using various levels of hierarchical allocation and possibly
>> obfuscation of vni (TNI). The nvo3 requirements on this are vague
>> ("100's of thousands of virtual networks"), but they clearly don't
>> expect this the VNI to be a simple flat space either.
>> - "Outer Ethernet Header"-- showing the outer Ethernet header in L3
>> encapsulations examples is not necessary, use of Ethernet is not a
>> requirement, and this is potentially very misleading. For instance,
>> the outer Ethernet FCS does *not* protect the packet end to end in an
>> L3 routed network. Personally, I think it would be more illustrative
>> to show the IP packet in the inner Ethernet frame instead to see how
>> its alignment is affected.
>>
>> Thanks,
>> Tom
>>
>> B.R.
>> Frank
>>
>> -----Original Message-----
>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>> Sent: Thursday, April 10, 2014 11:22 AM
>> To: Xialiang (Frank); Zhen Cao; Fanduoliang; Zehn Cao; Namgon Kim;
>>Namgon
>> Kim; Fanduoliang; Xialiang (Frank)
>> Subject: New Version Notification for draft-fan-l2tp-vp-01.txt
>>
>>
>> A new version of I-D, draft-fan-l2tp-vp-01.txt has been successfully
>> submitted
>> by Liang Xia and posted to the IETF repository.
>>
>> Name:         draft-fan-l2tp-vp
>> Revision:     01
>> Title:                L2TP-VP: Layer Two Tunneling Protocol -
>>Virtualization
>> Profile
>> Document date:        2014-04-10
>> Group:                Individual Submission
>> Pages:                9
>> URL:
>> http://www.ietf.org/internet-drafts/draft-fan-l2tp-vp-01.txt
>> Status:         https://datatracker.ietf.org/doc/draft-fan-l2tp-vp/
>> Htmlized:       http://tools.ietf.org/html/draft-fan-l2tp-vp-01
>> Diff:           http://www.ietf.org/rfcdiff?url2=3Ddraft-fan-l2tp-vp-01
>>
>> Abstract:
>>   This document describes Layer Two Tunneling Protocol (L2TP)'s
>>   virtualization profile (L2TP-VP), which reuses session header of L2TP
>>   data message to securely support overlay networks for multiple
>>   tenants, and simplifies tunnel setup by disabling all kinds of L2TP
>>   control messages.
>>
>>
>>
>>
>> Please note that it may take a couple of minutes from the time of
>>submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> The IETF Secretariat
>>
>>
>> _______________________________________________
>> nvo3 mailing list
>> nvo3@ietf.org
>> https://www.ietf.org/mailman/listinfo/nvo3
>>
>>
>> _______________________________________________
>> nvo3 mailing list
>> nvo3@ietf.org
>> https://www.ietf.org/mailman/listinfo/nvo3
>>
>>
>
>_______________________________________________
>L2tpext mailing list
>L2tpext@ietf.org
>https://www.ietf.org/mailman/listinfo/l2tpext


From nobody Thu Apr 10 11:53:31 2014
Return-Path: <therbert@google.com>
X-Original-To: l2tpext@ietfa.amsl.com
Delivered-To: l2tpext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C80B41A029C for <l2tpext@ietfa.amsl.com>; Thu, 10 Apr 2014 11:53:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.651
X-Spam-Level: 
X-Spam-Status: No, score=-1.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bos80n39bEcX for <l2tpext@ietfa.amsl.com>; Thu, 10 Apr 2014 11:53:28 -0700 (PDT)
Received: from mail-ig0-x22b.google.com (mail-ig0-x22b.google.com [IPv6:2607:f8b0:4001:c05::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 5D0971A0303 for <l2tpext@ietf.org>; Thu, 10 Apr 2014 11:53:28 -0700 (PDT)
Received: by mail-ig0-f171.google.com with SMTP id c1so8203962igq.10 for <l2tpext@ietf.org>; Thu, 10 Apr 2014 11:53:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=6lj5cSaAfwTnLAlSeeefQ4k6jiIBkh9DmIFcfuRO5b8=; b=JqRWFcTQ/XcVjaGSxim9OYL3Z9uEFEFijccjg/MLZtgsay5dDovB/DwlFFcMfKdb63 07f5F8MS2T9h23XdhKOdCN+h31Oc11cxurAJE5KNm0xjyAPZ+UiBDw2oYOI28yDl2UcI TzUEmDkBAFpx+h3DMg9WowzVDBk2uecAX3lcNrRwrU6lepxdcytO3J0WSZDn2i07qFA5 u5eul7nQ1pv/ssOlRRVy69FeIjkbyhAND5+u/sRwNhgu0P5Qpwgk9OWlUk1iXar1lwkr G+M3glCxs2OxuxKjEPqqKrfZWGMIt2dOQ3cQv3k17yLcwn2eVudhQ8jP0GeiIfjSMVfI Km5g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=6lj5cSaAfwTnLAlSeeefQ4k6jiIBkh9DmIFcfuRO5b8=; b=ZGxhPxlzvFL5hzO6pS44eHEvgj1Im0luLsMHOEhc0C67Cj0/28x52vXcRH8YKxNOLs /L1/5CvwpgbJfTVDpqPwC+8tbh+bMRTyPNRccb3/DgdCt4qpX9EjxQZPWncysr7+WjgM NsLWKTuJDtD23ULeCX4PsREd3Mw3MbO0bO+/dM5sJ79ARBVJpOG+XVTyFOYlZMR59/xo ilVV3G62FXn1aNTrnxi0rzecjOy8wUC2T8RvSxqWJUUjiRG6PuHmBsxA/5MI2r9kkIYU tOLl8eVSDreeeoWHD51vnl6T24nwL8d0+U5wh6gWDyzi+tGE7os0Crg9aJFFtw6wf42L mrKg==
X-Gm-Message-State: ALoCoQmuQFygqGA9v49zXV6HE4HPCTPGKSDCZK4OlMNHxrbN1CyN6/ZMKYoCZfHIHFkeyDeHSWPbM0B+na4rN9LH+4Cb7YwuCHi9zOCp3N7Ns9IQTHgP+TrsgqBxVG8unNHryXx+vDHfZSJGlaz10psYRm1gPUN80JbyORhtiROckzhq7+K/DDZczFBbHfPQaHAmT2Ioyl7c
MIME-Version: 1.0
X-Received: by 10.50.43.225 with SMTP id z1mr12468352igl.29.1397156007254; Thu, 10 Apr 2014 11:53:27 -0700 (PDT)
Received: by 10.64.148.98 with HTTP; Thu, 10 Apr 2014 11:53:27 -0700 (PDT)
In-Reply-To: <CF6C5B3D.52433%cpignata@cisco.com>
References: <20140410032205.30725.83163.idtracker@ietfa.amsl.com> <C02846B1344F344EB4FAA6FA7AF481F10F3E29D0@SZXEMA502-MBS.china.huawei.com> <CA+mtBx9r75d3bkk4FeHWXjPMwfetr97rBuxWoubDsx=_Y_RZ0g@mail.gmail.com> <1045434E-F6BE-444E-8E28-B2DCCE1B0A35@cisco.com> <CA+mtBx9480QZV-+FByVi2yF9dnGQDAFau8-Xak-vD+wuZjmTOQ@mail.gmail.com> <CF6C5B3D.52433%cpignata@cisco.com>
Date: Thu, 10 Apr 2014 11:53:27 -0700
Message-ID: <CA+mtBx98h3tA7aErjdQwnDhhcjpV6=ELXr-0DpOaaMvxpySbwg@mail.gmail.com>
From: Tom Herbert <therbert@google.com>
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/l2tpext/x9dV8PoC-dGMHCghhTDuA0u47xE
Cc: Fanduoliang <fanduoliang@huawei.com>, Zehn Cao <zehn.cao@gmail.com>, "nvo3@ietf.org" <nvo3@ietf.org>, "l2tpext@ietf.org" <l2tpext@ietf.org>, Namgon Kim <ng.kim@kt.com>
Subject: Re: [L2tpext] [nvo3] New Version Notification for draft-fan-l2tp-vp-01.txt
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2tpext/>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 18:53:29 -0000

> This is a larger topic, and certainly there have been many Foo-over-UDP
> and generic-UDP-tunnel/encap proposals out there.
>
Yes, I'm aware of those. But I think that the fact that many
Foo-over-UDP seem to require more than just encapsulating the basic
format might be problematic and is requiring us to considering each
protocol individually. For instance, looking at RFC 3931 there's a
different L2TP header format for L2TP/UDP than L2TP/IP. L2TP-VP could
work in UDP case by setting a version number and converting reserved
field to type and using some other bits for header length as I
described. Unfortunately, this doesn't work in the non-UDP case so it
still wouldn't be L2TP...

> Without rat-holing, my point was only that there=C2=B9s specs for ECMP fo=
r
> L2TPv3/GRE directly over IP, and also (agreeing with you here) you can ru=
n
> L2TPv3 over UDP.
>
> Thanks,
>
> =E2=80=B9 Carlos.
>
>>
>>Tom
>>
>>> Thanks,
>>>
>>> Carlos.
>>>
>>> - Even with Type field, this still suffers from the same problem L2TP
>>> has that network devices won't be able to parse the packet beyond the
>>> L2TP header (the cookie field makes the header variable length). This
>>> eliminates the ability to implement the protocol with LRO for
>>> instance. I suggest you take four or five bits from reserved section
>>> for header length to resolve this (see example in GUE).
>>> - Cookie mechanism is an advantage over VXLAN and nvgre I believe, but
>>> why limit it to 32 bits? 64 bits is much stronger, and at some point
>>> we might even want 128 bits to do strong authentication.
>>>
>>> Some more general questions applicable to this and some other proposals=
.
>>>
>>> - "TNI field"-- this seems to use the same 24 bit left shifted format
>>> of nvgre and VXLAN. I still don't see the rationale for this! Why
>>> can't the full 32 bit field be allocated for vni? A large deployment
>>> will be using various levels of hierarchical allocation and possibly
>>> obfuscation of vni (TNI). The nvo3 requirements on this are vague
>>> ("100's of thousands of virtual networks"), but they clearly don't
>>> expect this the VNI to be a simple flat space either.
>>> - "Outer Ethernet Header"-- showing the outer Ethernet header in L3
>>> encapsulations examples is not necessary, use of Ethernet is not a
>>> requirement, and this is potentially very misleading. For instance,
>>> the outer Ethernet FCS does *not* protect the packet end to end in an
>>> L3 routed network. Personally, I think it would be more illustrative
>>> to show the IP packet in the inner Ethernet frame instead to see how
>>> its alignment is affected.
>>>
>>> Thanks,
>>> Tom
>>>
>>> B.R.
>>> Frank
>>>
>>> -----Original Message-----
>>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>>> Sent: Thursday, April 10, 2014 11:22 AM
>>> To: Xialiang (Frank); Zhen Cao; Fanduoliang; Zehn Cao; Namgon Kim;
>>>Namgon
>>> Kim; Fanduoliang; Xialiang (Frank)
>>> Subject: New Version Notification for draft-fan-l2tp-vp-01.txt
>>>
>>>
>>> A new version of I-D, draft-fan-l2tp-vp-01.txt has been successfully
>>> submitted
>>> by Liang Xia and posted to the IETF repository.
>>>
>>> Name:         draft-fan-l2tp-vp
>>> Revision:     01
>>> Title:                L2TP-VP: Layer Two Tunneling Protocol -
>>>Virtualization
>>> Profile
>>> Document date:        2014-04-10
>>> Group:                Individual Submission
>>> Pages:                9
>>> URL:
>>> http://www.ietf.org/internet-drafts/draft-fan-l2tp-vp-01.txt
>>> Status:         https://datatracker.ietf.org/doc/draft-fan-l2tp-vp/
>>> Htmlized:       http://tools.ietf.org/html/draft-fan-l2tp-vp-01
>>> Diff:           http://www.ietf.org/rfcdiff?url2=3Ddraft-fan-l2tp-vp-01
>>>
>>> Abstract:
>>>   This document describes Layer Two Tunneling Protocol (L2TP)'s
>>>   virtualization profile (L2TP-VP), which reuses session header of L2TP
>>>   data message to securely support overlay networks for multiple
>>>   tenants, and simplifies tunnel setup by disabling all kinds of L2TP
>>>   control messages.
>>>
>>>
>>>
>>>
>>> Please note that it may take a couple of minutes from the time of
>>>submission
>>> until the htmlized version and diff are available at tools.ietf.org.
>>>
>>> The IETF Secretariat
>>>
>>>
>>> _______________________________________________
>>> nvo3 mailing list
>>> nvo3@ietf.org
>>> https://www.ietf.org/mailman/listinfo/nvo3
>>>
>>>
>>> _______________________________________________
>>> nvo3 mailing list
>>> nvo3@ietf.org
>>> https://www.ietf.org/mailman/listinfo/nvo3
>>>
>>>
>>
>>_______________________________________________
>>L2tpext mailing list
>>L2tpext@ietf.org
>>https://www.ietf.org/mailman/listinfo/l2tpext
>


From nobody Fri Apr 11 02:32:19 2014
Return-Path: <frank.xialiang@huawei.com>
X-Original-To: l2tpext@ietfa.amsl.com
Delivered-To: l2tpext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8519F1A0484; Fri, 11 Apr 2014 02:32:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.472
X-Spam-Level: 
X-Spam-Status: No, score=-4.472 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KjbID5ElNadR; Fri, 11 Apr 2014 02:32:12 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6A5021A031A; Fri, 11 Apr 2014 02:32:10 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BCZ42136; Fri, 11 Apr 2014 09:32:08 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 11 Apr 2014 10:30:59 +0100
Received: from SZXEMA410-HUB.china.huawei.com (10.82.72.42) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 11 Apr 2014 10:32:07 +0100
Received: from SZXEMA502-MBS.china.huawei.com ([169.254.4.203]) by SZXEMA410-HUB.china.huawei.com ([10.82.72.42]) with mapi id 14.03.0158.001; Fri, 11 Apr 2014 17:31:58 +0800
From: "Xialiang (Frank)" <frank.xialiang@huawei.com>
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, Tom Herbert <therbert@google.com>
Thread-Topic: [nvo3] New Version Notification for draft-fan-l2tp-vp-01.txt
Thread-Index: AQHPVGwUioKZm7B370uoJbPkmsBi+JsKMc1AgABHcYCAABbRgIABlx0Q
Date: Fri, 11 Apr 2014 09:31:57 +0000
Message-ID: <C02846B1344F344EB4FAA6FA7AF481F10F3E2BF2@SZXEMA502-MBS.china.huawei.com>
References: <20140410032205.30725.83163.idtracker@ietfa.amsl.com> <C02846B1344F344EB4FAA6FA7AF481F10F3E29D0@SZXEMA502-MBS.china.huawei.com> <CA+mtBx9r75d3bkk4FeHWXjPMwfetr97rBuxWoubDsx=_Y_RZ0g@mail.gmail.com> <1045434E-F6BE-444E-8E28-B2DCCE1B0A35@cisco.com>
In-Reply-To: <1045434E-F6BE-444E-8E28-B2DCCE1B0A35@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.135.42.220]
Content-Type: multipart/alternative; boundary="_000_C02846B1344F344EB4FAA6FA7AF481F10F3E2BF2SZXEMA502MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/l2tpext/AbQ5y5lu7UmXqoBce13E1QKpnaw
Cc: Fanduoliang <fanduoliang@huawei.com>, Zehn Cao <zehn.cao@gmail.com>, "nvo3@ietf.org" <nvo3@ietf.org>, "l2tpext@ietf.org" <l2tpext@ietf.org>, Namgon Kim <ng.kim@kt.com>
Subject: Re: [L2tpext] [nvo3] New Version Notification for draft-fan-l2tp-vp-01.txt
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2tpext/>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Apr 2014 09:32:16 -0000

--_000_C02846B1344F344EB4FAA6FA7AF481F10F3E2BF2SZXEMA502MBSchi_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Tom, Carlos,
Thanks for your comments, please see my response inline:

From: nvo3 [mailto:nvo3-bounces@ietf.org] On Behalf Of Carlos Pignataro (cp=
ignata)
Sent: Friday, April 11, 2014 1:09 AM
To: Tom Herbert
Cc: l2tpext@ietf.org; Namgon Kim; Fanduoliang; nvo3@ietf.org; Xialiang (Fra=
nk); Zehn Cao
Subject: Re: [nvo3] New Version Notification for draft-fan-l2tp-vp-01.txt

Frank, Tom,

Please find some additional comments inline, L2TPExt chair hat off.

On Apr 10, 2014, at 11:46 AM, Tom Herbert <therbert@google.com<mailto:therb=
ert@google.com>> wrote:


On Wed, Apr 9, 2014 at 8:37 PM, Xialiang (Frank)
<frank.xialiang@huawei.com<mailto:frank.xialiang@huawei.com>> wrote:

Hi folks,
We have updated the L2TP-VP version -01 draft.
In the new version draft, we add the motivation of this draft and modificat=
ion to the format of L2TP-VP header.
Welcome your comments and suggestions!
Hi Frank,

Thanks for posting. A few comments:

- This is so dramatically different from L2TP I wonder if it can still
honestly be called L2TP. Have you implemented this? How much of L2TP
stack can be leveraged?
- "Session ID is changed to a 31-bit field"-- doesn't this break L2TP then?

These two bullet points are critical. A "profile" of protocol is a constrai=
ned subset of it, within an applicability context. What this document shows=
 is not a profile.

The most-significant bit of the Session ID being used for something else ("=
Modified bit") has two implications:

  1.  This is not a profile, it's an attempt to redefine L2TPv3.
  2.  This non-profile draft describes a non-backwards compatible protocol.=
 Meaning, L2TPv3's Session ID allows for Session IDs with the MSB set. Cons=
equently, a packet cannot be differentiated between L2TPv3 and this other p=
rotocol (which is not a profile).
  3.  It breaks L2TPv3.
OK, I lied, three (or possibly more) implications :-)

The remaining points are subordinate to this high-order bit (no pun intende=
d).


- "Type field"-- I suspect this is meant to be an EtherType value.
Please be explicit about this.
- To get hashing (for ECMP, RSS, etc.) in the network we'd almost
certainly use L2TP over UDP, so L2TP-VP should probably have a format
defined for use with UDP.

There's also hashing for L2TPv3 directly over IP (e.g., RFC 5640)
[Frank] : Agree with all your comments. In current draft, we only specifies=
 L2TP-VP over IP. We indeed have considered L2TP-VP over UDP and can add th=
is part of content in next version if necessary.

Thanks,

Carlos.


- Even with Type field, this still suffers from the same problem L2TP
has that network devices won't be able to parse the packet beyond the
L2TP header (the cookie field makes the header variable length). This
eliminates the ability to implement the protocol with LRO for
instance. I suggest you take four or five bits from reserved section
for header length to resolve this (see example in GUE).
- Cookie mechanism is an advantage over VXLAN and nvgre I believe, but
why limit it to 32 bits? 64 bits is much stronger, and at some point
we might even want 128 bits to do strong authentication.

Some more general questions applicable to this and some other proposals.

- "TNI field"-- this seems to use the same 24 bit left shifted format
of nvgre and VXLAN. I still don't see the rationale for this! Why
can't the full 32 bit field be allocated for vni? A large deployment
will be using various levels of hierarchical allocation and possibly
obfuscation of vni (TNI). The nvo3 requirements on this are vague
("100's of thousands of virtual networks"), but they clearly don't
expect this the VNI to be a simple flat space either.
- "Outer Ethernet Header"-- showing the outer Ethernet header in L3
encapsulations examples is not necessary, use of Ethernet is not a
requirement, and this is potentially very misleading. For instance,
the outer Ethernet FCS does *not* protect the packet end to end in an
L3 routed network. Personally, I think it would be more illustrative
to show the IP packet in the inner Ethernet frame instead to see how
its alignment is affected.

Thanks,
Tom


B.R.
Frank


-----Original Message-----
From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> [mailto:int=
ernet-drafts@ietf.org]
Sent: Thursday, April 10, 2014 11:22 AM
To: Xialiang (Frank); Zhen Cao; Fanduoliang; Zehn Cao; Namgon Kim; Namgon
Kim; Fanduoliang; Xialiang (Frank)
Subject: New Version Notification for draft-fan-l2tp-vp-01.txt


A new version of I-D, draft-fan-l2tp-vp-01.txt has been successfully submit=
ted
by Liang Xia and posted to the IETF repository.

Name:         draft-fan-l2tp-vp
Revision:     01
Title:                L2TP-VP: Layer Two Tunneling Protocol - Virtualizatio=
n Profile
Document date:        2014-04-10
Group:                Individual Submission
Pages:                9
URL:
http://www.ietf.org/internet-drafts/draft-fan-l2tp-vp-01.txt
Status:         https://datatracker.ietf.org/doc/draft-fan-l2tp-vp/
Htmlized:       http://tools.ietf.org/html/draft-fan-l2tp-vp-01
Diff:           http://www.ietf.org/rfcdiff?url2=3Ddraft-fan-l2tp-vp-01

Abstract:
  This document describes Layer Two Tunneling Protocol (L2TP)'s
  virtualization profile (L2TP-VP), which reuses session header of L2TP
  data message to securely support overlay networks for multiple
  tenants, and simplifies tunnel setup by disabling all kinds of L2TP
  control messages.




Please note that it may take a couple of minutes from the time of submissio=
n
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

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

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


--_000_C02846B1344F344EB4FAA6FA7AF481F10F3E2BF2SZXEMA502MBSchi_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"\6279\6CE8\6846\6587\672C Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:9.0pt;
	font-family:"Times New Roman","serif";}
span.Char
	{mso-style-name:"\6279\6CE8\6846\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\6279\6CE8\6846\6587\672C;
	font-family:SimSun;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:42026094;
	mso-list-template-ids:1721108520;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"ZH-CN" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi
</span><span lang=3D"EN-US" style=3D"font-size:9.0pt">Tom</span><span lang=
=3D"EN-US" style=3D"font-size:9.0pt">, Carlos,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt">Thank=
s for your comments, please see my response inline:</span><span lang=3D"EN-=
US" style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans-se=
rif&quot;;color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> nvo3 [mailto:nvo3-bounces@ietf.org]
<b>On Behalf Of </b>Carlos Pignataro (cpignata)<br>
<b>Sent:</b> Friday, April 11, 2014 1:09 AM<br>
<b>To:</b> Tom Herbert<br>
<b>Cc:</b> l2tpext@ietf.org; Namgon Kim; Fanduoliang; nvo3@ietf.org; Xialia=
ng (Frank); Zehn Cao<br>
<b>Subject:</b> Re: [nvo3] New Version Notification for draft-fan-l2tp-vp-0=
1.txt<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Frank, Tom, <o:p></o:p></span><=
/p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Please find some additional com=
ments inline, L2TPExt chair hat off.
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">On Apr 10, 2014, at 11:46 AM, T=
om Herbert &lt;<a href=3D"mailto:therbert@google.com">therbert@google.com</=
a>&gt; wrote:<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><br>
<br>
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt">On We=
d, Apr 9, 2014 at 8:37 PM, Xialiang (Frank)<br>
&lt;<a href=3D"mailto:frank.xialiang@huawei.com">frank.xialiang@huawei.com<=
/a>&gt; wrote:<br>
<br>
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US" =
style=3D"font-size:9.0pt">Hi folks,<br>
We have updated the L2TP-VP version -01 draft.<br>
In the new version draft, we add the motivation of this draft and modificat=
ion to the format of L2TP-VP header.<br>
Welcome your comments and suggestions!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt">Hi Fr=
ank,<br>
<br>
Thanks for posting. A few comments:<br>
<br>
- This is so dramatically different from L2TP I wonder if it can still<br>
honestly be called L2TP. Have you implemented this? How much of L2TP<br>
stack can be leveraged?<br>
- &quot;Session ID is changed to a 31-bit field&quot;-- doesn't this break =
L2TP then?<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">These two bullet points are cri=
tical. A &quot;profile&quot; of protocol is a constrained subset of it, wit=
hin an applicability context. What this document shows is not a profile.&nb=
sp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The most-significant bit of the=
 Session ID being used for something else (&quot;Modified bit&quot;) has tw=
o implications:<o:p></o:p></span></p>
</div>
<div>
<ol start=3D"1" type=3D"1">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l0 level1 lfo1">
<span lang=3D"EN-US">This is not a profile, it's an attempt to redefine L2T=
Pv3.<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"mso-margin-top-=
alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span lang=3D"EN-US">This non-profile draft describes a non-backwards compa=
tible protocol. Meaning, L2TPv3's Session ID allows for Session IDs with th=
e MSB set. Consequently, a packet cannot be differentiated between L2TPv3 a=
nd this other protocol (which is not
 a profile).<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"mso-mar=
gin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span lang=3D"EN-US">It breaks L2TPv3.<o:p></o:p></span></li></ol>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">OK, I lied, three (or possibly =
more) implications :-)<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The remaining points are subord=
inate to this high-order bit (no pun intended).<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><br>
<br>
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt">- &qu=
ot;Type field&quot;-- I suspect this is meant to be an EtherType value.<br>
Please be explicit about this.<br>
- To get hashing (for ECMP, RSS, etc.) in the network we'd almost<br>
certainly use L2TP over UDP, so L2TP-VP should probably have a format<br>
defined for use with UDP.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">There's also hashing for L2TPv3=
 directly over IP (e.g., RFC&nbsp;5640)</span><span lang=3D"EN-US"><o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><b><i><span lang=3D"EN-US" style=3D"font-size:10.5pt=
;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">[Fra=
nk] : Agree with all your comments. In current draft, we only specifies L2T=
P-VP over IP. We indeed have considered L2TP-VP over UDP and
 can add this part of content in next version if necessary.</span></i></b><=
span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri&quo=
t;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Thanks,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Carlos.<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><br>
<br>
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt">- Eve=
n with Type field, this still suffers from the same problem L2TP<br>
has that network devices won't be able to parse the packet beyond the<br>
L2TP header (the cookie field makes the header variable length). This<br>
eliminates the ability to implement the protocol with LRO for<br>
instance. I suggest you take four or five bits from reserved section<br>
for header length to resolve this (see example in GUE).<br>
- Cookie mechanism is an advantage over VXLAN and nvgre I believe, but<br>
why limit it to 32 bits? 64 bits is much stronger, and at some point<br>
we might even want 128 bits to do strong authentication.<br>
<br>
Some more general questions applicable to this and some other proposals.<br=
>
<br>
- &quot;TNI field&quot;-- this seems to use the same 24 bit left shifted fo=
rmat<br>
of nvgre and VXLAN. I still don't see the rationale for this! Why<br>
can't the full 32 bit field be allocated for vni? A large deployment<br>
will be using various levels of hierarchical allocation and possibly<br>
obfuscation of vni (TNI). The nvo3 requirements on this are vague<br>
(&quot;100's of thousands of virtual networks&quot;), but they clearly don'=
t<br>
expect this the VNI to be a simple flat space either.<br>
- &quot;Outer Ethernet Header&quot;-- showing the outer Ethernet header in =
L3<br>
encapsulations examples is not necessary, use of Ethernet is not a<br>
requirement, and this is potentially very misleading. For instance,<br>
the outer Ethernet FCS does *not* protect the packet end to end in an<br>
L3 routed network. Personally, I think it would be more illustrative<br>
to show the IP packet in the inner Ethernet frame instead to see how<br>
its alignment is affected.<br>
<br>
Thanks,<br>
Tom<br>
<br>
<br>
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt">B.R.<=
br>
Frank<br>
<br>
<br>
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt">-----=
Original Message-----<br>
From: <a href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org<=
/a> [<a href=3D"mailto:internet-drafts@ietf.org">mailto:internet-drafts@iet=
f.org</a>]<br>
Sent: Thursday, April 10, 2014 11:22 AM<br>
To: Xialiang (Frank); Zhen Cao; Fanduoliang; Zehn Cao; Namgon Kim; Namgon<b=
r>
Kim; Fanduoliang; Xialiang (Frank)<br>
Subject: New Version Notification for draft-fan-l2tp-vp-01.txt<br>
<br>
<br>
A new version of I-D, draft-fan-l2tp-vp-01.txt has been successfully submit=
ted<br>
by Liang Xia and posted to the IETF repository.<br>
<br>
Name: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;draft-fan-l2tp-vp<br>
Revision: &nbsp;&nbsp;&nbsp;&nbsp;01<br>
Title: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;L2TP-VP: Layer Two Tunneling Protocol - Virtualizatio=
n Profile<br>
Document date: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2014-04-10<br>
Group: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;Individual Submission<br>
Pages: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;9<br>
URL:<br>
<a href=3D"http://www.ietf.org/internet-drafts/draft-fan-l2tp-vp-01.txt">ht=
tp://www.ietf.org/internet-drafts/draft-fan-l2tp-vp-01.txt</a><br>
Status: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"https://=
datatracker.ietf.org/doc/draft-fan-l2tp-vp/">https://datatracker.ietf.org/d=
oc/draft-fan-l2tp-vp/</a><br>
Htmlized: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"http://tools.ietf.=
org/html/draft-fan-l2tp-vp-01">http://tools.ietf.org/html/draft-fan-l2tp-vp=
-01</a><br>
Diff: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href=
=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-fan-l2tp-vp-01">http://www.iet=
f.org/rfcdiff?url2=3Ddraft-fan-l2tp-vp-01</a><br>
<br>
Abstract:<br>
&nbsp;&nbsp;This document describes Layer Two Tunneling Protocol (L2TP)'s<b=
r>
&nbsp;&nbsp;virtualization profile (L2TP-VP), which reuses session header o=
f L2TP<br>
&nbsp;&nbsp;data message to securely support overlay networks for multiple<=
br>
&nbsp;&nbsp;tenants, and simplifies tunnel setup by disabling all kinds of =
L2TP<br>
&nbsp;&nbsp;control messages.<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at tools.ietf.org.<br>
<br>
The IETF Secretariat<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt"><br>
_______________________________________________<br>
nvo3 mailing list<br>
<a href=3D"mailto:nvo3@ietf.org">nvo3@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/nvo3">https://www.ietf.org=
/mailman/listinfo/nvo3</a><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt"><br>
_______________________________________________<br>
nvo3 mailing list<br>
<a href=3D"mailto:nvo3@ietf.org">nvo3@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/nvo3">https://www.ietf.org=
/mailman/listinfo/nvo3</a><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_C02846B1344F344EB4FAA6FA7AF481F10F3E2BF2SZXEMA502MBSchi_--


From nobody Fri Apr 11 03:02:19 2014
Return-Path: <frank.xialiang@huawei.com>
X-Original-To: l2tpext@ietfa.amsl.com
Delivered-To: l2tpext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F5351A03B6; Fri, 11 Apr 2014 03:02:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.472
X-Spam-Level: 
X-Spam-Status: No, score=-4.472 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tJxRo9Ww1m-q; Fri, 11 Apr 2014 03:02:09 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 15FD11A01BF; Fri, 11 Apr 2014 03:02:06 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BCZ44977; Fri, 11 Apr 2014 10:02:05 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 11 Apr 2014 11:00:48 +0100
Received: from SZXEMA406-HUB.china.huawei.com (10.82.72.38) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 11 Apr 2014 11:01:55 +0100
Received: from SZXEMA502-MBS.china.huawei.com ([169.254.4.203]) by SZXEMA406-HUB.china.huawei.com ([10.82.72.38]) with mapi id 14.03.0158.001; Fri, 11 Apr 2014 18:01:46 +0800
From: "Xialiang (Frank)" <frank.xialiang@huawei.com>
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, Tom Herbert <therbert@google.com>
Thread-Topic: [nvo3] New Version Notification for draft-fan-l2tp-vp-01.txt
Thread-Index: AQHPVGwUioKZm7B370uoJbPkmsBi+JsKMc1AgABHcYCAABbRgIABmf0Q
Date: Fri, 11 Apr 2014 10:01:45 +0000
Message-ID: <C02846B1344F344EB4FAA6FA7AF481F10F3E2C07@SZXEMA502-MBS.china.huawei.com>
References: <20140410032205.30725.83163.idtracker@ietfa.amsl.com> <C02846B1344F344EB4FAA6FA7AF481F10F3E29D0@SZXEMA502-MBS.china.huawei.com> <CA+mtBx9r75d3bkk4FeHWXjPMwfetr97rBuxWoubDsx=_Y_RZ0g@mail.gmail.com> <1045434E-F6BE-444E-8E28-B2DCCE1B0A35@cisco.com>
In-Reply-To: <1045434E-F6BE-444E-8E28-B2DCCE1B0A35@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.135.42.220]
Content-Type: multipart/alternative; boundary="_000_C02846B1344F344EB4FAA6FA7AF481F10F3E2C07SZXEMA502MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/l2tpext/m6Gyw3_tKU3wV2_3tJlKUOvA0vM
Cc: Fanduoliang <fanduoliang@huawei.com>, Zehn Cao <zehn.cao@gmail.com>, "nvo3@ietf.org" <nvo3@ietf.org>, "l2tpext@ietf.org" <l2tpext@ietf.org>, Namgon Kim <ng.kim@kt.com>
Subject: Re: [L2tpext] [nvo3] New Version Notification for draft-fan-l2tp-vp-01.txt
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2tpext/>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Apr 2014 10:02:14 -0000

--_000_C02846B1344F344EB4FAA6FA7AF481F10F3E2C07SZXEMA502MBSchi_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Tom, Carlos,
Thanks for your comments, please see my response inline:

B.R.
Frank

From: nvo3 [mailto:nvo3-bounces@ietf.org] On Behalf Of Carlos Pignataro (cp=
ignata)
Sent: Friday, April 11, 2014 1:09 AM
To: Tom Herbert
Cc: l2tpext@ietf.org; Namgon Kim; Fanduoliang; nvo3@ietf.org; Xialiang (Fra=
nk); Zehn Cao
Subject: Re: [nvo3] New Version Notification for draft-fan-l2tp-vp-01.txt

Frank, Tom,

Please find some additional comments inline, L2TPExt chair hat off.

On Apr 10, 2014, at 11:46 AM, Tom Herbert <therbert@google.com<mailto:therb=
ert@google.com>> wrote:


On Wed, Apr 9, 2014 at 8:37 PM, Xialiang (Frank)
<frank.xialiang@huawei.com<mailto:frank.xialiang@huawei.com>> wrote:

Hi folks,
We have updated the L2TP-VP version -01 draft.
In the new version draft, we add the motivation of this draft and modificat=
ion to the format of L2TP-VP header.
Welcome your comments and suggestions!
Hi Frank,

Thanks for posting. A few comments:

- This is so dramatically different from L2TP I wonder if it can still
honestly be called L2TP. Have you implemented this? How much of L2TP
stack can be leveraged?
- "Session ID is changed to a 31-bit field"-- doesn't this break L2TP then?
[Frank] : The main differences we've made are:

1.       Session ID is changed to 31-bit: that's because we need the most s=
ignificant bit for differentiating  L2TPv3 packets with L2TP-VP packets in =
data plane. The only disadvantage is to limit the session ID scope for exis=
ting L2TPv3 protocol to < 2 ^ 31, but that scope is large enough to be used=
 for L2TPv3 session in practice;

2.       We reuse first 32 bit of cookie field to the TNI, the left 32 bit =
is still used for cookie field. This indeed limit the cookie mechanism's ca=
pability. In next version of the draft, we will solve this problem.
Except the above, we do not change anything of L2TPv3. What we currently do=
 is to reuse L2TPv3 for multi-tenant network scenarios, but keep its implem=
entation separating from existed L2TPv3 implementation in data plane clearl=
y.

These two bullet points are critical. A "profile" of protocol is a constrai=
ned subset of it, within an applicability context. What this document shows=
 is not a profile.

The most-significant bit of the Session ID being used for something else ("=
Modified bit") has two implications:

  1.  This is not a profile, it's an attempt to redefine L2TPv3.
  2.  This non-profile draft describes a non-backwards compatible protocol.=
 Meaning, L2TPv3's Session ID allows for Session IDs with the MSB set. Cons=
equently, a packet cannot be differentiated between L2TPv3 and this other p=
rotocol (which is not a profile).
  3.  It breaks L2TPv3.
OK, I lied, three (or possibly more) implications :-)

The remaining points are subordinate to this high-order bit (no pun intende=
d).
[Frank] : I think we can consider the relationship between L2TP-VP and L2TP=
v3 as the same thing of relationship between MPLS-TP and MPLS.


- "Type field"-- I suspect this is meant to be an EtherType value.
Please be explicit about this.
- To get hashing (for ECMP, RSS, etc.) in the network we'd almost
certainly use L2TP over UDP, so L2TP-VP should probably have a format
defined for use with UDP.

There's also hashing for L2TPv3 directly over IP (e.g., RFC 5640)
[Frank] : Agree with all your comments. In current draft, we only specifies=
 L2TP-VP over IP. We indeed have considered L2TP-VP over UDP and can add th=
is part of content in next version if necessary.

Thanks,

Carlos.


- Even with Type field, this still suffers from the same problem L2TP
has that network devices won't be able to parse the packet beyond the
L2TP header (the cookie field makes the header variable length). This
eliminates the ability to implement the protocol with LRO for
instance. I suggest you take four or five bits from reserved section
for header length to resolve this (see example in GUE).
[Frank] : good comments. Will consider it~~

- Cookie mechanism is an advantage over VXLAN and nvgre I believe, but
why limit it to 32 bits? 64 bits is much stronger, and at some point
we might even want 128 bits to do strong authentication.

Some more general questions applicable to this and some other proposals.

- "TNI field"-- this seems to use the same 24 bit left shifted format
of nvgre and VXLAN. I still don't see the rationale for this! Why
can't the full 32 bit field be allocated for vni? A large deployment
will be using various levels of hierarchical allocation and possibly
obfuscation of vni (TNI). The nvo3 requirements on this are vague
("100's of thousands of virtual networks"), but they clearly don't
expect this the VNI to be a simple flat space either.
[Frank] : It's an issue existing a long time. I have no personal preference=
 on it. It totally depends on real requirement.



- "Outer Ethernet Header"-- showing the outer Ethernet header in L3
encapsulations examples is not necessary, use of Ethernet is not a
requirement, and this is potentially very misleading. For instance,
the outer Ethernet FCS does *not* protect the packet end to end in an
L3 routed network. Personally, I think it would be more illustrative
to show the IP packet in the inner Ethernet frame instead to see how
its alignment is affected.
[Frank] : Actually, It's only a encapsulation example. But your comment is =
right. We will correct in the next version. Thanks!


Thanks,
Tom


B.R.
Frank


-----Original Message-----
From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> [mailto:int=
ernet-drafts@ietf.org]
Sent: Thursday, April 10, 2014 11:22 AM
To: Xialiang (Frank); Zhen Cao; Fanduoliang; Zehn Cao; Namgon Kim; Namgon
Kim; Fanduoliang; Xialiang (Frank)
Subject: New Version Notification for draft-fan-l2tp-vp-01.txt


A new version of I-D, draft-fan-l2tp-vp-01.txt has been successfully submit=
ted
by Liang Xia and posted to the IETF repository.

Name:         draft-fan-l2tp-vp
Revision:     01
Title:                L2TP-VP: Layer Two Tunneling Protocol - Virtualizatio=
n Profile
Document date:        2014-04-10
Group:                Individual Submission
Pages:                9
URL:
http://www.ietf.org/internet-drafts/draft-fan-l2tp-vp-01.txt
Status:         https://datatracker.ietf.org/doc/draft-fan-l2tp-vp/
Htmlized:       http://tools.ietf.org/html/draft-fan-l2tp-vp-01
Diff:           http://www.ietf.org/rfcdiff?url2=3Ddraft-fan-l2tp-vp-01

Abstract:
  This document describes Layer Two Tunneling Protocol (L2TP)'s
  virtualization profile (L2TP-VP), which reuses session header of L2TP
  data message to securely support overlay networks for multiple
  tenants, and simplifies tunnel setup by disabling all kinds of L2TP
  control messages.




Please note that it may take a couple of minutes from the time of submissio=
n
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

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

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


--_000_C02846B1344F344EB4FAA6FA7AF481F10F3E2C07SZXEMA502MBSchi_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"\6279\6CE8\6846\6587\672C Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:9.0pt;
	font-family:"Times New Roman","serif";}
span.MsoPlaceholderText
	{mso-style-priority:99;
	color:gray;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin:0cm;
	margin-bottom:.0001pt;
	text-indent:21.0pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.Char
	{mso-style-name:"\6279\6CE8\6846\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\6279\6CE8\6846\6587\672C;
	font-family:SimSun;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:42026094;
	mso-list-template-ids:1721108520;}
@list l1
	{mso-list-id:901211217;
	mso-list-type:hybrid;
	mso-list-template-ids:-796349320 1191108594 67698713 67698715 67698703 676=
98713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:18.0pt;
	text-indent:-18.0pt;
	mso-ansi-font-weight:bold;
	mso-ansi-font-style:italic;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"ZH-CN" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi Tom, Ca=
rlos,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks for=
 your comments, please see my response inline:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">B.R.<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Frank<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> nvo3 [mailto:nvo3-bounces@ietf.org]
<b>On Behalf Of </b>Carlos Pignataro (cpignata)<br>
<b>Sent:</b> Friday, April 11, 2014 1:09 AM<br>
<b>To:</b> Tom Herbert<br>
<b>Cc:</b> l2tpext@ietf.org; Namgon Kim; Fanduoliang; nvo3@ietf.org; Xialia=
ng (Frank); Zehn Cao<br>
<b>Subject:</b> Re: [nvo3] New Version Notification for draft-fan-l2tp-vp-0=
1.txt<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Frank, Tom, <o:p></o:p></span><=
/p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Please find some additional com=
ments inline, L2TPExt chair hat off.
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">On Apr 10, 2014, at 11:46 AM, T=
om Herbert &lt;<a href=3D"mailto:therbert@google.com">therbert@google.com</=
a>&gt; wrote:<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><br>
<br>
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt">On We=
d, Apr 9, 2014 at 8:37 PM, Xialiang (Frank)<br>
&lt;<a href=3D"mailto:frank.xialiang@huawei.com">frank.xialiang@huawei.com<=
/a>&gt; wrote:<br>
<br>
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US" =
style=3D"font-size:9.0pt">Hi folks,<br>
We have updated the L2TP-VP version -01 draft.<br>
In the new version draft, we add the motivation of this draft and modificat=
ion to the format of L2TP-VP header.<br>
Welcome your comments and suggestions!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt">Hi Fr=
ank,<br>
<br>
Thanks for posting. A few comments:<br>
<br>
- This is so dramatically different from L2TP I wonder if it can still<br>
honestly be called L2TP. Have you implemented this? How much of L2TP<br>
stack can be leveraged?<br>
- &quot;Session ID is changed to a 31-bit field&quot;-- doesn't this break =
L2TP then?</span><span lang=3D"EN-US" style=3D"font-size:9.0pt"><o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><b><i><span lang=3D"EN-US" style=3D"font-size:10.5pt=
;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">[Fra=
nk] : The main differences we&#8217;ve made are:<o:p></o:p></span></i></b><=
/p>
<p class=3D"MsoListParagraph" style=3D"margin-left:18.0pt;text-indent:-18.0=
pt;mso-list:l1 level1 lfo2">
<![if !supportLists]><b><i><span lang=3D"EN-US" style=3D"font-size:10.5pt;f=
ont-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span =
style=3D"mso-list:Ignore">1.<span style=3D"font:7.0pt &quot;Times New Roman=
&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span></i></b><![endif]><span lang=3D"EN-US" style=3D"font-s=
ize:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F=
497D">Session ID is changed to 31-bit: that&#8217;s because we need the mos=
t significant bit for differentiating &nbsp;L2TPv3 packets with L2TP-VP
 packets in data plane. The only disadvantage is to limit the session ID sc=
ope for existing L2TPv3 protocol to &lt; 2 ^ 31, but that scope is large en=
ough to be used for L2TPv3 session in practice;<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:18.0pt;text-indent:-18.0=
pt;mso-list:l1 level1 lfo2">
<![if !supportLists]><b><i><span lang=3D"EN-US" style=3D"font-size:10.5pt;f=
ont-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span =
style=3D"mso-list:Ignore">2.<span style=3D"font:7.0pt &quot;Times New Roman=
&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span></i></b><![endif]><span lang=3D"EN-US" style=3D"font-s=
ize:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F=
497D">We reuse first 32 bit of cookie field to the TNI, the left 32 bit is =
still used for cookie field. This indeed limit the cookie
 mechanism&#8217;s capability. In next version of the draft, we will solve =
this problem.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Except the=
 above, we do not change anything of L2TPv3. What we currently do is to reu=
se L2TPv3 for multi-tenant network scenarios, but keep its
 implementation separating from existed L2TPv3 implementation in data plane=
 clearly.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">These two bullet points are cri=
tical. A &quot;profile&quot; of protocol is a constrained subset of it, wit=
hin an applicability context. What this document shows is not a profile.&nb=
sp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The most-significant bit of the=
 Session ID being used for something else (&quot;Modified bit&quot;) has tw=
o implications:<o:p></o:p></span></p>
</div>
<div>
<ol start=3D"1" type=3D"1">
<li class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-=
alt:auto;mso-list:l0 level1 lfo1">
<span lang=3D"EN-US">This is not a profile, it's an attempt to redefine L2T=
Pv3.<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"mso-margin-top-=
alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span lang=3D"EN-US">This non-profile draft describes a non-backwards compa=
tible protocol. Meaning, L2TPv3's Session ID allows for Session IDs with th=
e MSB set. Consequently, a packet cannot be differentiated between L2TPv3 a=
nd this other protocol (which is not
 a profile).<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"mso-mar=
gin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span lang=3D"EN-US">It breaks L2TPv3.<o:p></o:p></span></li></ol>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">OK, I lied, three (or possibly =
more) implications :-)<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The remaining points are subord=
inate to this high-order bit (no pun intended).</span><span lang=3D"EN-US">=
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><i><span lang=3D"EN-US" style=3D"font-size:10.5pt=
;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">[Fra=
nk] : I think we can consider the relationship between L2TP-VP and L2TPv3 a=
s the same thing of relationship between MPLS-TP and MPLS.</span></i></b><s=
pan lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot=
;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><br>
<br>
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt">- &qu=
ot;Type field&quot;-- I suspect this is meant to be an EtherType value.<br>
Please be explicit about this.<br>
- To get hashing (for ECMP, RSS, etc.) in the network we'd almost<br>
certainly use L2TP over UDP, so L2TP-VP should probably have a format<br>
defined for use with UDP.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">There's also hashing for L2TPv3=
 directly over IP (e.g., RFC&nbsp;5640)<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><b><i><span lang=3D"EN-US" style=3D"font-size:10.5pt=
;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">[Fra=
nk] : Agree with all your comments. In current draft, we only specifies L2T=
P-VP over IP. We indeed have considered L2TP-VP over UDP and
 can add this part of content in next version if necessary.</span></i></b><=
span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri&quo=
t;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Thanks,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Carlos.<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><br>
<br>
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt">- Eve=
n with Type field, this still suffers from the same problem L2TP<br>
has that network devices won't be able to parse the packet beyond the<br>
L2TP header (the cookie field makes the header variable length). This<br>
eliminates the ability to implement the protocol with LRO for<br>
instance. I suggest you take four or five bits from reserved section<br>
for header length to resolve this (see example in GUE).</span><span lang=3D=
"EN-US" style=3D"font-size:9.0pt;color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><i><span lang=3D"EN-US" style=3D"font-size:10.5pt=
;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">[Fra=
nk] : good comments. Will consider it~~<o:p></o:p></span></i></b></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt"><br>
- Cookie mechanism is an advantage over VXLAN and nvgre I believe, but<br>
why limit it to 32 bits? 64 bits is much stronger, and at some point<br>
we might even want 128 bits to do strong authentication.<br>
<br>
Some more general questions applicable to this and some other proposals.<br=
>
<br>
- &quot;TNI field&quot;-- this seems to use the same 24 bit left shifted fo=
rmat<br>
of nvgre and VXLAN. I still don't see the rationale for this! Why<br>
can't the full 32 bit field be allocated for vni? A large deployment<br>
will be using various levels of hierarchical allocation and possibly<br>
obfuscation of vni (TNI). The nvo3 requirements on this are vague<br>
(&quot;100's of thousands of virtual networks&quot;), but they clearly don'=
t<br>
expect this the VNI to be a simple flat space either.</span><span lang=3D"E=
N-US" style=3D"font-size:9.0pt;color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><i><span lang=3D"EN-US" style=3D"font-size:10.5pt=
;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">[Fra=
nk] : It&#8217;s an issue existing a long time. I have no personal preferen=
ce on it. It totally depends on real requirement.</span></i></b><span lang=
=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt;color:=
#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt;color:=
#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt"><br>
- &quot;Outer Ethernet Header&quot;-- showing the outer Ethernet header in =
L3<br>
encapsulations examples is not necessary, use of Ethernet is not a<br>
requirement, and this is potentially very misleading. For instance,<br>
the outer Ethernet FCS does *not* protect the packet end to end in an<br>
L3 routed network. Personally, I think it would be more illustrative<br>
to show the IP packet in the inner Ethernet frame instead to see how<br>
its alignment is affected.</span><span lang=3D"EN-US" style=3D"font-size:9.=
0pt;color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><i><span lang=3D"EN-US" style=3D"font-size:10.5pt=
;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">[Fra=
nk] : Actually, It&#8217;s only a encapsulation example. But your comment i=
s right. We will correct in the next version. Thanks!<o:p></o:p></span></i>=
</b></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt"><br>
<br>
Thanks,<br>
Tom<br>
<br>
<br>
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt">B.R.<=
br>
Frank<br>
<br>
<br>
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt">-----=
Original Message-----<br>
From: <a href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org<=
/a> [<a href=3D"mailto:internet-drafts@ietf.org">mailto:internet-drafts@iet=
f.org</a>]<br>
Sent: Thursday, April 10, 2014 11:22 AM<br>
To: Xialiang (Frank); Zhen Cao; Fanduoliang; Zehn Cao; Namgon Kim; Namgon<b=
r>
Kim; Fanduoliang; Xialiang (Frank)<br>
Subject: New Version Notification for draft-fan-l2tp-vp-01.txt<br>
<br>
<br>
A new version of I-D, draft-fan-l2tp-vp-01.txt has been successfully submit=
ted<br>
by Liang Xia and posted to the IETF repository.<br>
<br>
Name: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;draft-fan-l2tp-vp<br>
Revision: &nbsp;&nbsp;&nbsp;&nbsp;01<br>
Title: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;L2TP-VP: Layer Two Tunneling Protocol - Virtualizatio=
n Profile<br>
Document date: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2014-04-10<br>
Group: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;Individual Submission<br>
Pages: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;9<br>
URL:<br>
<a href=3D"http://www.ietf.org/internet-drafts/draft-fan-l2tp-vp-01.txt">ht=
tp://www.ietf.org/internet-drafts/draft-fan-l2tp-vp-01.txt</a><br>
Status: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"https://=
datatracker.ietf.org/doc/draft-fan-l2tp-vp/">https://datatracker.ietf.org/d=
oc/draft-fan-l2tp-vp/</a><br>
Htmlized: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"http://tools.ietf.=
org/html/draft-fan-l2tp-vp-01">http://tools.ietf.org/html/draft-fan-l2tp-vp=
-01</a><br>
Diff: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href=
=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-fan-l2tp-vp-01">http://www.iet=
f.org/rfcdiff?url2=3Ddraft-fan-l2tp-vp-01</a><br>
<br>
Abstract:<br>
&nbsp;&nbsp;This document describes Layer Two Tunneling Protocol (L2TP)'s<b=
r>
&nbsp;&nbsp;virtualization profile (L2TP-VP), which reuses session header o=
f L2TP<br>
&nbsp;&nbsp;data message to securely support overlay networks for multiple<=
br>
&nbsp;&nbsp;tenants, and simplifies tunnel setup by disabling all kinds of =
L2TP<br>
&nbsp;&nbsp;control messages.<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at tools.ietf.org.<br>
<br>
The IETF Secretariat<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt"><br>
_______________________________________________<br>
nvo3 mailing list<br>
<a href=3D"mailto:nvo3@ietf.org">nvo3@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/nvo3">https://www.ietf.org=
/mailman/listinfo/nvo3</a><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt"><br>
_______________________________________________<br>
nvo3 mailing list<br>
<a href=3D"mailto:nvo3@ietf.org">nvo3@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/nvo3">https://www.ietf.org=
/mailman/listinfo/nvo3</a><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_C02846B1344F344EB4FAA6FA7AF481F10F3E2C07SZXEMA502MBSchi_--


From nobody Fri Apr 11 05:29:50 2014
Return-Path: <cpignata@cisco.com>
X-Original-To: l2tpext@ietfa.amsl.com
Delivered-To: l2tpext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE8BA1A0167; Fri, 11 Apr 2014 05:29:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.772
X-Spam-Level: 
X-Spam-Status: No, score=-14.772 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YH1EelozHr3P; Fri, 11 Apr 2014 05:29:41 -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 632341A00FD; Fri, 11 Apr 2014 05:29:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=34409; q=dns/txt; s=iport; t=1397219380; x=1398428980; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=AVL4xtQ1XE8IeWuR9t4jvXUM7g1ZN9biNsHgooCow2c=; b=IF9MQHMvKgbmCwlOcyRLsoMoxFcVQOSovf6fJ+IodJ6hT9T1peekT0h4 0WsT2oLM7zutX50bFdzjM1pnWsYJpMzLTYP793MXWwb4LGDLKy2L0JFqT JxUzEUlVUU8w92zI9z+Kju11g01deApF4SxBXijEVfIK0WKvvLd3joMoU s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnEFAO3eR1OtJA2D/2dsb2JhbABZgkJEO1EGu1aBP4ZkUYEbFnSCJQEBAQQBAQFrBAUCDAQCAQgRBAEBIQEGBycLFAkIAgQOBQmHcwgFzBEXjhVTBAYBBgODG4EUBJRzg22BNZENgzGBakE
X-IronPort-AV: E=Sophos;i="4.97,841,1389744000";  d="scan'208,217";a="316780054"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-1.cisco.com with ESMTP; 11 Apr 2014 12:29:39 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s3BCTd9Z003298 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 11 Apr 2014 12:29:39 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.99]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.03.0123.003; Fri, 11 Apr 2014 07:29:39 -0500
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: "Xialiang (Frank)" <frank.xialiang@huawei.com>
Thread-Topic: [L2tpext] [nvo3] New Version Notification for draft-fan-l2tp-vp-01.txt
Thread-Index: AQHPVW0pcy4KQg49x0ifU8sA9B1saZsMrGGA
Date: Fri, 11 Apr 2014 12:29:38 +0000
Message-ID: <088D92B9-1E8F-4382-9798-6B57A94B3FA4@cisco.com>
References: <20140410032205.30725.83163.idtracker@ietfa.amsl.com> <C02846B1344F344EB4FAA6FA7AF481F10F3E29D0@SZXEMA502-MBS.china.huawei.com> <CA+mtBx9r75d3bkk4FeHWXjPMwfetr97rBuxWoubDsx=_Y_RZ0g@mail.gmail.com> <1045434E-F6BE-444E-8E28-B2DCCE1B0A35@cisco.com> <C02846B1344F344EB4FAA6FA7AF481F10F3E2C07@SZXEMA502-MBS.china.huawei.com>
In-Reply-To: <C02846B1344F344EB4FAA6FA7AF481F10F3E2C07@SZXEMA502-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.117.115.51]
Content-Type: multipart/alternative; boundary="_000_088D92B91E8F438297986B57A94B3FA4ciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/l2tpext/7_teEegzRaqvxSJhvfY8rlUjung
Cc: "l2tpext@ietf.org" <l2tpext@ietf.org>, Namgon Kim <ng.kim@kt.com>, Fanduoliang <fanduoliang@huawei.com>, "nvo3@ietf.org" <nvo3@ietf.org>, Zehn Cao <zehn.cao@gmail.com>, Tom Herbert <therbert@google.com>
Subject: Re: [L2tpext] [nvo3] New Version Notification for draft-fan-l2tp-vp-01.txt
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2tpext/>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Apr 2014 12:29:47 -0000

--_000_088D92B91E8F438297986B57A94B3FA4ciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Frank,

Please see inline.

On Apr 11, 2014, at 6:01 AM, Xialiang (Frank) <frank.xialiang@huawei.com<ma=
ilto:frank.xialiang@huawei.com>> wrote:

Hi Tom, Carlos,
Thanks for your comments, please see my response inline:

B.R.
Frank

From: nvo3 [mailto:nvo3-bounces@ietf.org] On Behalf Of Carlos Pignataro (cp=
ignata)
Sent: Friday, April 11, 2014 1:09 AM
To: Tom Herbert
Cc: l2tpext@ietf.org<mailto:l2tpext@ietf.org>; Namgon Kim; Fanduoliang; nvo=
3@ietf.org<mailto:nvo3@ietf.org>; Xialiang (Frank); Zehn Cao
Subject: Re: [nvo3] New Version Notification for draft-fan-l2tp-vp-01.txt

Frank, Tom,

Please find some additional comments inline, L2TPExt chair hat off.

On Apr 10, 2014, at 11:46 AM, Tom Herbert <therbert@google.com<mailto:therb=
ert@google.com>> wrote:


On Wed, Apr 9, 2014 at 8:37 PM, Xialiang (Frank)
<frank.xialiang@huawei.com<mailto:frank.xialiang@huawei.com>> wrote:

Hi folks,
We have updated the L2TP-VP version -01 draft.
In the new version draft, we add the motivation of this draft and modificat=
ion to the format of L2TP-VP header.
Welcome your comments and suggestions!
Hi Frank,

Thanks for posting. A few comments:

- This is so dramatically different from L2TP I wonder if it can still
honestly be called L2TP. Have you implemented this? How much of L2TP
stack can be leveraged?
- "Session ID is changed to a 31-bit field"-- doesn't this break L2TP then?
[Frank] : The main differences we=92ve made are:
1.       Session ID is changed to 31-bit: that=92s because we need the most=
 significant bit for differentiating  L2TPv3 packets with L2TP-VP packets i=
n data plane. The only disadvantage is to limit the session ID scope for ex=
isting L2TPv3 protocol to < 2 ^ 31, but that scope is large enough to be us=
ed for L2TPv3 session in practice;
2.       We reuse first 32 bit of cookie field to the TNI, the left 32 bit =
is still used for cookie field. This indeed limit the cookie mechanism=92s =
capability. In next version of the draft, we will solve this problem.
Except the above, we do not change anything of L2TPv3.

I will say that both things are a non-starter. You can appreciate it's not =
only 31 vs 32 bits. As it was already pointed out, you cannot differentiate=
 an L2TPv3 packet with the MSB set. Regarding the cookie, please read RFC 3=
931 on the discussion of 32 vs. 64 bits.

Best,

Carlos.

What we currently do is to reuse L2TPv3 for multi-tenant network scenarios,=
 but keep its implementation separating from existed L2TPv3 implementation =
in data plane clearly.

These two bullet points are critical. A "profile" of protocol is a constrai=
ned subset of it, within an applicability context. What this document shows=
 is not a profile.

The most-significant bit of the Session ID being used for something else ("=
Modified bit") has two implications:

  1.  This is not a profile, it's an attempt to redefine L2TPv3.
  2.  This non-profile draft describes a non-backwards compatible protocol.=
 Meaning, L2TPv3's Session ID allows for Session IDs with the MSB set. Cons=
equently, a packet cannot be differentiated between L2TPv3 and this other p=
rotocol (which is not a profile).
  3.  It breaks L2TPv3.

OK, I lied, three (or possibly more) implications :-)

The remaining points are subordinate to this high-order bit (no pun intende=
d).
[Frank] : I think we can consider the relationship between L2TP-VP and L2TP=
v3 as the same thing of relationship between MPLS-TP and MPLS.


- "Type field"-- I suspect this is meant to be an EtherType value.
Please be explicit about this.
- To get hashing (for ECMP, RSS, etc.) in the network we'd almost
certainly use L2TP over UDP, so L2TP-VP should probably have a format
defined for use with UDP.

There's also hashing for L2TPv3 directly over IP (e.g., RFC 5640)
[Frank] : Agree with all your comments. In current draft, we only specifies=
 L2TP-VP over IP. We indeed have considered L2TP-VP over UDP and can add th=
is part of content in next version if necessary.

Thanks,

Carlos.


- Even with Type field, this still suffers from the same problem L2TP
has that network devices won't be able to parse the packet beyond the
L2TP header (the cookie field makes the header variable length). This
eliminates the ability to implement the protocol with LRO for
instance. I suggest you take four or five bits from reserved section
for header length to resolve this (see example in GUE).
[Frank] : good comments. Will consider it~~

- Cookie mechanism is an advantage over VXLAN and nvgre I believe, but
why limit it to 32 bits? 64 bits is much stronger, and at some point
we might even want 128 bits to do strong authentication.

Some more general questions applicable to this and some other proposals.

- "TNI field"-- this seems to use the same 24 bit left shifted format
of nvgre and VXLAN. I still don't see the rationale for this! Why
can't the full 32 bit field be allocated for vni? A large deployment
will be using various levels of hierarchical allocation and possibly
obfuscation of vni (TNI). The nvo3 requirements on this are vague
("100's of thousands of virtual networks"), but they clearly don't
expect this the VNI to be a simple flat space either.
[Frank] : It=92s an issue existing a long time. I have no personal preferen=
ce on it. It totally depends on real requirement.



- "Outer Ethernet Header"-- showing the outer Ethernet header in L3
encapsulations examples is not necessary, use of Ethernet is not a
requirement, and this is potentially very misleading. For instance,
the outer Ethernet FCS does *not* protect the packet end to end in an
L3 routed network. Personally, I think it would be more illustrative
to show the IP packet in the inner Ethernet frame instead to see how
its alignment is affected.
[Frank] : Actually, It=92s only a encapsulation example. But your comment i=
s right. We will correct in the next version. Thanks!


Thanks,
Tom


B.R.
Frank


-----Original Message-----
From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> [mailto:int=
ernet-drafts@ietf.org]
Sent: Thursday, April 10, 2014 11:22 AM
To: Xialiang (Frank); Zhen Cao; Fanduoliang; Zehn Cao; Namgon Kim; Namgon
Kim; Fanduoliang; Xialiang (Frank)
Subject: New Version Notification for draft-fan-l2tp-vp-01.txt


A new version of I-D, draft-fan-l2tp-vp-01.txt has been successfully submit=
ted
by Liang Xia and posted to the IETF repository.

Name:         draft-fan-l2tp-vp
Revision:     01
Title:                L2TP-VP: Layer Two Tunneling Protocol - Virtualizatio=
n Profile
Document date:        2014-04-10
Group:                Individual Submission
Pages:                9
URL:
http://www.ietf.org/internet-drafts/draft-fan-l2tp-vp-01.txt
Status:         https://datatracker.ietf.org/doc/draft-fan-l2tp-vp/
Htmlized:       http://tools.ietf.org/html/draft-fan-l2tp-vp-01
Diff:           http://www.ietf.org/rfcdiff?url2=3Ddraft-fan-l2tp-vp-01

Abstract:
  This document describes Layer Two Tunneling Protocol (L2TP)'s
  virtualization profile (L2TP-VP), which reuses session header of L2TP
  data message to securely support overlay networks for multiple
  tenants, and simplifies tunnel setup by disabling all kinds of L2TP
  control messages.




Please note that it may take a couple of minutes from the time of submissio=
n
until the htmlized version and diff are available at tools.ietf.org<http://=
tools.ietf.org/>.

The IETF Secretariat

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

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

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


--_000_088D92B91E8F438297986B57A94B3FA4ciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <AE974A3BA32D0A448A29B6A5F2930528@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;">
Frank,
<div><br>
</div>
<div>Please see inline.</div>
<div><br>
<div>
<div>On Apr 11, 2014, at 6:01 AM, Xialiang (Frank) &lt;<a href=3D"mailto:fr=
ank.xialiang@huawei.com">frank.xialiang@huawei.com</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div lang=3D"ZH-CN" link=3D"blue" vlink=3D"purple" style=3D"font-family: He=
lvetica; font-size: 12px; font-style: normal; font-variant: normal; font-we=
ight: normal; letter-spacing: normal; line-height: normal; orphans: auto; t=
ext-align: start; text-indent: 0px; text-transform: none; white-space: norm=
al; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<div class=3D"WordSection1" style=3D"page: WordSection1;">
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US" style=3D"font-size: 10.5pt; font-family: Calibri, sans=
-serif; color: rgb(31, 73, 125);">Hi Tom, Carlos,<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US" style=3D"font-size: 10.5pt; font-family: Calibri, sans=
-serif; color: rgb(31, 73, 125);">Thanks for your comments, please see my r=
esponse inline:<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US" style=3D"font-size: 10.5pt; font-family: Calibri, sans=
-serif; color: rgb(31, 73, 125);">&nbsp;</span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US" style=3D"font-size: 10.5pt; font-family: Calibri, sans=
-serif; color: rgb(31, 73, 125);">B.R.<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US" style=3D"font-size: 10.5pt; font-family: Calibri, sans=
-serif; color: rgb(31, 73, 125);">Frank<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US" style=3D"font-size: 10.5pt; font-family: Calibri, sans=
-serif; color: rgb(31, 73, 125);">&nbsp;</span></div>
<div style=3D"border-style: none none none solid; border-left-color: blue; =
border-left-width: 1.5pt; padding: 0cm 0cm 0cm 4pt; position: static; z-ind=
ex: auto;">
<div>
<div style=3D"border-style: solid none none; border-top-color: rgb(181, 196=
, 223); border-top-width: 1pt; padding: 3pt 0cm 0cm;">
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<b><span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: Tahoma, sans=
-serif;">From:</span></b><span lang=3D"EN-US" style=3D"font-size: 10pt; fon=
t-family: Tahoma, sans-serif;"><span class=3D"Apple-converted-space">&nbsp;=
</span>nvo3 [<a href=3D"mailto:nvo3-bounces@ietf.org" style=3D"color: purpl=
e; text-decoration: underline;">mailto:nvo3-bounces@ietf.org</a>]<span clas=
s=3D"Apple-converted-space">&nbsp;</span><b>On
 Behalf Of<span class=3D"Apple-converted-space">&nbsp;</span></b>Carlos Pig=
nataro (cpignata)<br>
<b>Sent:</b><span class=3D"Apple-converted-space">&nbsp;</span>Friday, Apri=
l 11, 2014 1:09 AM<br>
<b>To:</b><span class=3D"Apple-converted-space">&nbsp;</span>Tom Herbert<br=
>
<b>Cc:</b><span class=3D"Apple-converted-space">&nbsp;</span><a href=3D"mai=
lto:l2tpext@ietf.org" style=3D"color: purple; text-decoration: underline;">=
l2tpext@ietf.org</a>; Namgon Kim; Fanduoliang;<span class=3D"Apple-converte=
d-space">&nbsp;</span><a href=3D"mailto:nvo3@ietf.org" style=3D"color: purp=
le; text-decoration: underline;">nvo3@ietf.org</a>;
 Xialiang (Frank); Zehn Cao<br>
<b>Subject:</b><span class=3D"Apple-converted-space">&nbsp;</span>Re: [nvo3=
] New Version Notification for draft-fan-l2tp-vp-01.txt<o:p></o:p></span></=
div>
</div>
</div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US">&nbsp;</span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US">Frank, Tom,<o:p></o:p></span></div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US">&nbsp;</span></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US">Please find some additional comments inline, L2TPExt c=
hair hat off.<o:p></o:p></span></div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US">&nbsp;</span></div>
<div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US">On Apr 10, 2014, at 11:46 AM, Tom Herbert &lt;<a href=
=3D"mailto:therbert@google.com" style=3D"color: purple; text-decoration: un=
derline;">therbert@google.com</a>&gt; wrote:<o:p></o:p></span></div>
</div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US"><br>
<br>
<o:p></o:p></span></div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US" style=3D"font-size: 9pt;">On Wed, Apr 9, 2014 at 8:37 =
PM, Xialiang (Frank)<br>
&lt;<a href=3D"mailto:frank.xialiang@huawei.com" style=3D"color: purple; te=
xt-decoration: underline;">frank.xialiang@huawei.com</a>&gt; wrote:<br>
<br>
<o:p></o:p></span></div>
<p class=3D"MsoNormal" style=3D"margin: 0cm 0cm 12pt; font-size: 12pt; font=
-family: 'Times New Roman', serif;">
<span lang=3D"EN-US" style=3D"font-size: 9pt;">Hi folks,<br>
We have updated the L2TP-VP version -01 draft.<br>
In the new version draft, we add the motivation of this draft and modificat=
ion to the format of L2TP-VP header.<br>
Welcome your comments and suggestions!<o:p></o:p></span></p>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US" style=3D"font-size: 9pt;">Hi Frank,<br>
<br>
Thanks for posting. A few comments:<br>
<br>
- This is so dramatically different from L2TP I wonder if it can still<br>
honestly be called L2TP. Have you implemented this? How much of L2TP<br>
stack can be leveraged?<br>
- &quot;Session ID is changed to a 31-bit field&quot;-- doesn't this break =
L2TP then?</span><span lang=3D"EN-US" style=3D"font-size: 9pt;"><o:p></o:p>=
</span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<b><i><span lang=3D"EN-US" style=3D"font-size: 10.5pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">[Frank] : The main differences we=
=92ve made are:<o:p></o:p></span></i></b></div>
<div style=3D"margin: 0cm 0cm 0.0001pt 18pt; text-indent: -18pt; font-size:=
 12pt; font-family: 'Times New Roman', serif;">
<b><i><span lang=3D"EN-US" style=3D"font-size: 10.5pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);"><span>1.<span style=3D"font-style: =
normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-hei=
ght: normal; font-family: 'Times New Roman';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span></span></span></s=
pan></i></b><span lang=3D"EN-US" style=3D"font-size: 10.5pt; font-family: C=
alibri, sans-serif; color: rgb(31, 73, 125);">Session
 ID is changed to 31-bit: that=92s because we need the most significant bit=
 for differentiating &nbsp;L2TPv3 packets with L2TP-VP packets in data plan=
e. The only disadvantage is to limit the session ID scope for existing L2TP=
v3 protocol to &lt; 2 ^ 31, but that scope
 is large enough to be used for L2TPv3 session in practice;<o:p></o:p></spa=
n></div>
<div style=3D"margin: 0cm 0cm 0.0001pt 18pt; text-indent: -18pt; font-size:=
 12pt; font-family: 'Times New Roman', serif;">
<b><i><span lang=3D"EN-US" style=3D"font-size: 10.5pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);"><span>2.<span style=3D"font-style: =
normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-hei=
ght: normal; font-family: 'Times New Roman';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span></span></span></s=
pan></i></b><span lang=3D"EN-US" style=3D"font-size: 10.5pt; font-family: C=
alibri, sans-serif; color: rgb(31, 73, 125);">We
 reuse first 32 bit of cookie field to the TNI, the left 32 bit is still us=
ed for cookie field. This indeed limit the cookie mechanism=92s capability.=
 In next version of the draft, we will solve this problem.<o:p></o:p></span=
></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US" style=3D"font-size: 10.5pt; font-family: Calibri, sans=
-serif; color: rgb(31, 73, 125);">Except the above, we do not change anythi=
ng of L2TPv3.</span></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>I will say that both things are a non-starter. You can appreciate it's=
 not only 31 vs 32 bits. As it was already pointed out, you cannot differen=
tiate an L2TPv3 packet with the MSB set. Regarding the cookie, please read =
RFC 3931 on the discussion of 32
 vs. 64 bits.</div>
<div><br>
</div>
<div>Best,</div>
<div><br>
</div>
<div>Carlos.</div>
<br>
<blockquote type=3D"cite">
<div lang=3D"ZH-CN" link=3D"blue" vlink=3D"purple" style=3D"font-family: He=
lvetica; font-size: 12px; font-style: normal; font-variant: normal; font-we=
ight: normal; letter-spacing: normal; line-height: normal; orphans: auto; t=
ext-align: start; text-indent: 0px; text-transform: none; white-space: norm=
al; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<div class=3D"WordSection1" style=3D"page: WordSection1;">
<div style=3D"border-style: none none none solid; border-left-color: blue; =
border-left-width: 1.5pt; padding: 0cm 0cm 0cm 4pt; position: static; z-ind=
ex: auto;">
<div>
<div>
<div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US" style=3D"font-size: 10.5pt; font-family: Calibri, sans=
-serif; color: rgb(31, 73, 125);">What we currently do is to reuse L2TPv3 f=
or multi-tenant network scenarios, but keep its implementation separating f=
rom existed L2TPv3 implementation in
 data plane clearly.<o:p></o:p></span></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US">&nbsp;</span></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US">These two bullet points are critical. A &quot;profile&=
quot; of protocol is a constrained subset of it, within an applicability co=
ntext. What this document shows is not a profile.&nbsp;<o:p></o:p></span></=
div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US">&nbsp;</span></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US">The most-significant bit of the Session ID being used =
for something else (&quot;Modified bit&quot;) has two implications:<o:p></o=
:p></span></div>
</div>
<div>
<ol start=3D"1" type=3D"1" style=3D"margin-bottom: 0cm;">
<li class=3D"MsoNormal" style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt;=
 font-family: 'Times New Roman', serif;">
<span lang=3D"EN-US">This is not a profile, it's an attempt to redefine L2T=
Pv3.<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"margin: 0cm 0cm=
 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;">
<span lang=3D"EN-US">This non-profile draft describes a non-backwards compa=
tible protocol. Meaning, L2TPv3's Session ID allows for Session IDs with th=
e MSB set. Consequently, a packet cannot be differentiated between L2TPv3 a=
nd this other protocol (which is not
 a profile).<o:p></o:p></span></li><li class=3D"MsoNormal" style=3D"margin:=
 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"=
>
<span lang=3D"EN-US">It breaks L2TPv3.<o:p></o:p></span></li></ol>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US">OK, I lied, three (or possibly more) implications :-)<=
o:p></o:p></span></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US">&nbsp;</span></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US">The remaining points are subordinate to this high-orde=
r bit (no pun intended).</span><span lang=3D"EN-US"><o:p></o:p></span></div=
>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<b><i><span lang=3D"EN-US" style=3D"font-size: 10.5pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">[Frank] : I think we can consider t=
he relationship between L2TP-VP and L2TPv3 as the same thing of relationshi=
p between MPLS-TP and MPLS.</span></i></b><span lang=3D"EN-US" style=3D"fon=
t-size: 10.5pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"=
><o:p></o:p></span></div>
</div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US"><br>
<br>
<o:p></o:p></span></div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US" style=3D"font-size: 9pt;">- &quot;Type field&quot;-- I=
 suspect this is meant to be an EtherType value.<br>
Please be explicit about this.<br>
- To get hashing (for ECMP, RSS, etc.) in the network we'd almost<br>
certainly use L2TP over UDP, so L2TP-VP should probably have a format<br>
defined for use with UDP.<o:p></o:p></span></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US">&nbsp;</span></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US">There's also hashing for L2TPv3 directly over IP (e.g.=
, RFC&nbsp;5640)<o:p></o:p></span></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<b><i><span lang=3D"EN-US" style=3D"font-size: 10.5pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">[Frank] : Agree with all your comme=
nts. In current draft, we only specifies L2TP-VP over IP. We indeed have co=
nsidered L2TP-VP over UDP and can add
 this part of content in next version if necessary.</span></i></b><span lan=
g=3D"EN-US" style=3D"font-size: 10.5pt; font-family: Calibri, sans-serif; c=
olor: rgb(31, 73, 125);"><o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US">&nbsp;</span></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US">Thanks,<o:p></o:p></span></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US">&nbsp;</span></div>
</div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US">Carlos.<o:p></o:p></span></div>
</div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US"><br>
<br>
<o:p></o:p></span></div>
<div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US" style=3D"font-size: 9pt;">- Even with Type field, this=
 still suffers from the same problem L2TP<br>
has that network devices won't be able to parse the packet beyond the<br>
L2TP header (the cookie field makes the header variable length). This<br>
eliminates the ability to implement the protocol with LRO for<br>
instance. I suggest you take four or five bits from reserved section<br>
for header length to resolve this (see example in GUE).</span><span lang=3D=
"EN-US" style=3D"font-size: 9pt; color: rgb(31, 73, 125);"><o:p></o:p></spa=
n></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<b><i><span lang=3D"EN-US" style=3D"font-size: 10.5pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">[Frank] : good comments. Will consi=
der it~~<o:p></o:p></span></i></b></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US" style=3D"font-size: 9pt;"><br>
- Cookie mechanism is an advantage over VXLAN and nvgre I believe, but<br>
why limit it to 32 bits? 64 bits is much stronger, and at some point<br>
we might even want 128 bits to do strong authentication.<br>
<br>
Some more general questions applicable to this and some other proposals.<br=
>
<br>
- &quot;TNI field&quot;-- this seems to use the same 24 bit left shifted fo=
rmat<br>
of nvgre and VXLAN. I still don't see the rationale for this! Why<br>
can't the full 32 bit field be allocated for vni? A large deployment<br>
will be using various levels of hierarchical allocation and possibly<br>
obfuscation of vni (TNI). The nvo3 requirements on this are vague<br>
(&quot;100's of thousands of virtual networks&quot;), but they clearly don'=
t<br>
expect this the VNI to be a simple flat space either.</span><span lang=3D"E=
N-US" style=3D"font-size: 9pt; color: rgb(31, 73, 125);"><o:p></o:p></span>=
</div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<b><i><span lang=3D"EN-US" style=3D"font-size: 10.5pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">[Frank] : It=92s an issue existing =
a long time. I have no personal preference on it. It totally depends on rea=
l requirement.</span></i></b><span lang=3D"EN-US" style=3D"font-size: 10.5p=
t; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p></o:p><=
/span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US" style=3D"font-size: 9pt; color: rgb(31, 73, 125);">&nb=
sp;</span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US" style=3D"font-size: 9pt; color: rgb(31, 73, 125);">&nb=
sp;</span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US" style=3D"font-size: 9pt;"><br>
- &quot;Outer Ethernet Header&quot;-- showing the outer Ethernet header in =
L3<br>
encapsulations examples is not necessary, use of Ethernet is not a<br>
requirement, and this is potentially very misleading. For instance,<br>
the outer Ethernet FCS does *not* protect the packet end to end in an<br>
L3 routed network. Personally, I think it would be more illustrative<br>
to show the IP packet in the inner Ethernet frame instead to see how<br>
its alignment is affected.</span><span lang=3D"EN-US" style=3D"font-size: 9=
pt; color: rgb(31, 73, 125);"><o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<b><i><span lang=3D"EN-US" style=3D"font-size: 10.5pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">[Frank] : Actually, It=92s only a e=
ncapsulation example. But your comment is right. We will correct in the nex=
t version. Thanks!<o:p></o:p></span></i></b></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US" style=3D"font-size: 9pt;"><br>
<br>
Thanks,<br>
Tom<br>
<br>
<br>
<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US" style=3D"font-size: 9pt;">B.R.<br>
Frank<br>
<br>
<br>
<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US" style=3D"font-size: 9pt;">-----Original Message-----<b=
r>
From:<span class=3D"Apple-converted-space">&nbsp;</span><a href=3D"mailto:i=
nternet-drafts@ietf.org" style=3D"color: purple; text-decoration: underline=
;">internet-drafts@ietf.org</a><span class=3D"Apple-converted-space">&nbsp;=
</span>[<a href=3D"mailto:internet-drafts@ietf.org" style=3D"color: purple;=
 text-decoration: underline;">mailto:internet-drafts@ietf.org</a>]<br>
Sent: Thursday, April 10, 2014 11:22 AM<br>
To: Xialiang (Frank); Zhen Cao; Fanduoliang; Zehn Cao; Namgon Kim; Namgon<b=
r>
Kim; Fanduoliang; Xialiang (Frank)<br>
Subject: New Version Notification for draft-fan-l2tp-vp-01.txt<br>
<br>
<br>
A new version of I-D, draft-fan-l2tp-vp-01.txt has been successfully submit=
ted<br>
by Liang Xia and posted to the IETF repository.<br>
<br>
Name: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;draft-fan-l2tp-vp<br>
Revision: &nbsp;&nbsp;&nbsp;&nbsp;01<br>
Title: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;L2TP-VP: Layer Two Tunneling Protocol - Virtualizatio=
n Profile<br>
Document date: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2014-04-10<br>
Group: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;Individual Submission<br>
Pages: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;9<br>
URL:<br>
<a href=3D"http://www.ietf.org/internet-drafts/draft-fan-l2tp-vp-01.txt" st=
yle=3D"color: purple; text-decoration: underline;">http://www.ietf.org/inte=
rnet-drafts/draft-fan-l2tp-vp-01.txt</a><br>
Status: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"https://=
datatracker.ietf.org/doc/draft-fan-l2tp-vp/" style=3D"color: purple; text-d=
ecoration: underline;">https://datatracker.ietf.org/doc/draft-fan-l2tp-vp/<=
/a><br>
Htmlized: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"http://tools.ietf.=
org/html/draft-fan-l2tp-vp-01" style=3D"color: purple; text-decoration: und=
erline;">http://tools.ietf.org/html/draft-fan-l2tp-vp-01</a><br>
Diff: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href=
=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-fan-l2tp-vp-01" style=3D"color=
: purple; text-decoration: underline;">http://www.ietf.org/rfcdiff?url2=3Dd=
raft-fan-l2tp-vp-01</a><br>
<br>
Abstract:<br>
&nbsp;&nbsp;This document describes Layer Two Tunneling Protocol (L2TP)'s<b=
r>
&nbsp;&nbsp;virtualization profile (L2TP-VP), which reuses session header o=
f L2TP<br>
&nbsp;&nbsp;data message to securely support overlay networks for multiple<=
br>
&nbsp;&nbsp;tenants, and simplifies tunnel setup by disabling all kinds of =
L2TP<br>
&nbsp;&nbsp;control messages.<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at<span class=3D"Apple-co=
nverted-space">&nbsp;</span><a href=3D"http://tools.ietf.org/" style=3D"col=
or: purple; text-decoration: underline;">tools.ietf.org</a>.<br>
<br>
The IETF Secretariat<o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US" style=3D"font-size: 9pt;"><br>
_______________________________________________<br>
nvo3 mailing list<br>
<a href=3D"mailto:nvo3@ietf.org" style=3D"color: purple; text-decoration: u=
nderline;">nvo3@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/nvo3" style=3D"color: purp=
le; text-decoration: underline;">https://www.ietf.org/mailman/listinfo/nvo3=
</a><o:p></o:p></span></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US" style=3D"font-size: 9pt;"><br>
_______________________________________________<br>
nvo3 mailing list<br>
<a href=3D"mailto:nvo3@ietf.org" style=3D"color: purple; text-decoration: u=
nderline;">nvo3@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/nvo3" style=3D"color: purp=
le; text-decoration: underline;">https://www.ietf.org/mailman/listinfo/nvo3=
</a><o:p></o:p></span></div>
</div>
</div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: 'Time=
s New Roman', serif;">
<span lang=3D"EN-US">&nbsp;</span></div>
</div>
</div>
</div>
</div>
_______________________________________________<br>
L2tpext mailing list<br>
<a href=3D"mailto:L2tpext@ietf.org" style=3D"color: purple; text-decoration=
: underline;">L2tpext@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/l2tpext" style=3D"color: p=
urple; text-decoration: underline;">https://www.ietf.org/mailman/listinfo/l=
2tpext</a></div>
</blockquote>
</div>
<br>
</div>
</body>
</html>

--_000_088D92B91E8F438297986B57A94B3FA4ciscocom_--

