Re: Comments to draft-freed-charset-reg-04.txt

[Larry Masinter <masinter@parc.xerox.com>]

> > Registered charsets MUST conform to the definition of a
> > "charset" given above.  In addition, charsets intended for use
> > in MIME content types under the "text" top-level type must
> > conform to the restrictions on that type described in RFC
> > 2045. All registered charsets MUST note whether or not they
> > are suitable for use in MIME.
> 
> This is MIME as defined in RFC 2045. Other protocols, for
> better or for worse, in particular HTTP, have made wide
> use of MIME while relaxing certain restrictions for the
> "text" top level type. 

Actually, I think the paragraph is fine as it stands.
You shouldn't try to send an HTML file encoded in EBCDIC,
no matter what your 'charset' is. MIME is MIME. If HTTP
allows you to send some things that aren't exactly MIME,
it doesn't change MIME, it's just a headache for gateways
forward between HTTP and MIME-compliant implementations.