I created this as a “.policy”, but unfortunately left out the new Content-Type that would need to be declared. The idea of the rough draft was really to give folks an idea of what it would like, and stir the discussion. We could obviously change this to something that is more well-known (txt or similar) so that we don’t need to do this.
-- Alex Brotman Sr. Engineer, Anti-Abuse Comcast x5364 From: David Illsley [mailto:[email protected]] Sent: Monday, July 17, 2017 3:37 PM To: Brotman, Alexander <[email protected]> Cc: [email protected] Subject: Re: [Uta] MTA-STS: A Key-Value Alternative Is there a proposed Media Type/Content Type header value for this (can't see one in the diff)? One of the nice things about JSON is that web servers are likely to serve .json files as something appropriate out of the box. On Mon, Jul 17, 2017 at 8:17 PM, Brotman, Alexander <[email protected]<mailto:[email protected]>> wrote: Hello, The authors of the MTA-STS draft and the UTA group have been attempting to reach a consensus on the issue of JSON versus KV for the policy file that is served via HTTPS. In order to attempt to get over that issue, we've made a rough draft[1] that now uses key-value pairs instead of JSON. Overall, our preference would be to stay with JSON as the alteration will break existing and in-progress implementations, but we'd really like to move forward. We'd like to work toward a conclusion and welcome comments from the group. [1] https://raw.githubusercontent.com/mrisher/smtp-sts/KV_Version/mta-sts.txt -- Alex Brotman Sr. Engineer, Anti-Abuse Comcast x5364 _______________________________________________ Uta mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/uta
_______________________________________________ Uta mailing list [email protected] https://www.ietf.org/mailman/listinfo/uta
