>From what I know of my organization, it would be easier to create a separate >hostname (policy._mta_sts.comcast.net) than to get some content served by the >main domain's realm (comcast.net/foo/bar/sts-policy). I'm not saying it can't >be done, just that I interact often with the DNS group I would need to contact >to get records published versus the web team.
-- Alex Brotman Engineer, Anti-Abuse Comcast x5364 ________________________________________ From: Uta <[email protected]> on behalf of John Levine <[email protected]> Sent: Sunday, May 1, 2016 5:00 PM To: [email protected] Subject: Re: [Uta] draft-brotman-mta-sts/ >So using the domain as-is and dealing with any provisioning politics >looks to be the only sensible option. Not to put Daniel on the spot, but since he happens to work for one of the largest mail providers in the world, would it be a problem to put the STS stuff at URLs like these? https://google.com/.well-known/sts-policy https://gmail.com/.well-known/sts-policy My impression from the converstation in B.A. was that it'd be a big problem. R's, John _______________________________________________ Uta mailing list [email protected] https://www.ietf.org/mailman/listinfo/uta _______________________________________________ Uta mailing list [email protected] https://www.ietf.org/mailman/listinfo/uta
