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:14 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 D2A9F12969F for <regext@ietfa.amsl.com>; Wed, 29 Mar 2017 01:14:49 -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 Sdo36QkfDMAT for <regext@ietfa.amsl.com>; Wed, 29 Mar 2017 01:14:47 -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 3982C1294C9 for <regext@ietf.org>; Wed, 29 Mar 2017 01:14:37 -0700 (PDT)
Received: from localhost (localhost.bbone.knipp.de [127.0.0.1]) by kmx10a.knipp.de (Postfix) with ESMTP id 4DB5497D5; Wed, 29 Mar 2017 10:14:36 +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 yepxU1Qz2oMM; Wed, 29 Mar 2017 10:14:28 +0200 (MESZ)
Received: from hp9000.do.knipp.de (hp9000.do.knipp.de [195.253.2.54]) by kmx10a.knipp.de (Postfix) with ESMTP id D175797D4; Wed, 29 Mar 2017 10:14:28 +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 v2T8ESD7005935; Wed, 29 Mar 2017 10:14:28 +0200 (MESZ)
To: Alexander Mayrhofer <alexander.mayrhofer@nic.at>, "Gould, James" <jgould@verisign.com>, Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>, regext <regext@ietf.org>
References: <216C099C-41E6-48EA-8925-E239AA3F2015@verisign.com> <bfe3eb81-dce6-45fe-28a4-3ffdb29639c6@knipp.de> <19F54F2956911544A32543B8A9BDE07598F3B5C6@NICS-EXCH2.sbg.nic.at>
Cc: support@tango-rs.com
From: Thomas Corte <Thomas.Corte@knipp.de>
Message-ID: <91322db0-410f-bc1e-6493-cf52be69857a@knipp.de>
Date: Wed, 29 Mar 2017 10:14: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: <19F54F2956911544A32543B8A9BDE07598F3B5C6@NICS-EXCH2.sbg.nic.at>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/sKHSFwLMgJS_rvU2h7RYO1G6Ss8>
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:14:50 -0000

Hello Alexander,

On 29/03/2017 00:37, Alexander Mayrhofer wrote:

> i think you have mentioned an important argument *against* your own
> proposal. You write  "availability of a fee (and the domain in
> general)", which means that your proposal tries to mix in two
> different semantics into the same element - which, in turn, seems
> ambigious and probably even dangerous. The "avail" attribute can
> *either* indicate whether fee information is available, *or* whether a
> certain commmand on a certain domain in a certain phase (at the
> current point in time?) is "available".
> 
> I think it's easy to see that the second "type" of availability would
> entail all kinds of problems. Therefore i'd rather not go down that
> path. It would pack too much logic into the command (eg. "is a
> transfer on that domain available for that client during the given
> phase at the current time?" - i don't want to be in the position to
> decide about such cases..)

Good point, but it seems that we'll need a clearer definition of what
"fee information is available" is really supposed to mean. To me, it was
always implicitly clear that it essentially means "the domain can be
created/renewed/transferred/... with the given parameters, and it costs
this much", whereas avail="false" means "the operation isn't possible
because some parameter is wrong, hence no costs can be determined".

The current wording matches that interpretation in my opinion: "If the
value of this attribute evaluates to false, this indicates that the
server cannot calculate the relevant fees, because the object, command,
currency, period or class is invalid according to server policy."

So this does essentially boil down to an extended availability check,
which happens to also provide cost information. Not sure what the
alternative would be; if a combination of domain name, command, launch
phase, period and currency is valid, the server should be be able to tell
the costs. Simply replying "don't know" for a viable operation would not
provide useful information to the registrar.

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