Re: [eppext] Fwd: New Version Notification for draft-brown-epp-fees-04.txt

Keith Gaughan <keith@blacknight.com> Mon, 18 May 2015 15:48 UTC

Return-Path: <keith@blacknight.com>
X-Original-To: eppext@ietfa.amsl.com
Delivered-To: eppext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 607BD1AC401 for <eppext@ietfa.amsl.com>; Mon, 18 May 2015 08:48:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.099
X-Spam-Level:
X-Spam-Status: No, score=0.099 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 Nz5qozGnLicH for <eppext@ietfa.amsl.com>; Mon, 18 May 2015 08:48:09 -0700 (PDT)
Received: from merlin.blacknight.ie (merlin.blacknight.ie [81.17.240.211]) by ietfa.amsl.com (Postfix) with ESMTP id DD1281AC3FE for <eppext@ietf.org>; Mon, 18 May 2015 08:48:08 -0700 (PDT)
Received: from [81.17.243.239] (hegemon.blacknight.ie [81.17.243.239]) by merlin.blacknight.ie (Postfix) with ESMTP id D1A9A59C003 for <eppext@ietf.org>; Mon, 18 May 2015 16:47:52 +0100 (IST)
Message-ID: <555A09AA.2030604@blacknight.com>
Date: Mon, 18 May 2015 16:47:54 +0100
From: Keith Gaughan <keith@blacknight.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: eppext@ietf.org
References: <20150217101609.7180.94307.idtracker@ietfa.amsl.com> <54E32A6A.2050905@centralnic.com>
In-Reply-To: <54E32A6A.2050905@centralnic.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/fAW1BBTWR7BUOdWkNVGBDr2u9sw>
Subject: Re: [eppext] Fwd: New Version Notification for draft-brown-epp-fees-04.txt
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: <http://www.ietf.org/mail-archive/web/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: Mon, 18 May 2015 15:48:12 -0000

On 17/02/15 11:47, Gavin Brown wrote:

> I've just submitted a new version of the fee extension draft for
> your review.

To make it easier for a registrar to tell whether or not a domain is
being given premium pricing (as opposed to some pricing tier), I would
suggest the following change regarding the <fee:class> element in §3.7:

    If the domain is being charged at the standard fee, then the
    reserved fee class 'standard' class MUST be used. Omitting the
    <fee:class> element indicates that the domain is subject to bespoke
    pricing.

I'm open to ideas on this change. My main reason for suggesting this is
to ensure that for domains subject to standard pricing, there's a single
standard mechanism for indicating this. I tried formulating it in such a
way as to minimise potential incompatibility with existing
implementations. I also wanted to clarify what omitting the <fee:class>
element might mean, as this is left undefined and could mean anything.

K.

-- 
Keith Gaughan, Development Lead; PGP/GPG key ID: D5FC9D23
Blacknight Internet Solutions Ltd. <http://blacknight.host/>
12A Barrowside Business Park, Carlow, Ireland
Registered in Ireland, Company No.: 370845