Re: [regext] draft-ietf-regext-epp-fees-02.txt: currency error handling, command wildcard

Thomas Corte <Thomas.Corte@knipp.de> Wed, 29 March 2017 08:51 UTC

Return-Path: <Thomas.Corte@knipp.de>
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 58218129669 for <regext@ietfa.amsl.com>; Wed, 29 Mar 2017 01:51:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] 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 NXs_fUN1RWyO for <regext@ietfa.amsl.com>; Wed, 29 Mar 2017 01:51:39 -0700 (PDT)
Received: from kmx10a.knipp.de (clust3a.bbone.knipp.de [195.253.6.83]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11498129666 for <regext@ietf.org>; Wed, 29 Mar 2017 01:51:38 -0700 (PDT)
Received: from localhost (localhost.bbone.knipp.de [127.0.0.1]) by kmx10a.knipp.de (Postfix) with ESMTP id 119AA97D5; Wed, 29 Mar 2017 10:51:37 +0200 (MESZ)
X-Knipp-VirusScanned: Yes
Received: from kmx10a.knipp.de ([127.0.0.1]) by localhost (kmx10a.knipp.de [127.0.0.1]) (amavisd-new, port 10004) with ESMTP id drq7F0Ms+ZbR; Wed, 29 Mar 2017 10:51:29 +0200 (MESZ)
Received: from hp9000.do.knipp.de (hp9000.do.knipp.de [195.253.2.54]) by kmx10a.knipp.de (Postfix) with ESMTP id 3D70497D4; Wed, 29 Mar 2017 10:51:29 +0200 (MESZ)
Received: from flexo.fritz.box (fw-intranet-eth3-0.do.knipp.de [195.253.2.17]) by hp9000.do.knipp.de (@(#)Sendmail version 8.15.2 - Revision 1.0 :: HP-UX 11.31 - 29th July,2016/8.15.2) with ESMTP id v2T8pS8m015869; Wed, 29 Mar 2017 10:51:28 +0200 (MESZ)
To: regext@ietf.org
References: <216C099C-41E6-48EA-8925-E239AA3F2015@verisign.com> <bfe3eb81-dce6-45fe-28a4-3ffdb29639c6@knipp.de> <24593B92-2498-4770-AD5B-5626651A3ABD@verisign.com>
Cc: support@tango-rs.com
From: Thomas Corte <Thomas.Corte@knipp.de>
Message-ID: <b91ab308-15a4-a62e-0e7e-a9648c6a4b87@knipp.de>
Date: Wed, 29 Mar 2017 10:51:23 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <24593B92-2498-4770-AD5B-5626651A3ABD@verisign.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/Z7nHB300FeXbUc0weoX1pcjDEDU>
Subject: Re: [regext] draft-ietf-regext-epp-fees-02.txt: currency error handling, command wildcard
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 29 Mar 2017 08:51:41 -0000

Hello James,

On 28/03/2017 20:09, Gould, James wrote:

> Thomas,
> 
> Putting the avail attribute at the level of fee:cd addresses use cases
> where the domain name is invalid, reserved (without pricing), and the
> currency is invalid.  In these cases, you would not want to return all
> the commands with an avail=false to indicate that the fee information
> is not available for the domain.  If the server needs to get down to
> the detail of providing availability at the command level, then the
> avail attribute could be added there as well, but there is an extra
> level of complexity to handle it at the command level.  If the command
> is invalid, the period is invalid, having the avail flag only at the
> fee:cd level would fast-fail to not provide any of the fee
> information.  Although this may not be as functional, it allows the
> server to fast fail the fee check which is important to keep the
> availability check more lightweight.   I would prefer to fast fail if
> possible.

I agree that a fast fail is preferable if the domain name or currency
prevent the name from being available in any case.

The use case I'm thinking of refers to the provision in fee-0.15 that
allows the server to return availability information for all active
launch phases. In fee-0.15, this is possible by returning <fee:command>
elements with avail="true" for launch phases permitting the name, and
elements with avail="false" for launch phases not permitting it. But I
guess in the new approach (with avail in the framing element) this is
still possible by simply omitting the non-available results and only
including <fee:command> elements for the phases that support the
operation. The registrar doesn't need to learn about existing launch
phases that do not allow the registration of the name.

Best regards,

Thomas

-- 
TANGO REGISTRY SERVICES® is a product of:
Knipp Medien und Kommunikation GmbH
Technologiepark                             Phone: +49 231 9703-222
Martin-Schmeisser-Weg 9                       Fax: +49 231 9703-200
D-44227 Dortmund                       E-Mail: support@tango-rs.com
Germany