
Hi Ned, Thank you for the useful information buried in the unnecessary lecture. I am well aware that IANA != IESG. I began my search there because they have documents and instructions related to MIME type registration. I did search more widely without result. I was not looking for a license to not follow current rules, merely an explanation of your request related to security and a major image file format seemed like a good place to start. I read RFC4288 as I was preparing the registration template but I did not fully understand the import of the *fifth* bullet in Section 4.6. I will revise the section on security then submit my registration to the IESG. Regards -Mark On 07/09/2010 09:24, Ned Freed wrote:
I could find no information on the IANA web site that provides a definitive definition of "recognized" in this context. Um, exactly what part of "the IESG makes the determination" did you fail to understand? IANA != IESG. It would be frankly astonishing if the rules for how the IESG determines standards body status could be found on the IANA site.
Having served on the IESG in the past, I also doubt very much the IESG has bothered to create formalized rules for what consistitutes a recognized standards body - maybe they should, but I doubt they have. So IMO it's also pretty unlikely you'll find such rules on the IESG's site either, but at least you'd be looking in the right place...
However I believe Khronos should qualify as it is a widely supported industry consortium with responsibility for several well known standards. That's my reading as well, but again, this is up to the IESG to determine.
....