On Apr 14, 2009, at 3:40 PM, SM wrote:
Hi Daniel,
At 07:30 14-04-2009, Daniel Senie wrote:
I agree with Doug. The most reasonable course of action would be an
IETF document, perhaps a BCP, that indicates SMTP transports should
ONLY do MX lookups to find the mail server for a domain, and not fall
back on A records. I'd endorse this, and would work on such a
document
if there were interest. The big question is whether it would be done
in DNSOP, since it affects how DNS records are interpreted, or in the
defunct SMTP group's list, since it affects how mail servers
interpret
DNS information.
I don't think you can override a Draft Standard with a BCP. There
was a discussion about the fallback to A/AAAA RRs (implicit MX) last
year during a Last Call. The consensus was to keep it in the SMTP
standard. I doubt that any further discussion on the subject will
result in a different outcome.
See for example RFC 2644/BCP34, which updates RFC 1812, which is on
standards track. There is precedent for a BCP to recommend alteration
of the behavior of an earlier standard for the purposes of improving
security, and/or taking into account newer information or
observations. In the case of RFC2644/BCP34, the issue was that the
requirement for the default handling of directed broadcasts turned out
to be ill-advised.
As such I'm not convinced there is any issue with updating a standards
document with a BCP, having written one that did precisely that.
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
