RE: [Manet-dt] RE: Minor MANET Generic Message Format Comments

"Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com> Tue, 04 April 2006 10:35 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FQitB-0002HM-7A; Tue, 04 Apr 2006 06:35:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FQit9-0002HH-TR for manet-dt@ietf.org; Tue, 04 Apr 2006 06:35:55 -0400
Received: from smtp1.bae.co.uk ([20.133.0.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FQit8-00078a-FJ for manet-dt@ietf.org; Tue, 04 Apr 2006 06:35:55 -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 k34AZq621423 for <manet-dt@ietf.org>; Tue, 4 Apr 2006 11:35:52 +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 <0IX70058Z1JQWQ@ngbaux.net.bae.co.uk> for manet-dt@ietf.org; Tue, 4 Apr 2006 11:38:15 +0100 (BST)
Received: from glkms0001.GREENLNK.NET ([10.15.184.1]) by glkas0002.GREENLNK.NET with InterScan Message Security Suite; Tue, 04 Apr 2006 11:32:30 +0100
Received: from glkms0008.GREENLNK.NET ([10.15.184.8]) by glkms0001.GREENLNK.NET with Microsoft SMTPSVC(5.0.2195.6713); Tue, 04 Apr 2006 11:32:30 +0100
Date: Tue, 04 Apr 2006 11:32:29 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Subject: RE: [Manet-dt] RE: Minor MANET Generic Message Format Comments
To: Ian Chakeres <ian.chakeres@gmail.com>
Message-id: <C1DE3C7469FE5A4D95F9BF0F332D8B8D01EEE5AD@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] RE: Minor MANET Generic Message Format Comments
Thread-Index: AcZXWMYI5yp5NgTSTn2V8GCHkDO1ngAeTmqA
Content-class: urn:content-classes:message
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-OriginalArrivalTime: 04 Apr 2006 10:32:30.0246 (UTC) FILETIME=[136FFC60:01C657D3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: manet-dt@ietf.org, Thomas Heide Clausen <T.Clausen@computer.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

> #1) Chris (and others), how about switching the bits (bit0 and bit1)
> then the fields stay in the same place and I think everyone is happy.

I'm missing the point here. The issue over #1 is that the originator
address and the message sequence number, which stay or go together
based on a single bit (for sensible reasons) are separated by the
TTL (to be renamed hop limit, I think) and hop count. We're all agreed
that in an ideal world they'd be together, but this is OLSRv1 legacy
that some people (I'm one) want to keep, and the minor inconvenience
(more lack of aesthetics than a real inconvenience) of having them
separate isn't worth giving up the compatibility. But this is true
regardless of in which order the two bits are, and we have the bits
ordered so you use #0, then #1, then #0 again. I could argue this is
slightly better than reversing them, but really it makes no difference
which order they are in, so as I said, I don't see the point of the
change (and therefore might as well leave as is).


********************************************************************
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