Hi Andy,
> On 4 Jan 2024, at 14:22, Andrew Newton <[email protected]> wrote:
>
> On Wed, Jan 3, 2024 at 10:20 AM Gavin Brown <[email protected]> wrote:
>>
>> Do you think the ttl_values object needs an events array then?
>>
>> To support this I would change the ttl_values object as follows:
>>
>> "ttl": {
>> "values": {
>> "NS": 3600,
>> "DS": 60,
>> },
>> "events": [
>> {
>> "eventAction": "lastChanged",
>> "eventDate": "2012-07-23T05:15:47Z",
>> "eventActor": "registry-operator"
>> }
>> ]
>> }
>
> I was thinking that "ttl" would be an array of objects, with each
> object containing an array of DNS RR names, a TTL, an array of events
> and an array of links. This keeps it similar to the DNSSEC data. I
> know the links thing seems silly, but it could be used to point to TTL
> policies given some registrars, INRs, etc have TTL policies.
So something like this? I've also thrown in min/default/max values as well:
"ttl": [
{
"types": ["NS", "DELEG"],
"value": 3600,
"min": 60, // optional
"default": 86400, // optional
"max": 172800, // optional
"remarks": [ ... ], // optional
"events": [ ... ] // optional
},
{
"types": ["DS"],
"value": 3600,
"remarks": [ ... ],
"events": [ ... ]
},
...
],
...
So each RRtype could have a remark which provides the policy (or a link to the
policy) and some events.
G.
>
> To address the JG's point, there are registries that are not run by
> EPP (ccTLDs, RIRs) and registrars don't necessarily have to follow the
> EPP data model in their own RDAP servers as far as I know. I think
> this is generally useful and I know there have been times where I need
> to know what a registrar had as a TTL vs what I was seeing in DNS.
>
> -andy
--
Gavin Brown
Principal Engineer, Global Domains & Strategy
Internet Corporation for Assigned Names and Numbers (ICANN)
https://www.icann.org
_______________________________________________
regext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/regext
