Excerpts from mail: 24-Apr-91 Re: Comments on Draft RFC Einar
Stefferud(_at_)ics(_dot_)uci(_dot_) (1192)
So, do we also have "TeX-iso-10646" and "SCRIBE'iso-10646" ad nauseum?
Where do all these get registered, and who decides what they mean?
Does this group have to stay in sesion forever to decide these things?
As per my previous message, I think that the established registration
procedures will suffice. I really doubt that there are going to be a
lot of these types, anyway.
Do we need to pre-define every possible combination that people will use?
Not if we define things as "building blocks". Thus, for example, we
don't need to define anything special about compression headers if we
have a compressed-message content-type, because all the other mechanisms
can then work on it recursively. Similarly for encrypted messages. It
seems to me that this is a simple and elegant solution that avoids
making the headers even more complex than they already are..