Re: Validation of Packet Too Big Payload using Echo Request

神明達哉 <jinmei@wide.ad.jp> Thu, 30 January 2020 22:07 UTC

Return-Path: <jinmei.tatuya@gmail.com>
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 ED4A7120048 for <ipv6@ietfa.amsl.com>; Thu, 30 Jan 2020 14:07:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level:
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 2hbkYfU3r3AT for <ipv6@ietfa.amsl.com>; Thu, 30 Jan 2020 14:07:52 -0800 (PST)
Received: from mail-wr1-f46.google.com (mail-wr1-f46.google.com [209.85.221.46]) (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 BC74612009C for <6man@ietf.org>; Thu, 30 Jan 2020 14:07:51 -0800 (PST)
Received: by mail-wr1-f46.google.com with SMTP id w15so6122064wru.4 for <6man@ietf.org>; Thu, 30 Jan 2020 14:07:51 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=DkR+LkRXghiD25qWN2RmWUaBCIQ115dfE+o88IJVBeY=; b=ZZ99pS5A3Nah7od6WYwUZua2kzN7ghrBjwKGW2XzJLpYwIj8iVGLn86MOYXQ1QHjyz TMxr5jelap5oYmboFRy1agjwMM/lCPxBqOdY/8qjDH5J6yBI7xEzZ30Fx7fgcKF0uw2h LbQ0jjDxfonvuefpc7skFKUw/5r2Iqcfp7F79SCA+IUomMH9+G2C1lmjr4AxVKZbLJxR ibd6P2FsIenVrz/IJU1Y5ZEgtW9MtyrTbWOZAMC4NaXcLQVbFjbJw8Ht52ZGYNYW1m0e 20PPFjFjOzvgcq+Hj6NZ5u4z/0okn+1eM/VtSkvXeudVe6x/WnA09ABxZ56bW+1AkJ5c Fq6Q==
X-Gm-Message-State: APjAAAUpRGkN4QLVVEHRCivJFgHEl632UrMlLBklCfT16QV0+4GjxBgt S5jA5aAB7sW3KAFWfT97svjCrn90Vu2CsxNTYxY=
X-Google-Smtp-Source: APXvYqxogDuxT4cpI11MhY3M43YLLP+r8olq04E7jcsKrYyzZHnBBY1P9ZbLVkiomkyGgaaVOFPziGm6Z+rsxB2gf0U=
X-Received: by 2002:a5d:6ac3:: with SMTP id u3mr8263196wrw.25.1580422070015; Thu, 30 Jan 2020 14:07:50 -0800 (PST)
MIME-Version: 1.0
References: <CAOSSMjVzTmCRxLg8k+9t+j0u9iMMWa+T_8P7kVRKGLkiup_jDw@mail.gmail.com> <F9ACCBEA-D009-48BF-B2F6-7179C0DDCB2A@gmail.com>
In-Reply-To: <F9ACCBEA-D009-48BF-B2F6-7179C0DDCB2A@gmail.com>
From: 神明達哉 <jinmei@wide.ad.jp>
Date: Thu, 30 Jan 2020 14:07:38 -0800
Message-ID: <CAJE_bqeFO4hwJZaa_ChiEwP_zxdiaVS3QmoBAV3NFPNcwCWi_g@mail.gmail.com>
Subject: Re: Validation of Packet Too Big Payload using Echo Request
To: Fred Baker <fredbaker.ietf@gmail.com>
Cc: Timothy Winters <twinters@iol.unh.edu>, 6MAN <6man@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/xJ2d9lrT9MBkTYh-DzRb0Gz-H5s>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 30 Jan 2020 22:07:53 -0000

At Mon, 27 Jan 2020 11:39:58 -0800,
Fred Baker <fredbaker.ietf@gmail.com> wrote:

> PTB and PMTU activates in IPv4 applies to streams of packets, not
> sessions. Given that IPv6 operates from the same definitions, I
> don't see why it would be applied to something different in IPv6.

> Now, in fairness, TCP has a way to address PTB/PMTU - it changes the
> MSS in use for a session. UDP doesn't have anything so clear. But
> IMNSHO, that is a deficiency in UDP, not in ICMP. UDP, or the
> process using it, is informed of the limitation. It fails to act on
> it.

We can still fragment the subsequent UDP packets at the known PMTU (I
know everyone hates IP fragmentation but that's a different topic).
In my understanding PMTUD work less well with UDP application than TCP
apps because UDP apps tend to be "connectionless" (e.g. using
non-connected UDP sockets) and the OS's ICMP layer often doesn't like
to adjust its behavior upon receiving a packet too big error when it
cannot find an application that matches the src-dst pair specified in
the ICMP error (which is not the case for connectionless UDP apps).

BTW, RFC3542 provides a way to let UDP apps (even connectionless ones)
know the change of the path MTU that may affect those applications,
although I suspect RFC3542 in general, let alone this particular
option, is not so widely implemented.

Maybe an offtopic for this thread anyway, though.

--
JINMEI, Tatuya