On Wed, Apr 26, 2006 at 04:41:05PM -0700, Jim Fenton allegedly wrote: > Mark Delany wrote: > > [ re _dkim vs _domainkey ] > > > > Also worth considering is the s= option. If s=voip, would the address space > > be _dkvoip, etc? > > > Why, because the voip group might want to administer their keys
I was obviously being too obtuse. My point was that _domainkey is generic whereas _dkim is not. If people want to go down the non-generic path then it follows that for each service there should be a separate namespace (which would obviate the need for s= btw). My point being that a separate namespace for each service is likely to not scale well or admin well. Additionally it precludes the (easy) use of the same key across services. In short, I think _dkim is a bad idea even if it does save a whopping 5 bytes of query space. Mark. _______________________________________________ NOTE WELL: This list operates according to http://mipassoc.org/dkim/ietf-list-rules.html
