Re: IPv6 payload length check?

Erik Kline <ek.ietf@gmail.com> Mon, 03 February 2020 22:05 UTC

Return-Path: <ek.ietf@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 099AC120236 for <ipv6@ietfa.amsl.com>; Mon, 3 Feb 2020 14:05:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 ju-vyDiViJbM for <ipv6@ietfa.amsl.com>; Mon, 3 Feb 2020 14:05:53 -0800 (PST)
Received: from mail-oi1-x231.google.com (mail-oi1-x231.google.com [IPv6:2607:f8b0:4864:20::231]) (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 4793B12082F for <ipv6@ietf.org>; Mon, 3 Feb 2020 14:05:53 -0800 (PST)
Received: by mail-oi1-x231.google.com with SMTP id j132so16335902oih.9 for <ipv6@ietf.org>; Mon, 03 Feb 2020 14:05:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fRD2u4SgNEwI5qE6Vcmk8d4DKWzUvgAJvycNjvRofb4=; b=Khb814V5vDVTLO18HqDp5AIyztbGc8/p7fM8xHwtyGb/kvba5AFAYlPx1R9zpGvsBO s2MV1iUsUQe4NekXXP8g3qq0Szvc0vXjFkenCwutQeXvFP3BaWsSYecRZIHJ0Y6s35Fr FihCUMPXombC0ewg8MV1xxZmHWEq+MlC3Y7w2g38qlPfdkJSYzja6VFSNNt7qJTOicrV r1GgI8e4ZbfBPWQkVV90UkYTSz036RKglzoSd3f4Qkr9KpwXPEfNhtpzFDtafXdKLpHf penQYeseqFzGXnFcNpUHDe0W5+smvLzvn/Nqcynd56QU+rDopG8K2mfDLWgPZCo9ws0Z aZVw==
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=fRD2u4SgNEwI5qE6Vcmk8d4DKWzUvgAJvycNjvRofb4=; b=KYtAi4APbuJNc0AUiT2Yp7cGf0qtxO9mJrsbrXi2UnNibCkUZNDc1Hh89RRLvdkBGm 7M2DT2H+U1sUhMjF5gdd3XTe2AXYi2mQd8ASeXui0CgINu8/2qhoN4LjpT5gu3qkxgre NTLSZZpwAdhzAPEAbTlgvN3xtamU40oCLH+2++fh7WLcXof16kX/c5IGFcuosB1c+b3Q Od+na8pLsISerOAtlqofkIbPZOef1bjAm3fd9amk/AdQOtptw4n39xMgdbZrdKwVCiaW A4dGjYE4w2kY6QzNIuWUAzDbtIWuxBtuSXoqLz8iGjln1lRPPeOUVArKYN0EbDXvQBu2 pUCA==
X-Gm-Message-State: APjAAAU9FBkzeZSGImAkNqrZ6W+VkmE1l1g8HhorGoN02XAyftXpNctI Zn8LkMwde2KYNXbDAQ0nPgzgVmzBn+qas83ko9Nc1ZXo
X-Google-Smtp-Source: APXvYqxHPZI8Fzqm6PyP2NrVYhc78IrzeeuE0mk4YxKVeAK/gcwjRDWvsML3RE9hN39nYcorairdHm1EWSgIxEcwN+Y=
X-Received: by 2002:aca:318f:: with SMTP id x137mr904261oix.100.1580767552704; Mon, 03 Feb 2020 14:05:52 -0800 (PST)
MIME-Version: 1.0
References: <90342768-7f25-b9dd-eeae-29db6045b40a@intl.att.com> <77f55628-6f9d-d06a-4e38-f84d76e716bb@intl.att.com>
In-Reply-To: <77f55628-6f9d-d06a-4e38-f84d76e716bb@intl.att.com>
From: Erik Kline <ek.ietf@gmail.com>
Date: Mon, 03 Feb 2020 14:05:42 -0800
Message-ID: <CAMGpriWVN0EGLz5PyeyL5LTo_+A1i+xHCD6kw0E0pCRCcGcY2g@mail.gmail.com>
Subject: Re: IPv6 payload length check?
To: "Aitken, Paul" <paul.aitken@intl.att.com>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000073987d059db3205d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/EQ9J9bqzoNL2XVDmZmC4-Mmck0I>
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: Mon, 03 Feb 2020 22:05:55 -0000

Interestingly, 8200 contains this text in the Routing Header section (4.4):

"""
   If, after processing a Routing header of a received packet, an
   intermediate node determines that the packet is to be forwarded onto
   a link whose link MTU is less than the size of the packet, the node
   must discard the packet and send an ICMP Packet Too Big message to
   the packet's Source Address.
"""

Really that text would seem to apply even if a routing header is absent.
4443 on PTBs (3.2) has the text you might be looking for:

"""
   A Packet Too Big MUST be sent by a router in response to a packet
   that it cannot forward because the packet is larger than the MTU of
   the outgoing link.
"""

On Mon, Feb 3, 2020 at 7:31 AM Aitken, Paul <paul.aitken@intl.att.com>
wrote:

> Can anyone point me to a standards reference for the check to validate
> that the IPv6 payload length is less than or equal to the link layer
> frame size upon forwarding a packet?
>
> Thanks,
> Paul
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>