
From nobody Sun May  7 14:13:38 2017
Return-Path: <cpignata@cisco.com>
X-Original-To: l2tpext@ietfa.amsl.com
Delivered-To: l2tpext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEB9612714F; Sun,  7 May 2017 14:13:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 uX9ergKjNl5V; Sun,  7 May 2017 14:13:35 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 06934124E15; Sun,  7 May 2017 14:13:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16182; q=dns/txt; s=iport; t=1494191614; x=1495401214; h=from:to:cc:subject:date:message-id:references: mime-version; bh=9DQtLqhVjO8znyvGwDY/gLXfLnGCKWSWdA3azDM7q0M=; b=cCGyq+z+7d5uao18CxTFY38brso32r/+mcMwfS5PPE7MSukQlYAvQ4BO cCGlFBLxAtR1nFj7DbRVqYW1LWzqejKyDrDeSs1P2WJ0VJ0jw4wy/JiWj DIN0mn4jM1DA+KSTO4ib2UtKZoVcz9v8yUHd6rm3Qmo6GhO7aSNLCatnC I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A2AgCpjA9Z/4QNJK1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1VigQwHg2GKGJEzIZA6hTiCDyEBCoV4AhqELz8YAQIBAQEBAQE?= =?us-ascii?q?Bax0LhRUBAgEDAQEhKysQAgEZAwECDRsDAgICJQoBFAcCCAIEDgUUBwIEiX8Or?= =?us-ascii?q?z6CJopdAQEBAQEBAQEBAQEBAQEBAQEBAQEBGAWGX4IJC4JlgTyDCD8WglQugjE?= =?us-ascii?q?FnXkBhxuLfIIEhTyKLIh8i0EBHziBCnAVHDwBhG2Bc3aGdYEhgQ0BAQE?=
X-IronPort-AV: E=Sophos;i="5.38,305,1491264000";  d="scan'208,217";a="245347262"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 07 May 2017 21:13:33 +0000
Received: from XCH-RTP-017.cisco.com (xch-rtp-017.cisco.com [64.101.220.157]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id v47LDXdx007188 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 7 May 2017 21:13:34 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-017.cisco.com (64.101.220.157) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sun, 7 May 2017 17:13:33 -0400
Received: from xch-rtp-020.cisco.com ([64.101.220.160]) by XCH-RTP-020.cisco.com ([64.101.220.160]) with mapi id 15.00.1210.000; Sun, 7 May 2017 17:13:33 -0400
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: "l2tpext@ietf.org" <l2tpext@ietf.org>
CC: "draft-ietf-l2tpext-keyed-ipv6-tunnel@ietf.org" <draft-ietf-l2tpext-keyed-ipv6-tunnel@ietf.org>
Thread-Topic: RFC 8159 on Keyed IPv6 Tunnel
Thread-Index: AQHSxhsgQkwVManIgU61vzhM//Xo1Q==
Date: Sun, 7 May 2017 21:13:32 +0000
Message-ID: <3D0630CE-8073-46E1-B2D5-11444E8B2DD4@cisco.com>
References: <20170506034350.64F26B80EB0@rfc-editor.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.117.115.52]
Content-Type: multipart/alternative; boundary="_000_3D0630CE807346E1B2D511444E8B2DD4ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2tpext/NztvlSCYndpFhvE-Wvd2k8XnZCo>
Subject: [L2tpext] Fwd: RFC 8159 on Keyed IPv6 Tunnel
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 07 May 2017 21:13:38 -0000

--_000_3D0630CE807346E1B2D511444E8B2DD4ciscocom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

Q29uZ3JhdHVsYXRpb25zIEwydHBleHQgb24gYW5vdGhlciBSRkMgcHVibGlzaGVkIQ0KDQrigJQg
Q2FybG9zLg0KDQpCZWdpbiBmb3J3YXJkZWQgbWVzc2FnZToNCg0KRnJvbTogcmZjLWVkaXRvckBy
ZmMtZWRpdG9yLm9yZzxtYWlsdG86cmZjLWVkaXRvckByZmMtZWRpdG9yLm9yZz4NClN1YmplY3Q6
IFJGQyA4MTU5IG9uIEtleWVkIElQdjYgVHVubmVsDQpEYXRlOiBNYXkgNSwgMjAxNyBhdCAxMTo0
Mzo1MCBQTSBFRFQNClRvOiBpZXRmLWFubm91bmNlQGlldGYub3JnPG1haWx0bzppZXRmLWFubm91
bmNlQGlldGYub3JnPiwgcmZjLWRpc3RAcmZjLWVkaXRvci5vcmc8bWFpbHRvOnJmYy1kaXN0QHJm
Yy1lZGl0b3Iub3JnPg0KQ2M6IGRyYWZ0cy11cGRhdGUtcmVmQGlhbmEub3JnPG1haWx0bzpkcmFm
dHMtdXBkYXRlLXJlZkBpYW5hLm9yZz4sIHJmYy1lZGl0b3JAcmZjLWVkaXRvci5vcmc8bWFpbHRv
OnJmYy1lZGl0b3JAcmZjLWVkaXRvci5vcmc+DQpSZXBseS1UbzogaWV0ZkBpZXRmLm9yZzxtYWls
dG86aWV0ZkBpZXRmLm9yZz4NCg0KQSBuZXcgUmVxdWVzdCBmb3IgQ29tbWVudHMgaXMgbm93IGF2
YWlsYWJsZSBpbiBvbmxpbmUgUkZDIGxpYnJhcmllcy4NCg0KDQogICAgICAgUkZDIDgxNTkNCg0K
ICAgICAgIFRpdGxlOiAgICAgIEtleWVkIElQdjYgVHVubmVsDQogICAgICAgQXV0aG9yOiAgICAg
TS4gS29uc3RhbnR5bm93aWN6LCBFZC4sDQogICAgICAgICAgICAgICAgICAgRy4gSGVyb24sIEVk
LiwNCiAgICAgICAgICAgICAgICAgICBSLiBTY2hhdHptYXlyLA0KICAgICAgICAgICAgICAgICAg
IFcuIEhlbmRlcmlja3gNCiAgICAgICBTdGF0dXM6ICAgICBTdGFuZGFyZHMgVHJhY2sNCiAgICAg
ICBTdHJlYW06ICAgICBJRVRGDQogICAgICAgRGF0ZTogICAgICAgTWF5IDIwMTcNCiAgICAgICBN
YWlsYm94OiAgICBtYWNpZWtAY2lzY28uY29tPG1haWx0bzptYWNpZWtAY2lzY28uY29tPiwNCiAg
ICAgICAgICAgICAgICAgICBnaWhlcm9uQGNpc2NvLmNvbTxtYWlsdG86Z2loZXJvbkBjaXNjby5j
b20+LA0KICAgICAgICAgICAgICAgICAgIHJhaW5lci5zY2hhdHptYXlyQHRlbGVrb20uZGU8bWFp
bHRvOnJhaW5lci5zY2hhdHptYXlyQHRlbGVrb20uZGU+LA0KICAgICAgICAgICAgICAgICAgIHdp
bS5oZW5kZXJpY2t4QGFsY2F0ZWwtbHVjZW50LmNvbTxtYWlsdG86d2ltLmhlbmRlcmlja3hAYWxj
YXRlbC1sdWNlbnQuY29tPg0KICAgICAgIFBhZ2VzOiAgICAgIDEyDQogICAgICAgQ2hhcmFjdGVy
czogMjczMDINCiAgICAgICBVcGRhdGVzL09ic29sZXRlcy9TZWVBbHNvOiAgIE5vbmUNCg0KICAg
ICAgIEktRCBUYWc6ICAgIGRyYWZ0LWlldGYtbDJ0cGV4dC1rZXllZC1pcHY2LXR1bm5lbC0wNy50
eHQNCg0KICAgICAgIFVSTDogICAgICAgIGh0dHBzOi8vd3d3LnJmYy1lZGl0b3Iub3JnL2luZm8v
cmZjODE1OQ0KDQogICAgICAgRE9JOiAgICAgICAgMTAuMTc0ODcvUkZDODE1OQ0KDQpUaGlzIGRv
Y3VtZW50IGRlc2NyaWJlcyBhIHR1bm5lbCBlbmNhcHN1bGF0aW9uIGZvciBFdGhlcm5ldCBvdmVy
IElQdjYNCndpdGggYSBtYW5kYXRvcnkgNjQtYml0IGNvb2tpZSBmb3IgY29ubmVjdGluZyBMYXll
ciAyIChMMikgRXRoZXJuZXQNCmF0dGFjaG1lbnQgY2lyY3VpdHMgaWRlbnRpZmllZCBieSBJUHY2
IGFkZHJlc3Nlcy4gIFRoZSBlbmNhcHN1bGF0aW9uDQppcyBiYXNlZCBvbiB0aGUgTGF5ZXIgMiBU
dW5uZWxpbmcgUHJvdG9jb2wgVmVyc2lvbiAzIChMMlRQdjMpIG92ZXIgSVANCmFuZCBkb2VzIG5v
dCB1c2UgdGhlIEwyVFB2MyBjb250cm9sIHBsYW5lLg0KDQpUaGlzIGRvY3VtZW50IGlzIGEgcHJv
ZHVjdCBvZiB0aGUgTGF5ZXIgVHdvIFR1bm5lbGluZyBQcm90b2NvbCBFeHRlbnNpb25zIFdvcmtp
bmcgR3JvdXAgb2YgdGhlIElFVEYuDQoNClRoaXMgaXMgbm93IGEgUHJvcG9zZWQgU3RhbmRhcmQu
DQoNClNUQU5EQVJEUyBUUkFDSzogVGhpcyBkb2N1bWVudCBzcGVjaWZpZXMgYW4gSW50ZXJuZXQg
U3RhbmRhcmRzIFRyYWNrDQpwcm90b2NvbCBmb3IgdGhlIEludGVybmV0IGNvbW11bml0eSwgYW5k
IHJlcXVlc3RzIGRpc2N1c3Npb24gYW5kIHN1Z2dlc3Rpb25zDQpmb3IgaW1wcm92ZW1lbnRzLiAg
UGxlYXNlIHJlZmVyIHRvIHRoZSBjdXJyZW50IGVkaXRpb24gb2YgdGhlIE9mZmljaWFsDQpJbnRl
cm5ldCBQcm90b2NvbCBTdGFuZGFyZHMgKGh0dHBzOi8vd3d3LnJmYy1lZGl0b3Iub3JnL3N0YW5k
YXJkcykgZm9yIHRoZQ0Kc3RhbmRhcmRpemF0aW9uIHN0YXRlIGFuZCBzdGF0dXMgb2YgdGhpcyBw
cm90b2NvbC4gIERpc3RyaWJ1dGlvbiBvZiB0aGlzDQptZW1vIGlzIHVubGltaXRlZC4NCg0KVGhp
cyBhbm5vdW5jZW1lbnQgaXMgc2VudCB0byB0aGUgSUVURi1Bbm5vdW5jZSBhbmQgcmZjLWRpc3Qg
bGlzdHMuDQpUbyBzdWJzY3JpYmUgb3IgdW5zdWJzY3JpYmUsIHNlZQ0KIGh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vaWV0Zi1hbm5vdW5jZQ0KIGh0dHBzOi8vbWFpbG1hbi5y
ZmMtZWRpdG9yLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3JmYy1kaXN0DQoNCkZvciBzZWFyY2hpbmcg
dGhlIFJGQyBzZXJpZXMsIHNlZSBodHRwczovL3d3dy5yZmMtZWRpdG9yLm9yZy9zZWFyY2gNCkZv
ciBkb3dubG9hZGluZyBSRkNzLCBzZWUgaHR0cHM6Ly93d3cucmZjLWVkaXRvci5vcmcvcmV0cmll
dmUvYnVsaw0KDQpSZXF1ZXN0cyBmb3Igc3BlY2lhbCBkaXN0cmlidXRpb24gc2hvdWxkIGJlIGFk
ZHJlc3NlZCB0byBlaXRoZXIgdGhlDQphdXRob3Igb2YgdGhlIFJGQyBpbiBxdWVzdGlvbiwgb3Ig
dG8gcmZjLWVkaXRvckByZmMtZWRpdG9yLm9yZzxtYWlsdG86cmZjLWVkaXRvckByZmMtZWRpdG9y
Lm9yZz4uICBVbmxlc3MNCnNwZWNpZmljYWxseSBub3RlZCBvdGhlcndpc2Ugb24gdGhlIFJGQyBp
dHNlbGYsIGFsbCBSRkNzIGFyZSBmb3INCnVubGltaXRlZCBkaXN0cmlidXRpb24uDQoNCg0KVGhl
IFJGQyBFZGl0b3IgVGVhbQ0KQXNzb2NpYXRpb24gTWFuYWdlbWVudCBTb2x1dGlvbnMsIExMQw0K
DQoNCg0K

--_000_3D0630CE807346E1B2D511444E8B2DD4ciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <19626C3B2045234F97CCA7A0D6C53D9B@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KQ29uZ3JhdHVsYXRpb25zIEwydHBl
eHQgb24gYW5vdGhlciBSRkMgcHVibGlzaGVkIQ0KPGRpdiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+
DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+4oCUIENhcmxvcy48YnIgY2xhc3M9IiI+DQo8ZGl2Pjxi
ciBjbGFzcz0iIj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPg0KPGRpdiBjbGFz
cz0iIj5CZWdpbiBmb3J3YXJkZWQgbWVzc2FnZTo8L2Rpdj4NCjxiciBjbGFzcz0iQXBwbGUtaW50
ZXJjaGFuZ2UtbmV3bGluZSI+DQo8ZGl2IHN0eWxlPSJtYXJnaW4tdG9wOiAwcHg7IG1hcmdpbi1y
aWdodDogMHB4OyBtYXJnaW4tYm90dG9tOiAwcHg7IG1hcmdpbi1sZWZ0OiAwcHg7IiBjbGFzcz0i
Ij4NCjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTogLXdlYmtpdC1zeXN0ZW0tZm9udCwgSGVsdmV0
aWNhIE5ldWUsIEhlbHZldGljYSwgc2Fucy1zZXJpZjsgY29sb3I6cmdiYSgwLCAwLCAwLCAxLjAp
OyIgY2xhc3M9IiI+PGIgY2xhc3M9IiI+RnJvbToNCjwvYj48L3NwYW4+PHNwYW4gc3R5bGU9ImZv
bnQtZmFtaWx5OiAtd2Via2l0LXN5c3RlbS1mb250LCBIZWx2ZXRpY2EgTmV1ZSwgSGVsdmV0aWNh
LCBzYW5zLXNlcmlmOyIgY2xhc3M9IiI+PGEgaHJlZj0ibWFpbHRvOnJmYy1lZGl0b3JAcmZjLWVk
aXRvci5vcmciIGNsYXNzPSIiPnJmYy1lZGl0b3JAcmZjLWVkaXRvci5vcmc8L2E+PGJyIGNsYXNz
PSIiPg0KPC9zcGFuPjwvZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2luLXRvcDogMHB4OyBtYXJnaW4t
cmlnaHQ6IDBweDsgbWFyZ2luLWJvdHRvbTogMHB4OyBtYXJnaW4tbGVmdDogMHB4OyIgY2xhc3M9
IiI+DQo8c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6IC13ZWJraXQtc3lzdGVtLWZvbnQsIEhlbHZl
dGljYSBOZXVlLCBIZWx2ZXRpY2EsIHNhbnMtc2VyaWY7IGNvbG9yOnJnYmEoMCwgMCwgMCwgMS4w
KTsiIGNsYXNzPSIiPjxiIGNsYXNzPSIiPlN1YmplY3Q6DQo8L2I+PC9zcGFuPjxzcGFuIHN0eWxl
PSJmb250LWZhbWlseTogLXdlYmtpdC1zeXN0ZW0tZm9udCwgSGVsdmV0aWNhIE5ldWUsIEhlbHZl
dGljYSwgc2Fucy1zZXJpZjsiIGNsYXNzPSIiPjxiIGNsYXNzPSIiPlJGQyA4MTU5IG9uIEtleWVk
IElQdjYgVHVubmVsPC9iPjxiciBjbGFzcz0iIj4NCjwvc3Bhbj48L2Rpdj4NCjxkaXYgc3R5bGU9
Im1hcmdpbi10b3A6IDBweDsgbWFyZ2luLXJpZ2h0OiAwcHg7IG1hcmdpbi1ib3R0b206IDBweDsg
bWFyZ2luLWxlZnQ6IDBweDsiIGNsYXNzPSIiPg0KPHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiAt
d2Via2l0LXN5c3RlbS1mb250LCBIZWx2ZXRpY2EgTmV1ZSwgSGVsdmV0aWNhLCBzYW5zLXNlcmlm
OyBjb2xvcjpyZ2JhKDAsIDAsIDAsIDEuMCk7IiBjbGFzcz0iIj48YiBjbGFzcz0iIj5EYXRlOg0K
PC9iPjwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6IC13ZWJraXQtc3lzdGVtLWZvbnQs
IEhlbHZldGljYSBOZXVlLCBIZWx2ZXRpY2EsIHNhbnMtc2VyaWY7IiBjbGFzcz0iIj5NYXkgNSwg
MjAxNyBhdCAxMTo0Mzo1MCBQTSBFRFQ8YnIgY2xhc3M9IiI+DQo8L3NwYW4+PC9kaXY+DQo8ZGl2
IHN0eWxlPSJtYXJnaW4tdG9wOiAwcHg7IG1hcmdpbi1yaWdodDogMHB4OyBtYXJnaW4tYm90dG9t
OiAwcHg7IG1hcmdpbi1sZWZ0OiAwcHg7IiBjbGFzcz0iIj4NCjxzcGFuIHN0eWxlPSJmb250LWZh
bWlseTogLXdlYmtpdC1zeXN0ZW0tZm9udCwgSGVsdmV0aWNhIE5ldWUsIEhlbHZldGljYSwgc2Fu
cy1zZXJpZjsgY29sb3I6cmdiYSgwLCAwLCAwLCAxLjApOyIgY2xhc3M9IiI+PGIgY2xhc3M9IiI+
VG86DQo8L2I+PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTogLXdlYmtpdC1zeXN0ZW0t
Zm9udCwgSGVsdmV0aWNhIE5ldWUsIEhlbHZldGljYSwgc2Fucy1zZXJpZjsiIGNsYXNzPSIiPjxh
IGhyZWY9Im1haWx0bzppZXRmLWFubm91bmNlQGlldGYub3JnIiBjbGFzcz0iIj5pZXRmLWFubm91
bmNlQGlldGYub3JnPC9hPiwNCjxhIGhyZWY9Im1haWx0bzpyZmMtZGlzdEByZmMtZWRpdG9yLm9y
ZyIgY2xhc3M9IiI+cmZjLWRpc3RAcmZjLWVkaXRvci5vcmc8L2E+PGJyIGNsYXNzPSIiPg0KPC9z
cGFuPjwvZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2luLXRvcDogMHB4OyBtYXJnaW4tcmlnaHQ6IDBw
eDsgbWFyZ2luLWJvdHRvbTogMHB4OyBtYXJnaW4tbGVmdDogMHB4OyIgY2xhc3M9IiI+DQo8c3Bh
biBzdHlsZT0iZm9udC1mYW1pbHk6IC13ZWJraXQtc3lzdGVtLWZvbnQsIEhlbHZldGljYSBOZXVl
LCBIZWx2ZXRpY2EsIHNhbnMtc2VyaWY7IGNvbG9yOnJnYmEoMCwgMCwgMCwgMS4wKTsiIGNsYXNz
PSIiPjxiIGNsYXNzPSIiPkNjOg0KPC9iPjwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6
IC13ZWJraXQtc3lzdGVtLWZvbnQsIEhlbHZldGljYSBOZXVlLCBIZWx2ZXRpY2EsIHNhbnMtc2Vy
aWY7IiBjbGFzcz0iIj48YSBocmVmPSJtYWlsdG86ZHJhZnRzLXVwZGF0ZS1yZWZAaWFuYS5vcmci
IGNsYXNzPSIiPmRyYWZ0cy11cGRhdGUtcmVmQGlhbmEub3JnPC9hPiwNCjxhIGhyZWY9Im1haWx0
bzpyZmMtZWRpdG9yQHJmYy1lZGl0b3Iub3JnIiBjbGFzcz0iIj5yZmMtZWRpdG9yQHJmYy1lZGl0
b3Iub3JnPC9hPjxiciBjbGFzcz0iIj4NCjwvc3Bhbj48L2Rpdj4NCjxkaXYgc3R5bGU9Im1hcmdp
bi10b3A6IDBweDsgbWFyZ2luLXJpZ2h0OiAwcHg7IG1hcmdpbi1ib3R0b206IDBweDsgbWFyZ2lu
LWxlZnQ6IDBweDsiIGNsYXNzPSIiPg0KPHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiAtd2Via2l0
LXN5c3RlbS1mb250LCBIZWx2ZXRpY2EgTmV1ZSwgSGVsdmV0aWNhLCBzYW5zLXNlcmlmOyBjb2xv
cjpyZ2JhKDAsIDAsIDAsIDEuMCk7IiBjbGFzcz0iIj48YiBjbGFzcz0iIj5SZXBseS1UbzoNCjwv
Yj48L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiAtd2Via2l0LXN5c3RlbS1mb250LCBI
ZWx2ZXRpY2EgTmV1ZSwgSGVsdmV0aWNhLCBzYW5zLXNlcmlmOyIgY2xhc3M9IiI+PGEgaHJlZj0i
bWFpbHRvOmlldGZAaWV0Zi5vcmciIGNsYXNzPSIiPmlldGZAaWV0Zi5vcmc8L2E+PGJyIGNsYXNz
PSIiPg0KPC9zcGFuPjwvZGl2Pg0KPGJyIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj4NCjxkaXYg
Y2xhc3M9IiI+QSBuZXcgUmVxdWVzdCBmb3IgQ29tbWVudHMgaXMgbm93IGF2YWlsYWJsZSBpbiBv
bmxpbmUgUkZDIGxpYnJhcmllcy48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQo8YnIgY2xh
c3M9IiI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtSRkMgODE1
OTxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwO1RpdGxlOiAmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtLZXll
ZCBJUHY2IFR1bm5lbCA8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDtBdXRob3I6ICZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO00uIEtvbnN0YW50
eW5vd2ljeiwgRWQuLDxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO0cuIEhlcm9uLCBFZC4sPGJyIGNsYXNzPSIiPg0K
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Ui4gU2NoYXR6bWF5ciw8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtXLiBIZW5kZXJpY2t4PGJyIGNsYXNzPSIiPg0K
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7U3RhdHVzOiAmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDtTdGFuZGFyZHMgVHJhY2s8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtTdHJlYW06ICZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwO0lFVEY8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDtEYXRlOiAmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtNYXkg
MjAxNzxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwO01haWxib3g6ICZuYnNwOyZuYnNwOyZuYnNwOzxhIGhyZWY9Im1haWx0bzptYWNpZWtAY2lz
Y28uY29tIiBjbGFzcz0iIj5tYWNpZWtAY2lzY28uY29tPC9hPiwNCjxiciBjbGFzcz0iIj4NCiZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzxh
IGhyZWY9Im1haWx0bzpnaWhlcm9uQGNpc2NvLmNvbSIgY2xhc3M9IiI+Z2loZXJvbkBjaXNjby5j
b208L2E+LA0KPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7PGEgaHJlZj0ibWFpbHRvOnJhaW5lci5zY2hhdHptYXly
QHRlbGVrb20uZGUiIGNsYXNzPSIiPnJhaW5lci5zY2hhdHptYXlyQHRlbGVrb20uZGU8L2E+LDxi
ciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOzxhIGhyZWY9Im1haWx0bzp3aW0uaGVuZGVyaWNreEBhbGNhdGVsLWx1Y2Vu
dC5jb20iIGNsYXNzPSIiPndpbS5oZW5kZXJpY2t4QGFsY2F0ZWwtbHVjZW50LmNvbTwvYT48YnIg
Y2xhc3M9IiI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtQYWdl
czogJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7MTI8YnIgY2xhc3M9IiI+DQombmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtDaGFyYWN0ZXJzOiAyNzMwMjxiciBj
bGFzcz0iIj4NCiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO1VwZGF0
ZXMvT2Jzb2xldGVzL1NlZUFsc286ICZuYnNwOyZuYnNwO05vbmU8YnIgY2xhc3M9IiI+DQo8YnIg
Y2xhc3M9IiI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtJLUQg
VGFnOiAmbmJzcDsmbmJzcDsmbmJzcDtkcmFmdC1pZXRmLWwydHBleHQta2V5ZWQtaXB2Ni10dW5u
ZWwtMDcudHh0PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7VVJMOiAmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDs8YSBocmVmPSJodHRwczovL3d3dy5yZmMtZWRpdG9yLm9yZy9pbmZvL3Jm
YzgxNTkiIGNsYXNzPSIiPmh0dHBzOi8vd3d3LnJmYy1lZGl0b3Iub3JnL2luZm8vcmZjODE1OTwv
YT48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDtET0k6ICZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOzEwLjE3NDg3L1JGQzgxNTk8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpUaGlz
IGRvY3VtZW50IGRlc2NyaWJlcyBhIHR1bm5lbCBlbmNhcHN1bGF0aW9uIGZvciBFdGhlcm5ldCBv
dmVyIElQdjY8YnIgY2xhc3M9IiI+DQp3aXRoIGEgbWFuZGF0b3J5IDY0LWJpdCBjb29raWUgZm9y
IGNvbm5lY3RpbmcgTGF5ZXIgMiAoTDIpIEV0aGVybmV0PGJyIGNsYXNzPSIiPg0KYXR0YWNobWVu
dCBjaXJjdWl0cyBpZGVudGlmaWVkIGJ5IElQdjYgYWRkcmVzc2VzLiAmbmJzcDtUaGUgZW5jYXBz
dWxhdGlvbjxiciBjbGFzcz0iIj4NCmlzIGJhc2VkIG9uIHRoZSBMYXllciAyIFR1bm5lbGluZyBQ
cm90b2NvbCBWZXJzaW9uIDMgKEwyVFB2Mykgb3ZlciBJUDxiciBjbGFzcz0iIj4NCmFuZCBkb2Vz
IG5vdCB1c2UgdGhlIEwyVFB2MyBjb250cm9sIHBsYW5lLjxiciBjbGFzcz0iIj4NCjxiciBjbGFz
cz0iIj4NClRoaXMgZG9jdW1lbnQgaXMgYSBwcm9kdWN0IG9mIHRoZSBMYXllciBUd28gVHVubmVs
aW5nIFByb3RvY29sIEV4dGVuc2lvbnMgV29ya2luZyBHcm91cCBvZiB0aGUgSUVURi48YnIgY2xh
c3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpUaGlzIGlzIG5vdyBhIFByb3Bvc2VkIFN0YW5kYXJkLjxi
ciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NClNUQU5EQVJEUyBUUkFDSzogVGhpcyBkb2N1bWVu
dCBzcGVjaWZpZXMgYW4gSW50ZXJuZXQgU3RhbmRhcmRzIFRyYWNrPGJyIGNsYXNzPSIiPg0KcHJv
dG9jb2wgZm9yIHRoZSBJbnRlcm5ldCBjb21tdW5pdHksIGFuZCByZXF1ZXN0cyBkaXNjdXNzaW9u
IGFuZCBzdWdnZXN0aW9uczxiciBjbGFzcz0iIj4NCmZvciBpbXByb3ZlbWVudHMuICZuYnNwO1Bs
ZWFzZSByZWZlciB0byB0aGUgY3VycmVudCBlZGl0aW9uIG9mIHRoZSBPZmZpY2lhbDxiciBjbGFz
cz0iIj4NCkludGVybmV0IFByb3RvY29sIFN0YW5kYXJkcyAoPGEgaHJlZj0iaHR0cHM6Ly93d3cu
cmZjLWVkaXRvci5vcmcvc3RhbmRhcmRzIiBjbGFzcz0iIj5odHRwczovL3d3dy5yZmMtZWRpdG9y
Lm9yZy9zdGFuZGFyZHM8L2E+KSBmb3IgdGhlDQo8YnIgY2xhc3M9IiI+DQpzdGFuZGFyZGl6YXRp
b24gc3RhdGUgYW5kIHN0YXR1cyBvZiB0aGlzIHByb3RvY29sLiAmbmJzcDtEaXN0cmlidXRpb24g
b2YgdGhpcyA8YnIgY2xhc3M9IiI+DQptZW1vIGlzIHVubGltaXRlZC48YnIgY2xhc3M9IiI+DQo8
YnIgY2xhc3M9IiI+DQpUaGlzIGFubm91bmNlbWVudCBpcyBzZW50IHRvIHRoZSBJRVRGLUFubm91
bmNlIGFuZCByZmMtZGlzdCBsaXN0cy48YnIgY2xhc3M9IiI+DQpUbyBzdWJzY3JpYmUgb3IgdW5z
dWJzY3JpYmUsIHNlZTxiciBjbGFzcz0iIj4NCiZuYnNwOzxhIGhyZWY9Imh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vaWV0Zi1hbm5vdW5jZSIgY2xhc3M9IiI+aHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pZXRmLWFubm91bmNlPC9hPjxiciBjbGFzcz0i
Ij4NCiZuYnNwOzxhIGhyZWY9Imh0dHBzOi8vbWFpbG1hbi5yZmMtZWRpdG9yLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL3JmYy1kaXN0IiBjbGFzcz0iIj5odHRwczovL21haWxtYW4ucmZjLWVkaXRvci5v
cmcvbWFpbG1hbi9saXN0aW5mby9yZmMtZGlzdDwvYT48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9
IiI+DQpGb3Igc2VhcmNoaW5nIHRoZSBSRkMgc2VyaWVzLCBzZWUgPGEgaHJlZj0iaHR0cHM6Ly93
d3cucmZjLWVkaXRvci5vcmcvc2VhcmNoIiBjbGFzcz0iIj4NCmh0dHBzOi8vd3d3LnJmYy1lZGl0
b3Iub3JnL3NlYXJjaDwvYT48YnIgY2xhc3M9IiI+DQpGb3IgZG93bmxvYWRpbmcgUkZDcywgc2Vl
IDxhIGhyZWY9Imh0dHBzOi8vd3d3LnJmYy1lZGl0b3Iub3JnL3JldHJpZXZlL2J1bGsiIGNsYXNz
PSIiPg0KaHR0cHM6Ly93d3cucmZjLWVkaXRvci5vcmcvcmV0cmlldmUvYnVsazwvYT48YnIgY2xh
c3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpSZXF1ZXN0cyBmb3Igc3BlY2lhbCBkaXN0cmlidXRpb24g
c2hvdWxkIGJlIGFkZHJlc3NlZCB0byBlaXRoZXIgdGhlPGJyIGNsYXNzPSIiPg0KYXV0aG9yIG9m
IHRoZSBSRkMgaW4gcXVlc3Rpb24sIG9yIHRvIDxhIGhyZWY9Im1haWx0bzpyZmMtZWRpdG9yQHJm
Yy1lZGl0b3Iub3JnIiBjbGFzcz0iIj4NCnJmYy1lZGl0b3JAcmZjLWVkaXRvci5vcmc8L2E+LiAm
bmJzcDtVbmxlc3M8YnIgY2xhc3M9IiI+DQpzcGVjaWZpY2FsbHkgbm90ZWQgb3RoZXJ3aXNlIG9u
IHRoZSBSRkMgaXRzZWxmLCBhbGwgUkZDcyBhcmUgZm9yPGJyIGNsYXNzPSIiPg0KdW5saW1pdGVk
IGRpc3RyaWJ1dGlvbi48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+
DQpUaGUgUkZDIEVkaXRvciBUZWFtPGJyIGNsYXNzPSIiPg0KQXNzb2NpYXRpb24gTWFuYWdlbWVu
dCBTb2x1dGlvbnMsIExMQzxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0i
Ij4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxiciBjbGFzcz0iIj4N
CjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_3D0630CE807346E1B2D511444E8B2DD4ciscocom_--


From nobody Tue May 30 15:42:10 2017
Return-Path: <ietf@bobbriscoe.net>
X-Original-To: l2tpext@ietfa.amsl.com
Delivered-To: l2tpext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 639B312947F for <l2tpext@ietfa.amsl.com>; Tue, 30 May 2017 15:42:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.874
X-Spam-Level: 
X-Spam-Status: No, score=-0.874 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, HTTP_ESCAPED_HOST=1.125, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bobbriscoe.net
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 LOgzhs-rvfZg for <l2tpext@ietfa.amsl.com>; Tue, 30 May 2017 15:42:06 -0700 (PDT)
Received: from server.dnsblock1.com (server.dnsblock1.com [85.13.236.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6A11129476 for <l2tpext@ietf.org>; Tue, 30 May 2017 15:42:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=Content-Type:In-Reply-To:MIME-Version:Date: Message-ID:Cc:References:To:From:Subject:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=H/6y2/MDrptldD7afg6BvXUfqhopESeRT4rr0XDO2V0=; b=HPMFgIAybw68VY3VpqA/nH/aP vrSOC3q/pqjhy60qHlNjVR5kkqTx9WwQVdZikmQcQMfHykhWB/a9NCWiSygLxAVlCHucn5kXEuo9o gLLgNl6pQABO+m6ARUl/3933MVySX2zrDvVT1arDOBJMPshRuCh97jS0pEVzl/X/aSxkFwJ56xJTG 9CjCVdUKfLMlslUlfWTveGUkA7MJfNSH6nNyU20q7sa7QTNXHefPH/kEF+OiuYQqkkEA1zEjtx0UF goiNLqvuBcSaArl1WHfh/1c4MUSL8r8Yjd/f247RPcKu/Y1Z6mYq67/oH8gGk6r1Dkxgimyn5juqJ 5Bt+KNvcg==;
Received: from 197.74.9.51.dyn.plus.net ([51.9.74.197]:58340 helo=[192.168.0.2]) by server.dnsblock1.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from <ietf@bobbriscoe.net>) id 1dFpq0-0002vI-3d; Tue, 30 May 2017 23:42:04 +0100
From: Bob Briscoe <ietf@bobbriscoe.net>
To: l2tp IETF list <l2tpext@ietf.org>
References: <149618019740.19809.6421141487388928973.idtracker@ietfa.amsl.com> <435f45b8-9659-b06f-9adc-415f355ba743@bobbriscoe.net>
Cc: "Black, David" <david.black@emc.com>
Message-ID: <71177dab-7aff-3cb0-ccb8-84339d8f08ee@bobbriscoe.net>
Date: Tue, 30 May 2017 23:42:03 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <435f45b8-9659-b06f-9adc-415f355ba743@bobbriscoe.net>
Content-Type: multipart/alternative; boundary="------------D67289CC16037EEECB3751CA"
Content-Language: en-GB
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.dnsblock1.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bobbriscoe.net
X-Get-Message-Sender-Via: server.dnsblock1.com: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: server.dnsblock1.com: in@bobbriscoe.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2tpext/_sgl2D4prGTiGwwxUBb2NG8sP2Q>
Subject: Re: [L2tpext] New Version: draft-ietf-tsvwg-rfc6040update-shim-01
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 30 May 2017 22:42:08 -0000

This is a multi-part message in MIME format.
--------------D67289CC16037EEECB3751CA
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi l2tpext list,

This is a plea for help on a short subsection of a short draft that 
updates L2TP (amongst other tunnel protocols).

In the Transport Area WG (tsvwg) we have been working on defining 
propagation of the ECN field between IP headers separated by shim header(s):
     draft-ietf-tsvwg-rfc6040update-shim

L2TP is one such protocol (when the payload of the L2 protocol is IP, 
and the outer PSN is IP). This is particularly relevant at the moment, 
because of the low latency (L4S) work based on ECN and because 
deployment of ECN has finally taken off {Note 1}.

I presented this tunnelling work in intarea just under a year ago. Since 
then tsvwg has adopted the draft and asked that we include specific 
update text for each affected tunnel protocol. I just posted my first 
attempt at L2TP update text:
draft-ietf-tsvwg-rfc6040update-shim-01 
<https://tools.ietf.org/html/draft-ietf-tsvwg-rfc6040update-shim-01>

*Specific questions:**
*
Prize for the best answer to all 3 questions: you get to become a 
co-author (if you want :)

*Q1.* L2TP is meant for all sorts of outers and inners, so it is not 
clear where to define behaviour for the special (but very common) case 
of IP as the L2 payload and IP and as the PSN. That is:
      IP    :    [UDP]    :    L2TP    :    L2-specific-sublayer :    
L2    :    IP

I decided on updating S.4.5 of RFC3931 <Specific%20questions:>, but 
suggestions for a better place are welcome.
*
**Q2**.* L2TP is usually extended not updated. However, in this case, 
compliance with RFC6040 is non-optional, so I think update rather than 
extension is appropriate. Reason: Although RFC6040 is non-optional it 
includes a compatibility mode that defines what has to happen when a 
tunnel endpoint doesn't support ECN propagation.

Pls read the (short) draft and, if you disagree, suggest how an 
extension can be non-optional.
*
**Q3.* The tunnel initiator needs to check that the other end supports 
ECN propagation. I have proposed an Attribute Value Pair (AVP) for this 
that is effectively just a boolean choice from each end (Yes or 
silence). I expected to find an AVP with per-control-connection flags 
for tunnel endpoint capabilities that I could just extend with one more 
flag, but there doesn't seem to be such a thing already in L2TP. Did I 
miss it?


Cheers


Bob

{Note 1}: ~70% of Web servers, ~50% of Apple client devices on fixed or 
WiFi access, and now increasing router deployment of ECN is appearing.



On 30/05/17 22:49, Bob Briscoe wrote:
> David (as doc shepherd) and the tsvwg list,
>
> As requested, I have added specific text that updates the other 
> relevant RFCs under IETF change control (GRE and L2TP). I have also 
> explained the position in each case for specs not under IETF change 
> control.
>
> I will now go to the relevant WGs (intarea and lt2pext) and ask them 
> to improve my first attempt.
>
> I'll cc you and this list as appropriate.
>
> Cheers
>
>
>
> Bob
>
> PS. I have also said
>
>    the rules in [RFC6040] for
>    propagating the ECN field MUST be applied
>
> whereas before it said "SHOULD". And added an explanation for why 
> "MUST" is appropriate:
>
>    The above is written as a 'MUST' because RFC 6040 allows
>    a compatibility mode for the encapsulator in cases where the
>    decapsulator does not (or cannot) support ECN propagation.
>
>
>
>
>
>
> On 30/05/17 22:36, internet-drafts@ietf.org wrote:
>> A new version of I-D, draft-ietf-tsvwg-rfc6040update-shim-01.txt
>> has been successfully submitted by Bob Briscoe and posted to the
>> IETF repository.
>>
>> Name:        draft-ietf-tsvwg-rfc6040update-shim
>> Revision:    01
>> Title:        Propagating Explicit Congestion Notification Across IP 
>> Tunnel Headers Separated by a Shim
>> Document date:    2017-05-30
>> Group:        tsvwg
>> Pages:        10
>> URL: 
>> https://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rfc6040update-shim-01.txt
>> Status: 
>> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc6040update-shim/
>> Htmlized: 
>> https://tools.ietf.org/html/draft-ietf-tsvwg-rfc6040update-shim-01
>> Htmlized: 
>> https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-rfc6040update-shim-01
>> Diff: 
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-rfc6040update-shim-01
>>
>> Abstract:
>>     RFC 6040 on "Tunnelling of Explicit Congestion Notification" made 
>> the
>>     rules for propagation of ECN consistent for all forms of IP in IP
>>     tunnel.  This specification extends the scope of RFC 6040 to include
>>     tunnels where two IP headers are separated by at least one shim
>>     header that is not sufficient on its own for packet forwarding.
>>
>>
>>
>> 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
>>
>

-- 
________________________________________________________________
Bob Briscoe                               http://bobbriscoe.net/


--------------D67289CC16037EEECB3751CA
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Hi l2tpext list,<br>
    <br>
    This is a plea for help on a short subsection of a short draft that
    updates L2TP (amongst other tunnel protocols).<br>
    <br>
    In the Transport Area WG (tsvwg) we have been working on defining
    propagation of the ECN field between IP headers separated by shim
    header(s):<br>
        draft-ietf-tsvwg-rfc6040update-shim<br>
    <br>
    L2TP is one such protocol (when the payload of the L2 protocol is
    IP, and the outer PSN is IP). This is particularly relevant at the
    moment, because of the low latency (L4S) work based on ECN and
    because deployment of ECN has finally taken off {Note 1}.<br>
    <br>
    I presented this tunnelling work in intarea just under a year ago.
    Since then tsvwg has adopted the draft and asked that we include
    specific update text for each affected tunnel protocol. I just
    posted my first attempt at L2TP update text:<br>
        <a moz-do-not-send="true"
href="https://tools.ietf.org/html/draft-ietf-tsvwg-rfc6040update-shim-01">draft-ietf-tsvwg-rfc6040update-shim-01</a><br>
    <br>
    <b>Specific questions:</b><b><br>
    </b><br>
    Prize for the best answer to all 3 questions: you get to become a
    co-author (if you want :)<br>
    <br>
    <b>Q1.</b> L2TP is meant for all sorts of outers and inners, so it
    is not clear where to define behaviour for the special (but very
    common) case of IP as the L2 payload and IP and as the PSN. That is:<br>
         IP    :    [UDP]    :    L2TP    :    L2-specific-sublayer   
    :    L2    :    IP<br>
    <br>
    I decided on updating <a moz-do-not-send="true"
      href="Specific%20questions:">S.4.5 of RFC3931</a>, but suggestions
    for a better place are welcome.<br>
    <b><br>
    </b><b>Q2</b><b>.</b> L2TP is usually extended not updated. However,
    in this case, compliance with RFC6040 is non-optional, so I think
    update rather than extension is appropriate. Reason: Although
    RFC6040 is non-optional it includes a compatibility mode that
    defines what has to happen when a tunnel endpoint doesn't support
    ECN propagation. <br>
    <br>
    Pls read the (short) draft and, if you disagree, suggest how an
    extension can be non-optional.<br>
    <b><br>
    </b><b>Q3.</b> The tunnel initiator needs to check that the other
    end supports ECN propagation. I have proposed an Attribute Value
    Pair (AVP) for this that is effectively just a boolean choice from
    each end (Yes or silence). I expected to find an AVP with
    per-control-connection flags for tunnel endpoint capabilities that I
    could just extend with one more flag, but there doesn't seem to be
    such a thing already in L2TP. Did I miss it?<br>
    <br>
    <br>
    Cheers<br>
    <br>
    <br>
    Bob<br>
    <br>
    {Note 1}: ~70% of Web servers, ~50% of Apple client devices on fixed
    or WiFi access, and now increasing router deployment of ECN is
    appearing.<br>
    <br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 30/05/17 22:49, Bob Briscoe wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:435f45b8-9659-b06f-9adc-415f355ba743@bobbriscoe.net">David
      (as doc shepherd) and the tsvwg list,
      <br>
      <br>
      As requested, I have added specific text that updates the other
      relevant RFCs under IETF change control (GRE and L2TP). I have
      also explained the position in each case for specs not under IETF
      change control.
      <br>
      <br>
      I will now go to the relevant WGs (intarea and lt2pext) and ask
      them to improve my first attempt.
      <br>
      <br>
      I'll cc you and this list as appropriate.
      <br>
      <br>
      Cheers
      <br>
      <br>
      <br>
      <br>
      Bob
      <br>
      <br>
      PS. I have also said
      <br>
      <br>
         the rules in [RFC6040] for
      <br>
         propagating the ECN field MUST be applied
      <br>
      <br>
      whereas before it said "SHOULD". And added an explanation for why
      "MUST" is appropriate:
      <br>
      <br>
         The above is written as a 'MUST' because RFC 6040 allows
      <br>
         a compatibility mode for the encapsulator in cases where the
      <br>
         decapsulator does not (or cannot) support ECN propagation.
      <br>
      <br>
      <br>
      <br>
      <br>
      <br>
      <br>
      On 30/05/17 22:36, <a class="moz-txt-link-abbreviated" href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a> wrote:
      <br>
      <blockquote type="cite">A new version of I-D,
        draft-ietf-tsvwg-rfc6040update-shim-01.txt
        <br>
        has been successfully submitted by Bob Briscoe and posted to the
        <br>
        IETF repository.
        <br>
        <br>
        Name:        draft-ietf-tsvwg-rfc6040update-shim
        <br>
        Revision:    01
        <br>
        Title:        Propagating Explicit Congestion Notification
        Across IP Tunnel Headers Separated by a Shim
        <br>
        Document date:    2017-05-30
        <br>
        Group:        tsvwg
        <br>
        Pages:        10
        <br>
        URL:           
<a class="moz-txt-link-freetext" href="https://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rfc6040update-shim-01.txt">https://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rfc6040update-shim-01.txt</a><br>
        Status:        
        <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc6040update-shim/">https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc6040update-shim/</a>
        <br>
        Htmlized:      
        <a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-ietf-tsvwg-rfc6040update-shim-01">https://tools.ietf.org/html/draft-ietf-tsvwg-rfc6040update-shim-01</a>
        <br>
        Htmlized:      
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-rfc6040update-shim-01">https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-rfc6040update-shim-01</a><br>
        Diff:          
        <a class="moz-txt-link-freetext" href="https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-rfc6040update-shim-01">https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-rfc6040update-shim-01</a>
        <br>
        <br>
        Abstract:
        <br>
            RFC 6040 on "Tunnelling of Explicit Congestion Notification"
        made the
        <br>
            rules for propagation of ECN consistent for all forms of IP
        in IP
        <br>
            tunnel.  This specification extends the scope of RFC 6040 to
        include
        <br>
            tunnels where two IP headers are separated by at least one
        shim
        <br>
            header that is not sufficient on its own for packet
        forwarding.
        <br>
        <br>
                                                                                  
        <br>
        <br>
        Please note that it may take a couple of minutes from the time
        of submission
        <br>
        until the htmlized version and diff are available at
        tools.ietf.org.
        <br>
        <br>
        The IETF Secretariat
        <br>
        <br>
      </blockquote>
      <br>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
________________________________________________________________
Bob Briscoe                               <a class="moz-txt-link-freetext" href="http://bobbriscoe.net/">http://bobbriscoe.net/</a></pre>
  </body>
</html>

--------------D67289CC16037EEECB3751CA--


From nobody Tue May 30 15:49:56 2017
Return-Path: <ietf@bobbriscoe.net>
X-Original-To: l2tpext@ietfa.amsl.com
Delivered-To: l2tpext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24B9F120726 for <l2tpext@ietfa.amsl.com>; Tue, 30 May 2017 15:49:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.874
X-Spam-Level: 
X-Spam-Status: No, score=-0.874 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, HTTP_ESCAPED_HOST=1.125, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bobbriscoe.net
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 cpktBXkQby1p for <l2tpext@ietfa.amsl.com>; Tue, 30 May 2017 15:49:53 -0700 (PDT)
Received: from server.dnsblock1.com (server.dnsblock1.com [85.13.236.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E152B1200CF for <l2tpext@ietf.org>; Tue, 30 May 2017 15:49:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=Content-Type:In-Reply-To:MIME-Version:Date: Message-ID:References:Cc:To:Subject:From:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=4w0gVFG5UNdP8adFY4rj56tZdiJgmd7cib/WaU793co=; b=3N2XbOugA9J2PmUiy47VMf5Pv C4St2BMcox/sZ+2TXqqAxxHzKTQWq0jAy0i/SncuMcZg8lTv0MHY97zkQscxUkZTcE3W8jv423l6G 8cKCzKC+cj0hjR+IcfMjcpMpuo30WLTNkuRctNmSfm6jp+nOPrthtc8fg0bINp9fyPjVBIc7jC2Wc QTXIzMM/SxEGPrBU6Hhj+zQoy1frJYcA/fMfX4MaK1Qhzko5Y4oE1EUlzc/fcoHuHbNbZmz2JEUK0 BDp9rJ9bXWTtynITW4Zp9smtGsTwVb1tcEYlfn+22PGPgaiQebdGhvkLjJeBNSz4suULl3Lfe5W6C woZGQm4Hg==;
Received: from 197.74.9.51.dyn.plus.net ([51.9.74.197]:58346 helo=[192.168.0.2]) by server.dnsblock1.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from <ietf@bobbriscoe.net>) id 1dFpxX-0003K0-7V; Tue, 30 May 2017 23:49:51 +0100
From: Bob Briscoe <ietf@bobbriscoe.net>
To: l2tp IETF list <l2tpext@ietf.org>
Cc: "Black, David" <david.black@emc.com>
References: <149618019740.19809.6421141487388928973.idtracker@ietfa.amsl.com> <435f45b8-9659-b06f-9adc-415f355ba743@bobbriscoe.net>
Message-ID: <e4c97c52-36c9-3091-b005-06ef82ec58e3@bobbriscoe.net>
Date: Tue, 30 May 2017 23:49:50 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <435f45b8-9659-b06f-9adc-415f355ba743@bobbriscoe.net>
Content-Type: multipart/alternative; boundary="------------DED98231FE9FC0CE0323F37C"
Content-Language: en-GB
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.dnsblock1.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bobbriscoe.net
X-Get-Message-Sender-Via: server.dnsblock1.com: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: server.dnsblock1.com: in@bobbriscoe.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2tpext/GnT7Q7tILSffolUNOF299iohvZ8>
Subject: [L2tpext] Propagating IP/ECN field when L2TP sits between IP as both L2 payload and PSN
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 30 May 2017 22:49:55 -0000

This is a multi-part message in MIME format.
--------------DED98231FE9FC0CE0323F37C
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi l2tpext list,
[repeating previous post, but with self-explanatory subject line]

This is a plea for help on a short subsection of a short draft that 
updates L2TP (amongst other tunnel protocols).

In the Transport Area WG (tsvwg) we have been working on defining 
propagation of the ECN field between IP headers separated by shim header(s):
     draft-ietf-tsvwg-rfc6040update-shim

L2TP is one such protocol (when the payload of the L2 protocol is IP, 
and the outer PSN is IP). This is particularly relevant at the moment, 
because of the low latency (L4S) work based on ECN and because 
deployment of ECN has finally taken off {Note 1}.

I presented this tunnelling work in intarea just under a year ago. Since 
then tsvwg has adopted the draft and asked that we include specific 
update text for each affected tunnel protocol. I just posted my first 
attempt at L2TP update text:
draft-ietf-tsvwg-rfc6040update-shim-01 
<https://tools.ietf.org/html/draft-ietf-tsvwg-rfc6040update-shim-01>

*Specific questions:**
*
Prize for the best answer to all 3 questions: you get to become a 
co-author (if you want :)

*Q1.* L2TP is meant for all sorts of outers and inners, so it is not 
clear where to define behaviour for the special (but very common) case 
of IP as the L2 payload and IP and as the PSN. That is:
      IP    :    [UDP]    :    L2TP    :    L2-specific-sublayer :    
L2    :    IP

I decided on updating S.4.5 of RFC3931 <Specific%20questions:>, but 
suggestions for a better place are welcome.
*
**Q2**.* L2TP is usually extended not updated. However, in this case, 
compliance with RFC6040 is non-optional, so I think update rather than 
extension is appropriate. Reason: Although RFC6040 is non-optional it 
includes a compatibility mode that defines what has to happen when a 
tunnel endpoint doesn't support ECN propagation.

Pls read the (short) draft and, if you disagree, suggest how an 
extension can be non-optional.
*
**Q3.* The tunnel initiator needs to check that the other end supports 
ECN propagation. I have proposed an Attribute Value Pair (AVP) for this 
that is effectively just a boolean choice from each end (Yes or 
silence). I expected to find an AVP with per-control-connection flags 
for tunnel endpoint capabilities that I could just extend with one more 
flag, but there doesn't seem to be such a thing already in L2TP. Did I 
miss it?


Cheers


Bob

{Note 1}: ~70% of Web servers, ~50% of Apple client devices on fixed or 
WiFi access, and now increasing router deployment of ECN is appearing.



On 30/05/17 22:49, Bob Briscoe wrote:
> David (as doc shepherd) and the tsvwg list,
>
> As requested, I have added specific text that updates the other 
> relevant RFCs under IETF change control (GRE and L2TP). I have also 
> explained the position in each case for specs not under IETF change 
> control.
>
> I will now go to the relevant WGs (intarea and lt2pext) and ask them 
> to improve my first attempt.
>
> I'll cc you and this list as appropriate.
>
> Cheers
>
>
>
> Bob
>
> PS. I have also said
>
>    the rules in [RFC6040] for
>    propagating the ECN field MUST be applied
>
> whereas before it said "SHOULD". And added an explanation for why 
> "MUST" is appropriate:
>
>    The above is written as a 'MUST' because RFC 6040 allows
>    a compatibility mode for the encapsulator in cases where the
>    decapsulator does not (or cannot) support ECN propagation.
>
>
>
>
>
>
> On 30/05/17 22:36, internet-drafts@ietf.org wrote:
>> A new version of I-D, draft-ietf-tsvwg-rfc6040update-shim-01.txt
>> has been successfully submitted by Bob Briscoe and posted to the
>> IETF repository.
>>
>> Name:        draft-ietf-tsvwg-rfc6040update-shim
>> Revision:    01
>> Title:        Propagating Explicit Congestion Notification Across IP 
>> Tunnel Headers Separated by a Shim
>> Document date:    2017-05-30
>> Group:        tsvwg
>> Pages:        10
>> URL: 
>> https://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rfc6040update-shim-01.txt
>> Status: 
>> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc6040update-shim/
>> Htmlized: 
>> https://tools.ietf.org/html/draft-ietf-tsvwg-rfc6040update-shim-01
>> Htmlized: 
>> https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-rfc6040update-shim-01
>> Diff: 
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-rfc6040update-shim-01
>>
>> Abstract:
>>     RFC 6040 on "Tunnelling of Explicit Congestion Notification" made 
>> the
>>     rules for propagation of ECN consistent for all forms of IP in IP
>>     tunnel.  This specification extends the scope of RFC 6040 to include
>>     tunnels where two IP headers are separated by at least one shim
>>     header that is not sufficient on its own for packet forwarding.
>>
>>
>>
>> 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
>>
>

-- 
________________________________________________________________
Bob Briscoehttp://bobbriscoe.net/


--------------DED98231FE9FC0CE0323F37C
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Hi l2tpext list, <br>
    [repeating previous post, but with self-explanatory subject line]<br>
    <br>
    This is a plea for help on a short subsection of a short draft that
    updates L2TP (amongst other tunnel protocols).<br>
    <br>
    In the Transport Area WG (tsvwg) we have been working on defining
    propagation of the ECN field between IP headers separated by shim
    header(s):<br>
        draft-ietf-tsvwg-rfc6040update-shim<br>
    <br>
    L2TP is one such protocol (when the payload of the L2 protocol is
    IP, and the outer PSN is IP). This is particularly relevant at the
    moment, because of the low latency (L4S) work based on ECN and
    because deployment of ECN has finally taken off {Note 1}.<br>
    <br>
    I presented this tunnelling work in intarea just under a year ago.
    Since then tsvwg has adopted the draft and asked that we include
    specific update text for each affected tunnel protocol. I just
    posted my first attempt at L2TP update text:<br>
        <a moz-do-not-send="true"
href="https://tools.ietf.org/html/draft-ietf-tsvwg-rfc6040update-shim-01">draft-ietf-tsvwg-rfc6040update-shim-01</a><br>
    <br>
    <b>Specific questions:</b><b><br>
    </b><br>
    Prize for the best answer to all 3 questions: you get to become a
    co-author (if you want :)<br>
    <br>
    <b>Q1.</b> L2TP is meant for all sorts of outers and inners, so it
    is not clear where to define behaviour for the special (but very
    common) case of IP as the L2 payload and IP and as the PSN. That is:<br>
         IP    :    [UDP]    :    L2TP    :    L2-specific-sublayer   
    :    L2    :    IP<br>
    <br>
    I decided on updating <a moz-do-not-send="true"
      href="Specific%20questions:">S.4.5 of RFC3931</a>, but suggestions
    for a better place are welcome.<br>
    <b><br>
    </b><b>Q2</b><b>.</b> L2TP is usually extended not updated. However,
    in this case, compliance with RFC6040 is non-optional, so I think
    update rather than extension is appropriate. Reason: Although
    RFC6040 is non-optional it includes a compatibility mode that
    defines what has to happen when a tunnel endpoint doesn't support
    ECN propagation. <br>
    <br>
    Pls read the (short) draft and, if you disagree, suggest how an
    extension can be non-optional.<br>
    <b><br>
    </b><b>Q3.</b> The tunnel initiator needs to check that the other
    end supports ECN propagation. I have proposed an Attribute Value
    Pair (AVP) for this that is effectively just a boolean choice from
    each end (Yes or silence). I expected to find an AVP with
    per-control-connection flags for tunnel endpoint capabilities that I
    could just extend with one more flag, but there doesn't seem to be
    such a thing already in L2TP. Did I miss it?<br>
    <br>
    <br>
    Cheers<br>
    <br>
    <br>
    Bob<br>
    <br>
    {Note 1}: ~70% of Web servers, ~50% of Apple client devices on fixed
    or WiFi access, and now increasing router deployment of ECN is
    appearing.<br>
    <br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 30/05/17 22:49, Bob Briscoe wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:435f45b8-9659-b06f-9adc-415f355ba743@bobbriscoe.net">David
      (as doc shepherd) and the tsvwg list, <br>
      <br>
      As requested, I have added specific text that updates the other
      relevant RFCs under IETF change control (GRE and L2TP). I have
      also explained the position in each case for specs not under IETF
      change control. <br>
      <br>
      I will now go to the relevant WGs (intarea and lt2pext) and ask
      them to improve my first attempt. <br>
      <br>
      I'll cc you and this list as appropriate. <br>
      <br>
      Cheers <br>
      <br>
      <br>
      <br>
      Bob <br>
      <br>
      PS. I have also said <br>
      <br>
         the rules in [RFC6040] for <br>
         propagating the ECN field MUST be applied <br>
      <br>
      whereas before it said "SHOULD". And added an explanation for why
      "MUST" is appropriate: <br>
      <br>
         The above is written as a 'MUST' because RFC 6040 allows <br>
         a compatibility mode for the encapsulator in cases where the <br>
         decapsulator does not (or cannot) support ECN propagation. <br>
      <br>
      <br>
      <br>
      <br>
      <br>
      <br>
      On 30/05/17 22:36, <a class="moz-txt-link-abbreviated"
        href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a>
      wrote: <br>
      <blockquote type="cite">A new version of I-D,
        draft-ietf-tsvwg-rfc6040update-shim-01.txt <br>
        has been successfully submitted by Bob Briscoe and posted to the
        <br>
        IETF repository. <br>
        <br>
        Name:        draft-ietf-tsvwg-rfc6040update-shim <br>
        Revision:    01 <br>
        Title:        Propagating Explicit Congestion Notification
        Across IP Tunnel Headers Separated by a Shim <br>
        Document date:    2017-05-30 <br>
        Group:        tsvwg <br>
        Pages:        10 <br>
        URL:           
        <a class="moz-txt-link-freetext"
href="https://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rfc6040update-shim-01.txt">https://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rfc6040update-shim-01.txt</a><br>
        Status:         <a class="moz-txt-link-freetext"
href="https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc6040update-shim/">https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc6040update-shim/</a>
        <br>
        Htmlized:       <a class="moz-txt-link-freetext"
href="https://tools.ietf.org/html/draft-ietf-tsvwg-rfc6040update-shim-01">https://tools.ietf.org/html/draft-ietf-tsvwg-rfc6040update-shim-01</a>
        <br>
        Htmlized:      
        <a class="moz-txt-link-freetext"
href="https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-rfc6040update-shim-01">https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-rfc6040update-shim-01</a><br>
        Diff:           <a class="moz-txt-link-freetext"
href="https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-rfc6040update-shim-01">https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-rfc6040update-shim-01</a>
        <br>
        <br>
        Abstract: <br>
            RFC 6040 on "Tunnelling of Explicit Congestion Notification"
        made the <br>
            rules for propagation of ECN consistent for all forms of IP
        in IP <br>
            tunnel.  This specification extends the scope of RFC 6040 to
        include <br>
            tunnels where two IP headers are separated by at least one
        shim <br>
            header that is not sufficient on its own for packet
        forwarding. <br>
        <br>
                                                                                  
        <br>
        <br>
        Please note that it may take a couple of minutes from the time
        of submission <br>
        until the htmlized version and diff are available at
        tools.ietf.org. <br>
        <br>
        The IETF Secretariat <br>
        <br>
      </blockquote>
      <br>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
________________________________________________________________
Bob Briscoe                               <a class="moz-txt-link-freetext" href="http://bobbriscoe.net/">http://bobbriscoe.net/</a></pre>
  </body>
</html>

--------------DED98231FE9FC0CE0323F37C--


From nobody Tue May 30 18:52:14 2017
Return-Path: <ignacio.goyret@nokia.com>
X-Original-To: l2tpext@ietfa.amsl.com
Delivered-To: l2tpext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 426F6129B2E for <l2tpext@ietfa.amsl.com>; Tue, 30 May 2017 18:52:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.922
X-Spam-Level: 
X-Spam-Status: No, score=-1.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.com
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 hcNbisYF31RF for <l2tpext@ietfa.amsl.com>; Tue, 30 May 2017 18:52:11 -0700 (PDT)
Received: from EUR02-HE1-obe.outbound.protection.outlook.com (mail-eopbgr10131.outbound.protection.outlook.com [40.107.1.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4D68129B29 for <l2tpext@ietf.org>; Tue, 30 May 2017 18:52:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com;  s=selector1-nokia-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=gX0soOqJ5H2I2l4UzeBmsbuU3nu/UwD859e0YeA0ZWw=; b=OgIpF+Faw1ltWafkqSylM5QNZGUg1dXZOHruE4XtCipWnBilWINBven2xDA13YiNgXGlFDcgKW6Nh0xgmgBD3QU6CNFPLwuhzJNE02MEaQZNfA4ZErMYmIIc9oB9kUNypeEsVW3V8rqM4YWDaHXFm6/Za2K7EVhuZzw9uFvsIEE=
Received: from DB6PR07CA0096.eurprd07.prod.outlook.com (2603:10a6:6:2b::34) by DB4PR07MB0592.eurprd07.prod.outlook.com (2a01:111:e400:9845::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1143.6; Wed, 31 May 2017 01:52:08 +0000
Received: from VE1EUR03FT031.eop-EUR03.prod.protection.outlook.com (2a01:111:f400:7e09::207) by DB6PR07CA0096.outlook.office365.com (2603:10a6:6:2b::34) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1143.6 via Frontend Transport; Wed, 31 May 2017 01:52:08 +0000
Authentication-Results: spf=pass (sender IP is 135.245.43.121) smtp.mailfrom=nokia.com; emc.com; dkim=none (message not signed) header.d=none;emc.com; dmarc=pass action=none header.from=nokia.com;
Received-SPF: Pass (protection.outlook.com: domain of nokia.com designates 135.245.43.121 as permitted sender) receiver=protection.outlook.com; client-ip=135.245.43.121; helo=us70uusmtp4-o.zam.alcatel-lucent.com;
Received: from us70uusmtp4-o.zam.alcatel-lucent.com (135.245.43.121) by VE1EUR03FT031.mail.protection.outlook.com (10.152.18.69) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_RSA_WITH_AES_256_CBC_SHA) id 15.1.1101.12 via Frontend Transport; Wed, 31 May 2017 01:52:07 +0000
Received: from us70uusmtp4.zam.alcatel-lucent.com (us70uusmtp4-o.zam.alcatel-lucent.com [135.5.2.90]) by us70uusmtp4-o.zam.alcatel-lucent.com (GMO-o) with ESMTP id v4V1q5KC000991 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 31 May 2017 01:52:05 GMT
Received: from cliff.eng.ascend.com (cliff.eng.ascend.com [192.207.23.55]) by us70uusmtp4.zam.alcatel-lucent.com (GMO) with ESMTP id v4V1q44b000976 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 31 May 2017 01:52:04 GMT
Received: from igoyret-c1.nokia.com (igoyret-pc [135.227.139.12]) by cliff.eng.ascend.com (8.13.1/8.13.1) with ESMTP id v4V1sYQH013223 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 May 2017 18:54:34 -0700
Message-ID: <201705310154.v4V1sYQH013223@cliff.eng.ascend.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 30 May 2017 18:51:46 -0700
To: Bob Briscoe <ietf@bobbriscoe.net>
From: Ignacio Goyret <ignacio.goyret@nokia.com>
CC: l2tp IETF list <l2tpext@ietf.org>, "Black, David" <david.black@emc.com>
In-Reply-To: <e4c97c52-36c9-3091-b005-06ef82ec58e3@bobbriscoe.net>
References: <149618019740.19809.6421141487388928973.idtracker@ietfa.amsl.com> <435f45b8-9659-b06f-9adc-415f355ba743@bobbriscoe.net> <e4c97c52-36c9-3091-b005-06ef82ec58e3@bobbriscoe.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-HT: Tenant
X-Forefront-Antispam-Report: CIP:135.245.43.121; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(39840400002)(39400400002)(39410400002)(39850400002)(39450400003)(39860400002)(2980300002)(438002)(24454002)(199003)(189002)(9170700003)(6916009)(2950100002)(46406003)(8936002)(8676002)(50226002)(81166006)(478600001)(229853002)(6666003)(97756001)(4720700003)(8666007)(50466002)(189998001)(76176999)(356003)(50986999)(305945005)(8276002)(2906002)(54906002)(6246003)(110136004)(38730400002)(4326008)(47776003)(106466001)(53416004)(53936002)(23726003)(1076002)(6306002)(5660300001)(86362001)(9686003); DIR:OUT; SFP:1102; SCL:1; SRVR:DB4PR07MB0592; H:us70uusmtp4-o.zam.alcatel-lucent.com; FPR:; SPF:Pass; MLV:sfv; A:1; MX:1; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; VE1EUR03FT031; 1:zauvy6Hwkc01Ar7WPi3RGc5RvGxd9/5OGkBz+/17440P9hdGSOHGfMhUax+0vCqCOAyfN/3IE4hzlYPUoqfAPLz7JwhexlneBgaPGXr+CXRKOmqKHdHRSN/XIivsMgbQSKYE/ieZqBsG+m1iQyEUwNG503OyNATeFlwk1zNDS864VwSAGS/XU7r1FL/SbI6d6l/DxLpjpoF1C5LEUOhQ3ksNe2LLVBKsVpMtFbnECjy6zt71YFsTpzVqg/QMBJerb6WmjgVNSsyIfL8XxpLj4vD4Mfa2/Q/PTF0hVKqNk54K6SL9+SguRe9HYvLyXIcvtgPrHMW4Od1w1fUcUBIFPRedgTQp7VE8+um7j/EQo5f1GO8OqBBXesAjEIY/4bS/+SZ8s3Tl23ZL75aeKro0X+/l7z6OMAnqyo1W4B4n5TUP46ulmSD8cJNkZPCzi4icMNEkpYYe8LBNyWdorda4t/+ykXbNeGGlZuoMVWloIavXD60lfE2pKxXRZbSwqVFY1BP6sZobghy6f0ymaX1Xk8stggTqZWBWeoTDtnYtMTMgCFYrTM0X+7+o/x7w1R84
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: DB4PR07MB0592:
X-MS-Office365-Filtering-Correlation-Id: 0fdd0d69-632e-4e1d-6a90-08d4a7c7a536
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(8251501002)(2017030254075)(201703131423075)(201703031133081); SRVR:DB4PR07MB0592; 
X-Microsoft-Exchange-Diagnostics: 1; DB4PR07MB0592; 3:YVm/EF62wKDNjYDE7SB2otCihCEamZgonDsi262gu4aUNkJ5qiNITx5Dx3u9UgG21vDVjfleusxxFZ3LkVJ1hGst2EwSy0a83vPJgtwZ/is+zGyj8hET4lyqhd+FpcT17efVQD0TLeS6RrkOqH7cUFQBLLguHkV0IYfN+C48GV3CC/XalCAzXKo/at3G+w+Dhzzkz6nlFZJhX+ctQC+fs5xstbuIUV108yRbF2iMyRYCpkbBX9/q/CzWJbH1iRpsH6+3FbyPSWCkSb1Q48ex3cJM6OFwomCgKXEGkdVTNVZwR+OT+WJy/xuGcV1E0Y0eARJ/vYTsl+tsYpBogt4jYgNb3EwDOKtEYRe81i23KVZf/g26BHWS1m77Jk55El4ao188I0TalzkuZ4VgdqLpzupN+ZPeFEA35YV9BeN0peyb8HIxFDhOrMs8owGpmJyXo15IbBiRGduObYyM6nJpnW1HpWiiVxpr1ovh4X6E9q1aXk6J1g7QIhmycb54NsbY
X-Microsoft-Exchange-Diagnostics: 1; DB4PR07MB0592; 25:RyVkXTq5T94akPn9RZfxfayhi5xWPT9+EGUGqY9xmyf+XBXe90OmpJ100VvAGhNNvQKjHP1uyNod391qV/c2gd+/yGKsJUTgVwMrDO0lHsGHTRUghIW5Qtu8BmjWSw1cll+ThnFC3JIGDEByEjuec3aUyE+hAz4ME6xWt1XBRvEs+LOo3dzcpcqCm+6B3t3Y9bwjKFfyLO1ryvp3Zer0eX/iuWtRwHbSuBwEIk3g0OX5wkz58BmGzc8fAAOZrG/WpoADokJpisTIX2XhFK7KiU6YnGi0tGKy50YENWwdHiFyBmvnnFyDR27rgl3NeIwCo/Z+EGXi7gNS85eiT4sX5iAh7U6r+5unLgMJBhYb/hpl8spur27BF6eU3//J2ueFxj9IYi2ZTLi39ConcY/x1fwnTwBKyOwiA2pXegPNN/Rqa9NZDsd8XlyzWeQcFKT8gkYS7IfAocTEqq8f7HssvIcZOFhCHab3UVqQ7+lTVU4=; 31:SDcErljksYSFyLZNXc4qoatyhhFtRb8fBjS0fObpkBNVQZcgqlb0KhlNAIXgn4sVOTG6e5HqCy9W4tlOAyqTMnxOTi+cecqFNES8w5aJ3NQphPvh47qLmXDoxLQ49i1COqfw20XOomDIS7xr1rjUJVrs0zpoZegjImOTBTfFAD9mPVWDxpu6tuvAg7mA/JDrvmk8ufeqHGNOv1uMolnpE9fx1tZaFnn8b4J1vmrOwF4oj0gb1/lnHvClzjyaCRPVrv4HOSQltkph8p2RVg7G4w==
X-Microsoft-Exchange-Diagnostics: 1; DB4PR07MB0592; 20:bEQ2rHyidkuiC0hqR6KUunD4b5z+bMz08/avuI5POB6YekQteAmJXdOU1Bu4LDZqvHXU54RAByklIzTxJ6eI/DzkiPOzR7p1EZtvSbQkX0nCCd4SYwPgVmPU4Cfy45aI6X8p0cJswZi2ZHPHJsywEYLB8kbjDl+Z3Lb+cFtKY0Bafx6KkghTsnwC9zWR3sjibQcnTkVlsXF4/KWRhbfvdcXK84/qstmjG1SepaHF53pwMEWByC5MoeqpSkbTsrGPcTKjZIVeWxh8qxxfxniAIHQT7UZPEQg6cQ8y0EXmRtsrV3zLmKjzO2MfwYFnJt5784urSfcrTx0VH2NY3Me0UvNswzPHm5sV0B7uHfRKlsWQ0neTSZIdoRqnoceidBvDpWB7IQHsstYXOCoVH28T2mrVcr0LbsucQyAWEBHffDnfwCPACdkWU75+D+KrYBeRwetNy7Bt1jfuT4IjaSMtdrLq0JPqW1y7/cxq9XyZRJmjoLss2NZ9fiAIG/l7w7s1xEdkjtk8y3j4INyy/BjYe7Bw5lMhirWW481QWo9+0WWIuRqOzFeYCIeiMHlw+wkjwitkoDIQcSYtB9h4elBTY8zZSarKBFEpemAGpxecZnY=
X-Microsoft-Antispam-PRVS: <DB4PR07MB05923446C1C73E1B75490C3D8FF10@DB4PR07MB0592.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(13016025)(5005006)(8121501046)(13018025)(10201501046)(3002001)(93006095)(93004095)(6055026)(6041248)(20161123555025)(20161123564025)(20161123562025)(20161123560025)(20161123558100)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(6072148); SRVR:DB4PR07MB0592; BCL:0; PCL:0; RULEID:; SRVR:DB4PR07MB0592; 
X-Microsoft-Exchange-Diagnostics: 1; DB4PR07MB0592; 4:jnQ8PyfSwstnMmrhK2QDt/DtNb9xnkXNzVHXJ5XNBet4zjoJOAupRT1KymuiSCcdH/1MQxnScPM6rVnKWGZT5ri4fvj7RiVZmi41uoqJEOGW096D9ONlXUdinhKxKQrMTcT9Xg9j9j4jX5ii/3x0PiLcWhTnAD2OvFbes/ieVOggNeiwZ7eCQUKwsd9TuLYRafle6Bvz3+uzbwSlnurqnG3Uq0ug2ae2w3iGxFv9JzYaRcAOJpqkoz/cECaAiAK8BB8CmSgE7QT6v9VlrY+nhwflxuZzoB5oZsN6+uW2k9EDZ3GFxV/bnWOuC07tdcYkGZ0E9+T+9ynComVJGEEoczzTYEzOqpu+hxjzj4yM+UhsIJUKGW2VKe54990J5Og0U63QvkMQruBY6af8t0PwznKC5D30m8MWxSYu9QgSSLfBCrIgMmhxuHJvienxggdNOLa8GloGwK0psIT7B4+C9T3jLtbvzgKbv3866KUYaEt/HoYvm+pI6vzjSyoWzy6/tw9kRqx4XmFkzF8i5SRej4MbAGG0YulPZ8YEiBIkxJVJ+GG7dk61eZmPdLBshDsr1fL77lK4HvjzHm0wxr4qe/pdwC6a2q9N0Gd44M+KH8FvwhOAyDJxIGJJqIG2RC7g5853tOi1yZF7ftHMm0ixp4ovLGFBhEsWuuP8hD58aEDmTHrXPyd+FvLnCuLLc6ZB6zgsG6cZqV77HthEGQLjT9fZDWG90xTIlPzSO94hb2cZ9Rxt2/XGjQoxzGYen9scBj/SQvtJe36loMUAlaDwhNKhQvbVeFjc2cbff0dDsRST19k9vCQp7VnJxAPksVNVJLnkyilg2sGt4OIZQ5QpMA==
X-Forefront-PRVS: 0324C2C0E2
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; DB4PR07MB0592; 23:hl0Fj57tu1jh7uZN6NY/gqdvkAwC/TBcXmao7l/0t?= =?us-ascii?Q?S+5f1irfp31ggARiXgvntvR32bwH6wftHG8RBnRgUzQEFZvZybAntPeXg1w1?= =?us-ascii?Q?ITdOleIWveATMo9zbIBebCRK5h9WN5gZ3phbvBmpNdBIYPOtxsDbGjz2cYuf?= =?us-ascii?Q?d0Jo3vHdpY8yssS1bEMIfbD0xhcWAXYpZ+jL9z4P8YTt9kr0m5N4OzhSNR9h?= =?us-ascii?Q?7EOs/Dha/KrSN99xDYGt7HQl+GbTpGaPrkS4+Erp2ED5XXMCjM7/uRIM0p6S?= =?us-ascii?Q?z1n9OmLC9T3zvSb6NAJGMZR1ZUKV99GqslG8mQU9qeCfRdS/+MlyLm5wsbDo?= =?us-ascii?Q?oWuP5t5x70Gt1fmPal2Ea9zJsNawIhH3oZXjXBFMCkLYruDmEAJG9gHZ8Rrb?= =?us-ascii?Q?plaJ8jqBYhcgyE8FcNJkS+QU0ksDsiYot9oKHdhtgBi4R+u07owl/mzpGsTL?= =?us-ascii?Q?b1wHbqUmJJeLZYqp0F0r1y2w+jJOTtG0aiE1LqvSGAbJbLl5chKZjCVAjmLj?= =?us-ascii?Q?TKtJfm8s0Uzp8PeyHCnKN9loduMPoIvO2HYAjR05eNsCIZSjg+2fFARYrTqn?= =?us-ascii?Q?CGpsx5CwgxItLmWRcWYlgmQgzYSscG+cdmVoZMRiGgapyIrgfLAiQ87kButK?= =?us-ascii?Q?u4lIIcerYSypDjhZnqdBz9s7s6NuhImi3HVeBO1DSRKxwTtP0iEIEK6w97w5?= =?us-ascii?Q?dZNqT7lGQKhx27Pkg/XAwCvoKS/p/orI01iZVR7pXX6kU73cqQvdW9JRev83?= =?us-ascii?Q?Iex1Z+Dqzb01f698hoTtEsVJ43DBJyiRvZ65iQDjJAJMV0h85jCOMyvYga8m?= =?us-ascii?Q?RizFeUylBdnKuOFLqURhEILwOqDq6wEgA10TkfQnTEJNFQwfNUq/5pZz9RS2?= =?us-ascii?Q?SsiXB4uPNQUYtgR5Bxeg+rdAftSWleTPVFodAmDfVBEUdNuP1eEPAB9f9oi2?= =?us-ascii?Q?A4Chp2FjwSCK8EDvHHsdPv+xertFlp2y8pvPS9u3U1aJit50G8FttPADHsdf?= =?us-ascii?Q?d7JiuwHwqQGVV3B/SWK+2oDPZ3Wi3OUqmBUQK209BdjJ2rfZT81wcb1BeNm5?= =?us-ascii?Q?wykY8SEtIJdRbOJqUyr24FnE1UFSKO4CXmqmG64Jy9aEirbb7GbtMLbM2jTi?= =?us-ascii?Q?SzD3lrmNffpCoGVDcC6m6BOdTRCgQZFrbBCnW2l1UPYnujWgvS3RvE4cEIQi?= =?us-ascii?Q?33L+Ztjdm9RLeuNnaMGHcbRFS/HWvwR6Xxe?=
X-Microsoft-Exchange-Diagnostics: 1; DB4PR07MB0592; 6:ogBS6xStUOFZBbmwz+cEoQIr5Z8mvANZkF7qOE23oWzF6bH8eXpYo3Ik17kDtDdZZ8qxjmzJim8fX3WLR3eR4XIijenALBXac+5oSZUA1AlFBvJJMyjKYY/yyoy8EvT4vx2bLb8VWb3QY7ux/fTD1genojhedafdaVE+CnooLNfCJJY45NMIm12QNRsuHnariacZr1BuQjcWbiFpglSsc3pzZ6SttTrMtgTAdllxS5Ack7xXklLyGNPeyhCXixFTdbAk1REE8gmXDtPuLR5pqYIhqiIM3xbFc7Ryya49TzOFS8vVRX8ME2l/pLFn9t2jJ4yD8fR0u7Lyy9h/cm0PcVsszp4SXSIfEPH5E/IkIclqnYeRk9oOCNoKLRpddqe/1Q9Wf/ExkVlYOhBRoHNjbhnTizvzGAiryYcaTimG+lxUFVQsTsU3bsJL/tQGAiA8fR3Le/T3y4A99QjBMLY0jGt8oUZt5Jlh0lf6CBLeTzJeeVv07Ma/ISjcGrC5n654r9eT55PpwFxBAZ7VUR4gCC2am39zvaL8tJq3272tffo=; 5:SilK8uwRl7bigvIUjdOeMzqMqzqW5ZnSuvWUwAWtlSsOYPRhi8q/4m7obThyVnIaI/3mNSbFYX3n08zodYeQbPxSEhPls7VoRILh/E5zreRJWDN9htBkRL+SPy74I3Qaj8XsrFnRzIsyI1Ymcg/q3sG7QVuMhEGnVcz62y1tm/4=; 24:fs51V742jAmSYCBzbNhYY46C8INvIiVOaKUR9VXef0SXX3MwT8tsilxU2idR8YFWWPnIBU5pY1IBOHcKZlH7s1uGvyTfu+UqaD1RUSgrDQw=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; DB4PR07MB0592; 7:jBRdUeoq2Hygx/xf1yf6N6/uVCzoL2xesbJ8Ih7ygQzMzA6Gl9dHaqza9Pw+JKq8j8efk96EcxOcEpOgCLGDDs1JPbQzOsUNeFeRcDoIfphgoq174F9pdqWmudkeTwWUpYKjIwvNu8oXpSzSN8twUygROBOv167eWlrDl8v4J0/cn7hTVbDE4jFGMj2EbdEvayeP9WDhKaWJTiKQkeWSCWisyzXUjdr08BgmdMM8Cng7j7OjkTDUAjoY1rGjETUUNlXCYQk52OvrxQof360u5gBrBTUzhBC14v4Yuhu8goDC8VVKcASs3EQellASvM3O60iVUAn8r7X3OFmCr6YBVg==
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 31 May 2017 01:52:07.3063 (UTC)
X-MS-Exchange-CrossTenant-Id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=5d471751-9675-428d-917b-70f44f9630b0; Ip=[135.245.43.121];  Helo=[us70uusmtp4-o.zam.alcatel-lucent.com]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB4PR07MB0592
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2tpext/lL38hjSfwPNPOl4LTmzDimjOqsM>
Subject: Re: [L2tpext] Propagating IP/ECN field when L2TP sits between IP as both L2 payload and PSN
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 31 May 2017 01:52:13 -0000

I am a little confused by the double negative in "non-optional".
Do you mean "mandatory"? If so, why not just say that?

The lack of a capabilities AVP that you were looking for is mainly
because it hasn't been needed so far. You are welcome to submit a
draft with something like that. Generally speaking, adding a simple
binary AVP is easy and simpler to handle.

I have no problem with the new suggested AVP, but can you explain
why is it important to know if the remote supports or not this
extension? Can't a tunnel end deduce this information by observing
the IP header received?

Regarding the extension vs update question: if it is an update,
then why negotiate support? Wouldn't ECN propagation be mandated
by this update?

There is no section for L2TPv2 (RFC2661) or any further suggestion
on how to handle it. I'm not saying that it is necessary, but since
it is mentioned earlier in the document, you may want to add a few
words. Note that things are a bit more complicated in v2 because
it transports PPP packets, which may include IP packets (or portions
of PPP packets if using Multilink). I have no issue punting on L2TPv2
details.

-Ignacio


At 15:49 5/30/2017, Bob Briscoe wrote:

>Hi l2tpext list, 
>[repeating previous post, but with self-explanatory subject line]
>
>This is a plea for help on a short subsection of a short draft that updates L2TP (amongst other tunnel protocols).
>
>In the Transport Area WG (tsvwg) we have been working on defining propagation of the ECN field between IP headers separated by shim header(s):
>    draft-ietf-tsvwg-rfc6040update-shim
>
>L2TP is one such protocol (when the payload of the L2 protocol is IP, and the outer PSN is IP). This is particularly relevant at the moment, because of the low latency (L4S) work based on ECN and because deployment of ECN has finally taken off {Note 1}.
>
>I presented this tunnelling work in intarea just under a year ago. Since then tsvwg has adopted the draft and asked that we include specific update text for each affected tunnel protocol. I just posted my first attempt at L2TP update text:
>    <https://tools.ietf.org/html/draft-ietf-tsvwg-rfc6040update-shim-01>draft-ietf-tsvwg-rfc6040update-shim-01
>
>Specific questions:
>
>Prize for the best answer to all 3 questions: you get to become a co-author (if you want :)
>
>Q1. L2TP is meant for all sorts of outers and inners, so it is not clear where to define behaviour for the special (but very common) case of IP as the L2 payload and IP and as the PSN. That is:
>     IP    :    [UDP]    :    L2TP    :    L2-specific-sublayer    :    L2    :    IP
>
>I decided on updating <Specific%20questions:>S.4.5 of RFC3931, but suggestions for a better place are welcome.
>
>Q2. L2TP is usually extended not updated. However, in this case, compliance with RFC6040 is non-optional, so I think update rather than extension is appropriate. Reason: Although RFC6040 is non-optional it includes a compatibility mode that defines what has to happen when a tunnel endpoint doesn't support ECN propagation. 
>
>Pls read the (short) draft and, if you disagree, suggest how an extension can be non-optional.
>
>Q3. The tunnel initiator needs to check that the other end supports ECN propagation. I have proposed an Attribute Value Pair (AVP) for this that is effectively just a boolean choice from each end (Yes or silence). I expected to find an AVP with per-control-connection flags for tunnel endpoint capabilities that I could just extend with one more flag, but there doesn't seem to be such a thing already in L2TP. Did I miss it?
>
>
>Cheers
>
>
>Bob
>
>{Note 1}: ~70% of Web servers, ~50% of Apple client devices on fixed or WiFi access, and now increasing router deployment of ECN is appearing.


From nobody Tue May 30 19:48:04 2017
Return-Path: <ietf@bobbriscoe.net>
X-Original-To: l2tpext@ietfa.amsl.com
Delivered-To: l2tpext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E2AD126DC2 for <l2tpext@ietfa.amsl.com>; Tue, 30 May 2017 19:48:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bobbriscoe.net
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 p579cD4jRcf0 for <l2tpext@ietfa.amsl.com>; Tue, 30 May 2017 19:48:00 -0700 (PDT)
Received: from server.dnsblock1.com (server.dnsblock1.com [85.13.236.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B91E126BF6 for <l2tpext@ietf.org>; Tue, 30 May 2017 19:48:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To:Subject:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=C8XX+x1XiT773FnceDh0g6+PfK4hEIgicXGKjhEwdNI=; b=xajiSpGuJkWGyZhKLzGHzeTcaI B2szpRKLNAjhenNhygj7faBy/ER96SzXa1JeNQobWjkcmRzdFDsvHfjp0JBToD4l9MMz7GX1vO1iI eVfnn0njtWLq+ABJA6BSohxMWRzaQCWBywUDuCIeulBtCh30ZfXgJ07ogOhvWckbAgThh2ltD6V/H hUZIMiwClLg/XiRjhk3DH9ll8SqwKzekbVuTRoUgkLyUBda+jqkIteKkDhbqCYlpIAje3FRMH0c7E V6y6gKu3P7RkidOvFN411sduqMNUkTtgKUapreyiA1YJCUtywdQh4FZGMqlW3epreU8xCqVQbpmcG qLbNVAxg==;
Received: from [31.185.135.175] (port=60178 helo=[192.168.0.2]) by server.dnsblock1.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from <ietf@bobbriscoe.net>) id 1dFtfy-0001Kw-Gk; Wed, 31 May 2017 03:47:58 +0100
To: Ignacio Goyret <ignacio.goyret@nokia.com>
Cc: l2tp IETF list <l2tpext@ietf.org>, "Black, David" <david.black@emc.com>
References: <149618019740.19809.6421141487388928973.idtracker@ietfa.amsl.com> <435f45b8-9659-b06f-9adc-415f355ba743@bobbriscoe.net> <e4c97c52-36c9-3091-b005-06ef82ec58e3@bobbriscoe.net> <201705310154.v4V1sYQH013223@cliff.eng.ascend.com>
From: Bob Briscoe <ietf@bobbriscoe.net>
Message-ID: <67456091-a3e0-2db1-5f8a-5210a1f870f1@bobbriscoe.net>
Date: Wed, 31 May 2017 03:47:57 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <201705310154.v4V1sYQH013223@cliff.eng.ascend.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.dnsblock1.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bobbriscoe.net
X-Get-Message-Sender-Via: server.dnsblock1.com: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: server.dnsblock1.com: in@bobbriscoe.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2tpext/PpM64rKy7-PfobFzQEzMUiYxaUY>
Subject: Re: [L2tpext] Propagating IP/ECN field when L2TP sits between IP as both L2 payload and PSN
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 31 May 2017 02:48:03 -0000

Ignacio,

Thanks for your rapid response.

On 31/05/17 02:51, Ignacio Goyret wrote:
> I am a little confused by the double negative in "non-optional".
> Do you mean "mandatory"? If so, why not just say that?
Yes, mandatory.
That language was not in the draft; only in my email.
>
> The lack of a capabilities AVP that you were looking for is mainly
> because it hasn't been needed so far. You are welcome to submit a
> draft with something like that. Generally speaking, adding a simple
> binary AVP is easy and simpler to handle.
Good.
>
> I have no problem with the new suggested AVP, but can you explain
> why is it important to know if the remote supports or not this
> extension? Can't a tunnel end deduce this information by observing
> the IP header received?
I'm afraid not. It is critical for the ingress (in each direction) to 
check that the egress decap will correctly propagate the outer ECN field 
into the forwarded payload protocol. Otherwise explicit congestion 
signals added by a node within the tunnel could just get stripped at 
decap. With congestion feedback black-holed, the load would continue to 
increase until overload and tail drop.

BTW, the forwarded ECN field after decap has to be a combination of the 
ECN fields in the outer and inner IP headers (RFC6040 gives a 4x4 matrix 
of all the combinations of the two 2-bit ECN codepoints). So I am 
interested to know whether this might present problems for L2TP 
implementations (ECN propagation on decap has been implemented OK in 
Linux for similar structures like VXLAN).

>
> Regarding the extension vs update question: if it is an update,
> then why negotiate support? Wouldn't ECN propagation be mandated
> by this update?
Unfortunately, a mandatory update still has to cope with the above 
incremental deployment problem.
>
> There is no section for L2TPv2 (RFC2661) or any further suggestion
> on how to handle it. I'm not saying that it is necessary, but since
> it is mentioned earlier in the document, you may want to add a few
> words. Note that things are a bit more complicated in v2 because
> it transports PPP packets, which may include IP packets (or portions
> of PPP packets if using Multilink). I have no issue punting on L2TPv2
> details.
* Given you say L2TPv2 is more complicated cos it transports PPP 
packets, that seems to imply that L2TPv3 does not transport PPP, which 
doesn't sound right?

I don't fully understand the relationship between L2TPv2 & v3 (I have 
come across L2TP a lot in an operational context, but never really 
studied it as a protocol until now).

* Is there still a lot of L2TPv2 around?

* Would it be believable that a L2TPv2 implementation might be updated 
for ECN support but not updated to L2TPv3?

Cheers


Bob

>
> -Ignacio
>
>
> At 15:49 5/30/2017, Bob Briscoe wrote:
>
>> Hi l2tpext list,
>> [repeating previous post, but with self-explanatory subject line]
>>
>> This is a plea for help on a short subsection of a short draft that updates L2TP (amongst other tunnel protocols).
>>
>> In the Transport Area WG (tsvwg) we have been working on defining propagation of the ECN field between IP headers separated by shim header(s):
>>     draft-ietf-tsvwg-rfc6040update-shim
>>
>> L2TP is one such protocol (when the payload of the L2 protocol is IP, and the outer PSN is IP). This is particularly relevant at the moment, because of the low latency (L4S) work based on ECN and because deployment of ECN has finally taken off {Note 1}.
>>
>> I presented this tunnelling work in intarea just under a year ago. Since then tsvwg has adopted the draft and asked that we include specific update text for each affected tunnel protocol. I just posted my first attempt at L2TP update text:
>>     <https://tools.ietf.org/html/draft-ietf-tsvwg-rfc6040update-shim-01>draft-ietf-tsvwg-rfc6040update-shim-01
>>
>> Specific questions:
>>
>> Prize for the best answer to all 3 questions: you get to become a co-author (if you want :)
>>
>> Q1. L2TP is meant for all sorts of outers and inners, so it is not clear where to define behaviour for the special (but very common) case of IP as the L2 payload and IP and as the PSN. That is:
>>      IP    :    [UDP]    :    L2TP    :    L2-specific-sublayer    :    L2    :    IP
>>
>> I decided on updating <Specific%20questions:>S.4.5 of RFC3931, but suggestions for a better place are welcome.
>>
>> Q2. L2TP is usually extended not updated. However, in this case, compliance with RFC6040 is non-optional, so I think update rather than extension is appropriate. Reason: Although RFC6040 is non-optional it includes a compatibility mode that defines what has to happen when a tunnel endpoint doesn't support ECN propagation.
>>
>> Pls read the (short) draft and, if you disagree, suggest how an extension can be non-optional.
>>
>> Q3. The tunnel initiator needs to check that the other end supports ECN propagation. I have proposed an Attribute Value Pair (AVP) for this that is effectively just a boolean choice from each end (Yes or silence). I expected to find an AVP with per-control-connection flags for tunnel endpoint capabilities that I could just extend with one more flag, but there doesn't seem to be such a thing already in L2TP. Did I miss it?
>>
>>
>> Cheers
>>
>>
>> Bob
>>
>> {Note 1}: ~70% of Web servers, ~50% of Apple client devices on fixed or WiFi access, and now increasing router deployment of ECN is appearing.

-- 
________________________________________________________________
Bob Briscoe                               http://bobbriscoe.net/


From nobody Wed May 31 09:44:33 2017
Return-Path: <cpignata@cisco.com>
X-Original-To: l2tpext@ietfa.amsl.com
Delivered-To: l2tpext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DF1A129572 for <l2tpext@ietfa.amsl.com>; Wed, 31 May 2017 09:44:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 F1uTQBdg-Wxa for <l2tpext@ietfa.amsl.com>; Wed, 31 May 2017 09:44:30 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5711F1293DB for <l2tpext@ietf.org>; Wed, 31 May 2017 09:44:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=20999; q=dns/txt; s=iport; t=1496249070; x=1497458670; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=65aU0CisLZ6wYQeOznl9WI41+i+rwpa535hO6lR3q1c=; b=FxXppwavZPx1lSzmU9yN7Qoa9BgxL/LkxqI+3vELm+rdo4iv4k8uGyCl aw6L8x3rxL+NbhJSOqPfJ2ROt6yU+QlPUTLSMVRvQeQl/15HZ3FYQclQt NhyvxoKk1dttwTNpsITd79N8meeqLmKnaulhFD/y6vUGfrfaxBANZRHsK o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DcAAAG8i5Z/4YNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1VigQ2FeIgSkU6DCpMQgg8hAQqEHoEQSgKCZj8YAQIBAQEBAQE?= =?us-ascii?q?BayiFGQIBAwEBbAQHEAIBCA4xBycLFBECBA4FiUZkEK5Qi1EBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEdhmGBYCsLgV2BDIUhBoMDgjEFlnmHKgGHH4wIggZViFOGSYk?= =?us-ascii?q?Bi0wBHzh/C3QVRhIBhDc5HBmBSQF2iVMBAQE?=
X-IronPort-AV: E=Sophos;i="5.39,275,1493683200";  d="scan'208,217";a="431771281"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 31 May 2017 16:44:29 +0000
Received: from XCH-RTP-017.cisco.com (xch-rtp-017.cisco.com [64.101.220.157]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id v4VGiSZ7016735 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 31 May 2017 16:44:29 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-017.cisco.com (64.101.220.157) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 31 May 2017 12:44:28 -0400
Received: from xch-rtp-020.cisco.com ([64.101.220.160]) by XCH-RTP-020.cisco.com ([64.101.220.160]) with mapi id 15.00.1210.000; Wed, 31 May 2017 12:44:28 -0400
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Bob Briscoe <ietf@bobbriscoe.net>
CC: Ignacio Goyret <ignacio.goyret@nokia.com>, "Black, David" <david.black@emc.com>, l2tp IETF list <l2tpext@ietf.org>
Thread-Topic: [L2tpext] Propagating IP/ECN field when L2TP sits between IP as both L2 payload and PSN
Thread-Index: AQHS2ZcTIeyponFXbEO090UycmlUEaIN8MsAgAAPs4CAAKaqpw==
Date: Wed, 31 May 2017 16:44:28 +0000
Message-ID: <B00A6885-6EB1-4361-8412-C408F23DC5E0@cisco.com>
References: <149618019740.19809.6421141487388928973.idtracker@ietfa.amsl.com> <435f45b8-9659-b06f-9adc-415f355ba743@bobbriscoe.net> <e4c97c52-36c9-3091-b005-06ef82ec58e3@bobbriscoe.net> <201705310154.v4V1sYQH013223@cliff.eng.ascend.com>, <67456091-a3e0-2db1-5f8a-5210a1f870f1@bobbriscoe.net>
In-Reply-To: <67456091-a3e0-2db1-5f8a-5210a1f870f1@bobbriscoe.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_B00A68856EB143618412C408F23DC5E0ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2tpext/HxC6uNbHgqYzXiEa-5OEE4orcZY>
Subject: Re: [L2tpext] Propagating IP/ECN field when L2TP sits between IP as both L2 payload and PSN
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 31 May 2017 16:44:32 -0000

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

Hi, Bob,

Adding on a couple of bits on top of Ignacio's response.

L2TPv2, RFC 2661, transports only PPP (and multi protocols within it, inclu=
ding of course IP) and runs over UDP. In contrast, L2TPv3 transports direct=
ly a variety of protocols (Ethernet, HDLC, etc.) and runs directly over IP =
protocol 115 or over UDP. RFC 3931 is the base L2TPv3 specification but nee=
ds a protocol companion document. Some of those protocols are finished, e.g=
. RFC 4719 but others like PPP or "raw" IP are in Internet-Drafts.

By the way you can find example of capabilities in subsections of Section 5=
.1.1 of https://tools.ietf.org/html/draft-ietf-l2tpext-l2tp-ppp-08

I do not understand however why "Update", or what that implies to a complia=
nt implementation. Many features of L2TP are specified in various WGs, not =
"Updating" the base specs.

Thanks,

Sent from my iPad

On May 30, 2017, at 10:48 PM, Bob Briscoe <ietf@bobbriscoe.net<mailto:ietf@=
bobbriscoe.net>> wrote:

Ignacio,

Thanks for your rapid response.

On 31/05/17 02:51, Ignacio Goyret wrote:
I am a little confused by the double negative in "non-optional".
Do you mean "mandatory"? If so, why not just say that?
Yes, mandatory.
That language was not in the draft; only in my email.

The lack of a capabilities AVP that you were looking for is mainly
because it hasn't been needed so far. You are welcome to submit a
draft with something like that. Generally speaking, adding a simple
binary AVP is easy and simpler to handle.
Good.

I have no problem with the new suggested AVP, but can you explain
why is it important to know if the remote supports or not this
extension? Can't a tunnel end deduce this information by observing
the IP header received?
I'm afraid not. It is critical for the ingress (in each direction) to check=
 that the egress decap will correctly propagate the outer ECN field into th=
e forwarded payload protocol. Otherwise explicit congestion signals added b=
y a node within the tunnel could just get stripped at decap. With congestio=
n feedback black-holed, the load would continue to increase until overload =
and tail drop.

BTW, the forwarded ECN field after decap has to be a combination of the ECN=
 fields in the outer and inner IP headers (RFC6040 gives a 4x4 matrix of al=
l the combinations of the two 2-bit ECN codepoints). So I am interested to =
know whether this might present problems for L2TP implementations (ECN prop=
agation on decap has been implemented OK in Linux for similar structures li=
ke VXLAN).


Regarding the extension vs update question: if it is an update,
then why negotiate support? Wouldn't ECN propagation be mandated
by this update?
Unfortunately, a mandatory update still has to cope with the above incremen=
tal deployment problem.

There is no section for L2TPv2 (RFC2661) or any further suggestion
on how to handle it. I'm not saying that it is necessary, but since
it is mentioned earlier in the document, you may want to add a few
words. Note that things are a bit more complicated in v2 because
it transports PPP packets, which may include IP packets (or portions
of PPP packets if using Multilink). I have no issue punting on L2TPv2
details.
* Given you say L2TPv2 is more complicated cos it transports PPP packets, t=
hat seems to imply that L2TPv3 does not transport PPP, which doesn't sound =
right?

I don't fully understand the relationship between L2TPv2 & v3 (I have come =
across L2TP a lot in an operational context, but never really studied it as=
 a protocol until now).

* Is there still a lot of L2TPv2 around?

* Would it be believable that a L2TPv2 implementation might be updated for =
ECN support but not updated to L2TPv3?

Cheers


Bob


-Ignacio


At 15:49 5/30/2017, Bob Briscoe wrote:

Hi l2tpext list,
[repeating previous post, but with self-explanatory subject line]

This is a plea for help on a short subsection of a short draft that updates=
 L2TP (amongst other tunnel protocols).

In the Transport Area WG (tsvwg) we have been working on defining propagati=
on of the ECN field between IP headers separated by shim header(s):
   draft-ietf-tsvwg-rfc6040update-shim

L2TP is one such protocol (when the payload of the L2 protocol is IP, and t=
he outer PSN is IP). This is particularly relevant at the moment, because o=
f the low latency (L4S) work based on ECN and because deployment of ECN has=
 finally taken off {Note 1}.

I presented this tunnelling work in intarea just under a year ago. Since th=
en tsvwg has adopted the draft and asked that we include specific update te=
xt for each affected tunnel protocol. I just posted my first attempt at L2T=
P update text:
   <https://tools.ietf.org/html/draft-ietf-tsvwg-rfc6040update-shim-01>draf=
t-ietf-tsvwg-rfc6040update-shim-01

Specific questions:

Prize for the best answer to all 3 questions: you get to become a co-author=
 (if you want :)

Q1. L2TP is meant for all sorts of outers and inners, so it is not clear wh=
ere to define behaviour for the special (but very common) case of IP as the=
 L2 payload and IP and as the PSN. That is:
    IP    :    [UDP]    :    L2TP    :    L2-specific-sublayer    :    L2  =
  :    IP

I decided on updating <Specific%20questions:>S.4.5 of RFC3931, but suggesti=
ons for a better place are welcome.

Q2. L2TP is usually extended not updated. However, in this case, compliance=
 with RFC6040 is non-optional, so I think update rather than extension is a=
ppropriate. Reason: Although RFC6040 is non-optional it includes a compatib=
ility mode that defines what has to happen when a tunnel endpoint doesn't s=
upport ECN propagation.

Pls read the (short) draft and, if you disagree, suggest how an extension c=
an be non-optional.

Q3. The tunnel initiator needs to check that the other end supports ECN pro=
pagation. I have proposed an Attribute Value Pair (AVP) for this that is ef=
fectively just a boolean choice from each end (Yes or silence). I expected =
to find an AVP with per-control-connection flags for tunnel endpoint capabi=
lities that I could just extend with one more flag, but there doesn't seem =
to be such a thing already in L2TP. Did I miss it?


Cheers


Bob

{Note 1}: ~70% of Web servers, ~50% of Apple client devices on fixed or WiF=
i access, and now increasing router deployment of ECN is appearing.

--
________________________________________________________________
Bob Briscoe                               http://bobbriscoe.net/

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

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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body dir=3D"auto">
<div><span></span></div>
<div>
<div>Hi, Bob,</div>
<div><br>
</div>
<div>Adding on a couple of bits on top of Ignacio's response.&nbsp;<br>
<br>
L2TPv2, RFC 2661, transports only PPP (and multi protocols within it, inclu=
ding of course IP) and runs over UDP. In contrast, L2TPv3 transports direct=
ly a variety of protocols (Ethernet, HDLC, etc.) and runs directly over IP =
protocol 115 or over UDP. RFC 3931
 is the base L2TPv3 specification but needs a protocol companion document. =
Some of those protocols are finished, e.g. RFC 4719 but others like PPP or =
&quot;raw&quot; IP are in Internet-Drafts.&nbsp;</div>
<div><br>
</div>
<div>By the way you can find example of capabilities in subsections of Sect=
ion 5.1.1 of&nbsp;<a href=3D"https://tools.ietf.org/html/draft-ietf-l2tpext=
-l2tp-ppp-08">https://tools.ietf.org/html/draft-ietf-l2tpext-l2tp-ppp-08</a=
></div>
<div><br>
</div>
<div>I do not understand however why &quot;Update&quot;, or what that impli=
es to a compliant implementation. Many features of L2TP are specified in va=
rious WGs, not &quot;Updating&quot; the base specs.&nbsp;</div>
<div><br>
</div>
<div>Thanks,<br>
<br>
<div>Sent from my iPad</div>
</div>
<div><br>
On May 30, 2017, at 10:48 PM, Bob Briscoe &lt;<a href=3D"mailto:ietf@bobbri=
scoe.net">ietf@bobbriscoe.net</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div><span>Ignacio,</span><br>
<span></span><br>
<span>Thanks for your rapid response.</span><br>
<span></span><br>
<span>On 31/05/17 02:51, Ignacio Goyret wrote:</span><br>
<blockquote type=3D"cite"><span>I am a little confused by the double negati=
ve in &quot;non-optional&quot;.</span><br>
</blockquote>
<blockquote type=3D"cite"><span>Do you mean &quot;mandatory&quot;? If so, w=
hy not just say that?</span><br>
</blockquote>
<span>Yes, mandatory.</span><br>
<span>That language was not in the draft; only in my email.</span><br>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>The lack of a capabilities AVP that you wer=
e looking for is mainly</span><br>
</blockquote>
<blockquote type=3D"cite"><span>because it hasn't been needed so far. You a=
re welcome to submit a</span><br>
</blockquote>
<blockquote type=3D"cite"><span>draft with something like that. Generally s=
peaking, adding a simple</span><br>
</blockquote>
<blockquote type=3D"cite"><span>binary AVP is easy and simpler to handle.</=
span><br>
</blockquote>
<span>Good.</span><br>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>I have no problem with the new suggested AV=
P, but can you explain</span><br>
</blockquote>
<blockquote type=3D"cite"><span>why is it important to know if the remote s=
upports or not this</span><br>
</blockquote>
<blockquote type=3D"cite"><span>extension? Can't a tunnel end deduce this i=
nformation by observing</span><br>
</blockquote>
<blockquote type=3D"cite"><span>the IP header received?</span><br>
</blockquote>
<span>I'm afraid not. It is critical for the ingress (in each direction) to=
 check that the egress decap will correctly propagate the outer ECN field i=
nto the forwarded payload protocol. Otherwise explicit congestion signals a=
dded by a node within the tunnel
 could just get stripped at decap. With congestion feedback black-holed, th=
e load would continue to increase until overload and tail drop.</span><br>
<span></span><br>
<span>BTW, the forwarded ECN field after decap has to be a combination of t=
he ECN fields in the outer and inner IP headers (RFC6040 gives a 4x4 matrix=
 of all the combinations of the two 2-bit ECN codepoints). So I am interest=
ed to know whether this might present
 problems for L2TP implementations (ECN propagation on decap has been imple=
mented OK in Linux for similar structures like VXLAN).</span><br>
<span></span><br>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>Regarding the extension vs update question:=
 if it is an update,</span><br>
</blockquote>
<blockquote type=3D"cite"><span>then why negotiate support? Wouldn't ECN pr=
opagation be mandated</span><br>
</blockquote>
<blockquote type=3D"cite"><span>by this update?</span><br>
</blockquote>
<span>Unfortunately, a mandatory update still has to cope with the above in=
cremental deployment problem.</span><br>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>There is no section for L2TPv2 (RFC2661) or=
 any further suggestion</span><br>
</blockquote>
<blockquote type=3D"cite"><span>on how to handle it. I'm not saying that it=
 is necessary, but since</span><br>
</blockquote>
<blockquote type=3D"cite"><span>it is mentioned earlier in the document, yo=
u may want to add a few</span><br>
</blockquote>
<blockquote type=3D"cite"><span>words. Note that things are a bit more comp=
licated in v2 because</span><br>
</blockquote>
<blockquote type=3D"cite"><span>it transports PPP packets, which may includ=
e IP packets (or portions</span><br>
</blockquote>
<blockquote type=3D"cite"><span>of PPP packets if using Multilink). I have =
no issue punting on L2TPv2</span><br>
</blockquote>
<blockquote type=3D"cite"><span>details.</span><br>
</blockquote>
<span>* Given you say L2TPv2 is more complicated cos it transports PPP pack=
ets, that seems to imply that L2TPv3 does not transport PPP, which doesn't =
sound right?</span><br>
<span></span><br>
<span>I don't fully understand the relationship between L2TPv2 &amp; v3 (I =
have come across L2TP a lot in an operational context, but never really stu=
died it as a protocol until now).</span><br>
<span></span><br>
<span>* Is there still a lot of L2TPv2 around?</span><br>
<span></span><br>
<span>* Would it be believable that a L2TPv2 implementation might be update=
d for ECN support but not updated to L2TPv3?</span><br>
<span></span><br>
<span>Cheers</span><br>
<span></span><br>
<span></span><br>
<span>Bob</span><br>
<span></span><br>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>-Ignacio</span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>At 15:49 5/30/2017, Bob Briscoe wrote:</spa=
n><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>Hi l2tpext list,</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>[repeating previous post, but with self-exp=
lanatory subject line]</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>This is a plea for help on a short subsecti=
on of a short draft that updates L2TP (amongst other tunnel protocols).</sp=
an><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>In the Transport Area WG (tsvwg) we have be=
en working on defining propagation of the ECN field between IP headers sepa=
rated by shim header(s):</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>&nbsp;&nbsp;&nbsp;draft-ietf-tsvwg-rfc6040u=
pdate-shim</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>L2TP is one such protocol (when the payload=
 of the L2 protocol is IP, and the outer PSN is IP). This is particularly r=
elevant at the moment, because of the low latency (L4S) work based on ECN a=
nd because deployment of ECN has finally
 taken off {Note 1}.</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>I presented this tunnelling work in intarea=
 just under a year ago. Since then tsvwg has adopted the draft and asked th=
at we include specific update text for each affected tunnel protocol. I jus=
t posted my first attempt at L2TP
 update text:</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>&nbsp;&nbsp;&nbsp;&lt;<a href=3D"https://to=
ols.ietf.org/html/draft-ietf-tsvwg-rfc6040update-shim-01">https://tools.iet=
f.org/html/draft-ietf-tsvwg-rfc6040update-shim-01</a>&gt;draft-ietf-tsvwg-r=
fc6040update-shim-01</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>Specific questions:</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>Prize for the best answer to all 3 question=
s: you get to become a co-author (if you want :)</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>Q1. L2TP is meant for all sorts of outers a=
nd inners, so it is not clear where to define behaviour for the special (bu=
t very common) case of IP as the L2 payload and IP and as the PSN. That is:=
</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>&nbsp;&nbsp;&nbsp;&nbsp;IP &nbsp;&nbsp;&nbs=
p;: &nbsp;&nbsp;&nbsp;[UDP] &nbsp;&nbsp;&nbsp;: &nbsp;&nbsp;&nbsp;L2TP &nbs=
p;&nbsp;&nbsp;: &nbsp;&nbsp;&nbsp;L2-specific-sublayer &nbsp;&nbsp;&nbsp;: =
&nbsp;&nbsp;&nbsp;L2 &nbsp;&nbsp;&nbsp;: &nbsp;&nbsp;&nbsp;IP</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>I decided on updating &lt;Specific%20questi=
ons:&gt;S.4.5 of RFC3931, but suggestions for a better place are welcome.</=
span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>Q2. L2TP is usually extended not updated. H=
owever, in this case, compliance with RFC6040 is non-optional, so I think u=
pdate rather than extension is appropriate. Reason: Although RFC6040 is non=
-optional it includes a compatibility
 mode that defines what has to happen when a tunnel endpoint doesn't suppor=
t ECN propagation.</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>Pls read the (short) draft and, if you disa=
gree, suggest how an extension can be non-optional.</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>Q3. The tunnel initiator needs to check tha=
t the other end supports ECN propagation. I have proposed an Attribute Valu=
e Pair (AVP) for this that is effectively just a boolean choice from each e=
nd (Yes or silence). I expected to
 find an AVP with per-control-connection flags for tunnel endpoint capabili=
ties that I could just extend with one more flag, but there doesn't seem to=
 be such a thing already in L2TP. Did I miss it?</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>Cheers</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>Bob</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>{Note 1}: ~70% of Web servers, ~50% of Appl=
e client devices on fixed or WiFi access, and now increasing router deploym=
ent of ECN is appearing.</span><br>
</blockquote>
</blockquote>
<span></span><br>
<span>-- </span><br>
<span>________________________________________________________________</spa=
n><br>
<span>Bob Briscoe &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"http://bobbrisco=
e.net/">http://bobbriscoe.net/</a></span><br>
<span></span><br>
<span>_______________________________________________</span><br>
<span>L2tpext mailing list</span><br>
<span><a href=3D"mailto:L2tpext@ietf.org">L2tpext@ietf.org</a></span><br>
<span><a href=3D"https://www.ietf.org/mailman/listinfo/l2tpext">https://www=
.ietf.org/mailman/listinfo/l2tpext</a></span><br>
</div>
</blockquote>
</div>
</body>
</html>

--_000_B00A68856EB143618412C408F23DC5E0ciscocom_--


From nobody Wed May 31 15:11:59 2017
Return-Path: <ietf@bobbriscoe.net>
X-Original-To: l2tpext@ietfa.amsl.com
Delivered-To: l2tpext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2ED6D129445 for <l2tpext@ietfa.amsl.com>; Wed, 31 May 2017 15:11:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bobbriscoe.net
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 7o8bV7gAVu6D for <l2tpext@ietfa.amsl.com>; Wed, 31 May 2017 15:11:54 -0700 (PDT)
Received: from server.dnsblock1.com (server.dnsblock1.com [85.13.236.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BD3F1271DF for <l2tpext@ietf.org>; Wed, 31 May 2017 15:11:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=Content-Type:In-Reply-To:MIME-Version:Date: Message-ID:From:References:Cc:To:Subject:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=R8CdCOD6EDk7uQE2k9zcLPleDaprAAyixdo60qpI1i0=; b=ea8cOB9Ny1BBz1DOyjHXwwU1F qaEbbYwBYhXS8Ih6I9cerpJX+qW0/GVM/4o2cyy7VjbAjWPsJ06EbcTD61byD50mdYLe3+A9X30Ju 2FVS5Junxe5M6lvyR7x12oE1ro0NymcCs1sdhu81NrF3p0PI7Qma3PTAL60hs4CWYGUJUuMP/7J5q DH1YaSl59qUzM67y59eie28IrrATbXeghCXJmbedhlTLH/nfNKEOKDFfnd4WmIwufMaopHKH30zMj diTA0liM3Hbc/N9ZM8kpCU4EwWOPkv12y5TkV1v66FNjxko1HjJhCz4EmxnJ1o7oBnP1um5oPk36b qdlrzIBVw==;
Received: from [31.185.135.175] (port=46454 helo=[192.168.0.2]) by server.dnsblock1.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from <ietf@bobbriscoe.net>) id 1dGBqJ-000379-GG; Wed, 31 May 2017 23:11:52 +0100
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Cc: Ignacio Goyret <ignacio.goyret@nokia.com>, "Black, David" <david.black@emc.com>, l2tp IETF list <l2tpext@ietf.org>
References: <149618019740.19809.6421141487388928973.idtracker@ietfa.amsl.com> <435f45b8-9659-b06f-9adc-415f355ba743@bobbriscoe.net> <e4c97c52-36c9-3091-b005-06ef82ec58e3@bobbriscoe.net> <201705310154.v4V1sYQH013223@cliff.eng.ascend.com> <67456091-a3e0-2db1-5f8a-5210a1f870f1@bobbriscoe.net> <B00A6885-6EB1-4361-8412-C408F23DC5E0@cisco.com>
From: Bob Briscoe <ietf@bobbriscoe.net>
Message-ID: <70866121-f350-d6d2-d89a-89ca1315f5ab@bobbriscoe.net>
Date: Wed, 31 May 2017 23:11:50 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <B00A6885-6EB1-4361-8412-C408F23DC5E0@cisco.com>
Content-Type: multipart/alternative; boundary="------------9C6D938E48909A273291594B"
Content-Language: en-GB
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.dnsblock1.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bobbriscoe.net
X-Get-Message-Sender-Via: server.dnsblock1.com: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: server.dnsblock1.com: in@bobbriscoe.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2tpext/JFmkzzJo9MgD35Bc3P3fEyAkH5g>
Subject: Re: [L2tpext] Propagating IP/ECN field when L2TP sits between IP as both L2 payload and PSN
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 31 May 2017 22:11:58 -0000

This is a multi-part message in MIME format.
--------------9C6D938E48909A273291594B
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

Carlos,

On 31/05/17 17:44, Carlos Pignataro (cpignata) wrote:
> Hi, Bob,
>
> Adding on a couple of bits on top of Ignacio's response.
>
> L2TPv2, RFC 2661, transports only PPP (and multi protocols within it, 
> including of course IP) and runs over UDP. In contrast, L2TPv3 
> transports directly a variety of protocols (Ethernet, HDLC, etc.) and 
> runs directly over IP protocol 115 or over UDP. RFC 3931 is the base 
> L2TPv3 specification but needs a protocol companion document. Some of 
> those protocols are finished, e.g. RFC 4719 but others like PPP or 
> "raw" IP are in Internet-Drafts.
Yup, got all that. Thanks.

I just didn't understand the implication of Ignacio's email that 
updating the v2 protocol (that solely supports PPP) could be more 
complex than updating the v3 protocol that I thought supported PPP and 
many more protocols. It implied (to me) that maybe v3 doesn't support 
PPP in some way.

>
> By the way you can find example of capabilities in subsections of 
> Section 5.1.1 of 
> https://tools.ietf.org/html/draft-ietf-l2tpext-l2tp-ppp-08
>
> I do not understand however why "Update", or what that implies to a 
> compliant implementation. Many features of L2TP are specified in 
> various WGs, not "Updating" the base specs.
By my understanding of the word extension, if a implementation that is 
compliant with RFC3931 does not implement an extension, it is still 
compliant with RFC3931. Is this how the word "extension" is used in L2TP 
land?

Whereas, if one IP header encapsulates another, if the ECN field were 
processed in any way other than RFC6040, it would be invalid (unless 
another RFC were written to update RFC6040). Therefore, whenever L2TP is 
tunnelling IP in IP, it is mandatory to comply with RFC6040. So I am 
asking the L2TPext WG for advice on how you guys would make a mandatory 
update to L2TP, rather than 'just' an optional extension.


Bob

> Thanks,
>
> Sent from my iPad
>
> On May 30, 2017, at 10:48 PM, Bob Briscoe <ietf@bobbriscoe.net 
> <mailto:ietf@bobbriscoe.net>> wrote:
>
>> Ignacio,
>>
>> Thanks for your rapid response.
>>
>> On 31/05/17 02:51, Ignacio Goyret wrote:
>>> I am a little confused by the double negative in "non-optional".
>>> Do you mean "mandatory"? If so, why not just say that?
>> Yes, mandatory.
>> That language was not in the draft; only in my email.
>>>
>>> The lack of a capabilities AVP that you were looking for is mainly
>>> because it hasn't been needed so far. You are welcome to submit a
>>> draft with something like that. Generally speaking, adding a simple
>>> binary AVP is easy and simpler to handle.
>> Good.
>>>
>>> I have no problem with the new suggested AVP, but can you explain
>>> why is it important to know if the remote supports or not this
>>> extension? Can't a tunnel end deduce this information by observing
>>> the IP header received?
>> I'm afraid not. It is critical for the ingress (in each direction) to 
>> check that the egress decap will correctly propagate the outer ECN 
>> field into the forwarded payload protocol. Otherwise explicit 
>> congestion signals added by a node within the tunnel could just get 
>> stripped at decap. With congestion feedback black-holed, the load 
>> would continue to increase until overload and tail drop.
>>
>> BTW, the forwarded ECN field after decap has to be a combination of 
>> the ECN fields in the outer and inner IP headers (RFC6040 gives a 4x4 
>> matrix of all the combinations of the two 2-bit ECN codepoints). So I 
>> am interested to know whether this might present problems for L2TP 
>> implementations (ECN propagation on decap has been implemented OK in 
>> Linux for similar structures like VXLAN).
>>
>>>
>>> Regarding the extension vs update question: if it is an update,
>>> then why negotiate support? Wouldn't ECN propagation be mandated
>>> by this update?
>> Unfortunately, a mandatory update still has to cope with the above 
>> incremental deployment problem.
>>>
>>> There is no section for L2TPv2 (RFC2661) or any further suggestion
>>> on how to handle it. I'm not saying that it is necessary, but since
>>> it is mentioned earlier in the document, you may want to add a few
>>> words. Note that things are a bit more complicated in v2 because
>>> it transports PPP packets, which may include IP packets (or portions
>>> of PPP packets if using Multilink). I have no issue punting on L2TPv2
>>> details.
>> * Given you say L2TPv2 is more complicated cos it transports PPP 
>> packets, that seems to imply that L2TPv3 does not transport PPP, 
>> which doesn't sound right?
>>
>> I don't fully understand the relationship between L2TPv2 & v3 (I have 
>> come across L2TP a lot in an operational context, but never really 
>> studied it as a protocol until now).
>>
>> * Is there still a lot of L2TPv2 around?
>>
>> * Would it be believable that a L2TPv2 implementation might be 
>> updated for ECN support but not updated to L2TPv3?
>>
>> Cheers
>>
>>
>> Bob
>>
>>>
>>> -Ignacio
>>>
>>>
>>> At 15:49 5/30/2017, Bob Briscoe wrote:
>>>
>>>> Hi l2tpext list,
>>>> [repeating previous post, but with self-explanatory subject line]
>>>>
>>>> This is a plea for help on a short subsection of a short draft that 
>>>> updates L2TP (amongst other tunnel protocols).
>>>>
>>>> In the Transport Area WG (tsvwg) we have been working on defining 
>>>> propagation of the ECN field between IP headers separated by shim 
>>>> header(s):
>>>>    draft-ietf-tsvwg-rfc6040update-shim
>>>>
>>>> L2TP is one such protocol (when the payload of the L2 protocol is 
>>>> IP, and the outer PSN is IP). This is particularly relevant at the 
>>>> moment, because of the low latency (L4S) work based on ECN and 
>>>> because deployment of ECN has finally taken off {Note 1}.
>>>>
>>>> I presented this tunnelling work in intarea just under a year ago. 
>>>> Since then tsvwg has adopted the draft and asked that we include 
>>>> specific update text for each affected tunnel protocol. I just 
>>>> posted my first attempt at L2TP update text:
>>>>    <https://tools.ietf.org/html/draft-ietf-tsvwg-rfc6040update-shim-01>draft-ietf-tsvwg-rfc6040update-shim-01
>>>>
>>>> Specific questions:
>>>>
>>>> Prize for the best answer to all 3 questions: you get to become a 
>>>> co-author (if you want :)
>>>>
>>>> Q1. L2TP is meant for all sorts of outers and inners, so it is not 
>>>> clear where to define behaviour for the special (but very common) 
>>>> case of IP as the L2 payload and IP and as the PSN. That is:
>>>>     IP    :    [UDP]    :    L2TP    :    L2-specific-sublayer    : 
>>>>    L2    :    IP
>>>>
>>>> I decided on updating <Specific%20questions:>S.4.5 of RFC3931, but 
>>>> suggestions for a better place are welcome.
>>>>
>>>> Q2. L2TP is usually extended not updated. However, in this case, 
>>>> compliance with RFC6040 is non-optional, so I think update rather 
>>>> than extension is appropriate. Reason: Although RFC6040 is 
>>>> non-optional it includes a compatibility mode that defines what has 
>>>> to happen when a tunnel endpoint doesn't support ECN propagation.
>>>>
>>>> Pls read the (short) draft and, if you disagree, suggest how an 
>>>> extension can be non-optional.
>>>>
>>>> Q3. The tunnel initiator needs to check that the other end supports 
>>>> ECN propagation. I have proposed an Attribute Value Pair (AVP) for 
>>>> this that is effectively just a boolean choice from each end (Yes 
>>>> or silence). I expected to find an AVP with per-control-connection 
>>>> flags for tunnel endpoint capabilities that I could just extend 
>>>> with one more flag, but there doesn't seem to be such a thing 
>>>> already in L2TP. Did I miss it?
>>>>
>>>>
>>>> Cheers
>>>>
>>>>
>>>> Bob
>>>>
>>>> {Note 1}: ~70% of Web servers, ~50% of Apple client devices on 
>>>> fixed or WiFi access, and now increasing router deployment of ECN 
>>>> is appearing.
>>
>> -- 
>> ________________________________________________________________
>> Bob Briscoe http://bobbriscoe.net/
>>
>> _______________________________________________
>> L2tpext mailing list
>> L2tpext@ietf.org <mailto:L2tpext@ietf.org>
>> https://www.ietf.org/mailman/listinfo/l2tpext

-- 
________________________________________________________________
Bob Briscoe                               http://bobbriscoe.net/


--------------9C6D938E48909A273291594B
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html;
      charset=windows-1252">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Carlos,<br>
    <br>
    <div class="moz-cite-prefix">On 31/05/17 17:44, Carlos Pignataro
      (cpignata) wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:B00A6885-6EB1-4361-8412-C408F23DC5E0@cisco.com">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <div><span></span></div>
      <div>
        <div>Hi, Bob,</div>
        <div><br>
        </div>
        <div>Adding on a couple of bits on top of Ignacio's response. <br>
          <br>
          L2TPv2, RFC 2661, transports only PPP (and multi protocols
          within it, including of course IP) and runs over UDP. In
          contrast, L2TPv3 transports directly a variety of protocols
          (Ethernet, HDLC, etc.) and runs directly over IP protocol 115
          or over UDP. RFC 3931 is the base L2TPv3 specification but
          needs a protocol companion document. Some of those protocols
          are finished, e.g. RFC 4719 but others like PPP or "raw" IP
          are in Internet-Drafts. <br>
        </div>
      </div>
    </blockquote>
    Yup, got all that. Thanks. <br>
    <br>
    I just didn't understand the implication of Ignacio's email that
    updating the v2 protocol (that solely supports PPP) could be more
    complex than updating the v3 protocol that I thought supported PPP
    and many more protocols. It implied (to me) that maybe v3 doesn't
    support PPP in some way.<br>
    <br>
    <blockquote type="cite"
      cite="mid:B00A6885-6EB1-4361-8412-C408F23DC5E0@cisco.com">
      <div>
        <div><br>
        </div>
        <div>By the way you can find example of capabilities in
          subsections of Section 5.1.1 of <a
            href="https://tools.ietf.org/html/draft-ietf-l2tpext-l2tp-ppp-08"
            moz-do-not-send="true">https://tools.ietf.org/html/draft-ietf-l2tpext-l2tp-ppp-08</a></div>
        <div><br>
        </div>
        <div>I do not understand however why "Update", or what that
          implies to a compliant implementation. Many features of L2TP
          are specified in various WGs, not "Updating" the base specs. <br>
        </div>
      </div>
    </blockquote>
    By my understanding of the word extension, if a implementation that
    is compliant with RFC3931 does not implement an extension, it is
    still compliant with RFC3931. Is this how the word "extension" is
    used in L2TP land?<br>
    <br>
    Whereas, if one IP header encapsulates another, if the ECN field
    were processed in any way other than RFC6040, it would be invalid
    (unless another RFC were written to update RFC6040). Therefore,
    whenever L2TP is tunnelling IP in IP, it is mandatory to comply with
    RFC6040. So I am asking the L2TPext WG for advice on how you guys
    would make a mandatory update to L2TP, rather than 'just' an
    optional extension.<br>
    <br>
    <br>
    Bob<br>
    <br>
    <blockquote type="cite"
      cite="mid:B00A6885-6EB1-4361-8412-C408F23DC5E0@cisco.com">
      <div>
        <div>Thanks,<br>
          <br>
          <div>Sent from my iPad</div>
        </div>
        <div><br>
          On May 30, 2017, at 10:48 PM, Bob Briscoe &lt;<a
            href="mailto:ietf@bobbriscoe.net" moz-do-not-send="true">ietf@bobbriscoe.net</a>&gt;
          wrote:<br>
          <br>
        </div>
        <blockquote type="cite">
          <div><span>Ignacio,</span><br>
            <span></span><br>
            <span>Thanks for your rapid response.</span><br>
            <span></span><br>
            <span>On 31/05/17 02:51, Ignacio Goyret wrote:</span><br>
            <blockquote type="cite"><span>I am a little confused by the
                double negative in "non-optional".</span><br>
            </blockquote>
            <blockquote type="cite"><span>Do you mean "mandatory"? If
                so, why not just say that?</span><br>
            </blockquote>
            <span>Yes, mandatory.</span><br>
            <span>That language was not in the draft; only in my email.</span><br>
            <blockquote type="cite"><span></span><br>
            </blockquote>
            <blockquote type="cite"><span>The lack of a capabilities AVP
                that you were looking for is mainly</span><br>
            </blockquote>
            <blockquote type="cite"><span>because it hasn't been needed
                so far. You are welcome to submit a</span><br>
            </blockquote>
            <blockquote type="cite"><span>draft with something like
                that. Generally speaking, adding a simple</span><br>
            </blockquote>
            <blockquote type="cite"><span>binary AVP is easy and simpler
                to handle.</span><br>
            </blockquote>
            <span>Good.</span><br>
            <blockquote type="cite"><span></span><br>
            </blockquote>
            <blockquote type="cite"><span>I have no problem with the new
                suggested AVP, but can you explain</span><br>
            </blockquote>
            <blockquote type="cite"><span>why is it important to know if
                the remote supports or not this</span><br>
            </blockquote>
            <blockquote type="cite"><span>extension? Can't a tunnel end
                deduce this information by observing</span><br>
            </blockquote>
            <blockquote type="cite"><span>the IP header received?</span><br>
            </blockquote>
            <span>I'm afraid not. It is critical for the ingress (in
              each direction) to check that the egress decap will
              correctly propagate the outer ECN field into the forwarded
              payload protocol. Otherwise explicit congestion signals
              added by a node within the tunnel could just get stripped
              at decap. With congestion feedback black-holed, the load
              would continue to increase until overload and tail drop.</span><br>
            <span></span><br>
            <span>BTW, the forwarded ECN field after decap has to be a
              combination of the ECN fields in the outer and inner IP
              headers (RFC6040 gives a 4x4 matrix of all the
              combinations of the two 2-bit ECN codepoints). So I am
              interested to know whether this might present problems for
              L2TP implementations (ECN propagation on decap has been
              implemented OK in Linux for similar structures like
              VXLAN).</span><br>
            <span></span><br>
            <blockquote type="cite"><span></span><br>
            </blockquote>
            <blockquote type="cite"><span>Regarding the extension vs
                update question: if it is an update,</span><br>
            </blockquote>
            <blockquote type="cite"><span>then why negotiate support?
                Wouldn't ECN propagation be mandated</span><br>
            </blockquote>
            <blockquote type="cite"><span>by this update?</span><br>
            </blockquote>
            <span>Unfortunately, a mandatory update still has to cope
              with the above incremental deployment problem.</span><br>
            <blockquote type="cite"><span></span><br>
            </blockquote>
            <blockquote type="cite"><span>There is no section for L2TPv2
                (RFC2661) or any further suggestion</span><br>
            </blockquote>
            <blockquote type="cite"><span>on how to handle it. I'm not
                saying that it is necessary, but since</span><br>
            </blockquote>
            <blockquote type="cite"><span>it is mentioned earlier in the
                document, you may want to add a few</span><br>
            </blockquote>
            <blockquote type="cite"><span>words. Note that things are a
                bit more complicated in v2 because</span><br>
            </blockquote>
            <blockquote type="cite"><span>it transports PPP packets,
                which may include IP packets (or portions</span><br>
            </blockquote>
            <blockquote type="cite"><span>of PPP packets if using
                Multilink). I have no issue punting on L2TPv2</span><br>
            </blockquote>
            <blockquote type="cite"><span>details.</span><br>
            </blockquote>
            <span>* Given you say L2TPv2 is more complicated cos it
              transports PPP packets, that seems to imply that L2TPv3
              does not transport PPP, which doesn't sound right?</span><br>
            <span></span><br>
            <span>I don't fully understand the relationship between
              L2TPv2 &amp; v3 (I have come across L2TP a lot in an
              operational context, but never really studied it as a
              protocol until now).</span><br>
            <span></span><br>
            <span>* Is there still a lot of L2TPv2 around?</span><br>
            <span></span><br>
            <span>* Would it be believable that a L2TPv2 implementation
              might be updated for ECN support but not updated to
              L2TPv3?</span><br>
            <span></span><br>
            <span>Cheers</span><br>
            <span></span><br>
            <span></span><br>
            <span>Bob</span><br>
            <span></span><br>
            <blockquote type="cite"><span></span><br>
            </blockquote>
            <blockquote type="cite"><span>-Ignacio</span><br>
            </blockquote>
            <blockquote type="cite"><span></span><br>
            </blockquote>
            <blockquote type="cite"><span></span><br>
            </blockquote>
            <blockquote type="cite"><span>At 15:49 5/30/2017, Bob
                Briscoe wrote:</span><br>
            </blockquote>
            <blockquote type="cite"><span></span><br>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span>Hi l2tpext list,</span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span>[repeating previous post,
                  but with self-explanatory subject line]</span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span></span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span>This is a plea for help on a
                  short subsection of a short draft that updates L2TP
                  (amongst other tunnel protocols).</span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span></span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span>In the Transport Area WG
                  (tsvwg) we have been working on defining propagation
                  of the ECN field between IP headers separated by shim
                  header(s):</span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span>   draft-ietf-tsvwg-rfc6040update-shim</span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span></span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span>L2TP is one such protocol
                  (when the payload of the L2 protocol is IP, and the
                  outer PSN is IP). This is particularly relevant at the
                  moment, because of the low latency (L4S) work based on
                  ECN and because deployment of ECN has finally taken
                  off {Note 1}.</span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span></span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span>I presented this tunnelling
                  work in intarea just under a year ago. Since then
                  tsvwg has adopted the draft and asked that we include
                  specific update text for each affected tunnel
                  protocol. I just posted my first attempt at L2TP
                  update text:</span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span>   &lt;<a
href="https://tools.ietf.org/html/draft-ietf-tsvwg-rfc6040update-shim-01"
                    moz-do-not-send="true">https://tools.ietf.org/html/draft-ietf-tsvwg-rfc6040update-shim-01</a>&gt;draft-ietf-tsvwg-rfc6040update-shim-01</span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span></span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span>Specific questions:</span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span></span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span>Prize for the best answer to
                  all 3 questions: you get to become a co-author (if you
                  want :)</span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span></span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span>Q1. L2TP is meant for all
                  sorts of outers and inners, so it is not clear where
                  to define behaviour for the special (but very common)
                  case of IP as the L2 payload and IP and as the PSN.
                  That is:</span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span>    IP    :    [UDP]    :
                     L2TP    :    L2-specific-sublayer    :    L2    :
                     IP</span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span></span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span>I decided on updating
                  &lt;Specific%20questions:&gt;S.4.5 of RFC3931, but
                  suggestions for a better place are welcome.</span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span></span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span>Q2. L2TP is usually extended
                  not updated. However, in this case, compliance with
                  RFC6040 is non-optional, so I think update rather than
                  extension is appropriate. Reason: Although RFC6040 is
                  non-optional it includes a compatibility mode that
                  defines what has to happen when a tunnel endpoint
                  doesn't support ECN propagation.</span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span></span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span>Pls read the (short) draft
                  and, if you disagree, suggest how an extension can be
                  non-optional.</span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span></span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span>Q3. The tunnel initiator
                  needs to check that the other end supports ECN
                  propagation. I have proposed an Attribute Value Pair
                  (AVP) for this that is effectively just a boolean
                  choice from each end (Yes or silence). I expected to
                  find an AVP with per-control-connection flags for
                  tunnel endpoint capabilities that I could just extend
                  with one more flag, but there doesn't seem to be such
                  a thing already in L2TP. Did I miss it?</span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span></span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span></span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span>Cheers</span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span></span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span></span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span>Bob</span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span></span><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span>{Note 1}: ~70% of Web
                  servers, ~50% of Apple client devices on fixed or WiFi
                  access, and now increasing router deployment of ECN is
                  appearing.</span><br>
              </blockquote>
            </blockquote>
            <span></span><br>
            <span>-- </span><br>
            <span>________________________________________________________________</span><br>
            <span>Bob Briscoe                               <a
                href="http://bobbriscoe.net/" moz-do-not-send="true">http://bobbriscoe.net/</a></span><br>
            <span></span><br>
            <span>_______________________________________________</span><br>
            <span>L2tpext mailing list</span><br>
            <span><a href="mailto:L2tpext@ietf.org"
                moz-do-not-send="true">L2tpext@ietf.org</a></span><br>
            <span><a
                href="https://www.ietf.org/mailman/listinfo/l2tpext"
                moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/l2tpext</a></span><br>
          </div>
        </blockquote>
      </div>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
________________________________________________________________
Bob Briscoe                               <a class="moz-txt-link-freetext" href="http://bobbriscoe.net/">http://bobbriscoe.net/</a></pre>
  </body>
</html>

--------------9C6D938E48909A273291594B--


From nobody Wed May 31 16:56:57 2017
Return-Path: <ignacio.goyret@nokia.com>
X-Original-To: l2tpext@ietfa.amsl.com
Delivered-To: l2tpext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DD6512EA24 for <l2tpext@ietfa.amsl.com>; Wed, 31 May 2017 16:56:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.922
X-Spam-Level: 
X-Spam-Status: No, score=-1.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.com
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 NHlqekZVITde for <l2tpext@ietfa.amsl.com>; Wed, 31 May 2017 16:56:54 -0700 (PDT)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01on0134.outbound.protection.outlook.com [104.47.1.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8435C129BBB for <l2tpext@ietf.org>; Wed, 31 May 2017 16:56:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com;  s=selector1-nokia-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=XdHhh0iOiW5AOuWAlL8laf1faM5qVmz62ZR/DbSgcYQ=; b=TDaql07zX2LdxDNicNKv52Mq2I65N0nWeXJbTJAph75uWipldar2lwk+6IHSCevm6Ygk1U0BSJhoMw3eU5aFC5GoJcbPJSv93ZJwijdOY093thcTDMqQCZJxrAVqHiBOejwV5tZuJIu+ch9r98Ybedna5xCRn395dTNzM9P1amg=
Received: from DB6PR07CA0021.eurprd07.prod.outlook.com (2603:10a6:6:2d::31) by AM3PR07MB0581.eurprd07.prod.outlook.com (2a01:111:e400:8833::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1143.6; Wed, 31 May 2017 23:56:51 +0000
Received: from VE1EUR03FT047.eop-EUR03.prod.protection.outlook.com (2a01:111:f400:7e09::204) by DB6PR07CA0021.outlook.office365.com (2603:10a6:6:2d::31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1157.3 via Frontend Transport; Wed, 31 May 2017 23:56:51 +0000
Authentication-Results: spf=pass (sender IP is 135.245.43.119) smtp.mailfrom=nokia.com; ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=pass action=none header.from=nokia.com;
Received-SPF: Pass (protection.outlook.com: domain of nokia.com designates 135.245.43.119 as permitted sender) receiver=protection.outlook.com; client-ip=135.245.43.119; helo=us70tusmtp2-o.zam.alcatel-lucent.com;
Received: from us70tusmtp2-o.zam.alcatel-lucent.com (135.245.43.119) by VE1EUR03FT047.mail.protection.outlook.com (10.152.19.218) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_RSA_WITH_AES_256_CBC_SHA) id 15.1.1101.12 via Frontend Transport; Wed, 31 May 2017 23:56:50 +0000
Received: from us70tusmtp2.zam.alcatel-lucent.com (us70tusmtp2-o.zam.alcatel-lucent.com [135.5.2.86]) by us70tusmtp2-o.zam.alcatel-lucent.com (GMO-o) with ESMTP id v4VNumx1007011 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 31 May 2017 23:56:48 GMT
Received: from cliff.eng.ascend.com (cliff.eng.ascend.com [192.207.23.55]) by us70tusmtp2.zam.alcatel-lucent.com (GMO) with ESMTP id v4VNukZp007005 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 31 May 2017 23:56:47 GMT
Received: from igoyret-c1.nokia.com (igoyret-pc [135.227.139.12]) by cliff.eng.ascend.com (8.13.1/8.13.1) with ESMTP id v4VNxHEU008912 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 31 May 2017 16:59:17 -0700
Message-ID: <201705312359.v4VNxHEU008912@cliff.eng.ascend.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 31 May 2017 16:55:47 -0700
To: Bob Briscoe <ietf@bobbriscoe.net>
From: Ignacio Goyret <ignacio.goyret@nokia.com>
CC: "Black, David" <david.black@emc.com>, l2tp IETF list <l2tpext@ietf.org>
In-Reply-To: <70866121-f350-d6d2-d89a-89ca1315f5ab@bobbriscoe.net>
References: <149618019740.19809.6421141487388928973.idtracker@ietfa.amsl.com> <435f45b8-9659-b06f-9adc-415f355ba743@bobbriscoe.net> <e4c97c52-36c9-3091-b005-06ef82ec58e3@bobbriscoe.net> <201705310154.v4V1sYQH013223@cliff.eng.ascend.com> <67456091-a3e0-2db1-5f8a-5210a1f870f1@bobbriscoe.net> <B00A6885-6EB1-4361-8412-C408F23DC5E0@cisco.com> <70866121-f350-d6d2-d89a-89ca1315f5ab@bobbriscoe.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-HT: Tenant
X-Forefront-Antispam-Report: CIP:135.245.43.119; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(39450400003)(39860400002)(39400400002)(39850400002)(2980300002)(438002)(199003)(189002)(24454002)(9170700003)(53936002)(9686003)(50986999)(97756001)(4326008)(110136004)(5660300001)(38730400002)(76176999)(2906002)(54906002)(53416004)(86362001)(305945005)(47776003)(6246003)(50466002)(93886004)(50226002)(46406003)(106466001)(4720700003)(8666007)(8936002)(6666003)(189998001)(23726003)(478600001)(1076002)(356003)(8676002)(81166006)(8276002)(229853002)(6916009)(2950100002); DIR:OUT; SFP:1102; SCL:1; SRVR:AM3PR07MB0581; H:us70tusmtp2-o.zam.alcatel-lucent.com; FPR:; SPF:Pass; MLV:sfv; A:1; MX:1; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; VE1EUR03FT047; 1:Veoxs+uvfW4I+SEJr+OM6TC+l+9SOl0shpvLOjCN49i9/2n2eyYTwV3maK5A7o2QffW5dEjsenZPTICUm63hFpb2u3wNKB/cohlueO/sfCX7uqGLqrCUyvssXTemPH/V+k9Wkjuq3k+9OY5Gb0SpdHd+QNgj9Ci3AaHtorvofu8cGOhUVQh0UqL+qkyTj2JKquhU8OSm0h6ktDqsRgWkR0ZbPr+2iQgbFaZpM7JXVEw00nuR1OkobzRtuCGuF4sGQkiJuj/fw8yP3aUdmv3xUnQXEmCfgP0VXNQJdn+mFjOxM4z4MMivdFJK795+FeWljPxvZ2iOdeMbEWWAlYYRcmGQdFz80S32uqKT+vkX0JauMK3d/Uk9dCvzCSkRgldQGcZ5qlsJtPtO7+BrPIwMQiDsoNIVfej8A1IDe7AOrcGolu5ccA8Jqy0CXSiY5u4Cw0wScUxyL37q/A4fn4YBGn18oMWPsFkpeYPZLMQplc/vcPtTCZ4CkhJLs/OmXeDOuhwzO8RCg4bffXELcjgGRDPzYNMjH/rNLswXmqW62mUtQUXK1uYSnqMxcOKnK2AB
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: AM3PR07MB0581:
X-MS-Office365-Filtering-Correlation-Id: 6a0d125e-718b-4525-5916-08d4a880b4c7
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(8251501002)(2017030254075)(201703131423075)(201703031133081)(201702281549075); SRVR:AM3PR07MB0581; 
X-Microsoft-Exchange-Diagnostics: 1; AM3PR07MB0581; 3:5DLJ4SlIct/CBIQu+Y/bcCECchHShv4/s9tE4AuVGItCLqLrbvJiCADt6NRa9nn5jP/X0t5Ni95iBk8YOH9TmaVkfnIGOlslPnEM/0mVQ98WJ9Cl48M0dVPIFp6cWzfr8LuoFYhQ9E3m77g/XqkjxrddizrEp0+eWOfiLFrtX8C2ct19imZEATHxOAwYjtpA9nsALhgLH69uHVDOX0Qq/82gnb5AAG+RKCRyTxz6G5fa8HevF13e+aJb3xdSNu1KrthDC71oIV2byS0ku9cns5ssV6KrX/fGAaO0pRLUzVnFOcewd5X6GY2YWJ9OxXZwAF3hIsQtmXjfBBDoM/rKFpEUsI6aY+UdpVeaQShi/NOCke/eC74jjQcdHkWTqhk64Qrfj6E8rYiOD07YF+nfnL9YnkKDRl75vmr5p2wCvDc3mec7WtNRGMQov25yUtpgEu1I+fhLpZdREf8Ghvg4BE3uvygsGNk9fYW3O+UTasWN8qAXY0N+oWtXmSu3CoN63yw2b2kFQ1dUvDUsjySIjw==
X-Microsoft-Exchange-Diagnostics: 1; AM3PR07MB0581; 25:4rKcbzOH+SGD1o8bt9prVo6Q2LxAgniGrc01KpqeUan+oWAgEsvKUFeanK4aaxAnrSgQBUXBPXQkNW52n+qbnEh1fN99v9YM+D8eLFE0Lr8VAKP7JwcjGuBmh/Bx/PeJujlRHJF13oPM+bJ6cfteV2mt4w+KDP9/2mB6okXLv4sGi9xtEvlzSocW2CNHw0K2oybyx53gqhqbl+x8DF01jKlkzYP2+03bI7LKwD0l6Z8yLa6kNl4xb0dCvImyzcerZaclfQhmGaOC61+ZVKvaDVG0DaBdZBDoDrUl92+T09Xo7N3RonmO4GhsQUXePOZtRkbRPYF8ZEe5fR+NKVujouARsePV3BNUqeo40+6ugYL2NVVXt7uVeozCN3DZWZgdv0BKfi54E+F1+fLrs4Iqi1HdcmlaQg71C57t3UNvnGJLc+G6yOgmb4F5HVNfky7cECZchg6FVpx5ezZETXIMQG8j3YmVyqZRezDkrYSNP50=; 31:8joF4KFbQ78nj1tkwWxcOhloAtZaDKzglqUPufuVM2tWdDBhqsaogxnH/pVGdaAH8udNyWtrJ3SBbttnTJRKtLnfzxfouebBkq+cgpoQ+4suMbDxF1kAjwTLw6aqc5ItRdI44hGkfgfhsuWm7A4GbzB8LQ6AAu4eCzq14DZfiSYFciWUu5bzHEsyXKJv8J9Zz0sNnZJLgUdHu5RgfDQEniRsfhB7lGwBzteZgo6cvnhTAgebnKJvdXzhtix5Kia6x17/ezZJtXS4+CtrXI4jkA==
X-Microsoft-Exchange-Diagnostics: 1; AM3PR07MB0581; 20:Zbxpri4aUn+xzqrlGGb6TgrTBxNmCf70UHZwrqIBOYPn60XOJOgHKztoAwBgmxsPAy/A1DTOfvBGD4r9D4njQKXxl1fCvbS8kgqRBw1qTQD7tEmC06gLfxBeAFYOCvqcW987Cxeh3Y3mOcvIlNm56oMJrwHBqV9Gdy66D8ZwrX5wdVXqa7jItC/ORN5xTQd41TdQ5c1D4ee2iBxO2zhey/HunClmbVNfWugYN5qvDw5GylsG9IEu318RhJ4vSo1YFS/KtZj0wQACbKqZBN3Co5nnVP+NpnxOjTJz4csxoB/Z80MvFx1zgMlJWzH8xn9WMVkA/s7NqaNwZ4HqIes4mt9xXfpWTweGXgIZ8yiUW8gZjeNs0McAPjDSGDYiwaZOsdFZ9hulj3L6Ha6Vg0lUYjqIcrzP1OhY5qPqQIy175s/KeP3QMM48fBH28ktBL8MgHGNZOh5+hwbAzCcw9Svf51O8KhBja70d0/RLzWq9EaNjYpYlclqDC8ZMERHK1v3yCNeJBUkVFJBMULhqqK6t8lq5ia5uBguYYasRwJudgrpj5AnTETRFjOp3x32tDlswmBMhjJ6AbGIpV3ib/o1xO8S+bSbr5x9cHUsyqd6PKY=
X-Microsoft-Antispam-PRVS: <AM3PR07MB058129AF1A4A0B0C88E691D48FF10@AM3PR07MB0581.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(13016025)(5005006)(8121501046)(13018025)(3002001)(93006095)(93004095)(10201501046)(6055026)(6041248)(20161123555025)(20161123562025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123564025)(20161123560025)(20161123558100)(6072148); SRVR:AM3PR07MB0581; BCL:0; PCL:0; RULEID:; SRVR:AM3PR07MB0581; 
X-Microsoft-Exchange-Diagnostics: 1; AM3PR07MB0581; 4:I1BFrWqNdaatzGpunZmlMX4P+QTVhBNzWGf4fcuYrY6Wgm7CQNbFrgO+XMzhAwQBbIChQIm/UZM00JmBZLXUTspIU+RzwnRdEGckpAFvU7XB0Yw7Foik4DohfMLxhWy6K8JR0eoXZic4/tBCZRaItf1EaJg8r815jJ1PbfGBxMjQ24SQ7hWxGDioOL2jAY+3jtBHPfk0411DX89wndaszbl8oqdP0xenaXoDAmVj8ifZ9mrisRmQmK2/1GJRharL/lAu9lvMRr6+ZZqXFUvK7RSD2WVD+BWg7m0i9wEeoq3NpEJ9mbr2uEV6cIchlr4nys0Y8WwBZdWaGrVWkiamOhg+qcvjxgPQxRB64lkzzpGDNOSHxOqckPQ2xHcdosNIlRNyvaBx0be0evWv8TaVYFpNhynm6nDVzt55zeZ0qez+Jd2gX9srqFERMBB6FTN9LDpMDYWk0fD4OkGmCR8neWDz0wbPHrTW4B+svmXtSyIN29lFCyzjJFQMuSBWM/lUViRyZkzeZ7RRuCG/TKB+4bjrPnejJVIWdq1DmRFoqsRZHcE4ae6pjpt7PMy58pA5jp5ju6Paq8YwM0Bf4UmB3klWVQseXBTRhh5yvuDVe35lnJMBlmcpCChGucFPQMdAbpH1s+SmuxteAhD+hAmS0861UwdkR1Q/0m97yE5K9yB98M/xjEPk/f/XkcOADqxIGdkJpX6NoIYElercnDZe/D4jXe0A6hNiWgPN+e4msHUEdYIywuPSTP7Hg08WfeEQuGRk+yEaXOOCsAS+gYXrWt1cR0LEhX0QLyI8I+EGeqE0ICm5lisXROlCHJlufZTnBQ+1kiqeMnHd/vK0WSfVaA==
X-Forefront-PRVS: 0324C2C0E2
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; AM3PR07MB0581; 23:LkMl4DsLBl7Iy1K0D6i002WFWZLgNR2CABp6+08iQ?= =?us-ascii?Q?/f72zhQUY1rLBFLdgZrFGjCC2QoZ6klsEalHdFgpnyUiQjTM/TPU6KeItdoi?= =?us-ascii?Q?ZRYz0bdy52HZ7OlxgKtdp07LSJ//9VK6TGATO6C8Y/Qw3Qq34nyNn3c8r3Nj?= =?us-ascii?Q?DTPfs9kSN0gNMZM85x2xi5YUTOP4x24nxlRRnQ81KVg/c1HRrEXSmGHQtRW9?= =?us-ascii?Q?mQxSu8AWFs2TXG8iGXy5b4IfVFiV5raOF6UTGMRSJw3oS+Sq3MCGcQl2f8HJ?= =?us-ascii?Q?KnrxbarauRaJv7zGBeirXbI8GEYjllZgPBtwI+vAHhPWPxXWrLNj04ChmqPD?= =?us-ascii?Q?kEGEYT25oRVBBfM6Df/wMwsY92zlkj5FhEe+fGnvXzF4mJiUoqFJzuMGbAFd?= =?us-ascii?Q?iP57xJKgfVr0Zrhlmj+5tzpNckZnxdI81zvzI575tfawTO2i57CvSdAumj21?= =?us-ascii?Q?G6uWRRXg8Y3suVudnYI3Aov0VwSrvyoffJ6Eq2DaS4d4nPJMUNce5GNiNUwZ?= =?us-ascii?Q?mPvbCYejo7mX1sdJ/tJayo5Kv6WPWb+HjDwL5fYEcLEB3/Kfu0vf4BgGpmDq?= =?us-ascii?Q?GpBEuZ13i32a6c+pysXzzl/S9qdAl/YBuU578h8uPeuDGsyFmqk7LWbf4H7w?= =?us-ascii?Q?XKY6R+as/yrO0Mb0Pj1kJMOsjkohdI/bUwrGNisVRBHHWF6WGFp+sFX26grm?= =?us-ascii?Q?CL32q2qEluyGAC6D3aMvPrHfDBPZ96LVcIuHg50xqoxYYCTqYjJxlPAk+UL2?= =?us-ascii?Q?wtzC8DCSOJYA3V/vVP4T6OyzGi/ltd6u5O+aK98dhJ1A0wkG5TGlyEOWoiIJ?= =?us-ascii?Q?KmuYDRtaHRwJlpG92LyO0CpFSPbXns6JbhqtuunSkEAxHqfqgQVEGIMLZqBY?= =?us-ascii?Q?gAmp5t4DOn4iG2cPsvI38Q5Q/zvzL/rtFpCiLtuDvDcM6lOazGVl10O2uxfJ?= =?us-ascii?Q?1J4zpZV0RmPlf4wWx+0f77Gt80udBMD6mXNRtim7M6HgeZDLCTRBO7UDlpBd?= =?us-ascii?Q?WaaL+fXzrpVanXyfTHQoSvNbHovbErTZ/egUCJtPv7nilFIEYEP+VyIamvU7?= =?us-ascii?Q?+04vptLWOg88g/yI8KMS5NHvE7LWjYLmDoY6giu0ZWLnEj0vGzCuP0F7BNJN?= =?us-ascii?Q?185ajAhJirXo4Tz0o/0vE6o1fVdc6EA?=
X-Microsoft-Exchange-Diagnostics: 1; AM3PR07MB0581; 6:9DljW7O131VI/eElLVw4PGx0MTuDtnVHD+RPWV6ntZeNI7IU+bP025uF4EsRRL2jKF3ooJX9ZrjSbItl5TMxIwMIvdCw2Y0K5XrNGQjAcfqcmYlEIOy3pWmMa351VGszS133zhWn5eFRac4ERbg0BmtPOW/QJXfkDLDTKuDd4ytler8GpwW5wkI8gFHezrjCBXComwulO/2pLGZO47jsNbBXr8l957DyUaRujr5Ch5TtAH6micgI39PxEDvob0cTy5i21KOhx2o5TReWD5Qa/AvVwKBKnoWX0VZ0f6wF0kZH1McN85lDAx38gK4X7UmxTVH2cunWTGUwO2j6pML0VcnxikfWZgmzcWqdg4tlCo3oeNVXlikPAbzo/8se+lbOz7uujD5Ci6RhXCFEYLDXIaCQmtKahuAYqdpjOBwO57xl9hDIKcwyf5HnvEO1zKl6vnuliiwH6zHeruXSLRGIJVi7/KC1yWWKhD9Agc1OECKm+XABTagNMOXDeuALxJ5oIvcUZOvAtDZTWTy3i6GjsOd1LEVf7Xn/sRIE9niTo8Q=; 5:BUlspC6EU358Z7RjtXS94wbhMUfH5PeNab4Hqu5GpNrSzwuZYBTxMpxCivDz73LUohdnf129fYAbre9Y8nwPUbMWv05Xb0xQwmP097tbWcra+d4jfyfpiyVAX6kupJCu1i72+f9WbFw+XJZJLVq/nQ==; 24:rdFX5dsXId4BTxlqKIUF/bEj2SwDj0Wbt4vbEGGjeLewwpL1y0ONFcd6ic+UanelF7/wGu+YAcJ8cX66qkCor9Q4wFuyWkIkUiTOaT7JdwA=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; AM3PR07MB0581; 7:CQd+5E15NAkRxACSWXXSku/LAm/zuTCVJmsgc+xLgdDXWncT1hi2/gqbpbbzAsYYJPI6cppqbEEVBKnuHlQtAGhtfwy6M4aOfdfTp36Kb9+8fdUgAV45O+4aqL9dROrQ/KbaEdsP+aV1mKA67tTE7dvFAHefxi5bT20kpbNRGQTvujK80UzyqZ+i+N+BJEkIusxmbAnF5ms+fX/D59WyU1jwBJ0/LlgW4iOgFj+TsJSBKSb01+Z4ix29ANjqGBRpo8Q1i/eZx9nG3/rgGEuCJ69em6jqkzhauKlsYtoy7ASi3LY4kHtv+G9FQCDT2Bq0lHU54XmfcZ76XJ+qQ/Pz1g==
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 31 May 2017 23:56:50.2544 (UTC)
X-MS-Exchange-CrossTenant-Id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=5d471751-9675-428d-917b-70f44f9630b0; Ip=[135.245.43.119];  Helo=[us70tusmtp2-o.zam.alcatel-lucent.com]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR07MB0581
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2tpext/AsPnIj_jNTmmBSG5REkg7EdCzF8>
Subject: Re: [L2tpext] Propagating IP/ECN field when L2TP sits between IP as both L2 payload and PSN
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 31 May 2017 23:56:55 -0000

At 15:11 5/31/2017, Bob Briscoe wrote:

>>I do not understand however why "Update", or what that implies to
>>a compliant implementation. Many features of L2TP are specified in
>>various WGs, not "Updating" the base specs.
>> 
>By my understanding of the word extension, if a implementation that
>is compliant with RFC3931 does not implement an extension, it is
>still compliant with RFC3931. Is this how the word "extension" is
>used in L2TP land?
>
>Whereas, if one IP header encapsulates another, if the ECN field
>were processed in any way other than RFC6040, it would be invalid
>(unless another RFC were written to update RFC6040). Therefore,
>whenever L2TP is tunnelling IP in IP, it is mandatory to comply
>with RFC6040. So I am asking the L2TPext WG for advice on how you
>guys would make a mandatory update to L2TP, rather than 'just' an
>optional extension.

I'm not sure you will get much traction for a "mandatory" update
because it would immediately invalidate any compliant deployed code
out there.

This goes back to the question of why negotiate it if it is mandatory.

Real life says that there will be some L2TP deployments that will
support ECN and some that won't, thus, the negotiation is needed
to maintain interoperability.

But if the negotiation is required, then this can't be an update
since it must allow for LCCEs that don't support ECN (which it must,
because some deployments may choose (or may have to) stay with
their non-ECN supporting code for a variety of reasons).

Yes, I know: it is sort of a circular argument but hopefully you
see what I mean.

-Ignacio


From nobody Wed May 31 21:02:07 2017
Return-Path: <ietf@bobbriscoe.net>
X-Original-To: l2tpext@ietfa.amsl.com
Delivered-To: l2tpext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08B40126CF9 for <l2tpext@ietfa.amsl.com>; Wed, 31 May 2017 21:02:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bobbriscoe.net
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 7m4RbNdsmtSe for <l2tpext@ietfa.amsl.com>; Wed, 31 May 2017 21:02:02 -0700 (PDT)
Received: from server.dnsblock1.com (server.dnsblock1.com [85.13.236.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF3331267BB for <l2tpext@ietf.org>; Wed, 31 May 2017 21:02:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To:Subject:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=rDO9tQo+p+byTr70uweL8+J+LklwOZC/+4fqNPwmezI=; b=2xZPZ1Wjpd6lvr3AEi9ax3Y0tl AhskIcD4bmNdXvbNvvXkkomcGISKdoCa9bLYuHyb6Rri+KitKtyFBER8LkLHdOv5T4M6ORY6kkn9P au7qLtmImsSvbzgqfeoz+z2FuU26VWgz0HWc3QnBHD5nqOuBupEjnHlWdpff1Tgs2/v5xLqo2yHiu rZDYr1rlG2/zkYd6IfMMav+7ThTr3QtRlYw/kZHS9UEs0usXLYzTb/jXj08h9mJXcLIWTVzqGGbNp fLshC48DcIdq+PJ2U3JueB1T6BjuT40nlzd7Ao7b5EsReCssewts9Dk39pl0D20cWczdVaiGiJK2+ JO/ZtS8A==;
Received: from [31.185.135.175] (port=55752 helo=[192.168.0.2]) by server.dnsblock1.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from <ietf@bobbriscoe.net>) id 1dGHJA-00027v-Nn; Thu, 01 Jun 2017 05:02:00 +0100
To: Ignacio Goyret <ignacio.goyret@nokia.com>
Cc: "Black, David" <david.black@emc.com>, l2tp IETF list <l2tpext@ietf.org>
References: <149618019740.19809.6421141487388928973.idtracker@ietfa.amsl.com> <435f45b8-9659-b06f-9adc-415f355ba743@bobbriscoe.net> <e4c97c52-36c9-3091-b005-06ef82ec58e3@bobbriscoe.net> <201705310154.v4V1sYQH013223@cliff.eng.ascend.com> <67456091-a3e0-2db1-5f8a-5210a1f870f1@bobbriscoe.net> <B00A6885-6EB1-4361-8412-C408F23DC5E0@cisco.com> <70866121-f350-d6d2-d89a-89ca1315f5ab@bobbriscoe.net> <201705312359.v4VNxHEU008912@cliff.eng.ascend.com>
From: Bob Briscoe <ietf@bobbriscoe.net>
Message-ID: <096cc75b-0bfd-e2ec-d3a5-6b182040ff5a@bobbriscoe.net>
Date: Thu, 1 Jun 2017 05:02:00 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <201705312359.v4VNxHEU008912@cliff.eng.ascend.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.dnsblock1.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bobbriscoe.net
X-Get-Message-Sender-Via: server.dnsblock1.com: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: server.dnsblock1.com: in@bobbriscoe.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2tpext/ztuPJwd7JphuvqThE4_MruItpIg>
Subject: Re: [L2tpext] Propagating IP/ECN field when L2TP sits between IP as both L2 payload and PSN
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Jun 2017 04:02:05 -0000

Ignacio,

On 01/06/17 00:55, Ignacio Goyret wrote:
> At 15:11 5/31/2017, Bob Briscoe wrote:
>
>>> I do not understand however why "Update", or what that implies to
>>> a compliant implementation. Many features of L2TP are specified in
>>> various WGs, not "Updating" the base specs.
>>>
>> By my understanding of the word extension, if a implementation that
>> is compliant with RFC3931 does not implement an extension, it is
>> still compliant with RFC3931. Is this how the word "extension" is
>> used in L2TP land?
>>
>> Whereas, if one IP header encapsulates another, if the ECN field
>> were processed in any way other than RFC6040, it would be invalid
>> (unless another RFC were written to update RFC6040). Therefore,
>> whenever L2TP is tunnelling IP in IP, it is mandatory to comply
>> with RFC6040. So I am asking the L2TPext WG for advice on how you
>> guys would make a mandatory update to L2TP, rather than 'just' an
>> optional extension.
> I'm not sure you will get much traction for a "mandatory" update
> because it would immediately invalidate any compliant deployed code
> out there.
I'm not asking for permission to make something mandatory. RFC6040 (or 
its predecessors {Note 1}) is already mandatory.
draft-ietf-tsvwg-rfc6040update-shim is just the "messenger", telling 
L2TP implementers that RFC6040 is already mandatory.

A mandatory update wouldn't invalidate any compliant deployed code, 
because the only way that deployed code could be compliant would be to 
already comply with RFC6040 or its predecessors. There is no other RFC 
that says how to construct an ECN field during tunnelling. The standards 
track predecessors of RFC6040 pre-dated L2TPv3 by 3.5 years. And the 
experimental track predecessor of ECN tunnelling pre-dated L2TPv2.

The ECN field is in the main IP header (v4 and v6). It cannot be 
omitted. When an L2TPv3 implementation creates an outer IP header during 
encap, or forwards an IP header after decap, it has to set the new ECN 
fields to some value. One would hope that an implementer would try to 
find a spec to follow, rather than guessing this value. There is only 
one RFC that says how to construct the ECN field during tunnelling 
(RFC6040 or its predecessors). If an implementer has not complied with 
one of these, she has not complied with the Internet Protocol.

draft-ietf-tsvwg-rfc6040update-shim is not changing the technical effect 
of the ECN tunnelling spec [RFC6040]. All it is really doing is:

a) Typing "Updates: 3931" at the top of a proposed RFC. This would 
ideally have been typed at the top of the original ECN RFC [RFC3168]. 
This flags to L2TP implementers that they need to take note of the 
standards track update to IP tunnelling that happened in 2001. Because, 
like you say, real life dictates there will be some L2TP implementations 
that don't do it right.

b) and helping to do it right, by providing the L2TP negotiation 
machinery (that is also already mandatory for any tunnelling of IP in IP).


{Note 1}: The predecessors of RFC6040 are RFC3168 and RFC4301. They all 
have the same technical effect - the deltas between them  merely altered 
trivia like handling combinations of ECN fields that wouldn't normally 
be expected and other tinkering round the edges.

> This goes back to the question of why negotiate it if it is mandatory.

The standards action that is mandatory is compliance with RFC6040, which 
made it mandatory to negotiate (or use configuration).

Specifically, RFC6040 made it mandatory for a tunnel ingress to check 
for (or be configured for) whether the egress supported ECN decap. In 
the predecessors to RFC6040, negotiation was only specified for IPsec. 
The only other type of tunnel considered was an RFC2003 tunnel, where no 
negotiation of tunnel set up process had been defined, so negotiation 
wasn't discussed for that case.

>
> Real life says that there will be some L2TP deployments that will
> support ECN and some that won't, thus, the negotiation is needed
> to maintain interoperability.
>
> But if the negotiation is required, then this can't be an update
> since it must allow for LCCEs that don't support ECN (which it must,
> because some deployments may choose (or may have to) stay with
> their non-ECN supporting code for a variety of reasons).

As above, the update is to make negotiation mandatory.

I hope this helps clarify.

Cheers



Bob

>
> Yes, I know: it is sort of a circular argument but hopefully you
> see what I mean.
>
> -Ignacio
>

-- 
________________________________________________________________
Bob Briscoe                               http://bobbriscoe.net/

