RE: Last Call <draft-sprecher-mpls-tp-oam-considerations-01.txt> (The Reasons for Selecting a Single Solution for MPLS-TP OAM) to Informational RFC

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> I didn't mean to say that the IETF in general allows multiple solutions but I think
> it is accurate to say that the IETF has a less than 100% success rate of preventing
> multiple solutions.

Correct. We are not perfect.

>> In the very many previous cases it was not necessary to write a
>> document because the second (or third, or ...) solution was within the
>> same standards body, and it was possible to either prevent publication,
>> or publish the second solution as informational, or publish the second
>> solution with a disclaimer up front saying some form of "we recommend
>> this other solution [add normative reference] which is the agreed IETF
>> standard".
>
> You are making a point on which I picked earlier because it is stated in the
> document as well. In case there are multiple solutions, documenting, but at
> the same time discouraging the other one has happened before. Why is this not
> possible in this case? Make one the default, the other optional with a big
> red warning sign.
>
> Best,
> Rolf

This is indeed possible in this case. It has been privately suggested multiple times, but 
I agree that this should have been publicly suggested as well (and thus I guess that I am
publicly suggesting it now). 

Ross
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf


[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]