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

Teco Boot <teco@inf-net.nl> Fri, 20 April 2007 08:02 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 1Heo4F-00065m-JK; Fri, 20 Apr 2007 04:02:07 -0400
Received: from manet-dt by megatron.ietf.org with local (Exim 4.43) id 1Heo4E-00065d-31 for manet-dt-confirm+ok@megatron.ietf.org; Fri, 20 Apr 2007 04:02:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Heo4A-00064O-HJ; Fri, 20 Apr 2007 04:02:02 -0400
Received: from smtp15.wxs.nl ([195.121.247.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Heo48-0005BR-TO; Fri, 20 Apr 2007 04:02:02 -0400
Received: from Teco (ip56530916.direct-adsl.nl [86.83.9.22]) by smtp15.wxs.nl (iPlanet Messaging Server 5.2 HotFix 2.15 (built Nov 14 2006)) with ESMTP id <0JGS00ET1EB2IZ@smtp15.wxs.nl>; Fri, 20 Apr 2007 10:02:00 +0200 (CEST)
Date: Fri, 20 Apr 2007 10:02:52 +0200
From: Teco Boot <teco@inf-net.nl>
In-reply-to:
To: manet-dt@ietf.org
Message-id: <001e01c78322$4d8a8980$0202a8c0@Teco>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Thread-index: Acd9rydWRR4SwktmRAOnEMcJZwZMYwFb4v0g
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: 'manet' <manet@ietf.org>
Subject: [Manet-dt] RE: SMF: Usage of IPv4 Identification field
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 have a remark on using IPv4 DPD and support for fragmentation. I think it
is not that difficult to support fragmentation, we only have to extent the
DPD filter for Fragment Offset (and Protocol, to be compliant with RFC791).
Incorporating the Flags field (e.g. more fragments) is not needed but not
harmful either.

The DPD filter should check on Source Address, Destination Address,
Protocol, Identification and Fragment Offset. Out of RFC791; header fields
not used by DPD are blanked:
                                
    0                   1                   2                   3   
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       |       |               |                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |         Identification        |     |      Fragment Offset    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |               |    Protocol   |                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                       Source Address                          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                    Destination Address                        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                               |               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                    Example Internet Datagram Header

                               Figure 4.

IMHO updating DPD to RFC791 is important. Also for using it as remedy for
unicast routing loops as I suggested before.

Cheers, Teco

> -----Original Message-----
> From: Teco Boot [mailto:teco@inf-net.nl]
> Sent: vrijdag 13 april 2007 11:36
> To: 'manet-dt@ietf.org'
> Subject: SMF: Usage of IPv4 Identification field
> 
> The SMF ID deviates from RFC791 for the Identification field.
> 
> 791: "The originating protocol module of an internet datagram sets the
> identification field to a value that must be unique for that source-
> destination pair and protocol"
> 
> SMF: "In the case that resequencing is deemed necessary, it is RECOMMENDED
> that sequence numbering be applied such that a different sequence number
> space per <sourceAddress::destinationAddress> duple be used"
> 
> The difference is the protocol field. I see two options, modify SMF or add
> text clarifying the deviation and analyze for consequences. Or are the
> rules for Identification changed since 791?
> 
> Teco



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