ietf-dkim
[Top] [All Lists]

Re: [ietf-dkim] ISSUE: non-ascii header text

2011-04-20 16:29:31
On 4/20/11 7:09 AM, John R. Levine wrote:
Is there anything that actually needs to be done with a UTF-8 header that
is not covered already in our DKIm spec.?
No, it's fine, so long as we make my proposed changes that clarify that
the bits of domain names in the DKIM-Signature: header (d= i= s=) are
represented as A-labels.
http://tools.ietf.org/html/draft-ietf-dkim-rfc4871bis-06#section-3.5

d= ...
       Internationalized domain names MUST be encoded as described in
       [RFC3490  <http://tools.ietf.org/html/rfc3490>].

Should be changed to:

Internationalized domain names MUST be encoded as Non-Reserved LDH, 
A-Labels as described in RFC5891, or equivalent U-Labels.  Validation 
therefore ensures U-Labels resolve DKIM resources published at valid 
A-Labels.  In some cases, labels that were valid per RFC3492 may need 
corresponding resources published at different domains. This may entail 
expressing labels using only lower case characters, for example.  
U-Labels SHOULD be used whenever UTF-8 is known to be supported by the 
receiver.  Otherwise, recipients will be unable to discern relationships 
with email domains also expressed in UTF-8 when A-Labels are used within 
DKIM header fields.

-Doug


_______________________________________________
NOTE WELL: This list operates according to 
http://mipassoc.org/dkim/ietf-list-rules.html