[net2-wg] SP vs. LinkEstimatorP/bi directional links

[Omprakash Gnawali]

> I feel that link estimation and neighbor table management require a
> lot more than what this document provides and requires a separate TEP,
> perhaps as part of a more encompasing SP-like link interface. First,
> the description on neighbor tables is pretty thin (e.g. we have not
> described how neighbors enter and leave the table, other than the
> NeighborTable interface which has a single event). Second, the link
> estimator can be used for network services other than just collection
> routing.

I would take a slightly different approach. This is a documentary TEP
so it is important to have a section on link quality estimation and
neighbor table management because this describes our first cut
reference implementation of collection. Once SP and neighbor/link
related material therein is ironed out, section 4.1 should just refer
to the appropriate TEP. So, my vote is to keep this section for now
and update it later. I agree the details are sparse at the moment
which will be addressed shortly.

> 
> Question: What is the difference between getLinkQuality and the other
> two commands? Is it intended to provide the bi-directional link
> quality?

Yes, those functions are there to provide bi-directional link quality
because we thought some routing protocols might need that information
separately.