[eppext] Suggestion for check domain extension

Michael Hansen <mih@one.com> Fri, 02 October 2015 09:10 UTC

Return-Path: <mih@one.com>
X-Original-To: eppext@ietfa.amsl.com
Delivered-To: eppext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 640E31AD08F for <eppext@ietfa.amsl.com>; Fri, 2 Oct 2015 02:10:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.79
X-Spam-Status: No, score=0.79 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id TDfFOitfX2xi for <eppext@ietfa.amsl.com>; Fri, 2 Oct 2015 02:10:55 -0700 (PDT)
Received: from officesmtp1.one.com (officesmtp1.one.com []) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01F931AD087 for <eppext@ietf.org>; Fri, 2 Oct 2015 02:10:54 -0700 (PDT)
Received: from localhost.localdomain (nat-cph1-dev.net.one.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by officesmtp1.one.com (Postfix) with ESMTPSA id 2082B1800B5655 for <eppext@ietf.org>; Fri, 2 Oct 2015 09:10:53 +0000 (UTC)
From: Michael Hansen <mih@one.com>
X-Enigmail-Draft-Status: N1110
Organization: One.com A/S
To: eppext@ietf.org
Message-ID: <560E4A1C.7050301@one.com>
Date: Fri, 2 Oct 2015 11:10:52 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------090602050704040605050004"
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/suqzjpfVMSEmzFMfO07x9io1mS8>
Subject: [eppext] Suggestion for check domain extension
X-BeenThere: eppext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPPEXT <eppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eppext>, <mailto:eppext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eppext/>
List-Post: <mailto:eppext@ietf.org>
List-Help: <mailto:eppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eppext>, <mailto:eppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Oct 2015 09:10:57 -0000

As a registrar I would like to see a standard way in check domain to get
information about if a domain is blocked or reserved, like in the AFNIC
extension ( http://www.afnic.fr/xml/epp/frnic-1.3):

AFNIC <check> response extensions details
<complexType name="resChkDataType">
    <element name="domain" type="frnic:resChkDomDataType"/>

<complexType name="resChkDomDataType">
    <element name="cd" type="frnic:domCheckType" maxOccurs="unbounded"/>

<complexType name="domCheckType">
    <element name="name" type="frnic:domCheckNameType"/>
    <element name="rsvReason" type="eppcom:reasonType" minOccurs="0"/>
    <element name="fbdReason" type="eppcom:reasonType" minOccurs="0"/>

<complexType name="domCheckNameType">
    <extension base="eppcom:labelType">
      <attribute name="reserved" type="boolean" use="required"/>
      <attribute name="forbidden" type="boolean" use="required"/>

Using the current check domain it is not possible to identify
blocked/reserved domains unless the reason can be parsed, as most just
return unavailable for blocked domains, and available for reserved domains.

It might also be extended with some kind of identifier for who the
domain is reserved to (i.e. domain name for .uk domains, or VAT number
for .rio domains).


Michael Hansen
Senior Developer
One.com A/S