Yoav Nir writes: > This draft represents a total shirking of our responsibility. Rather > than decide on one protocol that is "best" or even arbitrarily > choosing one that is "good enough", it proposes to build a framework > so that everyone and their dog can have their own method. This is a > nightmare for developers: since you can't know what method the peer > will support, you have to implement all of them.
Partially yes, but unfortunately all of the authors of those actual protocols decided that they wanted to continue publishing those drafts as individual RFCs, and each of them used different way to negotiate them, so there was no way to even implement multiple of them. At least this drafts gives you that option to implement multiple of them if you want. This draft only provides instructions for those other draft authors so they can at least common methods to negotiate the feature and use common method to trasmit data between peers. -- kivi...@iki.fi _______________________________________________ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
