Re: [regext] Using RDAP as a Domain Availability Service

"Francisco Obispo" <fobispo@uniregistry.com> Fri, 16 December 2016 16:55 UTC

Return-Path: <fobispo@uniregistry.com>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30EFF129AE9 for <regext@ietfa.amsl.com>; Fri, 16 Dec 2016 08:55:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.629
X-Spam-Level:
X-Spam-Status: No, score=-3.629 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_TAG_BALANCE_BODY=1.157, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-2.896, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4sjFEOQEeB5G for <regext@ietfa.amsl.com>; Fri, 16 Dec 2016 08:54:58 -0800 (PST)
Received: from zimbra1.uniregistry.com (zimbra1.uniregistry.com [162.221.214.42]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3A0A129AAD for <regext@ietf.org>; Fri, 16 Dec 2016 08:54:57 -0800 (PST)
Received: from zimbra1.uniregistry.com (localhost [127.0.0.1]) by zimbra1.uniregistry.com (Postfix) with ESMTPS id 7A0072443A7; Fri, 16 Dec 2016 16:54:56 +0000 (UTC)
Received: from zimbra1.uniregistry.com (localhost [127.0.0.1]) by zimbra1.uniregistry.com (Postfix) with ESMTPS id 5FCCF2449F4; Fri, 16 Dec 2016 16:54:56 +0000 (UTC)
Received: from [192.168.255.5] (ip68-4-185-161.oc.oc.cox.net [68.4.185.161]) by zimbra1.uniregistry.com (Postfix) with ESMTPSA id E2FE02443A7; Fri, 16 Dec 2016 16:54:55 +0000 (UTC)
From: Francisco Obispo <fobispo@uniregistry.com>
To: Andrew Newton <andy@hxr.us>
Date: Fri, 16 Dec 2016 08:54:49 -0800
Message-ID: <B7EF9FEC-8E49-4469-A863-5870886E8706@uniregistry.com>
In-Reply-To: <CAAQiQRcH6d23hT5aFYUve1LC+NhijpHwOvW+26G5wJw=gHoUuA@mail.gmail.com>
References: <CAAQiQRcH6d23hT5aFYUve1LC+NhijpHwOvW+26G5wJw=gHoUuA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_24F4B707-3513-44D1-963A-B306E6F9A903_="; micalg="pgp-sha1"; protocol="application/pgp-signature"
X-Mailer: MailMate (1.9.6r5310)
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/sPtgMMC-2xWCvfVZ0ckz18sfh3A>
Cc: Registration Protocols Extensions <regext@ietf.org>
Subject: Re: [regext] Using RDAP as a Domain Availability Service
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Dec 2016 16:55:00 -0000

I don’t like having to implement an RDAP client that would have to send two queries.

One to get the domain information, and if the resource does not exist, then another query to see if it’s available.

Checking for a reason on why the domain name is not available could or could not be expensive, but this should not be a reason to disallow it at the ‘presentation’ layer of the protocol.

In my opinion, we should have some OPTIONAL fields in the original negative response to signal whether the name is available or not, and if not, a way to provide a reason. If this is mandated or not by registry policy / contract, it should be a different issue.

regards

—
Francisco Obispo
Uniregistry Inc.
On 16 Dec 2016, at 3:34, Andrew Newton 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