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

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Wed, 10 January 2018 15:33 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FF1812D7F3 for <tsvwg@ietfa.amsl.com>; Wed, 10 Jan 2018 07:33:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zhb6rTKIKHAx for <tsvwg@ietfa.amsl.com>; Wed, 10 Jan 2018 07:33:06 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id F416A12751F for <tsvwg@ietf.org>; Wed, 10 Jan 2018 07:33:05 -0800 (PST)
Received: from Gs-MacBook-Pro.local (at-zeroshell-1.erg.abdn.ac.uk [139.133.217.68]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id ADA031B00237 for <tsvwg@ietf.org>; Wed, 10 Jan 2018 15:32:33 +0000 (GMT)
Message-ID: <5A563210.3050605@erg.abdn.ac.uk>
Date: Wed, 10 Jan 2018 15:32:32 +0000
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Reply-To: gorry@erg.abdn.ac.uk
Organization: University of Aberdeen
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: tsvwg@ietf.org
References: <CE03DB3D7B45C245BCA0D243277949362FE164EB@MX307CL04.corp.emc.com> <9837331A-76DF-4137-9612-CC653E869553@netapp.com> <20180110141644.GA70621@accordion.employees.org>
In-Reply-To: <20180110141644.GA70621@accordion.employees.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/Dw-SG2wpAyESMcH-iJYYnAfVxp4>
Subject: Re: [tsvwg] Adoption call: draft-fairhurst-tsvwg-datagram-plpmtud-02 to end 10th January 2018
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jan 2018 15:33:08 -0000

On 10/01/2018, 14:16, Derek Fawcus wrote:
> On Tue, Jan 09, 2018 at 11:11:35AM +0000, Eggert, Lars wrote:
>> 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.
> Similarly in section 1 (para 1&  9) mention is made of its applicability to DCCP,
> but then nothing is mentioned about it subsequently.
>
> Should this document also cover the details for DCCP at the same level as for UDP?
>
> DF

The DCCP Spec includes content on PMTUD, therefore it's not quite the 
same case as UDP, but the concepts of probing coild be applicable - 
although I do not know of any DCCP implementation that considered PMTUD. 
I'd be happy to thinkl about inputs from people using DCCP - speak up if 
there are key issues that you're experiencing with PMTU discovery and 
DCCP or with DCCP/UDP.

Gorry