On Wed, Jul 22, 2020 at 6:41 PM Ben Schwartz <bemasc= 40google....@dmarc.ietf.org> wrote:
> On Wed, Jul 22, 2020 at 9:20 PM Wellington, Brian <bwelling= > 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! > Definitions to use: Required: Must be present, and implies Mandatory to Implement. (Having a Required element that wasn't MTI would be silly.) Mandatory to Implement: exactly what it says. Optional: Neither Required nor MTI. Mandatory should only ever be used as MTI, otherwise it leads to confusion (i.e. needing subordinate phrase to disambiguate, e.g. mandatory to implement vs mandatory to include.) Then have a table of key names, and which kind they are (Req, MTI, Opt). That should clear it up, I think. Brian
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
