On 5/5/2015 1:33 PM, Scott Kitterman wrote:
On May 5, 2015 1:25:43 PM EDT, Hector Santos <hsan...@isdg.net> wrote:
The main point would be that DSAP protocols can still be completed
making the registration part out of scope. It would be part of the
publishing and adoption, migration section as a short or long prospect.
The same was true with SPF -- you had to wait until domains were
published and registered. Btw, What is your SPF payoff? Your average
daily SPF rejection?
It is up to yahoo and others if they want to put an effort of
registering domains in order to white list them. That shouldn't stop
an issue for most domains and it should not be a barrier to having a
3rd party authorization protocol.
As a receiver, I am willing to do a DNS call to the ADID/SDID pair
(when it differs) to see if there is an authorization. I don't really
wish to be changing code to read/write double signatures. This will
raise the adoption barrier.
Wrapping a 'somebody else's problem field' around the registration piece of
this doesn't make it any more feasible.
Feasibility? If we are basing progress solely on that, we wouldn't be
far along. IETF protocol engineering generally leaves optimization
considerations for implementations to work out.
The two problems are different. Its the same SPF had and still has.
Do you think its fair that the big domains are exerting high SPF
processing pressure with multiple DNS calls per transaction only to
result in soft or neutral? They are not sure. What if they decided
to switch to a hard fail? Will they get it right?
My proposal is based on the fact that DMARC overhead is already being
done, thus making it feasible to consider a piggy back design that
allows for a ATPS lookup. DMARC offers 3rd party extensions for this
purpose. It would be optional. Will there ever be high payoff
results? Probably not for a long time, but who knows. Maybe there
can be an in-band optimizer:
5322.DKIM-ATPS: The ADID creates ATPS records. Please Check the
ADID/SDID.
and let people decide if that offers some feasibility in minimizing
the lookup or if just always does a lookup anyway and crosses its finger.
--
HLS
_______________________________________________
dmarc mailing list
dmarc@ietf.org
https://www.ietf.org/mailman/listinfo/dmarc
