Re: [tsvwg] Adoption call: draft-fairhurst-tsvwg-datagram-plpmtud-02 to end 10th January 2018

"Eggert, Lars" <lars@netapp.com> Tue, 09 January 2018 11:11 UTC

Return-Path: <lars@netapp.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D06CB126C83; Tue, 9 Jan 2018 03:11:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netapp.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 GvDZObjPW2Og; Tue, 9 Jan 2018 03:11:39 -0800 (PST)
Received: from mx144.netapp.com (mx144.netapp.com [IPv6:2620:10a:4005:8000:2306::d]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EAF2E1250B8; Tue, 9 Jan 2018 03:11:38 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.46,335,1511856000"; d="asc'?scan'208,217";a="235566614"
Received: from vmwexchts01-prd.hq.netapp.com ([10.122.105.12]) by mx144-out.netapp.com with ESMTP; 09 Jan 2018 03:11:37 -0800
Received: from VMWEXCCAS04-PRD.hq.netapp.com (10.122.105.20) by VMWEXCHTS01-PRD.hq.netapp.com (10.122.105.12) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 9 Jan 2018 03:11:37 -0800
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (10.120.60.153) by VMWEXCCAS04-PRD.hq.netapp.com (10.122.105.20) with Microsoft SMTP Server (TLS) id 15.0.1320.4 via Frontend Transport; Tue, 9 Jan 2018 03:11:37 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netapp.onmicrosoft.com; s=selector1-netapp-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=WltuNfnOLppHJLSHd58+VJ2PeZvkmJcTo4ML+pdP7qU=; b=Z1iUJHIpN2/eqVyeXPzKr99Ql1oZaEptjMYT9t319JuhQmp2fXd+Stm1bGsRmjWbz1meWaNWfMpMs+y+dVbEKJvuwoHZDXimNQFIMs+N2QnTt1tGfOunr0MDwhs1aLEzk18DbCwVjeXI3inJ4spDGOrGBhxlA8ORCsAQ8SfneRA=
Received: from BLUPR06MB1764.namprd06.prod.outlook.com (10.162.224.150) by BLUPR06MB1762.namprd06.prod.outlook.com (10.162.224.148) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.386.5; Tue, 9 Jan 2018 11:11:35 +0000
Received: from BLUPR06MB1764.namprd06.prod.outlook.com ([10.162.224.150]) by BLUPR06MB1764.namprd06.prod.outlook.com ([10.162.224.150]) with mapi id 15.20.0386.008; Tue, 9 Jan 2018 11:11:35 +0000
From: "Eggert, Lars" <lars@netapp.com>
To: "Black, David" <David.Black@dell.com>
CC: "tsvwg@ietf.org" <tsvwg@ietf.org>, QUIC WG <quic@ietf.org>
Subject: Re: [tsvwg] Adoption call: draft-fairhurst-tsvwg-datagram-plpmtud-02 to end 10th January 2018
Thread-Topic: [tsvwg] Adoption call: draft-fairhurst-tsvwg-datagram-plpmtud-02 to end 10th January 2018
Thread-Index: AdN1GcwEk8+6wIkTQ1++dedJ90kdDwUIM6oA
Date: Tue, 9 Jan 2018 11:11:35 +0000
Message-ID: <9837331A-76DF-4137-9612-CC653E869553@netapp.com>
References: <CE03DB3D7B45C245BCA0D243277949362FE164EB@MX307CL04.corp.emc.com>
In-Reply-To: <CE03DB3D7B45C245BCA0D243277949362FE164EB@MX307CL04.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3445.5.20)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=lars@netapp.com;
x-originating-ip: [203.168.52.212]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BLUPR06MB1762; 7:A7gwB3kbWWJiOrjcsz2crcDIOOb3oEpdip4rJavhVpJ0d68qGNJavXSAH2CXTuieydTdtF9WAFBqmbUr27quUN+ViqE/w0PSngfAUG67cLK8vtG/Lcgg3WNWFxVwnBXLj0jaPedernELKVRqWCpaeL+VbP44lwgTxUyjAOGAnvcJOPjzZGegHXTWAqgfRhhLtO8ZaRmMIQuOmO5k5adW5R1R/uW2zcnhA8OBEHPp3AAbAJzlLahaeZ4BtsLCmt6i
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 73fc2416-1d53-42b2-d2e4-08d55751bf20
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(5600026)(4604075)(3008032)(2017052603307)(49563074)(7193020); SRVR:BLUPR06MB1762;
x-ms-traffictypediagnostic: BLUPR06MB1762:
x-microsoft-antispam-prvs: <BLUPR06MB1762FDEAC9ABC75AF4127FFEA7100@BLUPR06MB1762.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(56004941905204);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(102415395)(6040470)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3002001)(3231023)(944501075)(6055026)(6041268)(20161123558120)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123564045)(6072148)(201708071742011); SRVR:BLUPR06MB1762; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:BLUPR06MB1762;
x-forefront-prvs: 0547116B72
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(39380400002)(366004)(346002)(396003)(39860400002)(24454002)(377424004)(199004)(189003)(54906003)(3660700001)(5660300001)(8936002)(53546011)(106356001)(66066001)(6436002)(50226002)(33656002)(105586002)(229853002)(478600001)(102836004)(14454004)(4001150100001)(68736007)(76176011)(3280700002)(77096006)(6486002)(53936002)(97736004)(6506007)(8676002)(8666007)(81156014)(81166006)(99286004)(7736002)(36756003)(236005)(6246003)(54896002)(6512007)(3846002)(230783001)(6116002)(2950100002)(99936001)(86362001)(2900100001)(2906002)(316002)(25786009)(83716003)(6916009)(57306001)(82746002)(4326008); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR06MB1762; H:BLUPR06MB1764.namprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: netapp.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: rRIlvmGT2Uzx64nf5bzeQoWUjKdG8g+0K4dpP/685PsF9ANVy7HyzMDF0QgjNURscm1++PNolTourmQykUnwqQ==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; boundary="Apple-Mail=_28AA2C8F-9ABF-434C-9A82-878B6E4A2EBC"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 73fc2416-1d53-42b2-d2e4-08d55751bf20
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Jan 2018 11:11:35.1016 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4b0911a0-929b-4715-944b-c03745165b3a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR06MB1762
X-OriginatorOrg: netapp.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/avvzkSPqeYrd3ywMe9kBhu4vdPM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jan 2018 11:11:41 -0000

Hi,

would someone clarify what the intended relationship of the mechanism described in the document and QUIC is? For example, is the intention here that QUIC should implement this,  is this unrelated, or anything in between?

Asking, because if there is an intended relationship, it would be good to discuss this sooner rather than later.

Thanks,
Lars

> On 2017-12-15, at 7:27, Black, David <David.Black@dell.com> wrote:
> 
> I’m tardy in getting to this action item from the TSVWG meeting in Singapore …
> 
> The TSVWG chairs are considering adoption of the draft
> "Packetization Layer Path MTU Discovery for Datagram Transports".
> 
> This draft has been discussed at the previous IETF meeting and on the list, and the chairs are now looking for input from the group to help inform whether TSVWG should adopt this draft.
> 
> * Please send an email to this list if you would like to see this work adopted in TSVWG, or you have comments on the suitability for adoption.
> 
> * Please indicate if you are willing to REVIEW such a document during its development.
> 
> Please send all notes of support/comments to the TSVWG list or the WG chairs by the date above.
> 
> Best wishes,
> 
> David and Wes.
> (TSVWG Co-Chairs) [Gorry is recused from this adoption decision, as he is an author of this draft.]
> [The time period for this adoption call is longer than usual to allow for the winter holidays – may yours be joyous!]
> 
> Abstract
> 
>    This document describes a robust method for Path MTU Discovery
>    (PMTUD) for datagram Packetization layers.  The method allows a
>    Packetization layer (or a datagram application that uses it) to probe
>    an network path with progressively larger packets to determine a
>    maximum packet size.  The document describes as an extension to RFC
>    1191 and RFC 8201, which specify ICMP-based Path MTU Discovery for
>    IPv4 and IPv6.  This provides functionally for datagram transports
>    that is equivalent to the Packetization layer PMTUD specification for
>    TCP, specified in RFC4821.