before we get too semantically bogged down, a domain name implys dns
registration otherwise it is a label of convenience
Bill Oxley
Messaging Engineer
Cox Communications, Inc
404-847-6397
-----Original Message-----
From: ietf-dkim-bounces(_at_)mipassoc(_dot_)org
[mailto:ietf-dkim-bounces(_at_)mipassoc(_dot_)org] On Behalf Of Steve Atkins
Sent: Thursday, March 26, 2009 9:21 PM
To: DKIM IETF WG
Subject: Re: [ietf-dkim] (registered) domain name (Re: errata revision: opaque)
On Mar 26, 2009, at 6:10 PM, Dave CROCKER wrote:
Steve Atkins wrote:
On Mar 26, 2009, at 3:49 PM, Dave CROCKER wrote:
6. RFC4871 Section 2.9 Signing Domain Identifier (SDID)
...
New:
A single domain name that is the mandatory payload output of
DKIM and that refers to the identity claiming
responsibility for
introduction of a message into the mail stream. For DKIM
processing, the name has only basic domain name semantics; any
possible owner-specific semantics is outside the scope of
DKIM.
A single domain name -> A single, registered domain name
Registered with who?
If the SDID is, say, hatstand.beartrap.blighty.com?
Registered with the DNS, the global distributed hierarchical service.
From the other uses of this language I'm seeing on the net, this
isn't said explicitly. Do you really feel that the meaning is not
clear?
Registered means that the string is registered with a registry.
That's not something I'd want the language to even hint at, let alone
actually say. It's going to lead to confusion when explaining this to
people, as you'll need to directly contradict the wording in the spec
when you reassure them that, no, there is no central DKIM registry.
Cheers,
Steve
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html