Re: [manet] Questions regarding draft-ietf-manet-olsrv2-19

I think I speak for the authors that we have no intention of doing this. It may be editorial, but it's been accepted up to now, through the whole process, and the likelihood of making an error would massively outweigh any possible advantage, even if we agreed on what.

-- 
Christopher Dearlove
christopher.dearlove@gmail.com (iPhone)
chris@mnemosyne.demon.co.uk (home)

> On 20 Jan 2014, at 18:18, Henning Rogge <hrogge@gmail.com> wrote:
> 
>> On Mon, Jan 20, 2014 at 6:45 PM, Dearlove, Christopher (UK) <Chris.Dearlove@baesystems.com> wrote:
>> 2.   Good catch, and nicely timely as we are doing edits with the RFC Editor right now and can add this to the list. Note that (see point above) this gets rid of the Neighbor Tuple here.
> 
> I wonder if we should rename the "x_mpr_selector" variables into something like "x_flooding/routing_mpr_selector" to make sure they cannot be mixed up when implementing OLSRv2. It sounds like something that could be done in an editor change because it will change nothing to the protocol but make the description more foolproof.
> 
> Its not really that important, but it might be a good idea.
> 
> Henning Rogge
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet