Re: IPv6 payload length check?

"Aitken, Paul" <paul.aitken@intl.att.com> Tue, 04 February 2020 07:43 UTC

Return-Path: <paul.aitken@intl.att.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 48CB0120074 for <ipv6@ietfa.amsl.com>; Mon, 3 Feb 2020 23:43:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.498
X-Spam-Level:
X-Spam-Status: No, score=-2.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 x3fCsdDyWfRf for <ipv6@ietfa.amsl.com>; Mon, 3 Feb 2020 23:43:11 -0800 (PST)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4D1D120123 for <ipv6@ietf.org>; Mon, 3 Feb 2020 23:43:10 -0800 (PST)
Received: from pps.filterd (m0083689.ppops.net [127.0.0.1]) by m0083689.ppops.net-00191d01. (8.16.0.42/8.16.0.42) with SMTP id 0147a7gp033684; Tue, 4 Feb 2020 02:43:09 -0500
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0083689.ppops.net-00191d01. with ESMTP id 2xy2apu2ny-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 04 Feb 2020 02:43:09 -0500
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id 0147h8bn027723; Tue, 4 Feb 2020 02:43:09 -0500
Received: from zlp27129.vci.att.com (zlp27129.vci.att.com [135.66.87.42]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id 0147h70u027697 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 4 Feb 2020 02:43:07 -0500
Received: from zlp27129.vci.att.com (zlp27129.vci.att.com [127.0.0.1]) by zlp27129.vci.att.com (Service) with ESMTP id 72080401657E; Tue, 4 Feb 2020 07:43:07 +0000 (GMT)
Received: from gbcdcmbx11.intl.att.com (unknown [135.76.180.47]) by zlp27129.vci.att.com (Service) with ESMTPS id 27EB8401657D; Tue, 4 Feb 2020 07:43:07 +0000 (GMT)
Received: from gbcdcmbx17.intl.att.com (135.76.180.53) by gbcdcmbx11.intl.att.com (135.76.180.47) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.1913.5; Tue, 4 Feb 2020 07:43:04 +0000
Received: from gbcdcmbx17.intl.att.com ([fe80::610b:3cbc:a7b0:614c]) by gbcdcmbx17.intl.att.com ([fe80::610b:3cbc:a7b0:614c%7]) with mapi id 15.01.1913.005; Tue, 4 Feb 2020 07:43:04 +0000
From: "Aitken, Paul" <paul.aitken@intl.att.com>
To: Erik Kline <ek.ietf@gmail.com>
CC: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: IPv6 payload length check?
Thread-Topic: IPv6 payload length check?
Thread-Index: AQHV2qblFLgIwdEdzUiGzzYNpBgEAagKBtgAgAChUIA=
Date: Tue, 04 Feb 2020 07:43:04 +0000
Message-ID: <21c14789-73b8-1347-98bf-9c70c3d31e76@intl.att.com>
References: <90342768-7f25-b9dd-eeae-29db6045b40a@intl.att.com> <77f55628-6f9d-d06a-4e38-f84d76e716bb@intl.att.com> <CAMGpriWVN0EGLz5PyeyL5LTo_+A1i+xHCD6kw0E0pCRCcGcY2g@mail.gmail.com>
In-Reply-To: <CAMGpriWVN0EGLz5PyeyL5LTo_+A1i+xHCD6kw0E0pCRCcGcY2g@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1
x-originating-ip: [135.76.180.249]
Content-Type: multipart/alternative; boundary="_000_21c1478973b8134798bf9c70c3d31e76intlattcom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.572 definitions=2020-02-04_01:2020-02-04, 2020-02-04 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 malwarescore=0 phishscore=0 clxscore=1011 mlxscore=0 spamscore=0 lowpriorityscore=0 adultscore=0 bulkscore=0 mlxlogscore=999 priorityscore=1501 suspectscore=0 impostorscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1911200001 definitions=main-2002040055
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/yfxJ6oklGcXt0oDvv9eCTvmu7KE>
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, 04 Feb 2020 07:43:14 -0000

Thanks Eric.

In this case the packet is *not* larger than the MTU of the outgoing link. Rather a packet has been received (or possibly generated locally) with an IPv6 payload length greater than the link layer frame size.

Probably this packet should not be forwarded. However, I couldn't find anything to say that it's invalid.

Thanks,
P.


On 03/02/2020 22:05, Erik Kline wrote:
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<mailto: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<mailto:ipv6@ietf.org>
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_ipv6&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=ZfTZz_O9E1tN4KFtMYO2ZkKk5U5-6SlI-21vZEhzDuU&m=qBignlV2D2HjQ1OG98CXIFMbZryHbieyfesxKE4ZOfg&s=Hcp5fCXJd8pXcMtmqOUaw179roZQXSQntvE-zFdQYbY&e=>
--------------------------------------------------------------------