[DNSOP] Re: For consideration by DNSOP: "DNS Update with JSON"

[Pawel Kowalik]

Hi,

On 20.03.25 20:28, Petr Špaček wrote:

On 1/30/25 20:40, Paul Hoffman wrote:

Title:    DNS Update with JSON
Status:   https://datatracker.ietf.org/doc/draft-hoffman-duj

Ad version: 03

https://mailarchive.ietf.org/arch/msg/dnsop/8mW0o9JOkAkjgZTSP3SqLiLO8QA
Namely the mandatory RFC3597 syntax.

After the discussion in dnsop session today about escaping and doing DUJ64 only, and reading through all the discussions on list to date, I think we should adopt proposal by Robert Edmonds here: Using RFC3597 for RDATA portion of the record-data (which would get Base64 encoded anyway) will avoid lots of trouble with encoding and decoding.

Kind Regards,

Pawel

I don't think this is any good idea. Likely implementers of DUJ on the receiving side, at least for the copy-paste use case of unskilled users that Paul highlighted as main use case, will be front-end developers, not DNS experts. Making the format more complicated to decode and not understandable for them will just kill possible adoption of DUJ.

smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
DNSOP mailing list -- dnsop@ietf.org
To unsubscribe send an email to dnsop-le...@ietf.org