Thanks Tom,
I reviewed and looks good.
As to the IRR queries: Fair enough to me to have them in a separate document.
It was just a suggestion.
Regards,
Antoin (no hat)
> Op 2 mei 2023, om 01:17 heeft Tom Harrison het volgende
> geschreven:
>
> Hi Antoin,
>
> On Thu, Mar 30, 2023 at 10:37
Hi Antoin,
On Thu, Mar 30, 2023 at 10:37:54AM +0200, Antoin Verschuren wrote:
> I have read this draft, and have some comments/requests as discussed
> during our IETF 116 meeting session.
> Most of my remarks are about section 4, Link Relations:
>
> 1. Suggest to replace “operator” with “server o
Comments in-line:
On Thu, Mar 30, 2023 at 5:38 PM Antoin Verschuren
wrote:
>
> 2. With regards to the hierarchy itself, there are 2 use cases that can be
> served better:
> Most common use cases are:
>
> -Where is address space used when querying an IP address or prefix
> Usually, this is the as
Chair hat off.
Thank you Tom for this document and your presentation. I like it a lot.
I have read this draft, and have some comments/requests as discussed during our
IETF 116 meeting session.
Most of my remarks are about section 4, Link Relations:
1. Suggest to replace “operator” with “server
Hi Tom and Jasdip,
here in the following a first feedback on this draft:
1) It looks inconsistent to me that the draft is titled "RDAP RIR
Search" but in the rest of the document the term "INR registries" is
used instead.
However, I agree that "INR searches" is the right term to identify
c
