Re: DISCUSS's on rfc1981bis - MK Comments

"Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net> Mon, 22 May 2017 09:49 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8AFB127735 for <ipv6@ietfa.amsl.com>; Mon, 22 May 2017 02:49:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.698
X-Spam-Level:
X-Spam-Status: No, score=0.698 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.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 AFOKVn18uLMH for <ipv6@ietfa.amsl.com>; Mon, 22 May 2017 02:49:40 -0700 (PDT)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8356128D44 for <ipv6@ietfa.amsl.com>; Mon, 22 May 2017 02:49:39 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net; b=j2eb8wez+0E+FepvIfqYQiM20CSlAyFYnUB26Zzv9+rcVkWJjFCh9tDo6o/6U8s8btEGNHTkrLCJoCzI0Ed2DNmH0JVstc0QFxlANvocWPkZdWysX4gndwmU40mvi5RRRsviYO3l/0q4Y7r6Yza76ePqhkygQMdLkl1tOtlHgDk=; h=Received:Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-PPP-Message-ID:X-PPP-Vhost;
Received: (qmail 27848 invoked from network); 22 May 2017 11:49:37 +0200
Received: from pd9e110d0.dip0.t-ipconnect.de (HELO ?192.168.178.33?) (217.225.16.208) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 22 May 2017 11:49:37 +0200
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: DISCUSS's on rfc1981bis - MK Comments
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <59205C94.30200@erg.abdn.ac.uk>
Date: Mon, 22 May 2017 11:49:36 +0200
Cc: ipv6@ietfa.amsl.com
Content-Transfer-Encoding: quoted-printable
Message-Id: <52A24ADC-8D1D-47DA-ADC8-21D30C09D49E@kuehlewind.net>
References: <FF803F19-4253-4422-AFA5-B99A8894BD83@gmail.com> <5911B0EE.6080802@erg.abdn.ac.uk> <EC313F56-0193-4510-9CCB-4AEF85F3E590@kuehlewind.net> <59205C94.30200@erg.abdn.ac.uk>
To: gorry@erg.abdn.ac.uk
X-Mailer: Apple Mail (2.3273)
X-PPP-Message-ID: <20170522094937.27843.60152@lvps83-169-45-111.dedicated.hosteurope.de>
X-PPP-Vhost: kuehlewind.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/9YtRw05z-598VvWnQ1dkL1irDQw>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 May 2017 09:49:42 -0000

See below.


> Am 20.05.2017 um 17:11 schrieb Gorry Fairhurst <gorry@erg.abdn.ac.uk>:
> 
> On 19/05/2017, 15:51, Mirja Kuehlewind (IETF) wrote:
>> Hi Gorry, hi all,
>> 
>> thanks for the work and the update. All comments from Gorry seemed fine to me and I will try to review the changes in the updated doc soon. One more minor comment on this:
>> 
>>> Am 09.05.2017 um 08:07 schrieb Gorry Fairhurst<gorry@erg.abdn.ac.uk>:
>>> 
>>>> I don't understand the following paragraph. Can this be removed?
>>>> "Note: A packetization layer must not retransmit in response to
>>>> every Packet Too Big message, since a burst of several oversized
>>>> segments will give rise to several such messages and hence several
>>>> retransmissions of the same data. If the new estimated PMTU is
>>>> still wrong, the process repeats, and there is an exponential
>>>> growth in the number of superfluous segments sent."
>>>> 
>>> GF: I think the example is important. I'm not sure why that would be removed.
>> The problem is I don’t understand this example. Is there an assumption that all mtu probe packets have been ‚generated‘ on the same packet? If so that makes sense but must the spelled out somewhere!
>> 
>> Mirja
>> 
>> 
> I think the wording is maybe jumbled, but the point is OK. Perhaps something like this would be clearer?
> 
> "Note: A packetization layer ought to avoid retransmitting the data in a probe packet
> using the size reported in the last Packet Too Big message.
> This is to avoid an exponential growth in the number of superfluous segments
> that would be sent when a path encounters several successive smaller PMTU limits.
> (Each new estimated PMTU would result in retransmission of the data in a smaller
> packet that may itself fail if it encounters a still smaller PMTU in a device further
> along the same path)."
> 
> Gorry
> 
I still don’t get it. Each time a packet is dropped, you have to retransmit it (if your transport is reliable) because otherwise the other end will not have it. I also still don’t see how there can be an exponential grows. Sorry if I miss something but maybe you can explain again this case using different words…?

Mirja