James, Do you mean the section where the policy-string was declared? There are other references to RFC7493. If you'd like, I can add another reference to RFC7159 in the document as well. It was originally there to explicitly reference the section about the serialization for including the STS policy (which was a JSON body itself, which no longer is the case).
-- Alex Brotman Sr. Engineer, Anti-Abuse Comcast -----Original Message----- From: James Cloos [mailto:[email protected]] Sent: Friday, September 29, 2017 2:54 PM To: Brotman, Alexander <[email protected]> Cc: [email protected] Subject: Re: [Uta] Updated MTA-STS & TLSRPT >>>>> "BA" == Brotman, Alexander <[email protected]> writes: BA> TLSRPT: Changed the domains associated with reporting, added BA> examples for policy-strings, and added a MUST for not using l= for BA> the DKIM signature Looking at the diff, I noticed that the reference to RFC7159 (JSON) got dropped. Given that json is still in the draft, I can't tell whether that was intentional. -JimC -- James Cloos <[email protected]> OpenPGP: 0x997A9F17ED7DAEA6 _______________________________________________ Uta mailing list [email protected] https://www.ietf.org/mailman/listinfo/uta
