Re: Open Issue: Splitting of local-part into labels and where?

[email protected] (Claus Färber)
Newsgroups gmane.ietf.imaa
Organization KDE
Message-ID <[email protected]>
Marc Mutz <[email protected]> schrieb/wrote:
> The question of whether or not to split the dequoted local-part into
> labels and if so, at which delimiter characters, remains unanswered in
> the -00 draft.

Well, in draft-faerber-i18n-email-netnews-names-00.txt I suggested this
list:

     SP / %x00-1F / "." / "@" / "+" / "%" / "=" / "/" / "," / ";" / ":"
     / "!" / "(" / ")" / "[" / "]" / "<" / ">"

     [[RATIONALE: As much delimiters as possible are used to increase
     the chance that the encoding of individual parts of the identifier
     are encoded the same way when included in other identifiers:
     "@" - used to separate local-part and domain name.
     "+" - used by some mailers for subaddressing
     "%" - used by some MTAs to embed domains within the local-part of
           email addresses ("percent-hack")
     "=" - used within MIXER (RFC 2156)
     "/" - used wihtin MIXER (RFC 2156), used as a newsgroup component
           separator in some leagacy non-RFC BBS networks.
     ",", ";" - used to separate identifiers in many positions
     ":" - used to seperate (obsolete) source routes from the
           destination address
     " " - used to separate source routes from each other.
     "!" - used as a separator within the Path header in RFC 1036,
           used as a address separator within (obsolete) UUCP bang
           addresses
     "(", ")" - used for comments, used within the replacement for some
           seperators according to MIXER (e.g. "(a)" instead of "@")
     "[", "]", "<", ">" - as precaution     ]]

And all Unicode characters that have a compatibility mapping to one of
those, of course.

We might want to add control characters - just in case they appear.

I'm not quite sure about the quoting characters ``"'' and ``\''. If we  
apply toASCII/toUnicode after dequoting the local part, there's no  
reason to include them. If we keep some quotes (canonicalised to the  
minimal quoted version), we should probably include them.

Claus
-- 
http://www.faerber.muc.de/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.