Bob Smart wrote:
That being the case it might be nice to separate out the common character
set and encoding stuff into a separate RFC: "Character Sets and Encodings
for Internet Mail Messages". So there would be 3 rfcs. Alternatively
Keith's RFC can reference rfc-xxxx for this stuff. But the latter will
be a bit strange because there will be aspects which are not used in rfc-xxxx
(namely the short [single character] names for encodings and character
sets, and the _ in quoted-printable). The one character "names" for
character sets and encodings are an essential feature of Keith's proposal
in interoperating with existing software without embedding the real info
in very large amounts of junk.
Well I have written an internet draft "Character mnemonics and
character sets" RFC-CHAR which was written for the purpose of defining
character sets completely, and to give them names, for use in other
internet rfcs, such as RFC-XXXX and RFC-MNEM.
Are you suggesting another RFC with some other content but with
quite some overlap, or is this the information you were looking for?
Keld