Pekka Savola: Looking up RFC 3280, from the Trust Anchor option
(6.2.3), it strikes me that the FQDN part (at least) may be something
that may be subject to the i18n requirements for strings in the
specifications (something that always comes up in IESG review, and is
in ID nits).  I know very little about this myself, but this may be
something that a subject matter expert from apps area (for example)
might be able to help with.

--------------

Jari Arkko: I'm not an expert on this either, but it seems that the
FQDN internationalization cab be solved rather easily. Specifically,
RFC 3490 defines internationalized domain names (IDNs) through ToAscii
and FromAscii operations that map international names to good old
FQDNs and map. Protocols with with FQDN slots can most of the time
operate without awareness of IDNs.

So here are my suggested text modifications. Add to Section 6.2.3
under "Name":

    In the FQDN case the Name field is an "IDN-unaware domain
    name slot" as defined in [RFC3490].  That is, it can contain
    only ASCII characters.  An implementation MAY support
    internationalized domain names (IDNs) using the ToASCII
    operation; see [RFC3490] for more information.

--------------

--------------