Fragmented IPv6 packets

Muthukumar_Lakshmanan@McAfee.com Fri, 09 December 2005 06:42 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EkbxF-0005up-7O; Fri, 09 Dec 2005 01:42:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EkbxD-0005uU-4m for ipv6@megatron.ietf.org; Fri, 09 Dec 2005 01:42:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18041 for <ipv6@ietf.org>; Fri, 9 Dec 2005 01:40:59 -0500 (EST)
From: Muthukumar_Lakshmanan@McAfee.com
Received: from sncsmrelay2.nai.com ([67.97.80.206]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EkbxB-0006k1-EA for ipv6@ietf.org; Fri, 09 Dec 2005 01:42:02 -0500
Received: from sncexwsout1.na.nai.com (sncexwsout1.na.nai.com [161.69.206.120]) by sncsmrelay2.nai.com (Switch-3.1.3/Switch-3.1.0) with SMTP id jB99OZl8011143 for <ipv6@ietf.org>; Fri, 9 Dec 2005 01:24:35 -0800
Received: from (161.69.5.246) by sncexwsout1.na.nai.com via smtp id 348e_93a6d04c_6882_11da_9836_0002b3e6f1b3; Thu, 08 Dec 2005 23:08:19 -0800 (PST)
Received: from banexmb1.corp.nai.org ([161.69.182.237]) by sncexbr1.corp.nai.org with Microsoft SMTPSVC(5.0.2195.6713); Thu, 8 Dec 2005 22:41:43 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 09 Dec 2005 12:11:39 +0530
Message-ID: <CA22D36810B0A7459233616F36BFD59A07B0AD91@banexmb1.corp.nai.org>
Thread-Topic: Fragmented IPv6 packets
Thread-Index: AcX8hdzELVT/ttFuSQeWU120tfP+Qw==
To: ipv6@ietf.org
X-OriginalArrivalTime: 09 Dec 2005 06:41:43.0593 (UTC) FILETIME=[9E456990:01C5FC8B]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: quoted-printable
Subject: Fragmented IPv6 packets
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

I have a question on IPv6 fragments.  Since IPv6 mandates a minimum MTU
of 1280,  IPv6 fragments (except the last fragment) should be of minimum
1280 bytes right? When an end host receives an IPv6 fragment which is
lesser than 1280 bytes ( except the last fragment ) , should it treat it
as invalid and drop it or should it still consider the fragment for
reassembly. Are there any IPv6 implementations which reassemble them?

Thanks,
Muthu

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------