NOTICE: Tentative Program

Lunch

Management of OLSR(v2) - Operations

One of the new things in the OLSRv2 standardization process is, that we're looking to publish "Management Information Bases", or MIBs, for the constituent parts of the protocol. This is new, this is supposed to be helpful and a good thing -- but we have gotten little in terms of feedback from the community actually operating OLSR/OLSRv2 networks on what you need, probably because we've not asked (yet).

Ulrich Herberg, one of the authors of the MIB documents, and himself an OLSRv2 implementor, has kindly volunteered to give a presentation of the MIB work and of his "management interface" (currently, non-MIB-based) to his OLSRv2 implementation, as a way of kickstarting the discussions at this Workshop on this subject, and ask the question: what do YOU need as management information and interfaces? How do YOU think that this should proceed?

OLSRv1/RFC3626 has a couple of years behind it - and OLSRv2 is in the process of standardization. This years Interop is specifically held in Vienna, to be close to one of the biggest community networks "out there in the real world", which has build around, played with, extended OLSRv1.

This slot is an "OLSR-bashing" session of the constructive kind. After a brief introduction, it's YOUR turn: what went wrong in RC3626? What do YOU need to see in OLSRv2? Is it already there? If not, why not? How could you like to see what you need addressed?

Lunch

Lunch