Re: [manet] Default metric in OLSRv2

["Dearlove, Christopher (UK)" <Chris.Dearlove at baesystems.com>]

> I don't think this will work well for OLSRv2. Most people using OLSRv2
for 
> research (instead of doing research on OLSRv2) will continue to use
the "basic 
> RFC implementation" of OLSR... if the basic RFC does only contain
hopcount

That is not the proposal. See what's written in the metrics draft.
(I agree what you indicate would not be acceptable. But that's why
that isn't it.)

The proposal is that the default is an additive metric of unspecified
"real world" meaning. But it's still a metric, and not just hopcount.
It's just not a specific ETC/delay/whatever metric. At least not
specified as such. In a given deployment if you agree in advance that
this is ETX, fine. But if you definitely want ETX then get an allocation
of one of the reserved metric code points specifically for that purpose
and use that.

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