+1 As noted in my prior post on this topic, RDAP is a lookup protocol for what exists. Logic associated with availability is beyond the scope of a lookup protocol. Considering that RDAP is a RESTful protocol, anything could be represented with it but the question is whether it should. I too have heard interest in an availability service that could be discussed, but this should be separated from RDAP. I view availability via EPP as the best channel for authorized parties to go, since it is authoritative and it includes all the availability business logic. EPP is a standard, so registries that have chosen not to implement it may not implement another standard either.
A public availability service would look a lot more like a DNS service than an RDAP lookup service, since it could be a larger dependency for a broader set of real-time clients and therefore needs to be focused on scalability and accuracy (complete set of availability logic) over breadth of lookup features. It would be great to understand the use cases for a public availability service to define the need prior to making proposals on a solution. — JG James Gould Distinguished Engineer jgo...@verisign.com 703-948-3271 12061 Bluemont Way Reston, VA 20190 VerisignInc.com <http://verisigninc.com/> On 12/16/16, 6:40 AM, "regext on behalf of Michele Neylon - Blacknight" <regext-boun...@ietf.org on behalf of mich...@blacknight.com> wrote: Sorry, but why would RDAP be used for this? I know that whois is used by a lot of people for this, but it really shouldn’t be. Only a direct EPP query to the registry can give a “sane” response. What am I missing? Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains http://www.blacknight.host/ http://blacknight.blog/ http://www.blacknight.press - get our latest news & media coverage http://www.technology.ie Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Social: http://mneylon.social Random Stuff: http://michele.irish ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845 On 16/12/2016, 11:34, "regext on behalf of Andrew Newton" <regext-boun...@ietf.org on behalf of a...@hxr.us> wrote: This topic keeps appearing over and over again, so Marcos and I decided to address it. As it turns out, there's not much needed to achieve this. This draft suggests two new query parameters and re-uses the current RDAP domain query. In other words, its a very small addition to RDAP. -andy A new version of I-D, draft-newton-regext-rdap-domain-availability-00.txt has been successfully submitted by Andrew Lee Newton and posted to the IETF repository. Name: draft-newton-regext-rdap-domain-availability Revision: 00 Title: Using RDAP as a Domain Availability Service Document date: 2016-12-16 Group: Individual Submission Pages: 6 URL: https://www.ietf.org/internet-drafts/draft-newton-regext-rdap-domain-availability-00.txt Status: https://datatracker.ietf.org/doc/draft-newton-regext-rdap-domain-availability/ Htmlized: https://tools.ietf.org/html/draft-newton-regext-rdap-domain-availability-00 Abstract: This document describes a minimal profile of RDAP which can be used to check the availability of domain names available for registration. _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
