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

Rubens Kuhl <rubensk@nic.br> Mon, 04 May 2015 23:28 UTC

Return-Path: <rubensk@nic.br>
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 9962A1B2CCF for <eppext@ietfa.amsl.com>; Mon, 4 May 2015 16:28:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.339
X-Spam-Level:
X-Spam-Status: No, score=0.339 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_BR=0.955, HOST_EQ_BR=1.295, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 chOGYM1IwC5v for <eppext@ietfa.amsl.com>; Mon, 4 May 2015 16:28:44 -0700 (PDT)
Received: from mail.nic.br (mail.nic.br [IPv6:2001:12ff:0:4::5]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E73C91B2CD6 for <eppext@ietf.org>; Mon, 4 May 2015 16:28:34 -0700 (PDT)
Received: from rubens.in.registro.br (3.195.net.registro.br [200.160.3.195]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.nic.br (Postfix) with ESMTPSA id BA7932080265; Mon, 4 May 2015 20:28:32 -0300 (BRT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_1EDE8DCB-CA5C-4FEB-B21C-02DAD4359A6D"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: Rubens Kuhl <rubensk@nic.br>
In-Reply-To: <819AE333-55A5-4C22-B90F-86396AA0EFD2@verisign.com>
Date: Mon, 4 May 2015 20:28:32 -0300
Message-Id: <259A845A-4DD1-4B48-8139-151D3275FAA7@nic.br>
References: <20150217101609.7180.94307.idtracker@ietfa.amsl.com> <54E32A6A.2050905@centralnic.com> <819AE333-55A5-4C22-B90F-86396AA0EFD2@verisign.com>
To: "Gould, James" <JGould@verisign.com>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/rmkI0sPZCe4J-IgexCI_6lW2MDM>
Cc: "eppext@ietf.org" <eppext@ietf.org>, Gavin Brown <gavin.brown@centralnic.com>
Subject: Re: [eppext] 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, 04 May 2015 23:28:47 -0000

Perhaps it might not ignore, if the extension is being used to verify that client and server agree on the conditions for a specific name (its fee, whether a fraction of the application is refundable or not etc.)


Rubens


> Em 04/05/2015, à(s) 20:13:000, Gould, James <JGould@verisign.com> escreveu:
> 
> Gavin, 
> 
> I wanted to point out one item that may require more text in the draft to address.  The <fee:fee> element described in section 3.4 “Fees and Credits” covers its use when created by the server in the responses, but does not cover its use when created by the client in the transform commands (create, renew, transfer, and update).  My recommendation is to add text to section 3.4 covering the use case of the <fee:fee> element in the commands, since I don’t believe that the “description”, “refundable”, “grace-period”, and “applied” attributes are applicable in the command.  Both the “refundable” and “applied” attributes include defaults, so they will have values even if they are not explicitly set by the client.  I’m assuming that the server should ignore these attributes if they are set in the command, but I just want to confirm the expectation.  
> 
> Thanks,
> 
> —
> 
> JG
> 
> 
> <BF09FAA4-32D8-46E0-BED0-CD72F43BD6E0[81].png>
> 
> James Gould
> Distinguished Engineer
> jgould@Verisign.com <x-msg://32/jgould@Verisign.com>
> 
> 703-948-3271
> 12061 Bluemont Way
> Reston, VA 20190
> 
> VerisignInc.com <http://verisigninc.com/>
>> On Feb 17, 2015, at 6:47 AM, Gavin Brown <gavin.brown@centralnic.com <mailto:gavin.brown@centralnic.com>> wrote:
>> 
>> I've just submitted a new version of the fee extension draft for your
>> review.
>> 
>> 9.4. Changes from 03 to 04
>> 
>>   1.  Changed Intended Status to Standards Track.
>> 
>>   2.  As per suggestion from Michael Bauland, the <fee:period> element
>>       is no longer included in <check> and <info> responses for
>>       "restore" commands.  It's still mandatory for all other commands.
>> 
>>   3.  Added summary of the attributes for the <fee:fee> element.
>> 
>>   4.  Clarified that the "refundable" and "grace-period" attributes of
>>       the <fee> fee elements are dependant on each other and cannot
>>       appear on their own.
>> 
>>   5.  Removed the option of returning a 1001 response when the fee is
>>       incorrect.
>> 
>>   6.  Forbidden the inclusion of extension elements in transform
>>       responses if no fee/credit has been assessed.
>> 
>>   7.  Made the <fee:currency> element optional in transform commands.
>> 
>>   8.  Amended XML Namespace section of IANA Considerations, added EPP
>>       Extension Registry section.
>> 
>> 10. TODO
>> 
>> 
>>   (Note to RFC Editor: remove this section before publication as an
>>   RFC.)
>> 
>>   1.  Make the extension object-agnostic so it can be used with other
>>       objects, not just vanilla domains.
>> 
>>   2.  Change the <check> command so that availability data is not
>>       returned.
>> 
>> -------- Forwarded Message --------
>> Subject: New Version Notification for draft-brown-epp-fees-04.txt
>> Date: Tue, 17 Feb 2015 02:16:09 -0800
>> From: internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>
>> To: Gavin Brown <gavin.brown@centralnic.com <mailto:gavin.brown@centralnic.com>>
>> 
>> A new version of I-D, draft-brown-epp-fees-04.txt
>> has been successfully submitted by Gavin Brown and posted to the
>> IETF repository.
>> 
>> Name: draft-brown-epp-fees
>> Revision: 04
>> Title: Registry Fee Extension for the Extensible Provisioning Protocol
>> (EPP)
>> Document date: 2015-02-17
>> Group: Individual Submission
>> Pages: 36
>> URL:
>> http://www.ietf.org/internet-drafts/draft-brown-epp-fees-04.txt <http://www.ietf.org/internet-drafts/draft-brown-epp-fees-04.txt>
>> Status:         https://datatracker.ietf.org/doc/draft-brown-epp-fees/
>> Htmlized:       http://tools.ietf.org/html/draft-brown-epp-fees-04
>> Diff:           http://www.ietf.org/rfcdiff?url2=draft-brown-epp-fees-04
>> 
>> Abstract:
>>   This document describes an Extensible Provisioning Protocol (EPP)
>>   extension mapping for registry fees.
>> 
>> 
>> 
>> 
>> 
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>> 
>> The IETF Secretariat
>> 
>> 
>> -- 
>> Gavin Brown
>> Chief Technology Officer
>> CentralNic Group plc (LSE:CNIC)
>> Innovative, Reliable and Flexible Registry Services
>> for ccTLD, gTLD and private domain name registries
>> https://www.centralnic.com/
>> 
>> CentralNic Group plc is a company registered in England and Wales with
>> company number 8576358. Registered Offices: 35-39 Moorgate, London,
>> EC2R 6AR.
>> 
>> 
>> 
>> _______________________________________________
>> EppExt mailing list
>> EppExt@ietf.org
>> https://www.ietf.org/mailman/listinfo/eppext
> 
> _______________________________________________
> EppExt mailing list
> EppExt@ietf.org
> https://www.ietf.org/mailman/listinfo/eppext