more fodder for the principle of: don't write a spec until you have a good working reference implementation. ietf has really lost their way on this.
OCR Output (chars: 953)
Molasses has helped refine the MLS spec
The primary contribution of molasses has been in detecting errors in the
specification and other implementations through unit and interoperability
testing. Molasses implements most of MLS draft 6. Why not all of draft 6?
There was an error in the spec that made it impossible for members to be
added to any group. This broke all the unit tests that create non-trivial
groups. Errors like this are hard to catch just by reading the spec; they
require some amount of automated digging. Once they are found, the
necessary revisions are tend to be pretty obvious, and they are swiftly
incorporated into the subsequent draft.
Iterating this discovery/patching process using molasses has given me a
chance to put the spec through its paces and help make things clearer. This
winter internship (“winternship”) project has been a great experience,
especially as a first-time IETF contributor.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either! We adhere to an adapted version of the TootCat Code of Conduct and have documented a list of blocked instances. Ash is the admin and is supported by Fuzzface, Brian!, and Daniel Glus as moderators. Hosting costs are largely covered by our generous supporters on Patreon – thanks for all the help!