RE: [EPP-discuss] EPP update domain draft proposal

From: Tom Sommer <>
Date: Thu, 12 May 2016 12:56:48 +0000

Well, the correct term is actually "billing cycle", so I suggest we use this in order to avoid confusion.

A 'normal', non-dk domain does not have the concept of changing billing cycles, hence you won't find support for this in the EPP-spec.
Usually TLDs mandate a minimum registration/renew-period (1 or 2 years) and a maximum renew period of 10 years (from current expiration date).

It would be nice to be able to lower it through EPP though, if you wish to continue to support the setting.

Tom Sommer
CTO at UnoEuro A/S, a Zitcom A/S division

Phone: +45 69 10 60 09

-----Original Message-----
From: Jonas Brømsø Nielsen []
Sent: 12. maj 2016 14:51
To: Andreas Schraut-Petto <>
Subject: Re: [EPP-discuss] EPP update domain draft proposal

Hi Andreas,

And you might be right that this is the proper way.

We support altering the period via our self-service platform and would love to support the same feature via EPP.

The thing that confuses me is this:

> The EPP <update> command provides a transform operation that allows a
> client to modify the attributes of a domain object.


But it seems that it is only possible to change: roles, nameservers, DNSSEC (via extension) and registrant. So the period is all of a sudden regarded as a secondrate citizen, even though it influences the future invoicing cycle.

So based on that you would have to require a RENEW command to change it.

I will try to analyse it more deeply perhaps it is just a case of “same same, but different”, since it seems the effect will actually be the same.


> On 12 May 2016, at 14:33, Andreas Schraut-Petto <> wrote:
> Hi All,
> as far as I know, it's not common to change the registration period (or
> even to offer the possibility to do that).
> It's more like using the renew command to tell the system for how many
> years a domains lifetime should be extended.
> Best regards,
> Andreas
> Am 12.05.2016 um 14:22 schrieb Jonas Brømsø Nielsen:
>> Hello All,
>> I have created a somewhat first draft for an update domain command implementation, it is available at:
>> A lot of aspects are not clarified yet, please refer to the TODO file:
>> I have added a first shot at a privilege matrix:
>> I have revisited the issue of changing the registration period attribute using EPP and I cannot find any documentation on examples on this, so I think this is a dead end (brainfart from an old TODO list, which survived too long). The only relations to this attribute seems to be in relation to domain:transfer and domain:renew.
>> If anybody can provide me with information on who to change registration periode via EPP, please do. The only alternative I can see right now would be an extension along the lines of:
>> <extension>
>> <dkhm:updateDomain>
>> <chg>
>> <domain:period>5 </domain:period>
>> </chg>
>> </dkhm:updateDomain>
>> </extension>
>> Looking forward to your feedback.,
>> jonasbn
>> —
>> Med venlig hilsen/Best Regards
>> Jonas B. Nielsen
>> Development Team Leader / Team leder for Udvikling
>> Kalvebod Brygge 45, 3. sal
>> 1560 København V
>> Tlf. +45 33 64 60 60
>> Fax.: +45 33 64 60 66
>> Email:
>> Homepage:
>> .dk Danmarks plads på Internettet
>> -------------------------------------------------------------------------
>> Dette er en e-mail fra DK Hostmaster A/S. Denne e-mail kan indeholde
>> fortrolig information, som kun er til brug for den tiltænkte modtager.
>> Hvis du ved en fejl har modtaget denne e-mail, bedes du venligst straks
>> give afsenderen besked om dette og slette e-mailen fra dit system uden
>> at offentliggøre, videresende eller tage kopi af meddelelsen.
>> This is an email from DK Hostmaster A/S. This message may contain
>> confidential information and is intended solely for the use of the
>> intended addressee. If you are not the intended addressee please notify
>> the sender immediately and delete this e-mail from your system. You are
>> not permitted to disclose, distribute or copy the information in this
>> e-mail.
>> --------------------------------------------------------------------------

Received on Thu May 12 2016 - 14:56:48 CEST

This archive was generated by hypermail 2.3.0 : Thu May 12 2016 - 14:57:00 CEST