"If so, the IETF registration forms MUST be part of the language specification, and SHOULD be part of the specification starting at Candidate Recommendation status (or Last Call if the Working Group plans to have sufficient implementation experience to bypass Candidate Recommendation). "

20:11:10 [Ian]

DC: IETF area directors didn't say you had to have the mime type in registry before you could use it.

20:11:59 [DaveO]

hmm.. seeming less and less like an architectural principle and more like w3c process issue.

20:12:06 [Ian]

IJ: The text must be in spec, but isn't required to be registered.

20:12:15 [Stuart]

q?

20:12:15 [Ian]

q?

20:12:17 [TBray]

q+

20:12:30 [PaulC]

q+

20:12:41 [Ian]

DC: Area directors said "Don't want to put in the registry until it goes to Rec."

20:12:52 [Ian]

DC: They prefer to just have internet draft published every 6 months.

20:13:03 [Ian]

DC: They would rather your type not be in registry but not in internet draft index.

20:13:20 [Ian]

CL: What can we point to when people tell us we are doing it wrong?

20:13:22 [Stuart]

ack TBray

20:13:54 [Ian]

TB: I agree with DO's point that this is a process issue. Let's rewrite finding to say that registration process must proceed in parallel with w3c process, and documents must be readily available from w3c specs.

20:14:08 [Ian]

DC: Water down more: Registration information is relevant and needs to be reviewed along with everything else in your spec.