RE: [Manet-dt] RE: SMF: Usage of IPv4 Identification field

"Templin, Fred L" <Fred.L.Templin@boeing.com> Fri, 20 April 2007 15:33 UTC

Return-path: <manet-dt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hev71-0005IJ-0d; Fri, 20 Apr 2007 11:33:27 -0400
Received: from manet-dt by megatron.ietf.org with local (Exim 4.43) id 1Hev6z-0005AU-AE for manet-dt-confirm+ok@megatron.ietf.org; Fri, 20 Apr 2007 11:33:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hev6y-00058e-W9; Fri, 20 Apr 2007 11:33:25 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69] helo=blv-smtpout-01.ns.cs.boeing.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hev6x-0000pF-ME; Fri, 20 Apr 2007 11:33:24 -0400
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [192.42.227.216]) by blv-smtpout-01.ns.cs.boeing.com (8.13.6/8.13.6/TEST_SMTPIN) with ESMTP id l3KFXHPG013434 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 20 Apr 2007 08:33:22 -0700 (PDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.13.6/8.13.6/DOWNSTREAM_RELAY) with ESMTP id l3KFXGbe004221; Fri, 20 Apr 2007 08:33:16 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by blv-av-01.boeing.com (8.13.6/8.13.6/UPSTREAM_RELAY) with ESMTP id l3KFXD3E004058; Fri, 20 Apr 2007 08:33:16 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 20 Apr 2007 08:33:14 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Manet-dt] RE: SMF: Usage of IPv4 Identification field
Date: Fri, 20 Apr 2007 08:32:49 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED730@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <003501c78358$1cd12de0$0202a8c0@Teco>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Manet-dt] RE: SMF: Usage of IPv4 Identification field
Thread-Index: AceDSqfWn2b1+/XPRbWgeiWO2/QUIAACNBNQAAL5O/A=
References: <p06240800c24e61d9db8a@[132.250.92.151]> <003501c78358$1cd12de0$0202a8c0@Teco>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Teco Boot <teco@inf-net.nl>, Brian Adamson <adamson@itd.nrl.navy.mil>, manet-dt@ietf.org
X-OriginalArrivalTime: 20 Apr 2007 15:33:14.0381 (UTC) FILETIME=[35F73BD0:01C78361]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: manet <manet@ietf.org>
X-BeenThere: manet-dt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: MANET Design Team <manet-dt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet-dt>, <mailto:manet-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/manet-dt>
List-Post: <mailto:manet-dt@ietf.org>
List-Help: <mailto:manet-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet-dt>, <mailto:manet-dt-request@ietf.org?subject=subscribe>
Errors-To: manet-dt-bounces@ietf.org

> I leave implementation details up to you. The only hint I can 
> provide is the
> number of fragments for a full IP datagram is typically low, 
> as the maximum
> IPv4 packet is 64KB and the minimum supported MTU is often 
> mentioned as 576.
> 576 is the minimum size of IP datagram to be supported, so is 
> not exactly
> MTU (see RFC791).

(RFC791, Section 3.2) says:

    "Every internet module must be able to forward a datagram of 68
    octets without further fragmentation.  This is because an internet
    header may be up to 60 octets, and the minimum fragment is 8
octets."

This means that the minimum MTU all links must support is only
68 bytes; not 576. (RFC791, Section 3.2) also says:

    "Every internet destination must be able to receive a datagram of
576
    octets either in one piece or in fragments to be reassembled."

This means that all end systems must have a Maximum Receive
Unit (MRU) of at least 576 bytes. This is sustained by
(RFC1122, Section 3.2.2), which calls it the "Effective
MTU to Receive" (EMTU_R).

Main point - it is possible for both source hosts and
middleboxes to fragment datagrams into "tinygrams" as
small as 68 bytes - so this has to be accounted for by
any in-the-network function that might draw conclusions
about fragment offset. 

Fred
fred.l.templin@boeing.com


_______________________________________________
Manet-dt mailing list
Manet-dt@ietf.org
https://www1.ietf.org/mailman/listinfo/manet-dt