On 23. 07. 20 3:41, Ben Schwartz wrote: > On Wed, Jul 22, 2020 at 9:20 PM Wellington, Brian > <bwelling=40akamai....@dmarc.ietf.org <mailto:40akamai....@dmarc.ietf.org>> > wrote: > > ok. So, what this means is that keys listed in the “mandatory” parameter > must be included as parameters, and are required to be understood by clients. > The set of “automatically mandatory” keys are required to be understood by > clients, but are not required in the RR. > > > From the client's perspective, "mandatory" means "if you don't understand all > of these keys, discard the RR". Each key on the list is "mandatory" in the > sense that it conveys information that is required to make correct use of the > RR. All other keys are optional: they can be ignored and the RR will still > "work" for connection establishment. > > "Automatically mandatory" means "this key is mandatory if it is present". > > If you can think of a clearer presentation, please send text!
I'm not native English speaker and I personally find confusing that sequence of characters "mandatory" is used as verb and also as name of the key. "optional mandatory" sounds like a joke. To clarify this I propose to rename "mandatory" field to "critical", which terminologically aligns with X.509 and also LDAP. -- Petr Špaček @ CZ.NIC _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
