Re: [manet] Default metric in OLSRv2

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

>> Will you please read the metrics draft, and my postings here, which
have
>> said, again and again, that this is NOT the proposal.
> The default value in your metric draft will still create a hopcount
metric.

Yes, that's the default value. But that is not using a hop count metric.

> And there is no other example for a working link metric inside the
current 
> metric draft.

That's a separation of responsibility. While particular metrics
make motivation, it's putting too much into OLSRv2 to specify the
metric and how it is to be created. All of that is ideal for another
draft, which can discuss motivation, definition, IANA codepoints
(from the TLV defined) etc. I am hoping you will, with the various
people who have offered support, take up that task.

We may well reference, from the motivation part of the document,
something external (NOT the draft we're taling about below, that
creates a circular, possibly down, reference that is not appropriate)
to note the desirability of metrics. (The existing draft rather
glosses over that as preaching to the converted.) But this wants
to be about metrics in general, not (however suitable it may be
as a first choice) ETX or anything else.

> So if we include the metric draft into the OLSRv2 draft, the default 
> implementation will still be hopcount

NO. An implementation will not be compliant unless it implements
metrics, how to handle metrics in incoming messages. If it chooses
never to use that code it has implemented itself, there's really not
much one can do about that. But a pure hopcount implementation will
not be compliant.

Note that the default metric meaning will be up to local configuration.
But it will be there, and must be implemented.

> I fear there will be still a lot of 
> researchers around that will use "default rfc olsrv2".

They won't be doing that. If they don't implement metrics, they
won't have implemented the RFC.

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