Re: [Int-area] New draft to update L2TP, GRE, PPTP, GTP & VXLAN, etc. for ECN
"Carlos Pignataro (cpignata)" <cpignata@cisco.com> Fri, 08 July 2016 19:32 UTC
Return-Path: <cpignata@cisco.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 863ED12D16F; Fri, 8 Jul 2016 12:32:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level:
X-Spam-Status: No, score=-15.947 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=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HkHEfBXbazcn; Fri, 8 Jul 2016 12:32:50 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BF5112D528; Fri, 8 Jul 2016 12:32:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5388; q=dns/txt; s=iport; t=1468006370; x=1469215970; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=2laFoiKNA5kxQFg9IxqLUvp12f+KJI/RfLdyVV+hwy4=; b=VT7Zqq/jTxDKYDCaDJsQCQnef901l8GQeccDnx/Kv+JJlbRfLoXXiSqi fyNsUwEHVXYBp2S3HgQifPrbqvawMyvkQW87wfXN+G30zQcLtue+kk+DK wA/kEdb4N3gARxBZtZR+Gq0LoufOCqyatwuK7agUPw7uDyakCpmQIDxJM Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D/AQDu/n9X/5NdJa1cgz5WfAa5DIF7JIV0AhyBDDgUAQEBAQEBAWUnhEwBAQQBAQEhEToLBQsCAQgOCgICJgICAiULFRACBA4FiCgIDq56jyYBAQEBAQEBAQEBAQEBAQEBAQEBAQEcgQGFJoF4glWEQReCaiuCLwWOBIsQAYYLiEOBak6ECohqhlqJMwEeNoNxbgGIMn8BAQE
X-IronPort-AV: E=Sophos;i="5.28,331,1464652800"; d="scan'208";a="294774305"
Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Jul 2016 19:32:49 +0000
Received: from XCH-RTP-018.cisco.com (xch-rtp-018.cisco.com [64.101.220.158]) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id u68JWm6a013934 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 8 Jul 2016 19:32:49 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-018.cisco.com (64.101.220.158) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 8 Jul 2016 15:32:48 -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; Fri, 8 Jul 2016 15:32:48 -0400
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Bob Briscoe <ietf@bobbriscoe.net>
Thread-Topic: [Int-area] New draft to update L2TP, GRE, PPTP, GTP & VXLAN, etc. for ECN
Thread-Index: AQHR2RLWrqhogHBgPEuzHPcPIVpV8qAPL+uA
Date: Fri, 08 Jul 2016 19:32:48 +0000
Message-ID: <F166D944-9CC9-4E93-A471-A22A5C581A01@cisco.com>
References: <20160708114131.32189.93751.idtracker@ietfa.amsl.com> <577F9A07.2060906@bobbriscoe.net>
In-Reply-To: <577F9A07.2060906@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.53]
Content-Type: text/plain; charset="utf-8"
Content-ID: <13C572E27A29294894AA12FCA4BFF818@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/bDUIPfjgtFTHj9TD4O3MgG8blcQ>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, intarea IETF list <int-area@ietf.org>, tsvwg IETF list <tsvwg@ietf.org>
Subject: Re: [Int-area] New draft to update L2TP, GRE, PPTP, GTP & VXLAN, etc. for ECN
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jul 2016 19:32:52 -0000
Bob, When you say L2TP, do you mean only L2TPv2 [RFC 2661] as in the I-D, or also L2TPv3 [RFC 3931]? (I think should be both). One additional point of clarification — the draft says: This specification therefore updates the following specifications of tightly coupled shim headers by adding that RFC 6040 SHOULD apply when the shim header is used between IP headers: However, some of the listed tunneling technologies include additional encapsulations between the shim and the inner IP. Those are not part of the shim header per se. For example, IP | GRE | Ethernet | IP. Same for VXLAN. There’s PPP for L2TP, etc. The draft scope says: In many cases the shim header(s) and the outer IP header are always added (or removed) as part of the same process. We call this a tightly coupled shim header. It might be beneficial to tighten the scope to more definitively spec if it is IP | shim | something | IP, for “something” being non-null. However, Thanks, — Carlos. > On Jul 8, 2016, at 8:18 AM, Bob Briscoe <ietf@bobbriscoe.net> wrote: > > tsvwg, intarea, and respective co-chairs, > [re-sent with hyphen in int-area@] > > I have posted a new very brief draft (under 2 pages not incl. boilerplate), intended for standards track as a bis to RFC6040. > As suggested in Buenos Aires, this has been extracted from draft-ietf-tsvwg-ecn-encap-guidelines, to cut all the clutter and highlight solely the standards track stuff. > > Propagating Explicit Congestion Notification Across IP Tunnel Headers Separated by a Shim > https://tools.ietf.org/html/draft-briscoe-tsvwg-rfc6040bis-00 > > If approved, it is intended to update L2TP, GRE, PPTP, GTP & VXLAN. > Obviously the IETF does not control GTP - see text for how 3GPP might use this spec. > Simialrly, given VXLAN is informational, it's perhaps not appropriate to update it - exactly how this is worded is for discussion. > > For IETF-96, I've asked for a slot in intarea to explain, and I also hope to cover this in an ecn-encap-guidelines slot in tsvwg. > > I'd appreciate help identifying more tunnelling protocols that follow the pattern of a shim sandwiched between two IP headers. > Since posting, I've looked at Joe's Tunnelling draft and realised I missed out Geneve and GUE. More? > > Cheers > > > Bob > > On 08/07/16 12:41, internet-drafts@ietf.org wrote: >> A new version of I-D, draft-briscoe-tsvwg-rfc6040bis-00.txt >> has been successfully submitted by Bob Briscoe and posted to the >> IETF repository. >> >> Name: draft-briscoe-tsvwg-rfc6040bis >> Revision: 00 >> Title: Propagating Explicit Congestion Notification Across IP Tunnel Headers Separated by a Shim >> Document date: 2016-07-08 >> Group: Individual Submission >> Pages: 5 >> URL: https://www.ietf.org/internet-drafts/draft-briscoe-tsvwg-rfc6040bis-00.txt >> Status: https://datatracker.ietf.org/doc/draft-briscoe-tsvwg-rfc6040bis/ >> Htmlized: https://tools.ietf.org/html/draft-briscoe-tsvwg-rfc6040bis-00 >> >> >> 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 a shim header that >> cannot stand alone. >> >> >> >> >> Please note that it may take a couple of minutes from the time of submission >> until the htmlized version and diff are available at tools.ietf.org. >> >> The IETF Secretariat >> > > -- > ________________________________________________________________ > Bob Briscoe http://bobbriscoe.net/ > > _______________________________________________ > Int-area mailing list > Int-area@ietf.org > https://www.ietf.org/mailman/listinfo/int-area
- Re: [Int-area] New draft to update L2TP, GRE, PPT… Carlos Pignataro (cpignata)
- Re: [Int-area] [tsvwg] New draft to update L2TP, … Bob Briscoe
- Re: [Int-area] New draft to update L2TP, GRE, PPT… Bob Briscoe
- Re: [Int-area] New draft to update L2TP, GRE, PPT… Carlos Pignataro (cpignata)
- [Int-area] New draft to update L2TP, GRE, PPTP, G… Bob Briscoe
- Re: [Int-area] [tsvwg] New draft to update L2TP, … Carlos Pignataro (cpignata)