
From nobody Thu Jun  1 06:09:12 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 9024112EC34 for <l2tpext@ietfa.amsl.com>; Thu,  1 Jun 2017 06:09:10 -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 zGJtvECPW14l for <l2tpext@ietfa.amsl.com>; Thu,  1 Jun 2017 06:09:08 -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 380E312EC35 for <l2tpext@ietf.org>; Thu,  1 Jun 2017 06:09:08 -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:References:Cc:To:From: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=q6xv70Pk9bRS+JmqPk3OlrVWM/J8D4FWUIsT6tEX3e0=; b=5sltv4K4F7SAyh3zrDw4Ms4Ww0 Qp6NduLvpyiFTaT1HSrvGL5JKKYJLOqIeFLs0Xb4HSEMgYOfCys7YZSkqcf62aw6c/HEzzBQiQLx9 1wYlf4A0cb1djypBIZDp0ymWmAT7W+d2JKj93uvRGLSCgEqt8cSxCioXhVZ9hFz06n7PFFmehdZpc JH+9xdFadG9yWqwUEggpp09Vwl0oyc+P660hdV0HrHllZfGn9puITWhC+pDPUdeXHvp9x9BQQjqMQ rZbIEbAx38R7YAHFbj9AExOswK5B4uYlGVt6qiM5qkL9OOpdiddYGr/5kdrPoa3AnBEZN3Og18XLM kotgHdag==;
Received: from [31.185.135.175] (port=58824 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 1dGPqb-0007ya-M4; Thu, 01 Jun 2017 14:09:05 +0100
From: Bob Briscoe <ietf@bobbriscoe.net>
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> <096cc75b-0bfd-e2ec-d3a5-6b182040ff5a@bobbriscoe.net>
Message-ID: <a0803c13-c095-4250-227d-c1967d11f095@bobbriscoe.net>
Date: Thu, 1 Jun 2017 14:09:05 +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: <096cc75b-0bfd-e2ec-d3a5-6b182040ff5a@bobbriscoe.net>
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/cOLjCrHVdN5a366NZXOWiuLEu4c>
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 13:09:10 -0000

Ignacio,

I realized that my previous email may have come across as critical of 
L2TP implementers that don't already comply with RFC6040. No criticism 
was intended - it is not at all easy to determine which specs to follow 
- one reason for this clarifying draft.

I've also corrected one sentence below...

On 01/06/17 05:02, Bob Briscoe wrote:
> 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.
[BB adds:] RFC3168 did mention MPLS, GRE, L2TP and PPTP, but just said 
they "will be considered as the need arises"
>
>>
>> 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
>
> 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/


From nobody Thu Jun  1 06:23:35 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 2BAC7129BAD for <l2tpext@ietfa.amsl.com>; Thu,  1 Jun 2017 06:23:29 -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, 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, URIBL_BLOCKED=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 U0605ecOdtTM for <l2tpext@ietfa.amsl.com>; Thu,  1 Jun 2017 06:23:23 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7487012EC5C for <l2tpext@ietf.org>; Thu,  1 Jun 2017 06:23:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13734; q=dns/txt; s=iport; t=1496323400; x=1497533000; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=fvASBuSXHIb6FaVEv2Exiopm5mRXh1uQRvmJehQ0FL0=; b=In+QL9N2NUvuRMIXebFqdpiXNyvFiyy7Ya8qPvqgABtmAqAfGyb8AXXO QUVs1RbEyp2WAc/LkxopQtHZJACeNtZzBQJlJfAYsrLlNjSKEku0XweKl 8v1+ag8rZIllxcAJBzQv6SR2z2gT59hOivYDFZRbSSRJKCShQ4h40jBlU c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CuAADqEzBZ/4sNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1digQ0Hg2yKGZFzlXqCDyELhS5KAhqCWT8YAQIBAQEBAQEBayi?= =?us-ascii?q?FGAEBAQECAQEBIREzBwQHBQsCAQgOCgICJgICAiULFRACBA4FiiIIEKx0giaLU?= =?us-ascii?q?wEBAQEBAQEBAQEBAQEBAQEBAQEBAR2BC4VWgWArgWiBDIQ6EgEcFyECglgvgjE?= =?us-ascii?q?FkCqGU4csAYcgjAqCBlWIU4ZLiQaLUAEfOH8LdBVGEgGEcxwZgUkBdoc/gSOBD?= =?us-ascii?q?QEBAQ?=
X-IronPort-AV: E=Sophos;i="5.39,279,1493683200"; d="scan'208";a="252319475"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 01 Jun 2017 13:23:18 +0000
Received: from XCH-RTP-020.cisco.com (xch-rtp-020.cisco.com [64.101.220.160]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id v51DNIP1021473 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 1 Jun 2017 13:23:19 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-020.cisco.com (64.101.220.160) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 1 Jun 2017 09:23:18 -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; Thu, 1 Jun 2017 09:23:17 -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: AQHS2ZcTIeyponFXbEO090UycmlUEaIN8MsAgAAPs4CAAKaqp4AAnoUAgAD+qIA=
Date: Thu, 1 Jun 2017 13:23:17 +0000
Message-ID: <31104AD6-BE38-45D1-A148-67DF4D73529C@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> <B00A6885-6EB1-4361-8412-C408F23DC5E0@cisco.com> <70866121-f350-d6d2-d89a-89ca1315f5ab@bobbriscoe.net>
In-Reply-To: <70866121-f350-d6d2-d89a-89ca1315f5ab@bobbriscoe.net>
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: text/plain; charset="utf-8"
Content-ID: <79B7C141E8CA224DA713E5720A54437A@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2tpext/ceOCRKz9VqbdYp1UR3YOjwZhMLs>
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 13:23:29 -0000

SGksIEJvYiwNCg0KPiBPbiBNYXkgMzEsIDIwMTcsIGF0IDY6MTEgUE0sIEJvYiBCcmlzY29lIDxp
ZXRmQGJvYmJyaXNjb2UubmV0PiB3cm90ZToNCj4gDQo+IENhcmxvcywNCj4gDQo+IE9uIDMxLzA1
LzE3IDE3OjQ0LCBDYXJsb3MgUGlnbmF0YXJvIChjcGlnbmF0YSkgd3JvdGU6DQo+PiBIaSwgQm9i
LA0KPj4gDQo+PiBBZGRpbmcgb24gYSBjb3VwbGUgb2YgYml0cyBvbiB0b3Agb2YgSWduYWNpbydz
IHJlc3BvbnNlLiANCj4+IA0KPj4gTDJUUHYyLCBSRkMgMjY2MSwgdHJhbnNwb3J0cyBvbmx5IFBQ
UCAoYW5kIG11bHRpIHByb3RvY29scyB3aXRoaW4gaXQsIGluY2x1ZGluZyBvZiBjb3Vyc2UgSVAp
IGFuZCBydW5zIG92ZXIgVURQLiBJbiBjb250cmFzdCwgTDJUUHYzIHRyYW5zcG9ydHMgZGlyZWN0
bHkgYSB2YXJpZXR5IG9mIHByb3RvY29scyAoRXRoZXJuZXQsIEhETEMsIGV0Yy4pIGFuZCBydW5z
IGRpcmVjdGx5IG92ZXIgSVAgcHJvdG9jb2wgMTE1IG9yIG92ZXIgVURQLiBSRkMgMzkzMSBpcyB0
aGUgYmFzZSBMMlRQdjMgc3BlY2lmaWNhdGlvbiBidXQgbmVlZHMgYSBwcm90b2NvbCBjb21wYW5p
b24gZG9jdW1lbnQuIFNvbWUgb2YgdGhvc2UgcHJvdG9jb2xzIGFyZSBmaW5pc2hlZCwgZS5nLiBS
RkMgNDcxOSBidXQgb3RoZXJzIGxpa2UgUFBQIG9yICJyYXciIElQIGFyZSBpbiBJbnRlcm5ldC1E
cmFmdHMuIA0KPiBZdXAsIGdvdCBhbGwgdGhhdC4gVGhhbmtzLiANCj4gDQo+IEkganVzdCBkaWRu
J3QgdW5kZXJzdGFuZCB0aGUgaW1wbGljYXRpb24gb2YgSWduYWNpbydzIGVtYWlsIHRoYXQgdXBk
YXRpbmcgdGhlIHYyIHByb3RvY29sICh0aGF0IHNvbGVseSBzdXBwb3J0cyBQUFApIGNvdWxkIGJl
IG1vcmUgY29tcGxleCB0aGFuIHVwZGF0aW5nIHRoZSB2MyBwcm90b2NvbCB0aGF0IEkgdGhvdWdo
dCBzdXBwb3J0ZWQgUFBQIGFuZCBtYW55IG1vcmUgcHJvdG9jb2xzLiBJdCBpbXBsaWVkICh0byBt
ZSkgdGhhdCBtYXliZSB2MyBkb2Vzbid0IHN1cHBvcnQgUFBQIGluIHNvbWUgd2F5Lg0KDQpBZG1p
dHRlZGx5LCBJIGhhdmUgbm90IHJlYWQgaW4gZGV0YWlsIFJGQyA2MDQwIG9yIGRyYWZ0LWlldGYt
dHN2d2ctcmZjNjA0MHVwZGF0ZS1zaGltIOKAlCBob3dldmVyLCBJIGRvIGhhdmUgc29tZSBxdWVz
dGlvbnMgdG8gYmV0dGVyIHVuZGVyc3RhbmQgdGhlIGFwcGxpY2FiaWxpdHkuDQoNCmRyYWZ0LWll
dGYtdHN2d2ctcmZjNjA0MHVwZGF0ZS1zaGltIHRhbGtzIGFib3V0IOKAnElQLWluLUlQIFR1bm5l
bHMgd2l0aCBUaWdodGx5IENvdXBsZWQgU2hpbSBIZWFkZXJz4oCdLg0KDQpHUkUgY2FuIGJlIHRo
b3VnaHQgb2YgYW4gSVAtaW4tSVAgdHVubmVsIHdpdGggYSB0aWdodGx5IGNvdXBsZWQgc2hpbSwg
d2hlbiB0cmFuc3BvcnRpbmcgSVAgZGlyZWN0bHkgKGFsdGhvdWdoIEdSRSBjYW4gdHJhbnNwb3J0
IG11bHRpLXByb3RvY29scykuDQoNClthbmQgYSBzbWFsbCBub3RlIHRoYXQgeW91IG1pZ2h0IG5l
ZWQgYSByZWZlcmVuY2UgdG8gUkZDIDc2NzZdLg0KDQpIb3dldmVyLCBHUkUgY2FuIGNhcnJ5IFNv
bWV0aGluZy1pbi1JUCwgd2l0aCDigJxzb21ldGhpbmciIHBvdGVudGlhbGx5IGNhcnJ5aW5nIGFs
c28gSVAuIEluIHRoYXQgY2FzZSwgSSBkbyBub3QgYmVsaWV2ZSB0aGF04oCZcyBhbiBJUC1pbi1J
UC13aXRoLXNoaW0uDQoNCkZvciB0aGUgTDJUUHYyIGNhc2UsIEwyVFAgY2FycmllcyBQUFAuIFBQ
UCBjYW4gaW4gdHVybiBjYXJyeSBJUCwgYW5kL29yc29tZXRoaW5nIGVsc2UsIGFuZCB1c3VhbGx5
IGEgbWl4dHVyZS4gSXMgdGhpcyByZWFsbHkgYXBwbGljYWJsZSB0byB5b3VyIGRyYWZ0Pw0KDQpG
b3IgTDJUUHYzLCBMMlRQIGNhcnJpZXMgYSB2YXJpZXR5IG9mIHByb3RvY29scywgb25lIG9mIHdo
aWNoIGlzIElQIGRpcmVjdGx5LiBIb3dldmVyLCBhbHRob3VnaCB0aGVyZSBpcyBydW5uaW5nIGNv
ZGUsIHRoZXJl4oCZcyBubyBSRkMgZm9yIGl0IChodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwv
ZHJhZnQtaWV0Zi1sMnRwZXh0LXB3ZTMtaXAtMDUuKSBTaW1pbGFybHksIFJGQyAzOTMxIHNlZW1z
IG91dHNpZGUgc2NvcGUuDQoNClthbmQgYW5vdGhlciBxdWVzdGlvbiAsd2hhdCBhYm91dCBNUExT
LCB3aXRoIFJGQyA1MTI5P10NCg0KPiANCj4+IA0KPj4gQnkgdGhlIHdheSB5b3UgY2FuIGZpbmQg
ZXhhbXBsZSBvZiBjYXBhYmlsaXRpZXMgaW4gc3Vic2VjdGlvbnMgb2YgU2VjdGlvbiA1LjEuMSBv
ZiBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1sMnRwZXh0LWwydHAtcHBw
LTA4DQo+PiANCj4+IEkgZG8gbm90IHVuZGVyc3RhbmQgaG93ZXZlciB3aHkgIlVwZGF0ZSIsIG9y
IHdoYXQgdGhhdCBpbXBsaWVzIHRvIGEgY29tcGxpYW50IGltcGxlbWVudGF0aW9uLiBNYW55IGZl
YXR1cmVzIG9mIEwyVFAgYXJlIHNwZWNpZmllZCBpbiB2YXJpb3VzIFdHcywgbm90ICJVcGRhdGlu
ZyIgdGhlIGJhc2Ugc3BlY3MuIA0KPiBCeSBteSB1bmRlcnN0YW5kaW5nIG9mIHRoZSB3b3JkIGV4
dGVuc2lvbiwgaWYgYSBpbXBsZW1lbnRhdGlvbiB0aGF0IGlzIGNvbXBsaWFudCB3aXRoIFJGQzM5
MzEgZG9lcyBub3QgaW1wbGVtZW50IGFuIGV4dGVuc2lvbiwgaXQgaXMgc3RpbGwgY29tcGxpYW50
IHdpdGggUkZDMzkzMS4gSXMgdGhpcyBob3cgdGhlIHdvcmQgImV4dGVuc2lvbiIgaXMgdXNlZCBp
biBMMlRQIGxhbmQ/DQo+IA0KDQpUaGF04oCZcyBteSB1bmRlcnN0YW5kaW5nIG9mIHRoZSB1bnF1
YWxpZmllZCB3b3JkIOKAnGV4dGVuc2lvbuKAnSBiZXlvbmQgTDJUUCBsYW5kLiBJcyB0aGF0IGRp
ZmZlcmVudCBhbnl3aGVyZT8NCg0KPiBXaGVyZWFzLCBpZiBvbmUgSVAgaGVhZGVyIGVuY2Fwc3Vs
YXRlcyBhbm90aGVyLCBpZiB0aGUgRUNOIGZpZWxkIHdlcmUgcHJvY2Vzc2VkIGluIGFueSB3YXkg
b3RoZXIgdGhhbiBSRkM2MDQwLCBpdCB3b3VsZCBiZSBpbnZhbGlkICh1bmxlc3MgYW5vdGhlciBS
RkMgd2VyZSB3cml0dGVuIHRvIHVwZGF0ZSBSRkM2MDQwKS4gVGhlcmVmb3JlLCB3aGVuZXZlciBM
MlRQIGlzIHR1bm5lbGxpbmcgSVAgaW4gSVAsIGl0IGlzIG1hbmRhdG9yeSB0byBjb21wbHkgd2l0
aCBSRkM2MDQwLiBTbyBJIGFtIGFza2luZyB0aGUgTDJUUGV4dCBXRyBmb3IgYWR2aWNlIG9uIGhv
dyB5b3UgZ3V5cyB3b3VsZCBtYWtlIGEgbWFuZGF0b3J5IHVwZGF0ZSB0byBMMlRQLCByYXRoZXIg
dGhhbiAnanVzdCcgYW4gb3B0aW9uYWwgZXh0ZW5zaW9uLg0KPiANCg0KSSB0aGluayBmaXJzdCB3
ZSBwcm9iYWJseSBuZWVkIHRvIHVuZGVyc3RhbmQgdGhlIGFwcGxpY2FiaWxpdHkgYmVjYXVzZSBp
dCBpcyBub3QgYW4gSVAtaW4tSVAgZW5jYXAsIHRoZXJl4oCZcyBhIExheWVyIDIgaGVhZGVyIGlu
IGJldHdlZW4sIG5vdCB0aWdodGx5IGNvdXBsZWQgYnV0IHJhdGhlciBwYXJ0IG9mIHRoZSB0cmFu
c3BvcnRlZCBwYXlsb2FkLg0KDQpOb3csIHdoYXQgeW91IGRlc2NyaWJlIGluIHRlcm1zIG9mIGxl
dmVsIG9mIG1hbmRhdG9yeSBhcHBsaWVzIHRvIFJGQyA2MDQwLiBJZiBhbiBpbXBsZW1lbnRhdGlv
biBkb2VzIG5vdCBjb21wbHkgd2l0aCBSRkMgNjA0MCBpdCBpcywgd2VsbCwgbm90IGNvbXBsaWFu
dCB3aXRoIFJGQyA2MDQwLg0KDQpUaGFua3MhDQoNCkNhcmxvcy4NCg0KPiANCj4gQm9iDQo+IA0K
Pj4gVGhhbmtzLA0KPj4gDQo+PiBTZW50IGZyb20gbXkgaVBhZA0KPj4gDQo+PiBPbiBNYXkgMzAs
IDIwMTcsIGF0IDEwOjQ4IFBNLCBCb2IgQnJpc2NvZSA8aWV0ZkBib2JicmlzY29lLm5ldD4gd3Jv
dGU6DQo+PiANCj4+PiBJZ25hY2lvLA0KPj4+IA0KPj4+IFRoYW5rcyBmb3IgeW91ciByYXBpZCBy
ZXNwb25zZS4NCj4+PiANCj4+PiBPbiAzMS8wNS8xNyAwMjo1MSwgSWduYWNpbyBHb3lyZXQgd3Jv
dGU6DQo+Pj4+IEkgYW0gYSBsaXR0bGUgY29uZnVzZWQgYnkgdGhlIGRvdWJsZSBuZWdhdGl2ZSBp
biAibm9uLW9wdGlvbmFsIi4NCj4+Pj4gRG8geW91IG1lYW4gIm1hbmRhdG9yeSI/IElmIHNvLCB3
aHkgbm90IGp1c3Qgc2F5IHRoYXQ/DQo+Pj4gWWVzLCBtYW5kYXRvcnkuDQo+Pj4gVGhhdCBsYW5n
dWFnZSB3YXMgbm90IGluIHRoZSBkcmFmdDsgb25seSBpbiBteSBlbWFpbC4NCj4+Pj4gDQo+Pj4+
IFRoZSBsYWNrIG9mIGEgY2FwYWJpbGl0aWVzIEFWUCB0aGF0IHlvdSB3ZXJlIGxvb2tpbmcgZm9y
IGlzIG1haW5seQ0KPj4+PiBiZWNhdXNlIGl0IGhhc24ndCBiZWVuIG5lZWRlZCBzbyBmYXIuIFlv
dSBhcmUgd2VsY29tZSB0byBzdWJtaXQgYQ0KPj4+PiBkcmFmdCB3aXRoIHNvbWV0aGluZyBsaWtl
IHRoYXQuIEdlbmVyYWxseSBzcGVha2luZywgYWRkaW5nIGEgc2ltcGxlDQo+Pj4+IGJpbmFyeSBB
VlAgaXMgZWFzeSBhbmQgc2ltcGxlciB0byBoYW5kbGUuDQo+Pj4gR29vZC4NCj4+Pj4gDQo+Pj4+
IEkgaGF2ZSBubyBwcm9ibGVtIHdpdGggdGhlIG5ldyBzdWdnZXN0ZWQgQVZQLCBidXQgY2FuIHlv
dSBleHBsYWluDQo+Pj4+IHdoeSBpcyBpdCBpbXBvcnRhbnQgdG8ga25vdyBpZiB0aGUgcmVtb3Rl
IHN1cHBvcnRzIG9yIG5vdCB0aGlzDQo+Pj4+IGV4dGVuc2lvbj8gQ2FuJ3QgYSB0dW5uZWwgZW5k
IGRlZHVjZSB0aGlzIGluZm9ybWF0aW9uIGJ5IG9ic2VydmluZw0KPj4+PiB0aGUgSVAgaGVhZGVy
IHJlY2VpdmVkPw0KPj4+IEknbSBhZnJhaWQgbm90LiBJdCBpcyBjcml0aWNhbCBmb3IgdGhlIGlu
Z3Jlc3MgKGluIGVhY2ggZGlyZWN0aW9uKSB0byBjaGVjayB0aGF0IHRoZSBlZ3Jlc3MgZGVjYXAg
d2lsbCBjb3JyZWN0bHkgcHJvcGFnYXRlIHRoZSBvdXRlciBFQ04gZmllbGQgaW50byB0aGUgZm9y
d2FyZGVkIHBheWxvYWQgcHJvdG9jb2wuIE90aGVyd2lzZSBleHBsaWNpdCBjb25nZXN0aW9uIHNp
Z25hbHMgYWRkZWQgYnkgYSBub2RlIHdpdGhpbiB0aGUgdHVubmVsIGNvdWxkIGp1c3QgZ2V0IHN0
cmlwcGVkIGF0IGRlY2FwLiBXaXRoIGNvbmdlc3Rpb24gZmVlZGJhY2sgYmxhY2staG9sZWQsIHRo
ZSBsb2FkIHdvdWxkIGNvbnRpbnVlIHRvIGluY3JlYXNlIHVudGlsIG92ZXJsb2FkIGFuZCB0YWls
IGRyb3AuDQo+Pj4gDQo+Pj4gQlRXLCB0aGUgZm9yd2FyZGVkIEVDTiBmaWVsZCBhZnRlciBkZWNh
cCBoYXMgdG8gYmUgYSBjb21iaW5hdGlvbiBvZiB0aGUgRUNOIGZpZWxkcyBpbiB0aGUgb3V0ZXIg
YW5kIGlubmVyIElQIGhlYWRlcnMgKFJGQzYwNDAgZ2l2ZXMgYSA0eDQgbWF0cml4IG9mIGFsbCB0
aGUgY29tYmluYXRpb25zIG9mIHRoZSB0d28gMi1iaXQgRUNOIGNvZGVwb2ludHMpLiBTbyBJIGFt
IGludGVyZXN0ZWQgdG8ga25vdyB3aGV0aGVyIHRoaXMgbWlnaHQgcHJlc2VudCBwcm9ibGVtcyBm
b3IgTDJUUCBpbXBsZW1lbnRhdGlvbnMgKEVDTiBwcm9wYWdhdGlvbiBvbiBkZWNhcCBoYXMgYmVl
biBpbXBsZW1lbnRlZCBPSyBpbiBMaW51eCBmb3Igc2ltaWxhciBzdHJ1Y3R1cmVzIGxpa2UgVlhM
QU4pLg0KPj4+IA0KPj4+PiANCj4+Pj4gUmVnYXJkaW5nIHRoZSBleHRlbnNpb24gdnMgdXBkYXRl
IHF1ZXN0aW9uOiBpZiBpdCBpcyBhbiB1cGRhdGUsDQo+Pj4+IHRoZW4gd2h5IG5lZ290aWF0ZSBz
dXBwb3J0PyBXb3VsZG4ndCBFQ04gcHJvcGFnYXRpb24gYmUgbWFuZGF0ZWQNCj4+Pj4gYnkgdGhp
cyB1cGRhdGU/DQo+Pj4gVW5mb3J0dW5hdGVseSwgYSBtYW5kYXRvcnkgdXBkYXRlIHN0aWxsIGhh
cyB0byBjb3BlIHdpdGggdGhlIGFib3ZlIGluY3JlbWVudGFsIGRlcGxveW1lbnQgcHJvYmxlbS4N
Cj4+Pj4gDQo+Pj4+IFRoZXJlIGlzIG5vIHNlY3Rpb24gZm9yIEwyVFB2MiAoUkZDMjY2MSkgb3Ig
YW55IGZ1cnRoZXIgc3VnZ2VzdGlvbg0KPj4+PiBvbiBob3cgdG8gaGFuZGxlIGl0LiBJJ20gbm90
IHNheWluZyB0aGF0IGl0IGlzIG5lY2Vzc2FyeSwgYnV0IHNpbmNlDQo+Pj4+IGl0IGlzIG1lbnRp
b25lZCBlYXJsaWVyIGluIHRoZSBkb2N1bWVudCwgeW91IG1heSB3YW50IHRvIGFkZCBhIGZldw0K
Pj4+PiB3b3Jkcy4gTm90ZSB0aGF0IHRoaW5ncyBhcmUgYSBiaXQgbW9yZSBjb21wbGljYXRlZCBp
biB2MiBiZWNhdXNlDQo+Pj4+IGl0IHRyYW5zcG9ydHMgUFBQIHBhY2tldHMsIHdoaWNoIG1heSBp
bmNsdWRlIElQIHBhY2tldHMgKG9yIHBvcnRpb25zDQo+Pj4+IG9mIFBQUCBwYWNrZXRzIGlmIHVz
aW5nIE11bHRpbGluaykuIEkgaGF2ZSBubyBpc3N1ZSBwdW50aW5nIG9uIEwyVFB2Mg0KPj4+PiBk
ZXRhaWxzLg0KPj4+ICogR2l2ZW4geW91IHNheSBMMlRQdjIgaXMgbW9yZSBjb21wbGljYXRlZCBj
b3MgaXQgdHJhbnNwb3J0cyBQUFAgcGFja2V0cywgdGhhdCBzZWVtcyB0byBpbXBseSB0aGF0IEwy
VFB2MyBkb2VzIG5vdCB0cmFuc3BvcnQgUFBQLCB3aGljaCBkb2Vzbid0IHNvdW5kIHJpZ2h0Pw0K
Pj4+IA0KPj4+IEkgZG9uJ3QgZnVsbHkgdW5kZXJzdGFuZCB0aGUgcmVsYXRpb25zaGlwIGJldHdl
ZW4gTDJUUHYyICYgdjMgKEkgaGF2ZSBjb21lIGFjcm9zcyBMMlRQIGEgbG90IGluIGFuIG9wZXJh
dGlvbmFsIGNvbnRleHQsIGJ1dCBuZXZlciByZWFsbHkgc3R1ZGllZCBpdCBhcyBhIHByb3RvY29s
IHVudGlsIG5vdykuDQo+Pj4gDQo+Pj4gKiBJcyB0aGVyZSBzdGlsbCBhIGxvdCBvZiBMMlRQdjIg
YXJvdW5kPw0KPj4+IA0KPj4+ICogV291bGQgaXQgYmUgYmVsaWV2YWJsZSB0aGF0IGEgTDJUUHYy
IGltcGxlbWVudGF0aW9uIG1pZ2h0IGJlIHVwZGF0ZWQgZm9yIEVDTiBzdXBwb3J0IGJ1dCBub3Qg
dXBkYXRlZCB0byBMMlRQdjM/DQo+Pj4gDQo+Pj4gQ2hlZXJzDQo+Pj4gDQo+Pj4gDQo+Pj4gQm9i
DQo+Pj4gDQo+Pj4+IA0KPj4+PiAtSWduYWNpbw0KPj4+PiANCj4+Pj4gDQo+Pj4+IEF0IDE1OjQ5
IDUvMzAvMjAxNywgQm9iIEJyaXNjb2Ugd3JvdGU6DQo+Pj4+IA0KPj4+Pj4gSGkgbDJ0cGV4dCBs
aXN0LA0KPj4+Pj4gW3JlcGVhdGluZyBwcmV2aW91cyBwb3N0LCBidXQgd2l0aCBzZWxmLWV4cGxh
bmF0b3J5IHN1YmplY3QgbGluZV0NCj4+Pj4+IA0KPj4+Pj4gVGhpcyBpcyBhIHBsZWEgZm9yIGhl
bHAgb24gYSBzaG9ydCBzdWJzZWN0aW9uIG9mIGEgc2hvcnQgZHJhZnQgdGhhdCB1cGRhdGVzIEwy
VFAgKGFtb25nc3Qgb3RoZXIgdHVubmVsIHByb3RvY29scykuDQo+Pj4+PiANCj4+Pj4+IEluIHRo
ZSBUcmFuc3BvcnQgQXJlYSBXRyAodHN2d2cpIHdlIGhhdmUgYmVlbiB3b3JraW5nIG9uIGRlZmlu
aW5nIHByb3BhZ2F0aW9uIG9mIHRoZSBFQ04gZmllbGQgYmV0d2VlbiBJUCBoZWFkZXJzIHNlcGFy
YXRlZCBieSBzaGltIGhlYWRlcihzKToNCj4+Pj4+ICAgIGRyYWZ0LWlldGYtdHN2d2ctcmZjNjA0
MHVwZGF0ZS1zaGltDQo+Pj4+PiANCj4+Pj4+IEwyVFAgaXMgb25lIHN1Y2ggcHJvdG9jb2wgKHdo
ZW4gdGhlIHBheWxvYWQgb2YgdGhlIEwyIHByb3RvY29sIGlzIElQLCBhbmQgdGhlIG91dGVyIFBT
TiBpcyBJUCkuIFRoaXMgaXMgcGFydGljdWxhcmx5IHJlbGV2YW50IGF0IHRoZSBtb21lbnQsIGJl
Y2F1c2Ugb2YgdGhlIGxvdyBsYXRlbmN5IChMNFMpIHdvcmsgYmFzZWQgb24gRUNOIGFuZCBiZWNh
dXNlIGRlcGxveW1lbnQgb2YgRUNOIGhhcyBmaW5hbGx5IHRha2VuIG9mZiB7Tm90ZSAxfS4NCj4+
Pj4+IA0KPj4+Pj4gSSBwcmVzZW50ZWQgdGhpcyB0dW5uZWxsaW5nIHdvcmsgaW4gaW50YXJlYSBq
dXN0IHVuZGVyIGEgeWVhciBhZ28uIFNpbmNlIHRoZW4gdHN2d2cgaGFzIGFkb3B0ZWQgdGhlIGRy
YWZ0IGFuZCBhc2tlZCB0aGF0IHdlIGluY2x1ZGUgc3BlY2lmaWMgdXBkYXRlIHRleHQgZm9yIGVh
Y2ggYWZmZWN0ZWQgdHVubmVsIHByb3RvY29sLiBJIGp1c3QgcG9zdGVkIG15IGZpcnN0IGF0dGVt
cHQgYXQgTDJUUCB1cGRhdGUgdGV4dDoNCj4+Pj4+ICAgIDxodHRwczovL3Rvb2xzLmlldGYub3Jn
L2h0bWwvZHJhZnQtaWV0Zi10c3Z3Zy1yZmM2MDQwdXBkYXRlLXNoaW0tMDE+ZHJhZnQtaWV0Zi10
c3Z3Zy1yZmM2MDQwdXBkYXRlLXNoaW0tMDENCj4+Pj4+IA0KPj4+Pj4gU3BlY2lmaWMgcXVlc3Rp
b25zOg0KPj4+Pj4gDQo+Pj4+PiBQcml6ZSBmb3IgdGhlIGJlc3QgYW5zd2VyIHRvIGFsbCAzIHF1
ZXN0aW9uczogeW91IGdldCB0byBiZWNvbWUgYSBjby1hdXRob3IgKGlmIHlvdSB3YW50IDopDQo+
Pj4+PiANCj4+Pj4+IFExLiBMMlRQIGlzIG1lYW50IGZvciBhbGwgc29ydHMgb2Ygb3V0ZXJzIGFu
ZCBpbm5lcnMsIHNvIGl0IGlzIG5vdCBjbGVhciB3aGVyZSB0byBkZWZpbmUgYmVoYXZpb3VyIGZv
ciB0aGUgc3BlY2lhbCAoYnV0IHZlcnkgY29tbW9uKSBjYXNlIG9mIElQIGFzIHRoZSBMMiBwYXls
b2FkIGFuZCBJUCBhbmQgYXMgdGhlIFBTTi4gVGhhdCBpczoNCj4+Pj4+ICAgICBJUCAgICA6ICAg
IFtVRFBdICAgIDogICAgTDJUUCAgICA6ICAgIEwyLXNwZWNpZmljLXN1YmxheWVyICAgIDogICAg
TDIgICAgOiAgICBJUA0KPj4+Pj4gDQo+Pj4+PiBJIGRlY2lkZWQgb24gdXBkYXRpbmcgPFNwZWNp
ZmljJTIwcXVlc3Rpb25zOj5TLjQuNSBvZiBSRkMzOTMxLCBidXQgc3VnZ2VzdGlvbnMgZm9yIGEg
YmV0dGVyIHBsYWNlIGFyZSB3ZWxjb21lLg0KPj4+Pj4gDQo+Pj4+PiBRMi4gTDJUUCBpcyB1c3Vh
bGx5IGV4dGVuZGVkIG5vdCB1cGRhdGVkLiBIb3dldmVyLCBpbiB0aGlzIGNhc2UsIGNvbXBsaWFu
Y2Ugd2l0aCBSRkM2MDQwIGlzIG5vbi1vcHRpb25hbCwgc28gSSB0aGluayB1cGRhdGUgcmF0aGVy
IHRoYW4gZXh0ZW5zaW9uIGlzIGFwcHJvcHJpYXRlLiBSZWFzb246IEFsdGhvdWdoIFJGQzYwNDAg
aXMgbm9uLW9wdGlvbmFsIGl0IGluY2x1ZGVzIGEgY29tcGF0aWJpbGl0eSBtb2RlIHRoYXQgZGVm
aW5lcyB3aGF0IGhhcyB0byBoYXBwZW4gd2hlbiBhIHR1bm5lbCBlbmRwb2ludCBkb2Vzbid0IHN1
cHBvcnQgRUNOIHByb3BhZ2F0aW9uLg0KPj4+Pj4gDQo+Pj4+PiBQbHMgcmVhZCB0aGUgKHNob3J0
KSBkcmFmdCBhbmQsIGlmIHlvdSBkaXNhZ3JlZSwgc3VnZ2VzdCBob3cgYW4gZXh0ZW5zaW9uIGNh
biBiZSBub24tb3B0aW9uYWwuDQo+Pj4+PiANCj4+Pj4+IFEzLiBUaGUgdHVubmVsIGluaXRpYXRv
ciBuZWVkcyB0byBjaGVjayB0aGF0IHRoZSBvdGhlciBlbmQgc3VwcG9ydHMgRUNOIHByb3BhZ2F0
aW9uLiBJIGhhdmUgcHJvcG9zZWQgYW4gQXR0cmlidXRlIFZhbHVlIFBhaXIgKEFWUCkgZm9yIHRo
aXMgdGhhdCBpcyBlZmZlY3RpdmVseSBqdXN0IGEgYm9vbGVhbiBjaG9pY2UgZnJvbSBlYWNoIGVu
ZCAoWWVzIG9yIHNpbGVuY2UpLiBJIGV4cGVjdGVkIHRvIGZpbmQgYW4gQVZQIHdpdGggcGVyLWNv
bnRyb2wtY29ubmVjdGlvbiBmbGFncyBmb3IgdHVubmVsIGVuZHBvaW50IGNhcGFiaWxpdGllcyB0
aGF0IEkgY291bGQganVzdCBleHRlbmQgd2l0aCBvbmUgbW9yZSBmbGFnLCBidXQgdGhlcmUgZG9l
c24ndCBzZWVtIHRvIGJlIHN1Y2ggYSB0aGluZyBhbHJlYWR5IGluIEwyVFAuIERpZCBJIG1pc3Mg
aXQ/DQo+Pj4+PiANCj4+Pj4+IA0KPj4+Pj4gQ2hlZXJzDQo+Pj4+PiANCj4+Pj4+IA0KPj4+Pj4g
Qm9iDQo+Pj4+PiANCj4+Pj4+IHtOb3RlIDF9OiB+NzAlIG9mIFdlYiBzZXJ2ZXJzLCB+NTAlIG9m
IEFwcGxlIGNsaWVudCBkZXZpY2VzIG9uIGZpeGVkIG9yIFdpRmkgYWNjZXNzLCBhbmQgbm93IGlu
Y3JlYXNpbmcgcm91dGVyIGRlcGxveW1lbnQgb2YgRUNOIGlzIGFwcGVhcmluZy4NCj4+PiANCj4+
PiAtLSANCj4+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fDQo+Pj4gQm9iIEJyaXNjb2UgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgaHR0cDovL2JvYmJyaXNjb2UubmV0Lw0KPj4+IA0KPj4+IF9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+Pj4gTDJ0cGV4dCBtYWlsaW5nIGxp
c3QNCj4+PiBMMnRwZXh0QGlldGYub3JnDQo+Pj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9sMnRwZXh0DQo+IA0KPiAtLSANCj4gX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBCb2IgQnJpc2NvZSAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICANCj4gaHR0cDovL2JvYmJyaXNjb2UubmV0Lw0K
DQo=


From nobody Thu Jun  1 13:24:32 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 DA6DE128ACA for <l2tpext@ietfa.amsl.com>; Thu,  1 Jun 2017 13:24:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.702
X-Spam-Level: 
X-Spam-Status: No, score=-4.702 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_H2=-2.8, 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 ca7cnDX8JSmL for <l2tpext@ietfa.amsl.com>; Thu,  1 Jun 2017 13:24:30 -0700 (PDT)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-eopbgr30132.outbound.protection.outlook.com [40.107.3.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B6E112426E for <l2tpext@ietf.org>; Thu,  1 Jun 2017 13:24:29 -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=tW3uV6x5bXrkI4b7/B7x4IAlyc38bZ/i1Iztdt8cyV8=; b=CvCZDkp0wuJh8A5iuPeZGRvl6NGDz7xqPfztboQF/3SKwnHYk0cDtz9AxwCOcArvWr4dyNiymUaoulI86Y+XuU/jlTSEIz3y86n1vBWgAwcONyNqR0a7fUADHm2Qj8duiDxEFSdcUnbQ2HiNqs5qIsIBPOaeUlZ5jADJ2TWGiXw=
Received: from VI1PR0701CA0044.eurprd07.prod.outlook.com (2603:10a6:800:90::30) by VI1PR07MB0830.eurprd07.prod.outlook.com (2a01:111:e400:508e::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1143.6; Thu, 1 Jun 2017 20:24:26 +0000
Received: from AM5EUR03FT019.eop-EUR03.prod.protection.outlook.com (2a01:111:f400:7e08::202) by VI1PR0701CA0044.outlook.office365.com (2603:10a6:800:90::30) 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; Thu, 1 Jun 2017 20:24:26 +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 AM5EUR03FT019.mail.protection.outlook.com (10.152.16.104) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_RSA_WITH_AES_256_CBC_SHA) id 15.1.1101.12 via Frontend Transport; Thu, 1 Jun 2017 20:24:24 +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 v51KOMBj017221 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 1 Jun 2017 20:24:22 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 v51KOKvH017206 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 1 Jun 2017 20:24:21 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 v51KQpdI002347 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Jun 2017 13:26:51 -0700
Message-ID: <201706012026.v51KQpdI002347@cliff.eng.ascend.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 1 Jun 2017 13:24:10 -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: <31104AD6-BE38-45D1-A148-67DF4D73529C@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> <B00A6885-6EB1-4361-8412-C408F23DC5E0@cisco.com> <70866121-f350-d6d2-d89a-89ca1315f5ab@bobbriscoe.net> <31104AD6-BE38-45D1-A148-67DF4D73529C@cisco.com>
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)(39850400002)(39450400003)(39400400002)(39410400002)(39840400002)(39860400002)(2980300002)(438002)(189002)(199003)(9170700003)(8676002)(478600001)(47776003)(54906002)(50226002)(81166006)(8936002)(53416004)(8666007)(305945005)(93886004)(4326008)(53936002)(6246003)(38730400002)(8276002)(189998001)(5660300001)(6666003)(97756001)(110136004)(2906002)(4720700003)(9686003)(50466002)(229853002)(86362001)(46406003)(23726003)(356003)(1076002)(106466001)(50986999)(6916009)(76176999)(2950100002); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB0830; H:us70tusmtp2-o.zam.alcatel-lucent.com; FPR:; SPF:Pass; MLV:sfv; MX:1; A:1; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; AM5EUR03FT019; 1:nQWUMknBN9yu9quM5goPONZuZvcigB8mwRUVAMCglK07OInmXNB2/oyFBcpNPxiWch9UVJN/mxyG9gPOuqBDAS3F0B7OW4J3cfuI61oknyR+FfZv53FFw0Wh70TVWymGdoWkDsydcEKuk8OC/l4ZdPfF6Uy8+FmUHk2mewjFtpZBFHcANZORJvScM46b8q0IZuuLGXi1kE89Jk7ADzrk66BGk7WBayFP4EcBt3tPcQBIi1KrmM2xStMeFG4dm1uMNyRHBnTxGJtQrT2g8ZN4QDxdFQrkrGDUO2FxYyuOclEm86QCkbpqoJ5sruWXIkKR6hNnzd7iLTncgN/fmmb45w8P3+BQ3wpIcuUdiEhDy9XaQhjwjfmgs/y7A0gOMxlke15RWE+mLgx23fvcTToG1+WRs+9TJLzMkxBJnivRk13/nXu6yPQ9gpZ9WYpdPTQlH6ZjpTCzDc/Zd/eF4vzb4pL0Nb7DeR16CWml5+IQXju7+VF8GkiEpA2wNBhX+5S4elPuwsp47ea2ghjUnbZR1moTwOgNFON8ZacQklnQDq7c/lmCBdgreaOq2e5FYmQSb/xMfQ7ZiS+cWCgocozwUg==
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: VI1PR07MB0830:
X-MS-Office365-Filtering-Correlation-Id: e948aa90-7f2b-41bb-c72a-08d4a92c328a
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(8251501002)(2017030254075)(201703131423075)(201703031133081); SRVR:VI1PR07MB0830; 
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB0830; 3:65pdtcV9f6GJMnx393YlGqN/CTr7VwzPyz4PRvTl7ei5eU2ap04m0FBOYvDemItk8idnq00buGBhhhTxSYOpHJHvXvb8gQraBOIv1sWlRW08aLAm0VtUcyz5Z8ktRmTk62aj1TEb+hfZLHb5RqnVr1FcUY4Fg9Dngbdf25sxrSWiE4SaIVwC91U4vz7uyW1P/3GdZPbiHm2YMd7sv0r67WKhA2KATOG+ixeh+uHaZCqE9bifsgUZ/8FdrBQdeCQCse58/+FkTNC3sf+kCNYE7NdSO5tZTkNh1whSx+wlYH/q59nJ9QJUhl7xxt6nLjpcYCzVuMJ6fvpYgL4L6e0d2pdP+k+/IVb2GlU2+OO71NeecRmC0pQweE5H1NKM/L2t8ykJFUiiBuLT4FDbVypEmgIiZlZCOjpolrhIByXJNpSxEV57MxV+ZH6q8FIK7wlVjt45pmZzTZHZfWkaaIhKrdedha3bqxaWMjWzFKodZHONQEPVWmEmvF9uQO0DEdlT
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB0830; 25:5m9N1ZTkuSCE7ux45KfCFCZcLr5hd1YVxRXrvlol8W+rVXXtzrNDY+mMMmxJ+ZVCFpv8euRs5gIs/SaVsOI/YtfC/kePI+nR4mH2/9fHiEYdqxCpH3CgCDWCiTclRTxwm/82Oj4A5Xo+zA2yYOIFQEQ0sE5m08opZt8BA5ub2G+YeXORmijqyCStRpEYy6krVDaDbAPE4ZjXxl4hRCA9gB+wtWGTVZzCbsz91ke1MzKFskxDj0D1Lar2Jh5q9Ema4JVUYJGmaCZcvBptWxpmvvBKnnppZvt+xxPXLpwAa1RVJrDHO912J2nUyDvUC3aHJ1QiXv4CcY/X9lyqlztiYQbffs11wEhUtHNObVnmTFfPg6vATHI9kloCCdaHJgiYfCAbtQjuAjEv8LaGKK2DGhxf7IIVFTNvrtzdj6d+Mo79OV0X3RUdJVlMUpYyh3NwhuqbgjWD2QseYVJ+l7KTd0ggiCnuQlIpkFRCnhnv6dE=; 31:oZFJZ/oJP87iztnGs80fbCs/nqaELWeYnWfvATGVW2V+bnKvnjoUD3miVkiar0636YhIteBdMZLDf3vtQiXkqaltaI1jZ4l1Cr6+KIn3fHv76KlvKqvLgVvdIgXeRqfTGOpuSQN5DtoYgcrMspi1ZW7qPz9+YWZqjgcctyBafDQOmTW5xwargL+M+HUHf8AEik1DYByHMKohxwg9C8zM3TDz0u0GM+K0Atu1jrLoqq1uHKeJ5+Ctfl2PhfrbLMU0Kf2tLbkLnfAq+brK293nNQ==
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB0830; 20:yUoPP9b6A+bev2W5gbOE5tMzbIetyrEZYx6+FM3UZRNKOZcL/DcLpdOdG2bGlhNJB42NB+wcAEX6ZuZA323txfhVtNT7cjtPOiCGKewWqyvU46b8HOob1rvTIzXkxFD6KlLBFmUo2NCGHLxBsOhw8qyRKAf8fbnvb5KsvPkK3PZb/dHb70H2iAQO4HLUUn5YekXqvwaHRxkzyd70eG8M2XUxILdkBpTo7DOBYDuSh6TDNbQR09Rf2xEszTAJfGrGJs9QtuVK9WPD/d6vRV9fcEsHXSzCoLH496p8UW1g7SxDzc701SxrguucGhNfwOVFijT7n+1F3ZpQr5Xfwimg1N5/lFCiIHPG0RMtV8qBep9knbb8iQlhZ3TD8jkDic+Tw449/OrtdxrzfaBTFPgCmwmTFKJcs7xGIQQuepVsSoCYWalrpQhLmWTJH+6CqXXJrGtddNRb86L54Es5Ka0fmPT1aMnFmihxhrhINH3cdmLi/TFJYl4TJ2nmZuWJTv4pUJppyKjFUfAgZyRzc87v4kTA4ZSdef+8cbG4aBl6ZMryF/gmK+2Y5M4TAvjDRA57Q2w+ZDxWiakkXNEsCwKsMu+UMtm0QDgC2UagRl8t4Yo=
X-Microsoft-Antispam-PRVS: <VI1PR07MB08308E7EEF146152087AF54E8FF60@VI1PR07MB0830.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(5005006)(13018025)(8121501046)(13016025)(3002001)(93006095)(93004095)(100000703101)(100105400095)(10201501046)(6055026)(6041248)(20161123558100)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123555025)(20161123562025)(20161123564025)(20161123560025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:VI1PR07MB0830; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:VI1PR07MB0830; 
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; VI1PR07MB0830; 4:EQfhnzf+bsrJI559E7MWgLv5jX3xfOfKmhTk6dPqEh?= =?us-ascii?Q?LJfp2QCB0DrhN6t0roQNci2U2IOaX7aewaIIlnJasApSNbGKveEHB66SwcBq?= =?us-ascii?Q?manKgcdDEo3RbGFBV913lICRrTlvhNwc7AdJtUXMsAsRARf55Muif+fK+NV7?= =?us-ascii?Q?sOWZ/x/51COkXPBFtOuGt1EQosAeH00mvvbFwbhQbffVNWRLviyjdkQJoE4b?= =?us-ascii?Q?aBj2PvgJOmo2EULW/9sugKJ70Y2XzpQFkwx6KJraUHZKe+PmF/5Upq5kgF1Q?= =?us-ascii?Q?2PvgzVwoliZIeLb8q4OBAUkOa+THqh95AWCzES0qU7JoQ1wQDss9z5YFhHxy?= =?us-ascii?Q?IwyGRrO7AgU17cLwzWwDxHxWDb5nhYbANlbar6bfTkCLdUtYlYamIaAHEG6A?= =?us-ascii?Q?GydHkbAptT+I2R5a1MSsWWQKbKwXpl3dE9Ufv4gA2iKHpo6JG0GjY9BG/SAC?= =?us-ascii?Q?i9EwSRtXBLJ3BrIB7j7rDkVIvcNZGkUZV523YScQRlVTUpDu9zV3A16fxxDc?= =?us-ascii?Q?zDqbTbu/4Sras+wpD7jK8HSk18HSGWxlPIMSvB+20vwCSNLADhrZ1OqLqvap?= =?us-ascii?Q?Y5OFpcpDjyXUQbq3tqNMF9/qZb/ou4pNr1Ej55SwP6v9xDaeyylvZOUa28Qv?= =?us-ascii?Q?SbOfFxra2vnMk9Z6CCO8l+qJySxdz5gdQkC3SdD2Fd1zK4vWlfMED6OouqUF?= =?us-ascii?Q?wzXLIwV8yZ0bvtuAk1QHBxs5/fbWCOhzP0SRVIJAGqCVH/atzvlIC1/QwojY?= =?us-ascii?Q?m/iZ8LQF5Lf3Gx+itmd2A7oyk+7Jnz0ODRD66CrMdh3ysGPMKl/1uGfIV9W3?= =?us-ascii?Q?uwGiWMNV7Od7ScuBCAEd9+yDcTq3p4Fqms8B1Sexetw9jwhqIfyk7KZ7RaV1?= =?us-ascii?Q?Te5viYUtdiTbRPFSxp/+cfG7YhXil0j71DOefZsG7Hbc8HzIZOrmUKIe4p1m?= =?us-ascii?Q?ZwWsQxOTabxbqVH9t3QP5cBMPfXhGoo6aZIssu01Rc3wuganAKN4vg+CXC+z?= =?us-ascii?Q?ZeFDyIE3llLKqopSDDpu62zMTbo1xZw9coOopLZFFhYVwo7/Dfneq5qpPMA1?= =?us-ascii?Q?cQBWRYvrec0bquOgZg0mwxtY2kGF/BeE+gj4BylniaGV5GZ3kKjifn4eZuPQ?= =?us-ascii?Q?97GolSsOTKSQ0VRDbOMNqo1sxB9YrDY4HMXku5GYvw85kqCYAo36IxhqUP+X?= =?us-ascii?Q?l+Fb2J2Z3RJK/SbVe60EVg12E6ifzgqg3K?=
X-Forefront-PRVS: 0325F6C77B
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; VI1PR07MB0830; 23:y7T/iDXiS8pQP1uAzvdiu8OMuxQsMCkY47aHzwWs0?= =?us-ascii?Q?rz6n6Xf+Sq0Bqp+ixT70tQ/GDv0gvTf5uG5e4cak9b/U+mBwK5z1GYehX1Xn?= =?us-ascii?Q?OOLJa26Uj/Ju6GgKWrHeej6fM4H4bkL73S0kIeqzaEAWseyPLR4cRWuSBx7w?= =?us-ascii?Q?xHikShDFdu8iQ7nc+H8FR6c1SgTmp3P2AI4bEaWFQgDH5imABuGtCmZKIxRQ?= =?us-ascii?Q?Gl4P4fJqQ7h3eqdaYNjVPJmPl5tA3WXfiqxM7YKHaJBsrnEWo1R1ItxOiaOR?= =?us-ascii?Q?qIMQWPg4Bmx27Q7Njq4NqtNdTUTyGw+3IVM7yAlnOC2/+I+2IyoMHsl+ZKj3?= =?us-ascii?Q?ZFS+XP+JuoS8Uc+Ve3eZhQT3rLEu4AKkFkyfDgFDBLNc/fLy46URnCIxiVzk?= =?us-ascii?Q?EZgbLLF1NxNFKXg1yAf2mreWHyEDPC4TQ0DUk2rEHAMA9esyCUpwhsZdxJTS?= =?us-ascii?Q?5+MuMoKkwysB3mav4m40joycS/V/h2pC4g7/Rm2LDAByKBSmCuO0kv2aLkzI?= =?us-ascii?Q?vhR4qvRr1A0w8EI6UV3cAMzg0DCeWdcvKIQ8RMA0jG6S6usijVhF2hR1xmt6?= =?us-ascii?Q?b69oCEUc0Y5adHiN+ZHeTU/cbKcuRh7l1RQ+WDf6/l7bFHL9rsfWgar+owC3?= =?us-ascii?Q?x+KLLLcOaMV68e1bD4e+SxdzkBfzqJv9lygu7/ocm7kHKAtrJoW+tZ26LRMr?= =?us-ascii?Q?Sf90RGedIClrDjJqMtIJcGjqaYaLdKbJB8UUKSGh0ibwGm93ENV2Vswvh4Qd?= =?us-ascii?Q?LjMXIIz/riRuDjzyLBXwy1Vh4uRCAxDGIRP8QNIribuXVA69F/oGN8nzMA8G?= =?us-ascii?Q?Jhla/T9/glDbdune3d0CQc/dLTSypuTwoQuU8ceKhuZ1HHhD8KZQjeE11l7c?= =?us-ascii?Q?EFonDbgu/9dVPRbg0e80jXWkgF5LCOi2fN6WaqQedXiTcJHHE4SrLu/1hxd8?= =?us-ascii?Q?lAbTlpHDYh9yPM6VO5ZO8OyZgJ0ykwNZQya7HsF9YkwUmh3e5NwJjCnelL6h?= =?us-ascii?Q?FbsbCLbv8qdb/mrWEHJK/BjGzbq5U6Gsnj1hb90a+5ltXErlqPbJIF6uYn3v?= =?us-ascii?Q?yZE/icOSr5/exHmAxjPN/FeX7/5P6/l3oLKV/WpWPMKCJ3rleLk6eQ2WmJUs?= =?us-ascii?Q?Zyu4GoPmPRpW6obDqXZNu/V447Bq2Y4woB6kMJRMSZQ1KiBFMs+35JWLgCls?= =?us-ascii?Q?kfEFAOeFCPjee4=3D?=
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB0830; 6:+BiedUHi5jwRQ4nvSqZ+5yLDmW6u9FnY4WTsO2nsIR5VwsAU/fzPZn6mhN33luXUPEBKCnrkhTgMoHokm8/1FIEms1vhggbs/rlJpp17MXXAAozeW4u9GIsLq+UFKJa//SzExzf/emjuMQKjSP4UtKFfIDC0vEy3VWyVg8+MBSqpAzo4XEck5okpyDad/o2P5R3OmM/yV+h431zOh4w4qJ7DU1ZPC17WpMMSv/QalMjUoFsLCtXmWpdGMEzOUPcEVtZzLgqTV5fnkNwF7SDBYjXRg/OqKMnQZkbQ1TN0pdC7lyEAHIGdlMmXMmJleumIlQxp7ONVrK7/6O4QvLeUDXdn66808dMnEp8o7cJVQI/+p3FgKbQtScSY8sBNruPMtPDBlh+WRIvnN9o59+VaVpLUUTnQypqgywmwX8abpZmdN1TCp4zP/yeKhDi2H9fnLh5X6LS5pDWJclyPo5WF5Ui9pJEIrr9xLI8x0e+sGlVJ8hQCJgw14AVyZlm6YtVKMZkD4ZES3b1aiHzb3BMUs5vG8UteW+dB7jOuR4dloLk=
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB0830; 5:rNaNShVYzEPN1Cjxre5fZRVel7LTNXE3Ic+cyux6hAxhJSw+1MF70iG5CMSLsLtmVSUBaNO8LvdcQVBjCz5OMFcQYYBwItIm0hBZXN+wF2MZz9yf42C5r4Fz8Im+PS4ddlQgeGIJg2Rq5xz6A+tx4UinB9fIjDWcdUSQrC8svTE7EdJwKRGJnbWCaR8Uw/v1CM+hwQOxqSebBNk69a5RpDXxK7CYxxpC7/ssmMScuMMc+Ne8Vd67hwdj2xTJjkxu0huSuFdJ0V9USnJ0jz2CohxRoH5G5ul65mJ1+6sNsvUrtlL+SaE1YkzdOsKuEMUFkzG6a/cetPFJ1kGJ4m/xzA1sK3pLEY3lT+IltmETy/HFs2wlS/K812laWy9sor0cOXDZmGkf3Ah612I2u70uUiayPQFNo6OlZZEddV1/lKQMZTspKn0JTteJGQlNdp2zpvuPB2tdBgT5d1IvyzFU+hR73siI4N2EFiLh6YpnG+Cq2i3SaRt11sVths6avwgl; 24:geSkp/NMpXD3Hk8jMqHqg5Kn7YLl4BjYwPA5PMGzxjggx70hLDyo6A9reQ94fCeYfl5h2/maKlS9H9POdlGa4/wVJTK6jgBrQBo1SpCLIaI=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB0830; 7:JwQ8jUoTtFGJLPtyolDewHKxJ/2fCIOA2SKcWEiAXJU+ViUsCarZ2h5BNRsBxoVu8B2P/jFjpjH4E8Ku6y27Yvmd7qA+KxSorcsPPHfMFGO5UvCIv9EtRT4M+Ra0WEjdzlfGdOwOqFzqFOltJj62tPUs0uPfpHUhnnyCfp5sRbBpAgVodqCn+rv7rKZt2y2pZlFwNIrKMA5FC4ZWWkNysA6xg14trwamxtnRmahmbppqzFQqS+5lBssUsRkiE4HGvFCRUuKysaErb9MhfWGAXGICTqRKt4v2/eQxXbWRCPOphTZJAYCpZKFLv068QUR02S6PPC6senWXcbAKAQzAvA==
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 01 Jun 2017 20:24:24.2849 (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: VI1PR07MB0830
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2tpext/dbDUboy14G3or83MLjxfT6yBVwE>
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 20:24:32 -0000

>> 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 think first we probably need to understand the applicability because
>it is not an IP-in-IP encap, there's a Layer 2 header in between, not
>tightly coupled but rather part of the transported payload.

And an IP header (if present) may be down various layers and not easily
accessible.

So far, LCCEs do not need to decapsulate all the stacked layers trying
to look for a potential IP header. Adding that requirement as a MUST is
a tall order that may be too onerous and impossible to satisfy.


>Now, what you describe in terms of level of mandatory applies to RFC 6040.
>If an implementation does not comply with RFC 6040 it is, well, not
>compliant with RFC 6040.

Exactly.

And that's why I believe this should be a _recommended_ extension when
inner IP headers can be found easily but it cannot be a mandatory
requirement for the L2TP protocol as a whole.

-Ignacio


From nobody Fri Jun  2 06:24: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 DD107129B75 for <l2tpext@ietfa.amsl.com>; Fri,  2 Jun 2017 06:24:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.7
X-Spam-Level: 
X-Spam-Status: No, score=0.7 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  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 QiYCAxLPpQAi for <l2tpext@ietfa.amsl.com>; Fri,  2 Jun 2017 06:24: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 3638A126DCA for <l2tpext@ietf.org>; Fri,  2 Jun 2017 06:24:02 -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=NRCinc/Fn1UNrt6dPiIRe6gVZnmI0sqMpkDQBqPfTLE=; b=7k4q70FJtEdK2jLPeMvo0M2Bt 9t2tucrm8MTeTN71BOoLLqOwq4Es1lm8DW4/RhHrdeel9Cvo/geA8RV75iKup6pncP55/AuVMZzGn D1pnF/RXmrnYOGAfE03GeqEEGwpdrjZ7pT1BQmX9bbhmUaVnEnzCLnbnMv/4o22swNQEKqm39bjQX SHwvBj9pXAQrly48XdIeJgDA2GZUSFE93OYN3LdKxt480Y/ANnKJiildSPsUsIQ2rTm6ZZmICLugs WIzevuTri1cymHOGGlp8PtpX25UxsA27U4EgxMoy2Zi27q+TSk9FM6A+lq2n1iEs25jeIOMHyfAW/ tCzFxoHkA==;
Received: from 110.139.199.146.dyn.plus.net ([146.199.139.110]:33590 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 1dGmYZ-0000Eq-Ic; Fri, 02 Jun 2017 14:23:59 +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> <31104AD6-BE38-45D1-A148-67DF4D73529C@cisco.com> <201706012026.v51KQpdI002347@cliff.eng.ascend.com>
From: Bob Briscoe <ietf@bobbriscoe.net>
Message-ID: <c4aeeafa-1f6b-afa9-4599-2a747259be22@bobbriscoe.net>
Date: Fri, 2 Jun 2017 14:23:59 +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: <201706012026.v51KQpdI002347@cliff.eng.ascend.com>
Content-Type: multipart/alternative; boundary="------------5702327C13CE5A71D7068A8B"
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/FTV_6uJ-zFxULwemqSa8Kp6MoTc>
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: Fri, 02 Jun 2017 13:24:05 -0000

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

Ignacio,

RFC6040 contains the following para:

    If an ingress claims compliance with this specification, it MUST NOT
    permanently disable ECN processing across the tunnel (i.e., only
    using compatibility mode).  It is true that such a tunnel ingress is
    at least safe with the ECN behaviour of any egress it may encounter,
    but it does not meet the central aim of this specification:
    introducing ECN support to tunnels.

To be safe, an L2TP ingress could permanently use compatibility mode. 
Compatibility mode simply involves the ingress clearing the 2-bit ECN 
field in the outer (setting to 00). This would not allow the L2TP 
endpoint to claim compliance with RFC6040, but at least it would be 
safe. I think it would be useful to add this as operational advice to 
draft-ietf-tsvwg-rfc6040shim-update.

I would imagine most implementations of L2TP could be configured to do 
this (do you agree?). I suspect some still allow config of the setting 
the whole 8-bit ToS bytes, in which the 2 lowest significant bits are 
the ECN field (distinct from the 6-bit Diffserv field).


Nonetheless, altho safety is important, the main purpose of this draft 
is to go beyond that - to say how an implementer would add ECN support 
to L2TP. See inline...

On 01/06/17 21:24, Ignacio Goyret wrote:
>>> 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 think first we probably need to understand the applicability because
>> it is not an IP-in-IP encap, there's a Layer 2 header in between, not
>> tightly coupled but rather part of the transported payload.
> And an IP header (if present) may be down various layers and not easily
> accessible.
>
> So far, LCCEs do not need to decapsulate all the stacked layers trying
> to look for a potential IP header. Adding that requirement as a MUST is
> a tall order that may be too onerous and impossible to satisfy.

As recently discussed on int-area, I am going to widen the applicability 
of draft-ietf-tsvwg-rfc6040shim-update to include cases where a L2 
header is being encapsulated. But this wider scope would not be as 
mandatory.

I definitely do not want to make this a MUST. I made this point myself, 
in response to Tom Herbert on the int-area list a couple of days ago, 
pasted here:

> On 31/05/17 02:45, Bob Briscoe wrote:
>> One way to include all these cases in the scope of the draft is to 
>> say the tunnel endpoint SHOULD check the L2 payload for an IP header, 
>> even when the L2 header is not being added / removed. But that is 
>> rather an onerous requirement, don't you think? Especially given this 
>> would be asking the implementer to violate layering, we can only ask 
>> that it is done when feasible; it cannot be a hard requirement (e.g. 
>> L2 payload could be encrypted). 

I think MAY is too weak, but SHOULD is too strong, so how about this 
form of wording:
"If feasible, the tunnel endpoint SHOULD check the L2 payload for an IP 
header"

And I intend to add something along the lines of: "Otherwise, if the 
outer is IP, it MUST zero the outer ECN field."

>
>
>> Now, what you describe in terms of level of mandatory applies to RFC 6040.
>> If an implementation does not comply with RFC 6040 it is, well, not
>> compliant with RFC 6040.
> Exactly.
>
> And that's why I believe this should be a _recommended_ extension when
> inner IP headers can be found easily but it cannot be a mandatory
> requirement for the L2TP protocol as a whole.
As above, I strongly agree with you.


Bob

>
> -Ignacio
>

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


--------------5702327C13CE5A71D7068A8B
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Ignacio,<br>
    <br>
    RFC6040 contains the following para:<br>
    <pre class="newpage">   If an ingress claims compliance with this specification, it MUST NOT
   permanently disable ECN processing across the tunnel (i.e., only
   using compatibility mode).  It is true that such a tunnel ingress is
   at least safe with the ECN behaviour of any egress it may encounter,
   but it does not meet the central aim of this specification:
   introducing ECN support to tunnels.
</pre>
    To be safe, an L2TP ingress could permanently use compatibility
    mode. Compatibility mode simply involves the ingress clearing the
    2-bit ECN field in the outer (setting to 00). This would not allow
    the L2TP endpoint to claim compliance with RFC6040, but at least it
    would be safe. I think it would be useful to add this as operational
    advice to draft-ietf-tsvwg-rfc6040shim-update.<br>
    <br>
    I would imagine most implementations of L2TP could be configured to
    do this (do you agree?). I suspect some still allow config of the
    setting the whole 8-bit ToS bytes, in which the 2 lowest significant
    bits are the ECN field (distinct from the 6-bit Diffserv field).<br>
    <br>
    <br>
    Nonetheless, altho safety is important, the main purpose of this
    draft is to go beyond that - to say how an implementer would add ECN
    support to L2TP. See inline...<br>
    <br>
    <div class="moz-cite-prefix">On 01/06/17 21:24, Ignacio Goyret
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:201706012026.v51KQpdI002347@cliff.eng.ascend.com">
      <pre wrap="">
</pre>
      <blockquote type="cite">
        <blockquote type="cite">
          <pre wrap="">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.

</pre>
        </blockquote>
        <pre wrap="">
I think first we probably need to understand the applicability because
it is not an IP-in-IP encap, there's a Layer 2 header in between, not
tightly coupled but rather part of the transported payload.
</pre>
      </blockquote>
      <pre wrap="">
And an IP header (if present) may be down various layers and not easily
accessible.

So far, LCCEs do not need to decapsulate all the stacked layers trying
to look for a potential IP header. Adding that requirement as a MUST is
a tall order that may be too onerous and impossible to satisfy.</pre>
    </blockquote>
    <br>
    As recently discussed on int-area, I am going to widen the
    applicability of draft-ietf-tsvwg-rfc6040shim-update to include
    cases where a L2 header is being encapsulated. But this wider scope
    would not be as mandatory.<br>
    <br>
    I definitely do not want to make this a MUST. I made this point
    myself, in response to Tom Herbert on the int-area list a couple of
    days ago, pasted here:<br>
    <br>
    <blockquote type="cite">On 31/05/17 02:45, Bob Briscoe wrote:
      <blockquote type="cite">One way to include all these cases in the
        scope of the draft is to say the tunnel endpoint SHOULD check
        the L2 payload for an IP header, even when the L2 header is not
        being added / removed. But that is rather an onerous
        requirement, don't you think? Especially given this would be
        asking the implementer to violate layering, we can only ask that
        it is done when feasible; it cannot be a hard requirement (e.g.
        L2 payload could be encrypted).
      </blockquote>
    </blockquote>
    <br>
    I think MAY is too weak, but SHOULD is too strong, so how about this
    form of wording:<br>
    "If feasible, the tunnel endpoint SHOULD check the L2 payload for an
    IP header"<br>
    <br>
    And I intend to add something along the lines of: "Otherwise, if the
    outer is IP, it MUST zero the outer ECN field."<br>
    <br>
    <blockquote type="cite"
      cite="mid:201706012026.v51KQpdI002347@cliff.eng.ascend.com">
      <pre wrap="">


</pre>
      <blockquote type="cite">
        <pre wrap="">Now, what you describe in terms of level of mandatory applies to RFC 6040.
If an implementation does not comply with RFC 6040 it is, well, not
compliant with RFC 6040.
</pre>
      </blockquote>
      <pre wrap="">
Exactly.

And that's why I believe this should be a _recommended_ extension when
inner IP headers can be found easily but it cannot be a mandatory
requirement for the L2TP protocol as a whole.</pre>
    </blockquote>
    As above, I strongly agree with you.<br>
    <br>
    <br>
    Bob<br>
    <br>
    <blockquote type="cite"
      cite="mid:201706012026.v51KQpdI002347@cliff.eng.ascend.com">
      <pre wrap="">

-Ignacio

</pre>
    </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>

--------------5702327C13CE5A71D7068A8B--


From nobody Fri Jun  2 07:50:48 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 AE880129524 for <l2tpext@ietfa.amsl.com>; Fri,  2 Jun 2017 07:50:46 -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 yxktFdz-TVX1 for <l2tpext@ietfa.amsl.com>; Fri,  2 Jun 2017 07:50:43 -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 C1DBD128D3E for <l2tpext@ietf.org>; Fri,  2 Jun 2017 07:50:42 -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=Z7KEyuFiZglQEl082/pTTc75LPuuNm+JGmbbhLgQ8O0=; b=ttqvLE0p7C+7ejWcrGAZL4J/RJ MnjrzzmLq2CzhCLoSUBMRO/g96ntVeFBPtpi+T3jkkn93aBXc7wQ3FnVaum+b0IVf6mH+lHAmjoNk 47oX2Ws0IAtu5XQ/vjVmJmOo4zr3ETU1PCv/n+aalrsP6S4sVldHlTSKdt/wku0Ow+ynKOd0R8H9H 73wKtBa1lDxY6ex9vmnsoNz9wDALFQLd2Q0TGqG/p245z3uV073aQfOhu+2Y2/hhkdDmbgftg+azW 0UhyDlLbHtdRIarvq7u2tF5NvSR4tTvk1yYccjsIGE95dhbQ5+csk2w9UcBvnj4ocFAeBqtHQ8QqJ 2xvxyTmg==;
Received: from 110.139.199.146.dyn.plus.net ([146.199.139.110]:34300 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 1dGnuS-0000iD-Tw; Fri, 02 Jun 2017 15:50:41 +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> <70866121-f350-d6d2-d89a-89ca1315f5ab@bobbriscoe.net> <31104AD6-BE38-45D1-A148-67DF4D73529C@cisco.com>
From: Bob Briscoe <ietf@bobbriscoe.net>
Message-ID: <fa3cb9b0-9a6b-bd94-fbc8-c8fc3eab0ddc@bobbriscoe.net>
Date: Fri, 2 Jun 2017 15:50:40 +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: <31104AD6-BE38-45D1-A148-67DF4D73529C@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
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/_UWjOVje-Eiz2_gUyCLzmFbUmLw>
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: Fri, 02 Jun 2017 14:50:47 -0000

Carlos,

On 01/06/17 14:23, Carlos Pignataro (cpignata) wrote:
> Hi, Bob,
>
>> On May 31, 2017, at 6:11 PM, Bob Briscoe <ietf@bobbriscoe.net> wrote:
>>
>> 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.
> Admittedly, I have not read in detail RFC 6040 or draft-ietf-tsvwg-rfc6040update-shim — however, I do have some questions to better understand the applicability.
You will find that section 4 of RFC 6040 contains all the normative text 
(4 pages).
>
> draft-ietf-tsvwg-rfc6040update-shim talks about “IP-in-IP Tunnels with Tightly Coupled Shim Headers”.
>
> GRE can be thought of an IP-in-IP tunnel with a tightly coupled shim, when transporting IP directly (although GRE can transport multi-protocols).
>
> [and a small note that you might need a reference to RFC 7676].
>
> However, GRE can carry Something-in-IP, with “something" potentially carrying also IP. In that case, I do not believe that’s an IP-in-IP-with-shim.
See email to Ignacio just now (which included my response to a similar 
point from Tom Herbert on int-area)...

In summary, I intend to widen the scope of 
draft-ietf-tsvwg-rfc6040update-shim to include non-mandatory /guidance/ 
for when the shim encapsulates a L2 rather than L3 header (essentially, 
interpreting the guidance in draft-ietf-tsvwg-ecn-encap-guidance for the 
specific protocols in this draft like VXLAN, GRE, L2TP).
>
> For the L2TPv2 case, L2TP carries PPP. PPP can in turn carry IP, and/orsomething else, and usually a mixture. Is this really applicable to your draft?
Yes, very much so.

One of the main motivations is to be able to support ECN between an LNS 
and a LAC, as used in many broadband settings.

We have implemented a prototype of the ultra-low latency form of ECN 
(L4S-ECN) for the downstream queue of a BRAS.
For RTTs ranging from <5ms to >100ms, every packet has ultra-low queuing 
delay (in the hundreds of microseconds, whereas the best previous 
solution added 5-10ms of queuing and required thousands of per-microflow 
queues). ECN also gives zero congestion loss, of course. We have 
demonstrated interactive video processing in the cloud for virtual 
reality, remote presence, finger-gesture panning and zooming etc, along 
with many other delay sensitive apps - all running simultaneously over 
the same broadband line (all in the same queue on the BRAS). See video 
of demo here:
https://riteproject.eu/dctth/#1511dispatchwg

In the downstream queues of the BRAS, the IP packets have already been 
decapsulated from L2TP, so when they are ECN-marked they are only within 
their PPP encapsulation. However, there will be scenarios where the 
operator will want to deploy ECN on nodes within the L2TP tunnel. Then 
any outer ECN markings will need to be propagated to the IP header 
inside the PPP payload.


>
> For L2TPv3, L2TP carries a variety of protocols, one of which is IP directly. However, although there is running code, there’s no RFC for it (https://tools.ietf.org/html/draft-ietf-l2tpext-pwe3-ip-05.) Similarly, RFC 3931 seems outside scope.
See above, re adding guidance for widened scope.

>
> [and another question ,what about MPLS, with RFC 5129?]
Do you mean, "Is L2TP over an MPLS PSN outer header in the scope of this 
draft?"
It wasn't initially.

After I add guidance for what to do if the inner is a L2 header, I could 
also mention that there might be other PSN outers too. However, this 
draft was originally intended to clarify the scope of RFC6040, which is 
solely about IP-in-IP. So, whereas IP-shim-L2-IP can be legitimately 
included in scope, I think MPLS as the PSN is too much mission creep.

>
>>> 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
Thanks. I actually based my text on similar examples that I found in 
RFC2661 via the IANA registry of L2TP AVPs after Googling "L2TP 
capability AVP".

A question:
Do you think I should call this an LCCE Capability AVP to be more 
generic, then assign 1 bit for an ECN capability? (As opposed to an ECN 
Capability AVP that only uses 1 of 16 bits).

I doubt another LCCE capability will ever be added, since there have 
been none so far, and L2TP is already mature. However, would you agree 
that there is no harm in being generic like this?

Another question, I used 4-octet alignment for the AVP, cos other 
examples seemed to do that. Was I correct?


>>>
>>> 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?
>>
> That’s my understanding of the unqualified word “extension” beyond L2TP land. Is that different anywhere?
So, to be clear, here's further questions:

Is your advice (and Ignacio's) that I should write the L2TP-specific 
text in my draft as a extension to L2TP, rather than an update?

Is there a distinction in L2TP between an "extension" and a "recommended 
extension" (as mentioned earlier in this thread)?

Should the safety guidance still be an update to the base L2TP specs (v2 
& v3)? By safety guidance, I mean text about the ingress zeroing the ECN 
field in an IP PSN outer if it does not check within the L2 payload, or 
does not check the egress ECN capability.

>
>> 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 think first we probably need to understand the applicability because it is not an IP-in-IP encap, there’s a Layer 2 header in between, not tightly coupled but rather part of the transported payload.
>
> Now, what you describe in terms of level of mandatory applies to RFC 6040. If an implementation does not comply with RFC 6040 it is, well, not compliant with RFC 6040.
See my recent response to Ignacio on this.

Cheers



Bob
>
> Thanks!
>
> Carlos.
>
>> Bob
>>
>>> Thanks,
>>>
>>> Sent from my iPad
>>>
>>> On May 30, 2017, at 10:48 PM, Bob Briscoe <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
>>>> https://www.ietf.org/mailman/listinfo/l2tpext
>> -- 
>> ________________________________________________________________
>> Bob Briscoe
>> http://bobbriscoe.net/

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


From nobody Wed Jun 14 04:20:38 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 5E36012708C for <l2tpext@ietfa.amsl.com>; Wed, 14 Jun 2017 04:20:36 -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 lU-kGHApS5Yi for <l2tpext@ietfa.amsl.com>; Wed, 14 Jun 2017 04:20:33 -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 9A8041201FA for <l2tpext@ietf.org>; Wed, 14 Jun 2017 04:20:33 -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=WbNm/9SWqLCzCt5kFcLF0BYOGA+3Lbv91hznuB/Ty60=; b=Ges125lx1KZOTBKbOB7iqkyyp 35xm2NF7arUBqI0bS9oomfuHy9yHVd5tqoKME55D167GpTNb22FG/EQxfPBuQnF7XdYO8Cb9FZ6Y3 OIrATe44Uf92w81P05nZ6cDks3oGPW97pIh8/THvRMIha8wjQkBaVPAJqwJ/cTnwQY295jmiSePQY AM/wWYwAo9hiPb1exDyLpH40iK5U0cbJcThgk0VF1rxawDMHlLQoH3rgOFwOfnPgzUl8qX8lwLYBo 7OpHRZBErz5E83ursygZZT5lhtVsT+Co+rV5o6IlNM29Yjur8HMiwZe7kbvi9/EUWKnsRczynUXlW VdWju0HZg==;
Received: from 167.6.208.46.dyn.plus.net ([46.208.6.167]:46730 helo=[192.168.0.6]) by server.dnsblock1.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from <ietf@bobbriscoe.net>) id 1dL6Lf-00051h-Ia; Wed, 14 Jun 2017 12:20:31 +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: <65cf091f-a65e-412a-fa43-0bea38b00645@bobbriscoe.net>
Date: Wed, 14 Jun 2017 12:20:30 +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: multipart/alternative; boundary="------------B75EF603C5DE621DCD489FC7"
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/1w-wRWaOqbKGcg-Yx1aYxWdxoiU>
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, 14 Jun 2017 11:20:36 -0000

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

Ignacio,

On 31/05/17 02:51, Ignacio Goyret wrote:
> 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.
While going back over all the emails in this thread (I am writing up the 
next rev of the draft), the above point raised a couple of questions in 
my mind:

Q1. When you say "portions" of IP packets, does L2TPv2 fragmented these 
as per IP fragmentation so that each 'portion' has an IP header, or are 
they carved up in a PPP-specific way without IP headers on each?

Q2. Does L2TPv3 support PPP in the same way?

Q3. Are there other L2 protocols currently supported by L2TPv3 that can 
carve up IP packets so that there will not be an IP header at the start 
of each payload?

If framing boundaries might be different, I will need to refer to 
section 5.6 of draft-ietf-tsvwg-ecn-encap-guidelines 
<https://tools.ietf.org/html/draft-ietf-tsvwg-ecn-encap-guidelines-08#section-5.6> 
"Reframing and Congestion Markings", but I don't want to add complexity 
if it is not necessary.

Cheers


Bob

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


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

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Ignacio,<br>
    <br>
    <div class="moz-cite-prefix">On 31/05/17 02:51, Ignacio Goyret
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:201705310154.v4V1sYQH013223@cliff.eng.ascend.com">
      <pre wrap="">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.</pre>
    </blockquote>
    While going back over all the emails in this thread (I am writing up
    the next rev of the draft), the above point raised a couple of
    questions in my mind:<br>
    <br>
    Q1. When you say "portions" of IP packets, does L2TPv2 fragmented
    these as per IP fragmentation so that each 'portion' has an IP
    header, or are they carved up in a PPP-specific way without IP
    headers on each?<br>
    <br>
    Q2. Does L2TPv3 support PPP in the same way?<br>
    <br>
    Q3. Are there other L2 protocols currently supported by L2TPv3 that
    can carve up IP packets so that there will not be an IP header at
    the start of each payload?<br>
    <br>
    If framing boundaries might be different, I will need to refer to <a
      moz-do-not-send="true"
href="https://tools.ietf.org/html/draft-ietf-tsvwg-ecn-encap-guidelines-08#section-5.6">section
      5.6 of draft-ietf-tsvwg-ecn-encap-guidelines</a> "Reframing and
    Congestion Markings", but I don't want to add complexity if it is
    not necessary.<br>
    <br>
    Cheers<br>
    <br>
    <br>
    Bob<br>
    <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>

--------------B75EF603C5DE621DCD489FC7--


From nobody Fri Jun 16 07:58:49 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 A0AA1126FDC for <l2tpext@ietfa.amsl.com>; Fri, 16 Jun 2017 07:58:47 -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 55Luns6paWqU for <l2tpext@ietfa.amsl.com>; Fri, 16 Jun 2017 07:58:44 -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 1CC261300E8 for <l2tpext@ietf.org>; Fri, 16 Jun 2017 07:57:21 -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:To:References:Subject:Sender:Reply-To:Cc: 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=i4QJ6HLQlwArUvm9rtI/vqIlxHbs53SsRB7rOU4P6hY=; b=sIalpQ8hy/RIQ8HdBkITHb0LR qNBWMeNpKzp3aXP6H+ECsemd6qo43zg/Q1lyksaZzgmtYunmHWO4Q0EPrqa7nvEUrMA24sBlsaDsj DRZVL7mR1xNB/M+hENZPZw3fobQrALSS1Ri7YH2ILuFRciTRmcM/CCn64BqJhv3mOYhNjFnZJQbIA H0R8135Ijapk3BziZcGYHqQEmZgKyTmnrpEkWJnDJkKTxZYYxYVesjuZYWjbUF7Idbh0pOHttX/DU yqqPa1kHFElBAeQPVk3x+1H6tj9w7R6/j4KqVPNg6qJTsKHVLB2IpsU80mLDQllglV0QTsc/JjcnN eq7JclbHw==;
Received: from 167.6.208.46.dyn.plus.net ([46.208.6.167]:57680 helo=[192.168.0.6]) by server.dnsblock1.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from <ietf@bobbriscoe.net>) id 1dLsgZ-00028m-2Z; Fri, 16 Jun 2017 15:57:19 +0100
References: <d2e7d9eb-55d8-267c-ed0c-bfc1926e13b7@bobbriscoe.net>
To: Ignacio Goyret <ignacio.goyret@nokia.com>, "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, l2tp IETF list <l2tpext@ietf.org>, "Black, David" <david.black@emc.com>
From: Bob Briscoe <ietf@bobbriscoe.net>
X-Forwarded-Message-Id: <d2e7d9eb-55d8-267c-ed0c-bfc1926e13b7@bobbriscoe.net>
Message-ID: <65819fca-d1d0-af21-3392-6a7d6fb1f5e4@bobbriscoe.net>
Date: Fri, 16 Jun 2017 15:57:18 +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: <d2e7d9eb-55d8-267c-ed0c-bfc1926e13b7@bobbriscoe.net>
Content-Type: multipart/alternative; boundary="------------DBC2EFF1640885AAA7C8B873"
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/Ja0CF3zJ8JIfKjo3mq4peqY0IlQ>
Subject: [L2tpext] Updates to L2TP v2 & v3 for ECN: draft-ietf-tsvwg-rfc6040update-shim-02
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: Fri, 16 Jun 2017 14:58:48 -0000

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

Ignacio, Carlos, l2tpext list,

I have posted a rev of this draft with the new arrangement for minimally 
updating L2TP v2 & v3 to ensure legacy implementations are configured 
safely. The spec to support ECN properly is now within this draft itself 
as a RECOMMENDED L2TP extension, but it does not update any L2TP specs.

Pls review and comment.

This is planned to be last-called in tsvwg, deadline Sep 2017.
There is talk of also WGLC'ing in opsawg and int-area I think.

If you think the L2TP aspects should also be WGLC'd elsewhere in 
parallel, pls say where.
If you think I should give a heads-up presentation in Prague, also pls 
say where.

Cheers



Bob


-------- Forwarded Message --------
Subject: 	New Version draft-ietf-tsvwg-rfc6040update-shim-02
Date: 	Fri, 16 Jun 2017 15:47:58 +0100
From: 	Bob Briscoe <ietf@bobbriscoe.net>
To: 	Black, David <david.black@emc.com>
CC: 	tsvwg IETF list <tsvwg@ietf.org>



David, as doc shepherd.

I have just posted a major revision to draft-ietf-tsvwg-rfc6040update-shim

Please also take this as a request to give a 10min presentation in tsvwg.

As requested, I included specific text necessary to update certain shim 
tunnel protocols that didn't mention ECN at all (L2TPv2, L2TPv3, GRE).
There are two others to do:
* Teredo: I'll do this once I hear from the original author, Christian 
Huitema
* VXLAN-GPE: This is a draft currently going through NVO3 on the 
standards track. AFAIK the Linux implementation already supports ECN via 
RFC6040, but the authors will need to add ECN text to the spec, so there 
is something for other implementations to follow. I have contacted them 
- they should do this, not me.

I have also added more protocols to the list (e.g. CAPWAP, LISP), but 
these already supported ECN.

As you have seen, I have been in conversation with people on the l2tpext 
list, and on opsawg (for CAPWAP). I haven't found anyone specific to 
talk to regarding GRE yet, but I have notified int-area and I gave a 
heads-up at a recent IETF.


BTW, your plan was to last call draft-ietf-tsvwg-rfc6040update-shim 
along with ecn-encap-guidelines, deadline Sep 2017.
I should point out that draft-ietf-trill-ecn-support is in WGLC in 
trill, and it depends normatively on ecn-encap-guidelines

opsawg would like to last call draft-ietf-tsvwg-rfc6040update-shim as 
well (altho I have now realized that no update to CAPWAP is needed, but 
opsawg is now working on alternative tunnelling protocols to CAPWAP: 
draft-ietf-opsawg-capwap-alt-tunnel ). I guess int-area might want to 
last call draft-ietf-tsvwg-rfc6040update-shim too.



Bob


-------- Forwarded Message --------
Subject: 	New Version Notification for 
draft-ietf-tsvwg-rfc6040update-shim-02.txt
Date: 	Fri, 16 Jun 2017 07:14:46 -0700
From: 	internet-drafts@ietf.org
To: 	Bob Briscoe <ietf@bobbriscoe.net>



A new version of I-D, draft-ietf-tsvwg-rfc6040update-shim-02.txt
has been successfully submitted by Bob Briscoe and posted to the
IETF repository.

Name:		draft-ietf-tsvwg-rfc6040update-shim
Revision:	02
Title:		Propagating Explicit Congestion Notification Across IP Tunnel Headers Separated by a Shim
Document date:	2017-06-16
Group:		tsvwg
Pages:		15
URL:https://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rfc6040update-shim-02.txt
Status:https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc6040update-shim/
Htmlized:https://tools.ietf.org/html/draft-ietf-tsvwg-rfc6040update-shim-02
Htmlized:https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-rfc6040update-shim-02
Diff:https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-rfc6040update-shim-02

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.  It
    surveys widely deployed IP tunnelling protocols separated by a shim
    and updates the specifications of those that do not mention ECN
    propagation (L2TPv2, L2TPv3, GRE and Teredo).  The specification also
    updates RFC 6040 with configuration requirements needed to make any
    legacy tunnel ingress safe.

                                                                                   


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


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

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Ignacio, Carlos, l2tpext list,<br>
    <br>
    I have posted a rev of this draft with the new arrangement for
    minimally updating L2TP v2 &amp; v3 to ensure legacy implementations
    are configured safely. The spec to support ECN properly is now
    within this draft itself as a RECOMMENDED L2TP extension, but it
    does not update any L2TP specs.<br>
    <br>
    Pls review and comment.<br>
    <br>
    This is planned to be last-called in tsvwg, deadline Sep 2017.<br>
    There is talk of also WGLC'ing in opsawg and int-area I think.<br>
    <br>
    If you think the L2TP aspects should also be WGLC'd elsewhere in
    parallel, pls say where.<br>
    If you think I should give a heads-up presentation in Prague, also
    pls say where.<br>
    <br>
    Cheers<br>
    <br>
    <br>
    <br>
    Bob<br>
    <div class="moz-forward-container"><br>
      <br>
      -------- Forwarded Message --------
      <table class="moz-email-headers-table" cellspacing="0"
        cellpadding="0" border="0">
        <tbody>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Subject:
            </th>
            <td>New Version draft-ietf-tsvwg-rfc6040update-shim-02</td>
          </tr>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Date: </th>
            <td>Fri, 16 Jun 2017 15:47:58 +0100</td>
          </tr>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">From: </th>
            <td>Bob Briscoe <a class="moz-txt-link-rfc2396E" href="mailto:ietf@bobbriscoe.net">&lt;ietf@bobbriscoe.net&gt;</a></td>
          </tr>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">To: </th>
            <td>Black, David <a class="moz-txt-link-rfc2396E" href="mailto:david.black@emc.com">&lt;david.black@emc.com&gt;</a></td>
          </tr>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">CC: </th>
            <td>tsvwg IETF list <a class="moz-txt-link-rfc2396E" href="mailto:tsvwg@ietf.org">&lt;tsvwg@ietf.org&gt;</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <meta http-equiv="content-type" content="text/html; charset=utf-8">
      David, as doc shepherd.<br>
      <br>
      I have just posted a major revision to
      draft-ietf-tsvwg-rfc6040update-shim<br>
      <br>
      Please also take this as a request to give a 10min presentation in
      tsvwg.<br>
      <br>
      As requested, I included specific text necessary to update certain
      shim tunnel protocols that didn't mention ECN at all (L2TPv2,
      L2TPv3, GRE).<br>
      There are two others to do: <br>
      * Teredo: I'll do this once I hear from the original author,
      Christian Huitema<br>
      * VXLAN-GPE: This is a draft currently going through NVO3 on the
      standards track. AFAIK the Linux implementation already supports
      ECN via RFC6040, but the authors will need to add ECN text to the
      spec, so there is something for other implementations to follow. I
      have contacted them - they should do this, not me.<br>
      <br>
      I have also added more protocols to the list (e.g. CAPWAP, LISP),
      but these already supported ECN.<br>
      <br>
      As you have seen, I have been in conversation with people on the
      l2tpext list, and on opsawg (for CAPWAP). I haven't found anyone
      specific to talk to regarding GRE yet, but I have notified
      int-area and I gave a heads-up at a recent IETF.<br>
      <br>
      <br>
      BTW, your plan was to last call
      draft-ietf-tsvwg-rfc6040update-shim along with
      ecn-encap-guidelines, deadline Sep 2017.<br>
      I should point out that draft-ietf-trill-ecn-support is in WGLC in
      trill, and it depends normatively on ecn-encap-guidelines<br>
      <br>
      opsawg would like to last call draft-ietf-tsvwg-rfc6040update-shim
      as well (altho I have now realized that no update to CAPWAP is
      needed, but opsawg is now working on alternative tunnelling
      protocols to CAPWAP: draft-ietf-opsawg-capwap-alt-tunnel ). I
      guess int-area might want to last call
      draft-ietf-tsvwg-rfc6040update-shim too. <br>
      <br>
      <br>
      <br>
      Bob<br>
      <div class="moz-forward-container"><br>
        <br>
        -------- Forwarded Message --------
        <table class="moz-email-headers-table" cellspacing="0"
          cellpadding="0" border="0">
          <tbody>
            <tr>
              <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Subject:
              </th>
              <td>New Version Notification for
                draft-ietf-tsvwg-rfc6040update-shim-02.txt</td>
            </tr>
            <tr>
              <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Date:
              </th>
              <td>Fri, 16 Jun 2017 07:14:46 -0700</td>
            </tr>
            <tr>
              <th nowrap="nowrap" valign="BASELINE" align="RIGHT">From:
              </th>
              <td><a class="moz-txt-link-abbreviated"
                  href="mailto:internet-drafts@ietf.org"
                  moz-do-not-send="true">internet-drafts@ietf.org</a></td>
            </tr>
            <tr>
              <th nowrap="nowrap" valign="BASELINE" align="RIGHT">To: </th>
              <td>Bob Briscoe <a class="moz-txt-link-rfc2396E"
                  href="mailto:ietf@bobbriscoe.net"
                  moz-do-not-send="true">&lt;ietf@bobbriscoe.net&gt;</a></td>
            </tr>
          </tbody>
        </table>
        <br>
        <br>
        <pre>A new version of I-D, draft-ietf-tsvwg-rfc6040update-shim-02.txt
has been successfully submitted by Bob Briscoe and posted to the
IETF repository.

Name:		draft-ietf-tsvwg-rfc6040update-shim
Revision:	02
Title:		Propagating Explicit Congestion Notification Across IP Tunnel Headers Separated by a Shim
Document date:	2017-06-16
Group:		tsvwg
Pages:		15
URL:            <a class="moz-txt-link-freetext" href="https://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rfc6040update-shim-02.txt" moz-do-not-send="true">https://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rfc6040update-shim-02.txt</a>
Status:         <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc6040update-shim/" moz-do-not-send="true">https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc6040update-shim/</a>
Htmlized:       <a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-ietf-tsvwg-rfc6040update-shim-02" moz-do-not-send="true">https://tools.ietf.org/html/draft-ietf-tsvwg-rfc6040update-shim-02</a>
Htmlized:       <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-rfc6040update-shim-02" moz-do-not-send="true">https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-rfc6040update-shim-02</a>
Diff:           <a class="moz-txt-link-freetext" href="https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-rfc6040update-shim-02" moz-do-not-send="true">https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-rfc6040update-shim-02</a>

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.  It
   surveys widely deployed IP tunnelling protocols separated by a shim
   and updates the specifications of those that do not mention ECN
   propagation (L2TPv2, L2TPv3, GRE and Teredo).  The specification also
   updates RFC 6040 with configuration requirements needed to make any
   legacy tunnel ingress safe.

                                                                                  


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

</pre>
      </div>
    </div>
  </body>
</html>

--------------DBC2EFF1640885AAA7C8B873--


From nobody Tue Jun 27 08:24:44 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 A6555129AD1; Tue, 27 Jun 2017 05:00:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, 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 X3sn1z_sjLH9; Tue, 27 Jun 2017 05:00: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 6DE5E129ABE; Tue, 27 Jun 2017 05:00:06 -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:Cc:To:References: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=xEA3WGcZJ4DY7w+iccN9PQ7hDQNw6Tv/8nOsJeeDve4=; b=v1f995+2Nj3yxEa2m9Fo1TQ5z WsC1m3+Fe9t/oJg5KsIR9BSDLI8+qabOsUK7oNtKtBAYVcE0FtKnBzGMU0xkCPQY5a3WsXWuwUPcX KZaMCKe1A2xZOlVBQSNv3c08GpaGd9cUwCnmLS9X1Cw8Mg3iwWZl5+H/QiE3JXE/OdNQXctgvkYg/ cTrp8+ThxTURhE7wyJrPL0acfcn2hB7oqkr4Yqmn16GejOimWXErwAtr5sl+LQIg2EhcItU1JOO5m 67JNpYx16SEt9CCbLxF88+OJNfrbjLe3j7yXN4SsqXlyF3BdB6A7fUtwpwyKBBcTlxVbrPduDAlGb GcW694M5w==;
Received: from [31.185.128.124] (port=52714 helo=[192.168.0.6]) by server.dnsblock1.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from <ietf@bobbriscoe.net>) id 1dPpA3-0002YR-Bm; Tue, 27 Jun 2017 13:00:03 +0100
References: <149856203820.14897.6223506257752075989.idtracker@ietfa.amsl.com>
To: "Black, David" <david.black@emc.com>, "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, Ignacio Goyret <ignacio.goyret@nokia.com>, Alia ATLAS <akatlas@gmail.com>, Praveen Balasubramanian <pravb@microsoft.com>, Joe Touch <touch@isi.edu>, "nvo3@ietf.org" <nvo3@ietf.org>, Christian Huitema <huitema@microsoft.com>
Cc: tsvwg IETF list <tsvwg@ietf.org>, intarea IETF list <int-area@ietf.org>, l2tp IETF list <l2tpext@ietf.org>, "opsawg-chairs@ietf.org" <opsawg-chairs@ietf.org>, Service Function Chaining IETF list <sfc@ietf.org>
From: Bob Briscoe <ietf@bobbriscoe.net>
X-Forwarded-Message-Id: <149856203820.14897.6223506257752075989.idtracker@ietfa.amsl.com>
Message-ID: <291369ad-5f3a-e529-c2ef-24dfe2406b2f@bobbriscoe.net>
Date: Tue, 27 Jun 2017 13:00:01 +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: <149856203820.14897.6223506257752075989.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------6A1261D435D710497D63773F"
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/jK6ddpxK_vFiJu6lzpAj0PwqPmA>
X-Mailman-Approved-At: Tue, 27 Jun 2017 08:24:44 -0700
Subject: [L2tpext] ECN over IP-shim-(L2)-IP Tunnels: New draft-ietf-tsvwg-rfc6040update-shim-03
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, 27 Jun 2017 12:00:10 -0000

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

David (as doc shepherd),

This is the 3rd revision in the last 2 months. This revision attempts to 
capture all the comments collected thanks to Carlos, Ignacio, Praveen, 
Joe and Alia. It would be useful to have a confirmation from each of you 
that I have addressed your concerns (or not).

I have cross-posted all the lists potentially affected by this draft 
(intended proposed standard).
If you reply concerning a specific point, pls trim the distribution only 
to those interested/relevant.

* tsvwg: owns updates to ECN
* int-area: owns mtce of many tunnelling protocols, particularly GRE?, 
Teredo? GUE
* l2tpext: owns mtce of L2TP
* opsawg: owns mtce of CAPWAP
* nvo3: currently defining Geneve, VXLAN-GPE
* sfc: currently defining NSH

 From my point of view, this draft is now 'finished'. I.e. I am happy 
with it, and it is the first draft where all the ToDo's are done. I 
believe it is on track for the milestone of WGLC before the Nov'17 IETF. 
As I understand it, WGLC will run in tsvwg and in parallel in int-area, 
l2tpext and perhaps opsawg.

Main changes since -02:
* Completely restructured, with definitions of scope before even 
mentioning "tightly coupled shim headers", and new subsections where 
existing text on feasibility and desirability has been re-homed.
* Explanation of the safety problem, and the procedural problem this 
caused when previous ECN RFCs were written (an RFC cannot 
retrospectively set requirements on implementations, so we can only set 
operational requirements - configuration).
* Added NSH, but it doesn't seem to cover encapsulation.
* No longer categorized VXLAN-GPE as intended for standards track
* Added Teredo update text (for safety).

Cheers


Bob

-------- Forwarded Message --------
Subject: 	New Version Notification for 
draft-ietf-tsvwg-rfc6040update-shim-03.txt
Date: 	Tue, 27 Jun 2017 04:13:58 -0700
From: 	internet-drafts@ietf.org
To: 	Bob Briscoe <ietf@bobbriscoe.net>



A new version of I-D, draft-ietf-tsvwg-rfc6040update-shim-03.txt
has been successfully submitted by Bob Briscoe and posted to the
IETF repository.

Name:		draft-ietf-tsvwg-rfc6040update-shim
Revision:	03
Title:		Propagating Explicit Congestion Notification Across IP Tunnel Headers Separated by a Shim
Document date:	2017-06-27
Group:		tsvwg
Pages:		16
URL:            https://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rfc6040update-shim-03.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc6040update-shim/
Htmlized:       https://tools.ietf.org/html/draft-ietf-tsvwg-rfc6040update-shim-03
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-rfc6040update-shim-03
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-rfc6040update-shim-03

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 updates RFC 6040 to clarify that its
    scope includes tunnels where two IP headers are separated by at least
    one shim header that is not sufficient on its own for wide area
    packet forwarding.  It surveys widely deployed IP tunnelling
    protocols separated by such shim header(s) and updates the
    specifications of those that do not mention ECN propagation (L2TPv2,
    L2TPv3, GRE and Teredo).  This specification also updates RFC 6040
    with configuration requirements needed to make any legacy tunnel
    ingress safe.

                                                                                   


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


--------------6A1261D435D710497D63773F
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    David (as doc shepherd),<br>
    <br>
    This is the 3rd revision in the last 2 months. This revision
    attempts to capture all the comments collected thanks to Carlos,
    Ignacio, Praveen, Joe and Alia. It would be useful to have a
    confirmation from each of you that I have addressed your concerns
    (or not). <br>
    <br>
    I have cross-posted all the lists potentially affected by this draft
    (intended proposed standard).<br>
    If you reply concerning a specific point, pls trim the distribution
    only to those interested/relevant.<br>
    <br>
    * tsvwg: owns updates to ECN <br>
    * int-area: owns mtce of many tunnelling protocols, particularly
    GRE?, Teredo? GUE<br>
    * l2tpext: owns mtce of L2TP<br>
    * opsawg: owns mtce of CAPWAP<br>
    * nvo3: currently defining Geneve, VXLAN-GPE<br>
    * sfc: currently defining NSH<br>
    <div class="moz-forward-container"><br>
    </div>
    From my point of view, this draft is now 'finished'. I.e. I am happy
    with it, and it is the first draft where all the ToDo's are done. I
    believe it is on track for the milestone of WGLC before the Nov'17
    IETF. As I understand it, WGLC will run in tsvwg and in parallel in
    int-area, l2tpext and perhaps opsawg.<br>
    <br>
    Main changes since -02:<br>
    <div class="moz-forward-container">* Completely restructured, with
      definitions of scope before even mentioning "tightly coupled shim
      headers", and new subsections where existing text on feasibility
      and desirability has been re-homed.<br>
      * Explanation of the safety problem, and the procedural problem
      this caused when previous ECN RFCs were written (an RFC cannot
      retrospectively set requirements on implementations, so we can
      only set operational requirements - configuration).<br>
      * Added NSH, but it doesn't seem to cover encapsulation.<br>
      * No longer categorized VXLAN-GPE as intended for standards track<br>
      * Added Teredo update text (for safety).<br>
      <br>
      Cheers<br>
      <br>
      <br>
      Bob<br>
      <br>
      -------- Forwarded Message --------
      <table class="moz-email-headers-table" cellspacing="0"
        cellpadding="0" border="0">
        <tbody>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Subject:
            </th>
            <td>New Version Notification for
              draft-ietf-tsvwg-rfc6040update-shim-03.txt</td>
          </tr>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Date: </th>
            <td>Tue, 27 Jun 2017 04:13:58 -0700</td>
          </tr>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">From: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a></td>
          </tr>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">To: </th>
            <td>Bob Briscoe <a class="moz-txt-link-rfc2396E" href="mailto:ietf@bobbriscoe.net">&lt;ietf@bobbriscoe.net&gt;</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <pre>A new version of I-D, draft-ietf-tsvwg-rfc6040update-shim-03.txt
has been successfully submitted by Bob Briscoe and posted to the
IETF repository.

Name:		draft-ietf-tsvwg-rfc6040update-shim
Revision:	03
Title:		Propagating Explicit Congestion Notification Across IP Tunnel Headers Separated by a Shim
Document date:	2017-06-27
Group:		tsvwg
Pages:		16
URL:            <a class="moz-txt-link-freetext" href="https://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rfc6040update-shim-03.txt">https://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rfc6040update-shim-03.txt</a>
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>
Htmlized:       <a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-ietf-tsvwg-rfc6040update-shim-03">https://tools.ietf.org/html/draft-ietf-tsvwg-rfc6040update-shim-03</a>
Htmlized:       <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-rfc6040update-shim-03">https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-rfc6040update-shim-03</a>
Diff:           <a class="moz-txt-link-freetext" href="https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-rfc6040update-shim-03">https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-rfc6040update-shim-03</a>

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 updates RFC 6040 to clarify that its
   scope includes tunnels where two IP headers are separated by at least
   one shim header that is not sufficient on its own for wide area
   packet forwarding.  It surveys widely deployed IP tunnelling
   protocols separated by such shim header(s) and updates the
   specifications of those that do not mention ECN propagation (L2TPv2,
   L2TPv3, GRE and Teredo).  This specification also updates RFC 6040
   with configuration requirements needed to make any legacy tunnel
   ingress safe.

                                                                                  


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

</pre>
    </div>
  </body>
</html>

--------------6A1261D435D710497D63773F--

