ietf-dkim
[Top] [All Lists]

Re: [ietf-dkim] The challenge of an 'nxdomain' straw poll

2008-05-24 12:30:02

On May 24, 2008, at 11:37 AM, Dave Crocker wrote:

Arvel Hathcock wrote:
The phrasing of the query for a poll is a challenge, here.

Nope.  The question is on the removal of the NXDOMAIN step from the  
working group draft.

That's one question, yes, but there are more.  While I'm not sure it  
captures
the available choices, here's an attempt:


There really are two sets of choices:


Degree of requirement
---------------------

1. Make a domain 'validity' test mandatory.

ADSP is an extension showing the level of a domain's use of DKIM with  
SMTP.  Since this is being introduced into existing infrastructure,  
requests for ADSP records are therefore optional.  In addition,  
compliance with ADSP should not mandate more transactions than a  
receiving host finds merit in making.  ADSP can recommend a series of  
SMTP related checks using SHOULD to reduce the number of domains where  
an ADSP records would be required to preclude spoofing with otherwise  
non-SMTP sub-domains.

2. Make a 'validity' test optional (SHOULD vs. MAY)

3. Remove a 'validity' test


Type of 'validity' test
-----------------------

1. NXDomain

2. RFC2821bis

To ensure interchange, ADSP MUST indicate which protocol has adopted  
DKIM.

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

<Prev in Thread] Current Thread [Next in Thread>