[DNSOP] Re: [Ext] Re: AD review of draft-ietf-dnsop-structured-dns-error-19

[Paul Hoffman <[e-mail]>]

On May 8, 2026, at 06:27, Eric Vyncke (evyncke) <evyncke=[e-mail]> wrote:
> 
> Basically, I still a problem with the support of only one language in a *human readable* reply. I will think more over the weekend, but I am afraid that a change in the I-D s/human-readable/machine-readable/ or the support for multiple languages is required.

In order to make such a change be parsable JSON, the "j" and "o" and "l" fields would have to be lists of strings, not strings themselves. Such a requirement is very likely to cause mis-implementation.

In the case where a zone owner wants to emit "j" and "o" fields in multiple languages, they still can, using whatever punctuation they want. In such a case, they should omit the "l" field because that field only allows a single language tag.

If you want to complicate things, we can say that if the "j" and "o" fields contain a "|" character, the "l" field can be a list of language tags using "|" between them in the same order. That causes parsing beyond JSON and thus increases the attack surface, which I think should be avoided.

--Paul Hoffman, injured veteran of the language tag wars of the 90's and 00's