Opened 5 years ago

#55 new defect

Maintaining Multiple Routing Sets

Reported by: abdussalambaryun@… Owned by: draft-ietf-manet-olsrv2-multitopology@…
Priority: major Milestone:
Component: olsrv2-multitopology Version:
Severity: Waiting for Shepherd Writeup Keywords:
Cc: manet@…

Description

--- Old Edit ---

In a similar way, the role of this extension

can be described as to create and maintain multiple Routing Sets, one for each link metric type supported by the router maintaining the sets.

--- New Edit ---

In a similar way, the role of this extension

can be described as to maintain multiple Routing Sets, one for each link metric type supported by the router maintaining the sets.

AB> the draft does not specify creating routing sets.

AB> I am trying to find the routing sets maintenance of this extension, no information about the router's handling of multiple topologies within its processing time. What are the priorities of the single MT-routing function while receiving different messages for the different topologies, which that maintenance is not specified by RFC7181 and needs to be in this extension. Suggest a clear section to describe maintenance of multiple routing sets (as introduction mentions that this extension is about routing sets maintenance).


The draft mentions>

each router will maintain a Routing Set for each topology that it forms part of, allowing separate routing of packets for each topology.

AB> the draft needs to describe, How does MT-router do that separation for the multiple topology packets? If that answer in open for implementors then I don't think there is a maximum interoperability between MT-routers. Section 11 should describe updates and maintenance of multiple routing sets with packet separation (this should not to be left out of the draft as just considerations in last sections).


Section 12> MT-OLSRv2 may require greater management than unextended OLSRv2. In

particular MT-OLSRv2 requires the following management considerations: ...

AB> these MT routers require administration and specific management considerations to ensure good performance. Section 12 mentions it as MAY but I suggest to replace to MUST. The section is a must requirement not just recommendations, the section needs to be updated and moved after section 4.

Change History (0)

Note: See TracTickets for help on using tickets.