[{"author": "James Gould", "text": "<p>Go Rick!</p>", "time": "2022-07-28T21:35:22Z"}, {"author": "Richard Wilhelm", "text": "<p>doc is open... anyone feel free to put stuff in or fix stuff that I mess up</p>", "time": "2022-07-28T21:35:39Z"}, {"author": "James Galvin", "text": "<p>car</p>", "time": "2022-07-28T21:49:30Z"}, {"author": "Andrew Newton", "text": "<p>Does that hold true with EVs?</p>", "time": "2022-07-28T21:49:35Z"}, {"author": "Peter Koch", "text": "<p>not representing an ICANN contracted party, I still sympathize with Rick's concerns</p>", "time": "2022-07-28T21:51:55Z"}, {"author": "St\u00e9phane Bortzmeyer", "text": "<p>@Peter But why is it different than all the other RFCs that are used in ICANN contracts?</p>", "time": "2022-07-28T21:52:44Z"}, {"author": "Peter Koch", "text": "<p>not sure about \"all the other RFCs\", but to the best of my knowledge they point to protocol specifications</p>", "time": "2022-07-28T21:54:56Z"}, {"author": "St\u00e9phane Bortzmeyer", "text": "<p>The best example is RFC 8499 (nt</p>", "time": "2022-07-28T21:56:09Z"}, {"author": "St\u00e9phane Bortzmeyer", "text": "<p>(not a protocol specification)</p>", "time": "2022-07-28T21:56:24Z"}, {"author": "Peter Koch", "text": "<p>8499 has its own set of issues, but at least it is 'only' a BCP and does not use normative language</p>", "time": "2022-07-28T21:59:05Z"}, {"author": "Peter Koch", "text": "<p>(except for a quote from RFC 4035)</p>", "time": "2022-07-28T22:00:09Z"}, {"author": "James Gould", "text": "<p>I just want to ensure that the versioning of policy identifiers can still be registered</p>", "time": "2022-07-28T22:08:51Z"}, {"author": "Andrew Newton", "text": "<p>It exists so a client can know which query parameters to use when sending requests.</p>", "time": "2022-07-28T22:14:57Z"}, {"author": "James Gould", "text": "<p>Ensure that identifiers like icann_rdap_response_profile_0 and icann_rdap_technical_implementation_guide_0 can continue to be registered, since versioning is not an RDAP Extension Registry feature.</p>", "time": "2022-07-28T22:15:03Z"}, {"author": "Richard Wilhelm", "text": "<p>I think that as long as they are unique... they can be registered.  Fair?</p>", "time": "2022-07-28T22:15:33Z"}, {"author": "James Gould", "text": "<p>That sounds fair to me, as long as the proposal doesn't disallow versioning of these type of identifiers.</p>", "time": "2022-07-28T22:17:34Z"}, {"author": "Andrew Newton", "text": "<p>\"hint\" was bad language. :)</p>", "time": "2022-07-28T22:17:48Z"}, {"author": "Jasdip Singh", "text": "<p>On similar lines, the NRO RDAP Profile for RIRs also has an extension registered for conformance among the RIRs.</p>", "time": "2022-07-28T22:19:46Z"}, {"author": "James Gould", "text": "<p>Correct the policy / profile identifiers don't define structure but the data that would be returned in the structure.</p>", "time": "2022-07-28T22:19:47Z"}, {"author": "Andrew Newton", "text": "<p>I support the chairs proposal.</p>", "time": "2022-07-28T22:20:11Z"}, {"author": "James Gould", "text": "<p>For draft-ietf-regext-rdap-redacted, we would register \"redacted\", which will be used for the rdapConformance value and the response member of the extension.</p>", "time": "2022-07-28T22:21:15Z"}, {"author": "Jasdip Singh", "text": "<p>That's alright. :)</p>", "time": "2022-07-28T22:21:46Z"}, {"author": "Andrew Newton", "text": "<p>Yes! Thanks to the Chairs!</p>", "time": "2022-07-28T22:23:30Z"}, {"author": "Jabber", "text": "<p>Yoshiro Yoneya: clap!</p>", "time": "2022-07-28T22:23:47Z"}, {"author": "Jasdip Singh", "text": "<p>+1</p>", "time": "2022-07-28T22:23:52Z"}, {"author": "Tom Harrison", "text": "<p>+1</p>", "time": "2022-07-28T22:23:59Z"}, {"author": "George Michaelson", "text": "<p>redacted_level_0  :-)</p>", "time": "2022-07-28T22:24:30Z"}, {"author": "James Gould", "text": "<p>Thanks everyone!</p>", "time": "2022-07-28T22:27:29Z"}, {"author": "Mario Loffredo", "text": "<p>me too</p>", "time": "2022-07-28T22:27:30Z"}, {"author": "Richard Wilhelm", "text": "<p>Minutes are up-to-date... feel free to augment, update, and improve</p>", "time": "2022-07-28T22:27:33Z"}, {"author": "Jody Kolker", "text": "<p>thanks everyone!</p>", "time": "2022-07-28T22:27:41Z"}, {"author": "Mario Loffredo", "text": "<p>Thanks all. Good night</p>", "time": "2022-07-28T22:27:53Z"}]