RE: [Manet-dt] OLSRv2 NHDP comments

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

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FVlxd-0006Ea-Jy; Tue, 18 Apr 2006 04:53:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FVlxc-0006ET-Kv for manet-dt@ietf.org; Tue, 18 Apr 2006 04:53:24 -0400
Received: from smtp1.bae.co.uk ([20.133.0.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FVlxc-0008II-8Z for manet-dt@ietf.org; Tue, 18 Apr 2006 04:53:24 -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 k3I8rMG06574 for <manet-dt@ietf.org>; Tue, 18 Apr 2006 09:53:22 +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 <0IXW003NAU0KY0@ngbaux.net.bae.co.uk> for manet-dt@ietf.org; Tue, 18 Apr 2006 09:53:08 +0100 (BST)
Received: from glkms0001.GREENLNK.NET ([10.15.184.1]) by glkas0002.GREENLNK.NET with InterScan Message Security Suite; Tue, 18 Apr 2006 09:48:59 +0100
Received: from glkms0008.GREENLNK.NET ([10.15.184.8]) by glkms0001.GREENLNK.NET with Microsoft SMTPSVC(5.0.2195.6713); Tue, 18 Apr 2006 09:48:59 +0100
Date: Tue, 18 Apr 2006 09:48:58 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Subject: RE: [Manet-dt] OLSRv2 NHDP comments
To: Ian Chakeres <ian.chakeres@gmail.com>, manet-dt@ietf.org
Message-id: <C1DE3C7469FE5A4D95F9BF0F332D8B8D01EEE5C0@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] OLSRv2 NHDP comments
Thread-Index: AcZg3ecORJH3aVDJSjKY+opARqGWegB5NEew
Content-class: urn:content-classes:message
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-OriginalArrivalTime: 18 Apr 2006 08:48:59.0363 (UTC) FILETIME=[EF3EF330:01C662C4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
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 would like to change the name of HELLO messages to something else.
>
> How about neighborhood message (hood message) or neighborhood
> advertisement (NHA). Not nearly as catchy but a bit more descriptive.

I see the point, but HELLO messages have a long pedigree in MANET.

> As mentioned before, ND is an overloaded term. Perhaps MANET
> neighborhood building block (hoodBB) would be a good term. What do you
> think?

I don't like hoodbb, I prefer Brian's nhdp, and also to options
such as ndhpbb or ndhbb. I think the ideal name hasn't been
proposed, but probably never will be.

> MIN_INTERVAL. I think this should be a SHOULD. If a node knows
> something is really important I think it should be allowed to transmit
> faster than MIN_INTERVAL, plus it isn't required for interoperability.

I would tend to agree with that. I also think MIN_INTERVAL isn't quite
the ideal name when put into a wider context (e.g. OLSRv2) as there
may then be other minimum intervals.

> Should we limit hoodBB to 2-hop neighborhoods? Is there something
> fundamentally different if we allow more than 2-hop neighborhood
> discovery?

I think if anyone wants 3+ hop neighbourhoods that they could/should
create an extension, we all have quite enough on our plates for
something we don't need. I also think there may be some definite
issues with >2 hops and multiple interfaces. We (some before I was
on board) have gone through evolution steps (from OLSRv1) from
MID messages to MA messages to using TC messages to only needing
HELLO messages. I have a feeling (not analysed) that 3 hop
neighbourhoods would open that whole can of worms again - and
getting rid of them has been a major step in making this separation
work.

> Is there any motivation behind the parameters (Section 7 Proposed
> Values)? What happens if they aren't all set to the same value? Can
> you elaborate a little on the various parameters interactions with
> each other or dependence on one another too?

Certainly this ought to be said somewhere. We (OLSRv2 DT) still have
an aspiration to some sort of rationale document, but pressure of
other stuff has pushed it down the stack. But in short, apart from C,
different nodes can have different values of the parameters. The
hold times must be significantly longer than the interval times,
roughly speaking 3x (the suggested default) allows you to lose 2
consecutive messages (though don't make a habit of it).

> Does the hoodBB require a link local multicast other than all MANET
routers?

I don't think so.

> I'm going to start up another thread on security.

We ran out of time putting this in, that's not a finished section.


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