Bruce Lilly wrote:
> BCP 18 (RFC 2277, Frank) recommends an internationalization
> considerations section
Oh, that beast, a MUST UTF-8, not less. Didn't make it into
RfC 3912, can I declare it "broken by design" and return to
RfC 954, please ? It took me hours to find RfC 1032 for RFCI.
While we're at it, did you see draft-hoffman-utf8-rfcs-00.txt ?
OTOH Paul saw no problem to submit some I-Ds without a dummy
IANA section - and for gopher I even asked, after all there is
this IANA URI scheme registry, they might wish to update it.
> If the IETF feels that internationalization is an important
> issue, a similar guideline prompting authors/editors to
> include, and reviewers to review such a section might be
> worth adding.
Maybe. OTOH it wouldn't be polite to write "SMTP error texts
are i-default US-ASCII, stupid, so that's what you put in an
SPF exp= explanation, for more I18N you could use a http URL".
Thinking about IANA doesn't upset me, it's rather harmless,
just one of the dozens of nits distributed in at least three
obscure texts, none of them an RfC.
The IPR boilerplate makes me mad, but unfortunately the authors
of xml2rfc didn't adopt my ipr="full<meep>" or ipr="fulleula"
proposals. Insert four-letter word for <meep>. At most three
lines pointing to a "creative commons BY SA license" should be
good enough for most I-Ds.
Bye, Frank
_______________________________________________
Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf