[Manet-dt] Re: [manet] Need for DPD header (SMF document discussion) - ValidReason for Tagger ID
Brian Adamson <adamson@itd.nrl.navy.mil> Wed, 02 May 2007 16:37 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 1HjHq0-0000rp-Aj; Wed, 02 May 2007 12:37:56 -0400
Received: from manet-dt by megatron.ietf.org with local (Exim 4.43) id 1HjHpz-0000rh-1T for manet-dt-confirm+ok@megatron.ietf.org; Wed, 02 May 2007 12:37:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HjHpv-0000rG-RZ; Wed, 02 May 2007 12:37:51 -0400
Received: from s2.itd.nrl.navy.mil ([132.250.83.3]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HjHpu-0003dO-FL; Wed, 02 May 2007 12:37:51 -0400
Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by s2.itd.nrl.navy.mil (8.13.6+Sun/8.12.8) with SMTP id l42Gbffq000154; Wed, 2 May 2007 12:37:46 -0400 (EDT)
Received: from [132.250.92.151] ([132.250.92.151]) by smtp.itd.nrl.navy.mil (SMSSMTP 4.1.12.43) with SMTP id M2007050212374502797 ; Wed, 02 May 2007 12:37:46 -0400
Mime-Version: 1.0
Message-Id: <p06240807c25e69a50462@[132.250.92.151]>
Date: Wed, 02 May 2007 12:37:43 -0400
To: manet@ietf.org, manet-dt@ietf.org
From: Brian Adamson <adamson@itd.nrl.navy.mil>
X-Spam-Score: 1.0 (+)
X-Scan-Signature: 3fbd9b434023f8abfcb1532abaec7a21
Cc:
Subject: [Manet-dt] Re: [manet] Need for DPD header (SMF document discussion) - ValidReason for Tagger ID
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>
Content-Type: multipart/mixed; boundary="===============0883556494=="
Errors-To: manet-dt-bounces@ietf.org
Charlie, Teco Do either you have implementations of hash or packet lookup approaches that we could try or incorporate into our "nrlsmf" implementation so we can look at the performance/computation complexity/space trade-offs more? I am concerned that complexity/space needed for these approaches may be prohibitive for some applications (and I am curious about the performance of the hash to not have false duplicates) compared to our current approach. But I am not opposed to allowing for both approaches to be specified or options if appropriate. The other issue is that imposing a requirement on applications to generate unique packet payloads (while probably generally good practice) may be inappropriate for a network layer specification? Also, Teco had mentioned in an earlier email he was concerned that "a bit table with packets received with offsets to a sequence number base (as often used in IPsec replay detection code) is not usable" ... I am not sure if that comment was limited to the fragmentation issue that was being discussed or with regard to SMF DPD in general? We have used this sort of approach successfully with IPv4 and IPv6 in fairly extensive laboratory and field tests for the past few years (although not with any fragmentation). However, it is not strictly a a packet bit mask, a timer is used to detect/prune stale packet flows as well, and there is a strategy involved to allow for the bitmask to provide a sort of "sliding window" At 8:58:02 AM -0700 4/27/07, Charles E. Perkins wrote: >Hello Teco, > >>ext Teco Boot wrote: >>If memory is really cheap and memory lookups can be performed faster than >>hash calculations, the DPD code could use packet header lookup instead of >>hash lookup. Functionality is the same. >Check. >>Both mechanisms rely on unique >>packet headers (say 1st 64 bytes or defined fields). >The defined fields could include some amount of payload. >> >>That is what should be >>specified in the standard. Which method is used for verifying duplicates is >>an implementation issue. >I think for IPv6 has also to specify which hash function >to use. For IPv4 I am hoping we do not need a hash function or any >DPD header. >Regards, >Charlie P. -- Brian __________________________________ Brian Adamson <mailto:adamson@itd.nrl.navy.mil>
_______________________________________________ Manet-dt mailing list Manet-dt@ietf.org https://www1.ietf.org/mailman/listinfo/manet-dt
- [Manet-dt] Re: [manet] Need for DPD header (SMF d… Brian Adamson
- Re: [Manet-dt] Re: [manet] Need for DPD header (S… Charles E. Perkins
- Re: [Manet-dt] Re: [manet] Need for DPD header (S… Brian Adamson
- Re: [Manet-dt] Re: [manet] Need for DPD header (S… Charles E. Perkins
- Re: [Manet-dt] Re: [manet] Need for DPD header (S… Brian Adamson
- Re: [Manet-dt] Re: [manet] Need for DPD header (S… Ian Chakeres