<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">
+1 to using a mechanism that is already built in to the protocol.<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">
Cheers,<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">
Tomofumi<br>
<br>
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">
From: Gavin Brown<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">
Sent: Tuesday, January 8, 6:33 AM<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">
Subject: Re: [TSG-Access-RD] [Ext] Re: Bulk Data, Bulk Query, WhoWas and Charter scope<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">
To: Hollenbeck, Scott, jkolker@godaddy.com, andy@hxr.us<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">
Cc: tsg-access-rd@icann.org<br>
<br>
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">
+1. I also think using the RDAP protocol to discover the service would provide a model that could be deployed elsewhere, such as in ccTLD registries. G. On 08/01/2019 14:30, Hollenbeck, Scott wrote: >> -----Original Message----- >> From: Jody Kolker >> Sent:
Monday, January 7, 2019 4:10 PM >> To: Gavin Brown ; Hollenbeck, Scott >> ; andy@hxr.us >> Cc: tsg-access-rd@icann.org >> Subject: [EXTERNAL] RE: [TSG-Access-RD] [Ext] Re: Bulk Data, Bulk Query, >> WhoWas and Charter scope >> >> >> << >> 1. How do RDAP clients
learn the URL of ICANN's RDAP service? >> >> - an entry in the "links" object with an appropriate relation value >> (which may need to >> be registered with IANA since I don't see one that's applicable) >> seems like it would >> work. >>>> >> >> Why would
ICANN's RDAP service need to be published publicly anywhere? >> My understanding was that ICANN's service would only be used to access >> private data. Anyone approved to access private data would need to be >> approved by ICANN. When the client is approved
to receive private data, the >> RDAP address could be included in the approval communication. > > Jody, one thing to consider here is how this works with the RDAP bootstrap service described in RFC 7484. It's possible to associate multiple RDAP service URLs
with any given TLD, but what's missing is the clue that tells the client that they'll get different answers depending on the availability of access credentials and the service they send their query to. We also need to consider service evolution - that is,
the service URL may change over time. It would be nice for this information to be discoverable in-band. > > Scott > -- Gavin Brown Chief Technology Officer CentralNic Group plc (LSE:CNIC) Innovative, Reliable and Flexible Registry Services for ccTLD, gTLD
and private domain name registries https://clicktime.symantec.com/a/1/QcOhmvAbP6mSpQITNEOxpZzwoAeJ-vVfCWC03AuXfhQ=?d=-Eo_OMHJOCnc5fPsGBeouO1PFtuHPK6EAo0HWne9nnCQnOSP9-xmlQQPm2xt4HyEYz8f8kTVCUdbcVQVLj-jQRCDWKFsOnoe890_rcfcIcGKQv4CzGvQvz9QhvqKrlUTgn_TfBQP9z1mmbZEWX8SmCT9Q6Z0yVSbdp4g-k6qeo2kicJFLOp7hxARE-cyxbUvGm-1ylWriKdtqdQm3h_D7J6JOy2NY7n6lXKfAxfLiT6KkAv8iwHbYr4nzllzINWrVLhC9hk5b-AFq9yHLzoUydzM4xV4nN8AakfjClq2oDGuvyr-ynoaYoQFjGvLM_lHmgoWjP31A0iG-ioH5RXn5Ns2VmNdIiURk-OcMQUOPSeHN6WnLLD7Yeqq1-ya-45bI0MrHrcpRzNujhOn4RQmRJm3iJbxdwJPr0bxBzNx5R3nVRFdm97uCbRG4QvZBcP1vzY%3D&u=https%3A%2F%2Fwww.centralnic.com%2F
+44.7548243029 CentralNic Group plc is a company registered in England and Wales with company number 8576358. Registered Offices: 35-39 Moorgate, London, EC2R 6AR.
<br>
<br>
</div>
</body>
</html>