Warren Kumari has entered the following ballot position for draft-ietf-uta-smtp-tlsrpt-18: Discuss
When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-uta-smtp-tlsrpt/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- I'm guessing that I'm simply misunderstanding / not understanding (reformatted for clarity): 1: If multiple TXT records for "_smtp._tls" are returned by the resolver, records which do not begin with "v=TLSRPTv1;" are discarded. 2: If the number of resulting records is not one, senders MUST assume the recipient domain does not implement TLSRPT. 3: If the resulting TXT record contains multiple strings, then the record MUST be treated as if those strings are concatenated together without adding spaces. So, if I query for '_smtp._tls.example.com' and get back: "v=TLSRPTv1;rua=mailto:[email protected]"; "v=TLSRPTv3;rua=mailto:[email protected]"; I throw away the one that contains 'bar', fair enough, got it. What I don't understand is what a record would look like which is a single record (#2), but that contains multiple strings (#3). Can you provide an example of a TXT record with multiple strings? I don't *think* that this is just me being dense, and so I think that the document needs to better explain this / include the example. _______________________________________________ Uta mailing list [email protected] https://www.ietf.org/mailman/listinfo/uta
