Jim Fenton wrote:
Dave Crocker wrote:
Having non-normative text that describes it serves to promote the idea
but not couple it with the fate of ADSP.
Having the ADSP result depend on non-normative language in this case
does not meet the bar of interoperability that we need to achieve.
Making it non-normative means that two spec-compliant implementations of
ADSP would return completely different results for non-existent domains.
Sorry, but I can't let this one go by without asking:
I completely do not understand the claim of non-"interoperability" here.
Since the record(s) in question are not created with ADSP in mind, then the
domain owner cannot be said to be participating in ADSP, with respect to this
check.
SO how is inter-operation hurt or hindered by this specification's making the
check normative vs. non-normative?
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html