Hi Paul,

I can't really, as a DNS software vendor, say how much the draft is useful in general, but it looks interesting.

If I understand the background correctly, it might also help to declare that the DNS software vendors SHOULD NOT develop tools that automatically convert DUJ into DDNS and send it to a nameserver.

A nit: all examples in your draft have unmatching square brackets :)

Some of the little specific requirements look weird or odd to me, like 'The FQDN MUST NOT end with "." ' (isn't this actually a crime in DNSOP?) 'The FQDN MUST NOT contain a wildcard' (this might be a blocking limitation for potential users)...

Libor

On 30. 01. 25 20:40, Paul Hoffman wrote:
Greetings again. The following is a proposal to help end-users who are told "please 
enter this record in your zone to prove your existence". It simplifies the process 
without automating it; in short, it makes copy-and-pasting more likely to work, 
particularly for the _label names that are being used more. (DomainConnect is working on 
automation, but with a different target audience.)

If this interests you, please read the short draft, particularly the use case 
and design descriptions in the introduction. Those sections describe why the 
format is purposely limited for this narrow use case.

--Paul Hoffman


A new version of Internet-Draft draft-hoffman-duj-00.txt has been successfully
submitted by Paul Hoffman and posted to the IETF repository.

Name:     draft-hoffman-duj
Revision: 00
Title:    DNS Update with JSON
Date:     2025-01-30
Group:    Individual Submission
Pages:    8
URL:      https://www.ietf.org/archive/id/draft-hoffman-duj-00.txt
Status:   https://datatracker.ietf.org/doc/draft-hoffman-duj
HTMLized: https://datatracker.ietf.org/doc/html/draft-hoffman-duj


Abstract:

   It is common for service providers such as certificate authorities
   and social media providers to want users to update the users' zones
   to prove that they control those zones, or to add other features.
   Currently, service providers tell users to do this using human
   language describing the resource record type and data values to enter
   into the zone.  This document describes a text format, called "DNS
   update with JSON" or "DUJ", for such a service provider to give to a
   user, with the expectation that the user would copy and paste the
   text to their DNS operator to update the user's zone.  DNS operators
   who know how to handle DUJ strings will make the update process
   easier and more predictable for their users.

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

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

Reply via email to