Re: [apps-discuss] Status of the malformed mail BCP

[Peter Koch <[e-mail]>]

On Wed, Aug 10, 2011 at 09:10:38AM -0700, Murray S. Kucherawy wrote:

> IANA says they can indeed handle such a thing.  We would need to do the usual registry creation procedures including specifying what the fields are and the rules for making changes, and then give them some guidance about how we'd like it to be presented.

that IANA is technically capable or "willing" to do this does not
necessarily mean it is in line with IETF processes.  A registry
is not just "a collection of stuff" but would usually exist
for protocol parameters(!) to be uniquely identified.  I have a hard time
seeing that violations of a protocol spec qualify here.

> So I think my next step is to convert the existing document into exactly that.  Since the main objection to doing it as an RFC is the idea that it might need to be changed often, perhaps we should go with Expert Review instead of one of the rules that says a specification has to exist.  Any comments on that point?

This is so much Monty Python that i start to love it. Assume we have Expert
Review for this registry. What if a candidate brokenness fails the
review process - can the implementor enhance their misimplementation to
have it recognized (and eventually registered) as a reviewed protocol violation?

-Peter