Re: [tsvwg] Revised ID: draft-ietf-tsvwg-datagram-plpmtud-16.txt

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Mon, 09 March 2020 16:13 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 B2CC23A0D08; Mon, 9 Mar 2020 09:13:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] 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 I2E0ZNhX8RWW; Mon, 9 Mar 2020 09:13:14 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id 1A2F13A12C3; Mon, 9 Mar 2020 09:13:13 -0700 (PDT)
Received: from GF-MacBook-Pro.local (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 2085B1B001B7; Mon, 9 Mar 2020 16:13:08 +0000 (GMT)
To: tsvwg@ietf.org, secdir@ietf.org
References: <158376420248.14208.2438240270562621574@ietfa.amsl.com>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Message-ID: <c9bc0e9b-054f-e8be-2106-30db1522628d@erg.abdn.ac.uk>
Date: Mon, 9 Mar 2020 16:13:07 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <158376420248.14208.2438240270562621574@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/a0YQp8TEQgRwN5e18V3jjHNnpEs>
Subject: Re: [tsvwg] Revised ID: draft-ietf-tsvwg-datagram-plpmtud-16.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 09 Mar 2020 16:13:18 -0000

This revision follows the issues raised by the IETF Last Call SECDIR 
Review (of draft-15). We think this will address all the 
security-related issues that were noted. (It also addresses one case of 
repetition that was found.)

Gorry, et al

(DPLPMTUD editors)

On 09/03/2020 14:30, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Transport Area Working Group WG of the IETF.
>
>          Title           : Packetization Layer Path MTU Discovery for Datagram Transports
>          Authors         : Godred Fairhurst
>                            Tom Jones
>                            Michael Tuexen
>                            Irene Ruengeler
>                            Timo Voelker
> 	Filename        : draft-ietf-tsvwg-datagram-plpmtud-16.txt
> 	Pages           : 44
> 	Date            : 2020-03-09
>
> Abstract:
>     This document describes a robust method for Path MTU Discovery
>     (PMTUD) for datagram Packetization Layers (PLs).  It describes an
>     extension to RFC 1191 and RFC 8201, which specifies ICMP-based Path
>     MTU Discovery for IPv4 and IPv6.  The method allows a PL, or a
>     datagram application that uses a PL, to discover whether a network
>     path can support the current size of datagram.  This can be used to
>     detect and reduce the message size when a sender encounters a packet
>     black hole (where packets are discarded).  The method can probe a
>     network path with progressively larger packets to discover whether
>     the maximum packet size can be increased.  This allows a sender to
>     determine an appropriate packet size, providing functionality for
>     datagram transports that is equivalent to the Packetization Layer
>     PMTUD specification for TCP, specified in RFC 4821.
>
>     The document updates RFC 4821 to specify the method for datagram PLs,
>     and updates RFC 8085 as the method to use in place of RFC 4821 with
>     UDP datagrams.  Section 7.3 of RFC4960 recommends an endpoint apply
>     the techniques in RFC 4821 on a per-destination-address basis.  RFC
>     4960, RFC 6951 and RFC 8261 are updated to recommend that SCTP, SCTP
>     encapsulated in UDP and SCTP encapsulated in DTLS use the method
>     specified in this document instead of the method in RFC 4821.
>
>     The document also provides implementation notes for incorporating
>     Datagram PMTUD into IETF datagram transports or applications that use
>     datagram transports.
>
>     When published, this specification updates RFC 4960, RFC 4821, RFC
>     8085 and RFC 8261.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-datagram-plpmtud/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-tsvwg-datagram-plpmtud-16
> https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-datagram-plpmtud-16
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-datagram-plpmtud-16
>
>
> 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.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>