Re: [manet] #55 (olsrv2-multitopology): Maintaining Multiple Routing Sets

[Christopher Dearlove <[e-mail]>]

The chair has pointed out this discussion should stop. And strictly I'm violating that. But find another person, one who understands OLSRv2 but not MT-OLSRv2, then there may be something to say.

--  
Christopher Dearlove
[e-mail] (iPhone)
[e-mail] (home)

> On 26 Sep 2014, at 14:55, Abdussalam Baryun <[e-mail]> wrote:
> 
> Hi
> 
>> On Sunday, September 21, 2014, Stan Ratliff (sratliff) wrote:
>> Abdussalam,
>> 
>>> On Sep 21, 2014, at 7:53 AM, Abdussalam Baryun <[e-mail]> wrote:
>>> 
>>> Section 11 and subsection 6.8 need more specification details for routing maintenance. 
>>> 
>>>> On Saturday, August 23, 2014, Christopher Dearlove wrote:
>>>> ....
>>>> 
>>>> Yes, the draft does describe creating multiple routing sets. See Section 11. If familiar with OLSRv2, that's all you need - because OLSRv2 describes how a Routing Set is calculated and when it needs to change.
>>> 
>>> Already seen section 11 when reviewed but is not enough. Regarding RFC7181 (which section refers to) it is only for single topology, so for MT we need a fresh maintenance paragraph at least. In subsection 6.8 it does not describe how is the separation. In section 11 it does not describe how the calculation separates routing sets. The is a need to add an element in routing set for metric type. All maps are done with metric type reference, but in the routing sets there is no element for metric type or reference. 
>> 
>> I want to reinforce what Chris Dearlove said in another email. The text above implies (at least to me) that you have a specific deployment scenario in mind, and that when looking at the text of the draft, you conclude that your scenario won't work. If that is the case, describe the scenario 
> 
> 
> That is not the case, the scenarios are general purpose of MANET or as RFC7181. The case is the draft reader did not understand and is discussing to clarify the issues. The reader is referring to texts in the draft related to updating routing sets. Generally, the case is that some of my questions are not getting clear answers. It is good that reader reviewing and commenting on draft and sharing his/her understanding or misunderstanding. I want to implement the work then will think about scenarios. 
> 
>   
>> - I'm not able to follow your concerns, above some vague notion that "this won't work". Without the necessary detail, I can only conclude that consensus exists to progress the draft, and you are "in the rough". 
> 
>  I never said it does not work. I want the draft to be clear to readers how protocol works. Does your message mean stop discussing because your in the rough? Or stop because you have no scenario detail (usually my scenario is the draft scenario). The WG is small in size so maybe 10% participants don't understand the work. The IETF is not about only consensus, but about publishing readable work that full community can understand and implement. 
> 
> AB
>