Re: [Manet-dt] Generalised OLSR packet/message format comments - msg-semantics

Ian Chakeres <ian.chakeres@gmail.com> Wed, 01 February 2006 16:11 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F4KaG-0004s5-LV; Wed, 01 Feb 2006 11:11:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F4KaD-0004pQ-7A for manet-dt@megatron.ietf.org; Wed, 01 Feb 2006 11:11:51 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10890 for <manet-dt@ietf.org>; Wed, 1 Feb 2006 11:09:55 -0500 (EST)
Received: from wproxy.gmail.com ([64.233.184.204]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F4Kl9-0002tY-1w for manet-dt@ietf.org; Wed, 01 Feb 2006 11:23:08 -0500
Received: by wproxy.gmail.com with SMTP id 58so373626wri for <manet-dt@ietf.org>; Wed, 01 Feb 2006 08:11:30 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=HgqnFCq/Ztezot6EG1fbdJ4tL3CsosFfdQCpAspllxXYhFor27SwA4j+6bC9t6x0oULwYTPptXOIJ+roGo9vO6grnbkFZj3OwGxod97BjP5C/Jo4MB4URAap41KFL62Xrd09GFXA/K7jOs39eBckAlAdDBdISyHODSxkb5aXdbA=
Received: by 10.54.132.8 with SMTP id f8mr975899wrd; Wed, 01 Feb 2006 08:11:03 -0800 (PST)
Received: by 10.54.103.15 with HTTP; Wed, 1 Feb 2006 08:11:30 -0800 (PST)
Message-ID: <374005f30602010811v32b42675q77fbe5aed2f134f4@mail.gmail.com>
Date: Wed, 1 Feb 2006 08:11:30 -0800
From: Ian Chakeres <ian.chakeres@gmail.com>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Subject: Re: [Manet-dt] Generalised OLSR packet/message format comments - msg-semantics
In-Reply-To: <C1DE3C7469FE5A4D95F9BF0F332D8B8D02263D13@glkms0008.greenlnk.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <C1DE3C7469FE5A4D95F9BF0F332D8B8D02263D13@glkms0008.greenlnk.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: quoted-printable
Cc: manet-dt@ietf.org, Thomas 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>
Sender: manet-dt-bounces@ietf.org
Errors-To: manet-dt-bounces@ietf.org

My opinion is that several msg-types might have benefit from using a
few bits in the fixed portion for their specific use. I don't think
this goes against the common format philosophy. Perhaps, the
msg-semantics could be broken into 4 bits for msg-semantics and 4 bits
for msg-type-specific bits.

I am just proposing the idea. Would any of the OLSRv2 packets benefit
from having a few bits specific and available to it?

Ian

On 2/1/06, Dearlove, Christopher (UK) <chris.dearlove@baesystems.com> wrote:
>
> > One last comment. I would like to see several of the msg-semantic bits
> > reserved for msg-type specific bits. 4 ideally, but I would probably
> > settle for 2. For example in DYMO, RREQ messages could use a few of
> > these bits for its own purpose.
>
> I think this is exactly contrary to the common format philosophy
> (see my last message) and is not a good idea. If an RREQ needs
> RREQ specific information, the place for that is a message TLV.
>
>
> ********************************************************************
> 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