On Tue, Apr 14, 2015 at 10:12 AM, Terry Zink <[email protected]> wrote:
> But there's no way Google Apps and Microsoft's Office 365 (for example) > can publish DNS entries for all of its small, medium, and large businesses > that use its service and subscribe to mailing lists, because many times > those companies don't control the DNS for their customers. They'd (we'd) > have to get customers to update their DNS entries for every mailing list > they use if we don't have access to their DNS. Getting customers to update > their DNS is almost as pleasant as getting my teeth cleaned. > ...and remove entries when one of them stops using a mailing list. And for all we know this might happen with such scale that it begins to affect DNS caching of other useful data. > That's what we mean when we say it doesn't scale. Right. And since the largest problem is with the largest operators (because they have the biggest impact), a solution they aren't likely to adopt is probably a waste of precious working group resources. It's not "marketing" to decide to abandon a protocol that nobody will actually use. Rather, it's a highly pragmatic engineering (and working group) decision. -MSK
_______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
