Thanks Jorge! IMHO, the document is pretty much where I wanted to get it, but Maarten did raise this point:
> i would like to see some changes to the data format if possible, now there > are a bunch of nested arrays, as a developer i this is very annoying to work > with. > maybe we can make it a bit more developer friendly. (see: https://mailarchive.ietf.org/arch/msg/regext/Wl7I4AJ663z0W5Wn92pwBrZ42mM/) I'd appreciate the WG's feedback on this. This was actually the approach I took in the -00 version, but I changed it to the current syntax after receiving private feedback. One benefit of the current approach is that common TTL values, remarks and events are mapped to multiple DNS record types. This reduces the duplication (where a link has to be present in several places). Another approach might be a syntax like this: { "objectClassName": "nameserver", "ldhName": "ns1.example.com", "ttl": { "events": [ /* standard RDAP events */ ], "links": [ /* standard RDAP links */ ], "remarks": [ /* standard RDAP remarks */ ], "values": { "A": 3600, "AAAA": 86400 } } } Thoughts? -- Gavin Brown Principal Engineer, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
