Re: [manet] draft-ietf-manet-aodvv2-13 review - a couple of big ticket Items

[Jiazi YI <[e-mail]>]

>
> *Intermediate Route Replies, and all of section 10*
> Section 10 contains a set of “vaguely specified extensions”, which is
> incoherent with the intended status indicated for this document.
>
> Specifically, and this is not unrelated to the point about loops above,
> intermediate RREPs (section 10.3) are a potential source for loops.
>
> Expanding Ring Multicast (section 10.1) is not documented in a way that
> can be implemented (and also, see “Forwarding-vs-regeneration” below, it is
> in the present form of this protocol impossible), etc.
>

On those optional features, from the point of view of an engineer, I would
like to see:

   - how the features should be implemented. i.e., they should be clearly
specified.

   - What's the "benefit" of those features, as well as the "cost" -- for
example, message overhead, processing delay, complexity, etc., so that I
can decide if I need/should implement those features or not. If the
feature(s) has no cost but only benefit, it should go to the core
specification directly.

   - The interoperability with the implementations without the optional
features.

   - If the feature brings additional security threats. If yes, what's them
and how to mitigate them.

best

Jiazi