Define Exceeding Maximum Expiration Date Policy

[james-f-gould]

Patrick Mevzek comment on the REGEXT mailing list (https://mailarchive.ietf.org/arch/msg/regext/T33Zp_4pmwd94K_QuEDA6cPHK7Y):

• about periods

• something around maximum expiration date, like the ICANN rule on 10 years max and what happens for commands that would go beyond that (ex: create for 9 years and immediate renewal for 5)

Jim Gould reply to comment on the REGEXT mailing list:

What are the possible set of policies out in the wild? We clip the fractional period past the maximum year (10.5 years would become 10 years and attempting to go 11 or more years would fail).

We need additional information related to the possible set of policies from the registries. Right now the only policy discussed on the list is clipping fractional days beyond the maximum expiration date, but exceeded the maximum expiration by a full unit (year or month) will result in an error.

[james-f-gould]

I am going to leave this topic open for further discussion on the various registry policies associated with exceeding the maximum expiration date. I really only see two possible options:

1. Fail when the expiration date exceeds the maximum expiration date by a fraction of a period. An example is if the maximum expiration date is 10 years, and a client renews a domain to 10.5 years, the server will fail the renew.
2. Clip the fractional period when the expiration date exceeds the maximum expiration date by a fraction of a period. An example is if the maximum expiration date is 10 years, and the client renews a domain to 10.5 years, the server will clip the .5 fractional year so that the domain will expire exactly in 10 years.

Maybe we can add the <registry:exceedMaxExDate> element under the registry:domain element after the <registry:period> element, with the description:

Zero or more <registry:exceedMaxExDate> elements that defines the action taken by the server when executing commands that will result in an expiration date that exceeds the maximum expiration date. The required "command" attribute is used to define the command with a renewal feature, such as "renew" or "transfer". New commands can be defined that include a renewal feature, such as "sync". The possible values for the <registry:exceedMaxExDate> element include:

• "fail": The server will fail the renewal command when the expiration date exceeds the maximum expiration date. An example is if the maximum expiration date is 10 years, and a client renews a domain name to 10.5 years, the server will fail the renew.

• "clip": The server will clip the fractional period when the expiration date exceeds the maximum expiration date by a fraction of a period and will fail the renewal command when the expiration date exceeds the maximum expiration date by a whole period and above. An example is if the maximum expiration date is 10 years, and the client renews a domain to 10.5 years, the server will clip the .5 fractional year so that the domain name will expire exactly in 10 years.

• "disableRenewal": The server will execute the command with the renewal feature disabled when the expiration date exceeds the maximum expiration date. This may be the case for a command like "transfer" that includes a renewal feature in [RFC5731].

[james-f-gould]

Added the <registry:exceedMaxExDate> element under the <registry:domain> element to support returning the server policy when the client exceeds the maximum expiration date on a per renewal command basis, based on feedback from Patrick Mevzek.