|
Hi, Paul and Patrick,
Unassigned code points have diverse
implications on
stability of DNS and uniformity of global IDN
experiences.
I found somewhat obscure and unclear
terminologies in the section 6
of stringprep. That may come from my lack of
knowledge for
previous discussions, but for all late joiners
including me,
please
reply with clear answers for
the
following
**asterisked** interposed comments.
Thanks.
6. Unassigned Code Points in Stringprep Profiles
This section describes two different types of strings in typical protocols where internationalized strings are used: "stored strings" and "queries". Of course, different Internet protocols use strings very differently, so these terms cannot be used exactly in every protocol that needs to use stringprep. ** "CANNOT BE USED EXACTLY in EVERY
PROTOCOL" should be more
specific regarding to every
other protocols not mentioned in
this paragraph
in order
to eliminate
confusions of
implementors.
In general, "stored strings" are strings
** "IN GENERAL" ? ANY
Exceptional cases worth to research ?
that are used in protocol identifiers and named entities, such as names in digital certificates, DNS domain name parts, and names of SNMP objects. ** "DNS DOMAIN NAME PARTS"
point to what ? maybe those in any zone files.
all
the host names in any
webpages and
all the email addresses in
electronic address books is "queries" or "stored strings"?
"Queries" are strings that are used to match against strings that are stored identifiers, such as user-entered names for digital certificate authorities, DNS lookups, and SNMP requests. ** Email
composing windows accept TO: addresee before you
send.
Are both sender/recipient
addresses "stored strings" or "queries" for email
clients?
DNS lookups do not occur in email
composing/account-setup window. Recipient's
IDN email address will be nameprep/ACE
encoded in email clients without
any DNS lookup.
** What occurs when TAGALOG email
addresses are specified in the TO: addressee
in the email clients composing
window based on current nameprep without TAGALOG
supports ?
** SMTP servers receive
sender/recipient addresses from email clients by SMTP
protocol. Then,Does SMTP server
regard the incoming email
addresses as "stored ones" or
"queries"? it is
true that most SMTP servers will simply pass through those
ACE hostnames without any nameprep
validity check.
** What if sender's ACEed Tagalog
email address which is unassigned and invalid yet in
the current version
of nameprep?
should the recipient be warned for security reasons
?
All code points not assigned in the character repertoire named in the stringprep profile are called "unassigned code points". Stored strings using the profile MUST NOT contain any unassigned code points. Queries for matching strings MAY contain unassigned code points. Note that this is the only part of this document where the requirements for queries differs from the requirements for stored strings. ** Does this mean that old
nameprep/ACE email applications can't send
emails
to recipients with future TAGALOG IDN email addresses
without upgrading to new
version of nameprep? Or allowed with warnings?
Soobok Lee
|