Re: [regext] I-D Action: draft-ietf-regext-epp-fees-04.txt

2017-06-07 Thread Thomas Corte
Hello,

On 06/06/2017 20:27, Gould, James wrote:

> Thanks for posting the updated draft, it’s getting very close.  Below is
> my feedback to the latest version (04):
> ...
> a.   Revise the description of the  extension to define a new
> Fee Check Command, as defined in option #2 in the regext list
> (https://mailarchive.ietf.org/arch/msg/regext/2nZMuj9miTaEefyxeIgDnLKe9Rs/?qid=816ff935b150313c729350d5711051b1)
> message.  The last message on the thread message
> (https://mailarchive.ietf.org/arch/msg/regext/PV2lvVEZQEJKjhRhjT_2aPRVREA/?qid=ba41c1ce0656e3c9722d41f837d01b94)
> between Thomas Corte and I seemed to indicate that option #2 would meet
> the needs; although Thomas could weigh in on whether he agrees.

Yes, this was the option we agreed upon.

Best regards,

Thomas

-- 

 |   |
 | knipp |Knipp  Medien und Kommunikation GmbH
  ---Technologiepark
 Martin-Schmeißer-Weg 9
 44227 Dortmund
 Deutschland

 Dipl.-Informatiker  Tel:+49 231 9703-0
 Thomas CorteFax:+49 231 9703-200
 Stellvertretender LeiterSIP:thomas.co...@knipp.de
 Software-EntwicklungE-Mail: thomas.co...@knipp.de

 Registereintrag:
 Amtsgericht Dortmund, HRB 13728

 Geschäftsführer:
 Dietmar Knipp, Elmar Knipp

___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext


Re: [regext] I-D Action: draft-ietf-regext-epp-fees-04.txt

2017-06-07 Thread Thomas Corte
Hello,

On 05/06/2017 21:04, internet-dra...@ietf.org wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
> This draft is a work item of the Registration Protocols Extensions of the 
> IETF.
> 
> Title   : Registry Fee Extension for the Extensible 
> Provisioning Protocol (EPP)
> Authors : Roger Carney
>   Gavin Brown
>   Jothan Frakes
>   Filename: draft-ietf-regext-epp-fees-04.txt
> ...

Thanks for this new version. We're getting there :-)

In addition to what James wrote about section 3.1. ("Client Commands"),
there's also a discrepancy in that the text explicitly mentions the
"update" command, while the enumeration "commandEnum" doesn't contain
that command. I know it's unusual for registries to charge for updates,
and that this could essentially be covered by the "custom" case, but I
think it should be included as a first-class command for consistency.
This would require an XSD change though.

While we're at it, we should think about maybe including *automatic*
renewals (as opposed to explicit renewals) as a first-class type (e.g.
"auto-renew") here, too.
I know that it's not really a command (but an action that happens due to
the lack of a delete command), but *in theory* (and our own registry
system supports that) the price for an automatic renewal could be
different from an explicit renewal, e.g. if a registry wants to promote
the early renewal of domains. But if this deemed too exotic, I could live
with using the "custom" case to signal this.

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: supp...@tango-rs.com
Germany

___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext