Hi Gavin,I don't think it's sufficient. It reads (or can be interpreted so) what the value is but not what the JSON representation ought to be.
This is a specific issue with JSON, that some numbers can be natively represented as JSON number and some not - so that string is used instead in those cases [1]. Even if uint32 can be safely represented in JSON people mix them up in the wild with something like { "ttl": "3600" }, so it's more than stating the obvious imho.
The proposed addition " represented as JSON Number" with a reference to rfc8259 serves clarity.
[1] https://spec.openapis.org/registry/format/ Kind Regards, Pawel On 22.01.26 17:13, Gavin Brown wrote:
Hi Pawel, I added a paragraph at the bottom of Section 2, above the example: As specified in Section 8 of [RFC2181], a TTL value is a "an unsigned number, with a minimum value of 0, and a maximum value of 2147483647. That is, a maximum of 2^31 - 1." Is this insufficiently precise? G.On 22 Jan 2026, at 4:00 pm, Pawel Kowalik <[email protected]> wrote: Thx Gavin, I didn't notice this changed in -04 though. Kind Regards, Pawel On 22.01.26 11:24, Gavin Brown wrote:[snip] "TTL values MUST be unsigned integers in the range 0-2,147,483,647" I suggest to add " represented as JSON Number", to avoid packing number in string.Thanks, I will look to incorporate this feedback.-- Gavin Brown Principal Engineer, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
