ietf-dkim
[Top] [All Lists]

[ietf-dkim] requirement for one ADSP record per DNS entry makes ADSP undeployable

2008-05-27 02:15:22

In order for ADSP to be of use, it must be easily deployable by 
enterprises and service providers.  Otherwise, there is no point in 
bothering to check for answers.  The absence of a parent label check 
will mean that enterprises must list an ADSP record for each and every 
DNS entry they have.  It is not unusual for enterprises to have tens of 
thousands of DNS entries.  The vast majority of enterprises make use of 
provisioning systems that takes years to update and deploy.  ADSP 
deployment is now dependent on those implementations.  Because of that 
ADSP adoption can be expected to lag dramatically behind DKIM.  The 
result will be that recipient sites will infer policy by the existence 
of records and hence implicitly implement a strict test.

Hence as things stand I expect ADSP to never be deployed, and I request 
active consideration of the provisioning systems in use.

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