Re: X-* header fields (Was: Getting 2822 to Draft)

> But *why* would an implementation care about the publication 
> guidelines for the field? That's the *only* thing "X-" tells you.
because any field that doesn't have a published definition probably 
isn't something that should be implemented on a widespread basis - 
since without a definition you have no reason to expect it to work 
predictably from one implementation to another.
admittedly, this inference might be a bit subtle.  I see no harm in 
making it more explicit.
Keith