On Jul 20, 2006, at 11:36 AM, Barry Leiba wrote:
We should not be thinking about changing IDNA or RFC 2822 in the
DKIM WG.
The chairs agree, and the chairs also note that, related to this,
we have said that we will also mostly not be thinking about how to
work with EAI here. I say "mostly" because there's a likely
outcome for much of what EAI's doing, and we shouldn't make changes
to DKIM that will interoperate badly with that outcome.
The suggested change does not affect RFC2822 or IDNA.
The DKIM base draft has a rather fundamental problem. The definition
for sub-domain is both insufficient and erroneous. Also there is no
requirement for DKIM to even mention IDNA, nor does this reference
add any requisite definitions pertaining to DKIM. IDNA defines a
process for converting between Unicode strings for visual display and
host or domain name suitable strings. DKIM will _never_ perform any
of these conversions. Unless there is some process that detects
invalid ACE labels, which does not appear to be defined in RFC3490,
there is no reason to even mention this document. IDNA is required
when defining MUA interaction with DKIM information, which is
excluded from the DKIM base. The need to specify label length could
be seen as having increased importance in regard to the i=
parameter. When i= sub-domains are used, there are no other check
made on the validity of these labels.
----------
Remove:
2.5 Imported ABNF Tokens
RFC2821 sub-domain token reference
References to RFC3492 following i= and d= signature tag definitions:
Internationalized domain names MUST be punycode-encoded
[RFC3492].
-----------
Add (prior to or in Section 3):
ABNF:
hyphen = %x2D ; "-"
ldh = ALPHA | DIGIT | hyphen
let-dig = ALPHA | DIGIT
sub-domain = let-dig [*61(ldh) let-dig]
----------
----------
As reference:
(The referenced ABNF used in the DKIM base.)
RFC2821:
Let-dig = ALPHA / DIGIT
Ldh-str = *( ALPHA / DIGIT / "-" ) Let-dig
sub-domain = Let-dig [Ldh-str]
-----
RFC1034 (STD13):
The following syntax will result in fewer problems with many
applications that use domain names (e.g., mail, TELNET).
<label> ::= <letter> [ [ <ldh-str> ] <let-dig> ]
<ldh-str> ::= <let-dig-hyp> | <let-dig-hyp> <ldh-str>
<let-dig-hyp> ::= <let-dig> | "-"
<let-dig> ::= <letter> | <digit>
-----
ICANN/IANA: (the wild)
Consistent example of current domain name policy:
http://www.iana.org/cctld/specifications-policies-cctlds-01apr02.htm
alpha = %x41-5A / %x61-7A ; A-Z / a-z
digit = %x30-39 ; 0-9
ldh = alpha / digit / dash
id-prefix = alpha / digit
label = id-prefix [*61ldh id-prefix]
-Doug
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html