[ietf-dkim] forward movement, please? (was RE: Are lookalike domains like parent domains?)

robert at barclayfamily.com robert at barclayfamily.com
Thu May 1 10:01:00 PDT 2008


> Date: Wed, 30 Apr 2008 15:12:34 -0700
> From: dhc at dcrocker.net
> To: arvel.hathcock at altn.com
> CC: ietf-dkim at mipassoc.org
> Subject: Re: [ietf-dkim] forward movement, please? (was RE:  Are lookalike domains like parent domains?)
> 
> 
> 
> Arvel Hathcock wrote:
> > I propose that the side advocating removal of the NXDOMAIN check agree 
> > to language which makes this step AT LEAST a SHOULD and preferably a MUST.
> 
> 
> Having the ADSP specification include normative text that calls for validating 
> the From field domain name does two things:
> 
> 1. Couples an entirely separate and more generally useful mechanism (checking 
> domain name validity) to one that is considerably more limited (ADSP).

For reasons I have shared before I have to disagree. The check for domain existence is not unrelated. In short the check for domain existence tells you whether something is a D about which it is valid to search for a P. The fact that people may already be doing this elsewhere and that it is useful for other reasons doesn't have any impact on the fact that this check gives you a hard algorithmic boundary for what entitiies ADSP is intended to apply to. We have a specification that is currently intended to cover a narrow and well defined set of entities, that is domains, and a check to tell whether a given entity is such a thing. 



> 
> 2. Modifies SMTP.  (Yes, really.)

As I think has been pointed out before here is the definition of the domain portion of addr-spec from rfc2822.
"The domain portion identifies the point to which the mail is   delivered. In the dot-atom form, this is interpreted as an Internet   domain name (either a host name or a mail exchanger name) as   described in [STD3, STD13, STD14]."  Wouldn't something have to exist to meet this specification? Or does the term Internet domain include things that don't exist but maybe could?






> 
> Having non-normative text that describes it serves to promote the idea but not 
> couple it with the fate of ADSP.




> 
> d/
> -- 
> 
>    Dave Crocker
>    Brandenburg InternetWorking
>    bbiw.net
> _______________________________________________
> NOTE WELL: This list operates according to 
> http://mipassoc.org/dkim/ietf-list-rules.html

_________________________________________________________________
Express yourself wherever you are. Mobilize!
http://www.gowindowslive.com/Mobile/Landing/Messenger/Default.aspx?Locale=en-US?ocid=TAG_APRIL
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mipassoc.org/pipermail/ietf-dkim/attachments/20080501/b1f690ce/attachment.html 


More information about the ietf-dkim mailing list