RE: Fragmented IPv6 packets
"Vishwas Manral" <Vishwas@sinett.com> Fri, 09 December 2005 06:48 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 1Ekc3J-0007gS-IA; Fri, 09 Dec 2005 01:48:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ekc3H-0007dn-Ss for ipv6@megatron.ietf.org; Fri, 09 Dec 2005 01:48:19 -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 BAA18806 for <ipv6@ietf.org>; Fri, 9 Dec 2005 01:47:24 -0500 (EST)
Received: from 63-197-255-154.ded.pacbell.net ([63.197.255.154] helo=sinett.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ekc3O-0006w1-Fn for ipv6@ietf.org; Fri, 09 Dec 2005 01:48:27 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 08 Dec 2005 22:52:44 -0800
Message-ID: <BB6D74C75CC76A419B6D6FA7C38317B2B8755B@sinett-sbs.SiNett.LAN>
Thread-Topic: Fragmented IPv6 packets
Thread-Index: AcX8hdzELVT/ttFuSQeWU120tfP+QwABxCEQ
From: Vishwas Manral <Vishwas@sinett.com>
To: Muthukumar_Lakshmanan@McAfee.com, ipv6@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: quoted-printable
Cc:
Subject: RE: 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
Hi Muthu, You may want to shift the discussion to the v6ops list instead. Have a look at the draft http://www.ietf.org/internet-drafts/draft-manral-v6ops-tiny-fragments-is sues-00.txt in the meanwhile. Thanks, Vishwas -----Original Message----- From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Muthukumar_Lakshmanan@McAfee.com Sent: Friday, December 09, 2005 12:12 PM To: ipv6@ietf.org Subject: Fragmented IPv6 packets 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 --------------------------------------------------------------------
- Fragmented IPv6 packets Muthukumar_Lakshmanan
- RE: Fragmented IPv6 packets Vishwas Manral
- RE: Fragmented IPv6 packets sasson_shuki
- RE: Fragmented IPv6 packets Nuno Garcia
- Re: Fragmented IPv6 packets Elwyn Davies