[Olsr-dev] Multi-Topology Routing for OLSR

Teco Boot (spam-protected)
Fri Aug 10 08:20:46 CEST 2012


Op 6 aug. 2012, om 18:00 heeft Ferry Huberts het volgende geschreven:

> 
> 
> On 06-08-12 17:46, jpo wrote:
>> Hello all,
>> I already brought this topic up in the OLSR-Users list, but I think the development list is a more appropriate venue.
>> 
>> Basically what I'm interested in is what RFC 4915 provides for OSPF: a way to define topologies as subsets of the "physical" topology and calculate independent routing tables for each of these subset topologies.
>> 
>> Using the policy based routing tool chest would allow the selection of the routing table and those the topology for packets based on configurable markers.
>> 
>> Questions:
>> Is there somebody besides me interested in this?
>> Are you aware of an existing implementation (not necessarily in olsr.org)?
>> What needs to be done in olsrd to make this reality?
>> 
>> Here are my thoughts:HELLO, TC and probably MID need changes to carry the topology-id with the link information.
>> The internal link state databases need to be extended.
>> SPF calculation has to be done for each known topology.
>> 
> 
> That would mean a spec change.
> OLSR v2 is already spec-ed and in final call (http://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2/?include_text=1).
> 
> So you're talking about v3...
> Good luck with getting that past IETF...

OLSRv2 is designed for flexibility. MTR can be build on top of it, using "MTR link metric types".  Routers that do not support these extensions are only included in the default topology. How traffic is mapped to a topology (in a standard way) is still a research topic.

The IETF MANET WG would be interested in any outcome of an experiment. A good way of publishing is post an Internet Draft.

Teco

> 
> 
>> Anything I'm missing?
>> 
>> Thanks in advance and kind regards
>>   Joerg
>> 
>> 
> 
> -- 
> Ferry Huberts
> 
> -- 
> Olsr-dev mailing list
> (spam-protected)
> https://lists.olsr.org/mailman/listinfo/olsr-dev





More information about the Olsr-dev mailing list