> Hi Jacob,
> Perhaps not as elegant and concise, but a workaround would be to temporarily
> (until 6844-bis gets incorporated into the Baseline Requirements) prohibit
> multiple parameters in the same CAA record and instead require that multiple
> parameters span multiple issue/issuewild
I prefer the RFC 6844-bis interpretation, but I note that this is not
compliant
with the Baseline Requirements, which mandate RFC 6844. It's not clear
what that means though since as you correctly note, RFC 6844 contradicts
itself on this point.
I would support fixing the baseline requirements
Hi Jacob,
Perhaps not as elegant and concise, but a workaround would be to temporarily
(until 6844-bis gets incorporated into the Baseline Requirements) prohibit
multiple parameters in the same CAA record and instead require that multiple
parameters span multiple issue/issuewild records with
