IETF Logo Mail Archive

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

Patrick Mevzek <pm@dotandco.com> Tue, 04 April 2017 00:28 UTC

Return-Path: <patrick@shaktot.patoche.org>
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 58A54129480 for <regext@ietfa.amsl.com>; Mon, 3 Apr 2017 17:28:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 yl4wYVcg7lci for <regext@ietfa.amsl.com>; Mon, 3 Apr 2017 17:28:01 -0700 (PDT)
Received: from shaktot.patoche.org (shaktot.patoche.org [212.85.152.86]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB07312947B for <regext@ietf.org>; Mon, 3 Apr 2017 17:28:00 -0700 (PDT)
Received: from shaktot.patoche.org (localhost.localdomain [127.0.0.1]) by shaktot.patoche.org (8.14.3/8.14.3/Debian-9.4) with ESMTP id v340Roxn027964; Tue, 4 Apr 2017 02:27:50 +0200
Received: (from patrick@localhost) by shaktot.patoche.org (8.14.3/8.14.3/Submit) id v340Ro1T027963; Tue, 4 Apr 2017 02:27:50 +0200
Date: Tue, 04 Apr 2017 02:27:42 +0200
From: Patrick Mevzek <pm@dotandco.com>
To: Thomas Corte <Thomas.Corte@knipp.de>
Cc: regext@ietf.org, support@tango-rs.com
Message-ID: <20170404002742.GE4969@home.patoche.org>
References: <4E86D777-B3D0-4015-8FE1-56B4E5E39E1F@verisign.com> <b18198b3-3e9d-3bad-7411-eef1462e0b1c@knipp.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <b18198b3-3e9d-3bad-7411-eef1462e0b1c@knipp.de>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Scanned-By: shaktot_dot_patoche_dot_org on 212.85.152.86
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/bldge8-FZFQ7NCRGMCaN93ESHfA>
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: Tue, 04 Apr 2017 00:28:03 -0000

Thomas Corte <Thomas.Corte@knipp.de> 2017-03-29 10:43
> > Yes, the fee information should be returned for a reserved domain if pricing information does exist.  
> 
> Not sure what this would mean. If a domain is reserved, that usually
> means that it's not available for registration under *any* circumstances.

I'm not sure about that. A domain name can be on a registry "reserved"
list, meaning that it has specific conditions to be available (or
not), such as, for one case I know about, trying to acquire a domain
name corresponding to a town name, and by default you can not have it
(it is reserved) *except* if you give enough (OOB) information
explaining why you would be a good custodian for it. So it is reserved
in the sense that it is not freely registrable like any other domain
names, but it can still be registered with some specific extra
conditions.

Hence, even "reserved" domain names should display princing, if there is
one for them.

-- 
Patrick Mevzek

v2.23.0 | Report a Bug | By Email