We’ve got the existence proof of the counter example in SIP. I cannot count how many times I heard, “Yes, I know foo is broken, but it has been in 2543bis-02 and now we are at 2543bis-06 and we could not possibly make a change because so many vendors implemented to bis-02.” Egad! We could not change what was in an Internet *Draft*??? Imagine the pushback to changing an RFC. > On Dec 22, 2015, at 11:52 AM, Jari Arkko <jari.arkko@xxxxxxxxx> wrote: > > >> For better or worse, I have a lot of trouble believing that >> scenario could play out the same way today. > > Mumble. I’m not sure. I seem to recall many cases > where somebody has to explain to $vendor that > things have changed and they can’t do what > they wanted to do. In more cases than just > draft changes. > > Results of course vary. But, ultimately it is an IETF > community decision on what a working group does. > Do they weigh the existing implementation base > or some other factors more? You or me might > disagree with some of those decisions… perhaps > on good grounds. I’m not sure the overall situation > would be better if we somehow got to override > the wg opinions. (Except of course on clear > issues that fulfil Discuss criteria.) > > Jari >
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail