[Ietf-not43] off-list comments on requirements

[Eric Brunner-Williams in Portland Maine]

Morning Andy,

> so I don't see the !43 process trying to tackle anything new in
> i18n space.

Suppose that instance A of !43 and instance B of !43 differ in some
aspect of mechanism or policy or ... that some property of !43 has
non-universal scope. Do you plan on discovering the scope boundaries
and negociating the reconcilliation of the property?

If so, isn't encoding a candidate for "some property"?

You can of course posit global scope for whatever. rfc954 maked no
assumption, and one could use EBCDIC, just to be unique, beautiful,
and consistent with the intent, and specification, of rfc954.

>          ... If XML or LDAP or MIME or whatever does not support
> i18n to the fullest extent possible

After doing i18n work pre-iso2022, post-iso2022, for XPG/3 locales,
for double-byte encodings, multi-byte encodings, wide- and multi-byte
encodings in three operating systems, I don't know what this means.

I think I know what it means for XML (see 4.3.3 of the 1.0 TR).

Well, keep me informed as I'm idly curious,
Eric