RE: diffedge handling of fragments
Sumit Vakil <sumit@calynet.com> Wed, 06 October 1999 23:21 UTC
Received: from lists.tislabs.com (portal.gw.tislabs.com [192.94.214.101]) by mail.imc.org (8.9.3/8.9.3) with ESMTP id QAA01067; Wed, 6 Oct 1999 16:21:50 -0700 (PDT)
Received: by lists.tislabs.com (8.9.1/8.9.1) id SAA28576 Wed, 6 Oct 1999 18:08:23 -0400 (EDT)
Message-ID: <636C2D109E6CD3119C3600062905FE8F8D49@MAIL-CLUSTER.calynet.com>
From: Sumit Vakil <sumit@calynet.com>
To: ipsec@lists.tislabs.com
Subject: RE: diffedge handling of fragments
Date: Wed, 06 Oct 1999 15:02:56 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ipsec@lists.tislabs.com
Precedence: bulk
> >>>>> "Sumit" == Sumit Vakil <sumit@calynet.com> writes: > > Sumit> Michael, Section 4.4.2 of RFC 2401 also says that > if the port > Sumit> information is not available in a fragment it is > to be discarded. > Sumit> The exact text is as follows: > > Sumit> If the packet has been fragmented, then the port > information may > Sumit> not be available in the current fragment. If so, > discard the > Sumit> fragment. An ICMP PMTU should be sent for the > first fragment, > Sumit> which will have the port information. [MAY be supported] > > Uh, I read this to be in the context of doing ICMP PMTU > discovery for > the end hosts of the MTU of the tunnel. Line 3 of the table just above this paragraph (the one that shows how to derive the port selector for the SPD and the SAD) indicates the condition when a fragment is to be dropped: next header in fragment == transport layer protocol in SPD My understanding is that the table is to be used for all traffic. If that is true, then fragments satisfying the above condition have to be dropped. Sumit
- diffedge handling of fragments mcr
- RE: diffedge handling of fragments Sumit Vakil
- Re: diffedge handling of fragments Michael Richardson
- RE: diffedge handling of fragments Sumit Vakil