Re: [Manet-dt] Re: [manet] Need for DPD header (SMF document discussion) - ValidReason for Tagger ID

"Charles E. Perkins" <charles.perkins@nokia.com> Wed, 02 May 2007 18:09 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 1HjJH4-0006OP-O8; Wed, 02 May 2007 14:09:58 -0400
Received: from manet-dt by megatron.ietf.org with local (Exim 4.43) id 1HjJH3-0006O9-5B for manet-dt-confirm+ok@megatron.ietf.org; Wed, 02 May 2007 14:09:57 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HjJH2-0006Np-Gg; Wed, 02 May 2007 14:09:56 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HjJH0-0007Mn-Uc; Wed, 02 May 2007 14:09:56 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145]) by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l42I9XVr032742; Wed, 2 May 2007 21:09:51 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 2 May 2007 21:09:45 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 2 May 2007 13:09:43 -0500
Received: from [10.162.76.0] ([10.162.76.0]) by daebe101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 2 May 2007 13:09:42 -0500
Message-ID: <4638D3E0.4010106@nokia.com>
Date: Wed, 02 May 2007 11:09:36 -0700
From: "Charles E. Perkins" <charles.perkins@nokia.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
To: ext Brian Adamson <adamson@itd.nrl.navy.mil>
Subject: Re: [Manet-dt] Re: [manet] Need for DPD header (SMF document discussion) - ValidReason for Tagger ID
References: <p06240807c25e69a50462@[132.250.92.151]>
In-Reply-To: <p06240807c25e69a50462@[132.250.92.151]>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 May 2007 18:09:43.0012 (UTC) FILETIME=[0EFBA240:01C78CE5]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: manet@ietf.org, manet-dt@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

Hello Brian,

I have some 'C' code that I have adapted
from other sources, and if you like I can
send it to you.  Of course you have to
promise not to be too disappointed if you
find bugs, and please send any improvements
back to me so I can reincorporate it into
the code I have.  It isn't very much, and
at least half of it was grabbed from existing
code on the net (including RFC 1321, which
excuses me from any wrongdoing about the
formatting and stylistic issues).

Ian suggested that there was agreement
that the hashing was effective, and asked
whether the other features of the DPD
header were sufficient to warrant its use
(in favor of hashing).

I do _not_ suggest that applications take
any responsibility for generating unique
hash codes.  To summarize, I prefer if we
make hashing "good enough", and then use
the DPD header for the rare cases where
the hash function fails to distinguish different
flooded packets.  Used in this way, the
DPD header could be a lot simpler.

Regards,
Charlie P.


ext Brian Adamson wrote:
> 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"
> _______________________________________________
> Manet-dt mailing list
> Manet-dt@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet-dt
>   



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