CORE, BEEP, DREG from 04 to 05:

1

• CORE, BEEP, DREG from 04 to 05
• I18N and L10N
• Marcos Sanz
• sanz_at_denic.de
• CRISP Working Group
• 59th IETF, ??
• March 2, 2004

2
IRIS-CORE

• Dropped constraint for name transcribability of
  entities and entity classes
• Explicitly added charset encodings definitions to
  the Transport Mapping Checklist
• XML in UTF-8 is recommended (default in absence
  of encoding-declaration and BOM, preferred by RFC
  2277)

3
IRIS-BEEP

• XML messages packages restricted to UTF-8 and
  UTF-16 (other encodings MUST NOT be used)

4
IRIS-DREG

• Datetimes must be in UTC
• Phone/fax in E.164 is recommended
• A server answering ltlanguageNotSupportedgt must
  now specify which language(s) by means of child
  ltunsupportedLanguagegt

5
IRIS-DREG (contd)

• Element ltutf8eMailgt renamed to ltIDNeMailgt
• ltfindDomainsByIDNNamegt
• ltexactMatchgt explicitly references equivalence of
  IDNs as of RFC3490
• ltbeginsWithgt and ltendsWithgt dropped (see next
  slide).

6
IRIS-DREG (contd)

• IDNA standard only defines equivalence, that
  works in terms of the ACE.
• Even if preparing IDN substrings by means of
  Nameprep() or ToUnicode(ToASCII()), collation has
  just begun.
• Collator strength? Contextual matching?
  Tailorings? Visit a world of oddities at
  http//www.unicode.org/reports/tr10/Searching
• Feeling that this is not the right time and place
  to define IDN matching.