Re: Validation of Packet Too Big Payload using Echo Request

Ole Troan <otroan@employees.org> Tue, 28 January 2020 13:58 UTC

Return-Path: <otroan@employees.org>
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 DE05D1200D7 for <ipv6@ietfa.amsl.com>; Tue, 28 Jan 2020 05:58:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 QVzZdZWCb-xt for <ipv6@ietfa.amsl.com>; Tue, 28 Jan 2020 05:58:09 -0800 (PST)
Received: from clarinet.employees.org (clarinet.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB2A21200BA for <6man@ietf.org>; Tue, 28 Jan 2020 05:58:09 -0800 (PST)
Received: from [IPv6:2a02:2121:2c3:638a:b04a:44de:a6e4:ba8d] (unknown [IPv6:2a02:2121:2c3:638a:b04a:44de:a6e4:ba8d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by clarinet.employees.org (Postfix) with ESMTPSA id 3A67E4E11B6C; Tue, 28 Jan 2020 13:58:07 +0000 (UTC)
Content-Type: multipart/alternative; boundary="Apple-Mail-722CC6FD-255C-453C-8D69-756FD99053CD"
Content-Transfer-Encoding: 7bit
From: Ole Troan <otroan@employees.org>
Mime-Version: 1.0 (1.0)
Subject: Re: Validation of Packet Too Big Payload using Echo Request
Date: Tue, 28 Jan 2020 14:58:04 +0100
Message-Id: <8EA75E98-1B2C-4608-88B8-72428328FB55@employees.org>
References: <CAOSSMjXdiurDTQgFF6=616ZOxUeRvBXeq_33M1zFebEUt6rjMw@mail.gmail.com>
Cc: 6MAN <6man@ietf.org>
In-Reply-To: <CAOSSMjXdiurDTQgFF6=616ZOxUeRvBXeq_33M1zFebEUt6rjMw@mail.gmail.com>
To: Timothy Winters <twinters@iol.unh.edu>
X-Mailer: iPhone Mail (17D5026c)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/EoqfTLYobSdD8hafX_eLBo5QmeU>
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: Tue, 28 Jan 2020 13:58:11 -0000


> On 28 Jan 2020, at 14:39, Timothy Winters <twinters@iol.unh.edu> wrote:
> 
>> 
>> RFC8201 is a network layer mechanism, and the paragraph above applies to all packets sent by the node. Regardless of transport layer protocol.
> Thanks for the replies that's my opinion as well.  We'll leave it as documented.

Then we can argue of course argue over how easy this is to implement in the different cases...

Cheers 
Ole