>For those, who do not work at the IETF, the spec comes before the >implementation. If the spec defines a grammar that looks as >authoritative as the one in section 5.4, then an implementation might just >solve a decision problem whether a string matches >the grammar or not. This is a yes or no question. But as you have pointed out, >the authors have an implementation in mind that >leaks back into the spec:
As an example libopendmarc [1] is willing to be "generous" : >/* >* Be generous. Accept, for example, "p=r, p=rej, or any >* left match of "reject". >*/ >if (strncasecmp((char *)vp, "reject", strlen((char *)vp)) == 0) > pctx->p = DMARC_RECORD_P_REJECT; [1] https://github.com/trusteddomainproject/OpenDMARC/blob/2aafb015a56d40e8a1949dc6d2ab0057aaf8b32f/libopendmarc/opendmarc_policy.c#L1009
_______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
