RE: [Manet-dt] MANET packet security

"Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com> Tue, 18 April 2006 09:02 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FVm6V-0007JW-19; Tue, 18 Apr 2006 05:02:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FVm6U-0007JR-Lv for manet-dt@ietf.org; Tue, 18 Apr 2006 05:02:34 -0400
Received: from smtp1.bae.co.uk ([20.133.0.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FVm6T-0000Bj-A5 for manet-dt@ietf.org; Tue, 18 Apr 2006 05:02:34 -0400
Received: from ngbaux (ngbaux.msd.bae.co.uk [141.245.68.234]) by smtp1.bae.co.uk (Switch-2.2.8/Switch-2.2.8) with ESMTP id k3I92TG11036 for <manet-dt@ietf.org>; Tue, 18 Apr 2006 10:02:29 +0100 (BST)
Received: from glkas0002.GREENLNK.NET ([10.15.184.52]) by ngbaux.net.bae.co.uk (PMDF V5.2-33 #44998) with ESMTP id <0IXW004X6UEX1C@ngbaux.net.bae.co.uk> for manet-dt@ietf.org; Tue, 18 Apr 2006 10:01:45 +0100 (BST)
Received: from glkms0002.GREENLNK.NET ([10.15.184.2]) by glkas0002.GREENLNK.NET with InterScan Message Security Suite; Tue, 18 Apr 2006 09:57:35 +0100
Received: from glkms0008.GREENLNK.NET ([10.15.184.8]) by glkms0002.GREENLNK.NET with Microsoft SMTPSVC(5.0.2195.6713); Tue, 18 Apr 2006 09:57:35 +0100
Date: Tue, 18 Apr 2006 09:57:35 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Subject: RE: [Manet-dt] MANET packet security
To: Ian Chakeres <ian.chakeres@gmail.com>, manet-dt@ietf.org
Message-id: <C1DE3C7469FE5A4D95F9BF0F332D8B8D02263E88@glkms0008>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.0.6556.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: quoted-printable
Thread-Topic: [Manet-dt] MANET packet security
Thread-Index: AcZg4Zvqz7OB2/qKSXK2VIhcARfe+QB42iKA
Content-class: urn:content-classes:message
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-OriginalArrivalTime: 18 Apr 2006 08:57:35.0246 (UTC) FILETIME=[22BC72E0:01C662C6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc:
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 think the base specs of our MANET protocols should include a
> mechanism to secure packets, that is authenticate the source, as well
> as ensure the contents of the packet have not been modified, replayed,
> etc.

If we want to achieve a timescale anything like that which the MANET
WG is chartered for, I do not agree. Of course we must ensure that
the capability to add this is possible - and message (and packet for
those who want hop by hop rather than end to end) TLVs provide this.
But trying to standardise a mechanism in the base spec, I would be
strongly against - and I'm coming from a background which would want
such a mechanism (but maybe not the one devised).

> If we need to do this type of procedure, I think it should probably
> live with the packetBB document or another BB document. What do you
> think?

Now that's different. If someone wants to work on a separate building
block that is compatible with the formats and functions of the
protocols,
fine - except for issues of whether it's a MANET WG item, and if not
ought to stay author draft. Calling it up in a Standards Track RFC
(DYMO, OLSRv2, maybe SMF) would be problematic of course.


********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************

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