> Since so many parts of the base specification are optional MAYs, and there is no prescribed mechanism for feature detection, there is no way to figure out if

> Since so many parts of the base specification are optional MAYs, and there is no prescribed mechanism for feature detection, there is no way to figure out if a server supports a particular feature of this spec without trying to do something and failing > The spec has made many breaking changes on the road to 1.0 Interestingly, most of the breaking changes on the road to 1.0 were about drastically reducing MAY in favor of MUSTs. Optional features were moved to named extensions, and there is now an explicit way to negotiate about those extensions. For anyone who was put off earlier on by the number of MAYs, know that we heard you loud and clear. It may (no pun intended) be worth another look.