> -----Original Message----- > From: Hollenbeck, Scott > Sent: Monday, January 5, 2026 11:17 AM > To: [email protected]; [email protected]; regext- > [email protected]; [email protected] > Subject: RE: [EXTERNAL] [regext] WG Last Call: draft-ietf-regext-rdap-ttl- > extension-03 (Ends 2026-01-19) >
[SAH] [snip] > Speaking of that first paragraph, what exactly does "TTL values MUST be > unsigned integers in the range 0-2,147,483,647" mean? The given examples > use values 300, 3600, and 86400. None of those values fall in the given range. > It may be better to cite Section 4.1.3 of RFC 1035. [SAH] LOL, one of my colleagues gently reminded me that the given range is meant to be interpreted as "0 to 2,147,483,647", and not "0-2, 147, 483, or 647". Sorry about that! I still believe that it's better to cite 1035, though, instead of interpreting the specification text found in 1035. 1035 says "a 32 bit unsigned integer that specifies the time interval (in seconds) that the resource record may be cached before it should be discarded. Zero values are interpreted to mean that the RR can only be used for the transaction in progress, and should not be cached". Scott _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
