The MPLS WG Archive

[Loa Andersson <loa@pi.se>]

Steve,

Bala said it was a joke! And it wasn't hard to parse with a bit of humor.
Actuall quite funny :). I guess I could make a very similar flow chart,
in trying to discuss with some people around mpls.

But seriously claiming (you are not joking, are you?) that Balas flow
chart demonstrates that we intend to give work "externally generated"
a fast track to the trash I find below the level of this discussion.

The intention of the change process is to create a way for the (g)mpls
technology area to recieve and handle new requirements and new ideas, the
exact opposite of you are claiming.

In fact every time I send a new  ID (draft-andersson-xxxx-foo-00.txt) seen
from the IETF and the working groups it is in some sense "external". 
What is that
makes something that originates from "the other SDOs" so special from a 
technical
point of view. The change process are focused on guaranteeing that new
(g)mpls technology ideas are  evaluated based on their technical merits.

/Loa

Stephen Trowbridge wrote:

>Curtis,
>I have no problem to seperate the liaison process from the internal process.
>In fact, a good liaison process is needed that would have much broader
>applicability than (G)MPLS protocols.
>
>However, I do disagree that we can go forward on one with out the other.
>As Bala's flowchart shows, the effect of applying this draft to internally
>and externally initated work alike is to give the externally initiated
>work a fast track to the trash. Without the liaison process, this draft
>seems to make what is already a bad problem with how we deal with input
>from other SDOs even worse.
>Regards,
>Steve
>
>Curtis Villamizar wrote:
>  
>
>>In message <3E5F8A25.8030201@pi.se>, Loa Andersson writes:
>>    
>>
>>>- I don't think it is agood idea to describe the two process in the same
>>>  document. the chnage-process is for our internal use, the liasion process
>>>  is for our commuinication with other SDOs
>>>      
>>>
>>If we can agree on this, then we can move forward with your document.
>>
>>Curtis
>>    
>>
>
>
>  
>