Re: [Gen-art] Genart telechat review of draft-ietf-6man-rfc1981bis-06

Fred Baker <fredbaker.ietf@gmail.com> Wed, 26 April 2017 20:08 UTC

Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5ABA12EB55; Wed, 26 Apr 2017 13:08:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Wxfv12-ExCL2; Wed, 26 Apr 2017 13:08:37 -0700 (PDT)
Received: from mail-wr0-x241.google.com (mail-wr0-x241.google.com [IPv6:2a00:1450:400c:c0c::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 925CB1294A9; Wed, 26 Apr 2017 13:08:31 -0700 (PDT)
Received: by mail-wr0-x241.google.com with SMTP id g12so1450040wrg.2; Wed, 26 Apr 2017 13:08:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Zjkl0qMkyaeqzgOEKMUFJke58SC/VxzeNgHcnRnjEp0=; b=Ai/urVsadKiIfFc6DOvBt563jFnPvN0xV4kTW14eAA5w2aoUYKHsG6UysZW6RCNdjl it9eBmgWpfqdumyzKJU0JnsdO8KVHkG/Fvx2KfLlF/mswmu4wU49XhznVKZOxrxwomKZ BfuT7/wcMR6G/0Gh2afvMzfyxhHbG3kDX1bWPSMc0WOn/85Tke6DCMqJxl4nxPe9wNHL VfTRcsr34/6g4fGKimDMCmunu13xs7SgTc5FVgbXyDQhT4FeR4x+pIDBRsWIP3kDrKT7 D7hOKIqRNqFts6NZReAKFujY8JuoPwaEq4z7sU1jYfA0krr391veCHWS3v4sArR2+KeZ RP7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Zjkl0qMkyaeqzgOEKMUFJke58SC/VxzeNgHcnRnjEp0=; b=Bju76Gica9+F0AH9R1ABK11P9S3Obf8C8krFHIUf+OZ1N16ZRjrKxA6t9vISWcBwdG s6voANOYt3ud3aUA/GqwQ5o/laI79Cawc9+6mDNtpkTi6vUZAxmK03ot01JRTRZ63uDv aj8deDH+dv7d7kHvvK65VLVJ5YMkUsWaCltSD2EqQ0OIAMn4OBr7JeM2aodc2PvQ+Eze wya0CbIadG5V0yvCX4KUos8t/8U77/NPz33O9q0+nptxs3bZgo2Zbsf/Bl/ycx/lqNR4 kAls4T8JpDfwi9sQkkdk4wrrGjC+rmt9eGiXcnQ4h7RahgTgFsRPPjy/112SkfNn9TeT TbnA==
X-Gm-Message-State: AN3rC/4usKrtpzWbHh1OPG4u9RO73sBHOmpCrVVux7TOqExoMs9FwICn AqOVQS3Yaw83CVoOSAM=
X-Received: by 10.223.154.240 with SMTP id a103mr1018926wrc.5.1493237310104; Wed, 26 Apr 2017 13:08:30 -0700 (PDT)
Received: from 202.66.20.149.in-addr.arpa (202.66.20.149.in-addr.arpa. [149.20.66.202]) by smtp.gmail.com with ESMTPSA id 39sm280734wru.50.2017.04.26.13.08.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Apr 2017 13:08:29 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <f6088ab8-3533-96f1-d9eb-f8462b1f4a1b@isi.edu>
Date: Wed, 26 Apr 2017 13:08:25 -0700
Cc: Stewart Bryant <stewart.bryant@gmail.com>, gen-art@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, draft-ietf-6man-rfc1981bis.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <99FD5A05-EDBE-4764-941C-C95BD689237B@gmail.com>
References: <149305392811.25808.15115824976388262628@ietfa.amsl.com> <497d3868-406a-a38f-56d8-391b0fc16032@isi.edu> <a974da1d-a9e7-8c64-8086-0955f2dffb12@gmail.com> <f6088ab8-3533-96f1-d9eb-f8462b1f4a1b@isi.edu>
To: Joe Touch <touch@isi.edu>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/0BGhFBnrAOUi2UNTvw5oQrsxFx0>
Subject: Re: [Gen-art] Genart telechat review of draft-ietf-6man-rfc1981bis-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 20:08:39 -0000

> On Apr 26, 2017, at 11:35 AM, Joe Touch <touch@isi.edu> wrote:
> 
> Hi, Stewart,
> 
> 
> On 4/26/2017 1:48 AM, Stewart Bryant wrote:
>> 
>> 
>> On 25/04/2017 19:26, Joe Touch wrote:
>>> Hi, Stewart,
>>> 
>>> ...
>>> 
>>>> SB>
>>>> SB> Otherwise I would have thought that this was entirely a matter
>>>> SB> for the host whether it wanted to use a Path MTU below the IPv6
>>>> SB> link minimum. Nothing breaks if the host takes a more conservative
>>>> SB> decision.
>>> I don't agree; the host at that point is violating RFC2460. It should
>>> never think that an IPv6 link or path with an MTU below what RFC2460
>>> requires is valid.
>>> 
>>> Joe
>>> 
>> 
>> That is as maybe, but a host can do more or less what it wants, so
>> this is surely an
>> unenforceable constraint, or are you telling me that the receiving
>> host MUST drop a
>> fragment that is shorter than this? In which case the question whether
>> in practice
>> they do, and whether such a constraint is reasonable.
> 
> A "path MTU" is a value calculated from information from various sources
> (attached links, ICMP messages, and perhaps other information), but IMO
> it's never appropriate to set a "path MTU" smaller than the limit
> established by IPv6 for a single link.

You are, of course, quoting RFC 1981:
   A node MUST NOT reduce its estimate of the Path MTU below the IPv6
   minimum link MTU.

> Individual packets and fragments can be smaller than the MTU, of course.
> Nothing forces fragments to push up against any MTU limit at all. But I
> would not describe that has a host changing its path MTU; it's just
> sending packets.

I disagree, both on the definition and the action. You are correct in "how the Path MTU is calculated". But the Path MTU, by definition, is the largest packet that can be sent end to end under current routing conditions. It is not, actually, an IP concept: it's a TCP concept if anything, or a transport layer concept (if UDP ever decides to have one). I can imagine TCP probing the Path MTU by trying packets that are larger than its current estimate to see if the estimate is still accurate (1981 section 4), but I can't imagine any reason that TCP would send packets larger than the "largest packet that can be sent end to end under current routing conditions" in the normal case, as those packets will by definition either be fragmented or not arrive.