mirror of
https://github.com/google/nomulus.git
synced 2025-07-20 01:35:59 +02:00
f28104ad03
It turns out that this ICANN policy appears to prohibit transfers with registration extensions other than 1 year (section A.8): https://www.icann.org/resources/pages/policy-2012-03-07-en This is backed up by the practical fact that we've never seen a registrar request a transfer for any period other than one year. And removing the support for multi-year transfers vastly simplifies transfer logic and eliminates a bunch of annoying corner cases. Users still can achieve the same thing by doing a 1-year transfer plus a manual renewal afterwards for the remainder of the desired extension. This change leaves in place lots of infrastructure to support multi-year transfers that is now obsolete (e.g. TransferData.extendedRegistrationYears). This should all be cleaned up, but it's a lower priority than fixing the gap itself and insulating ourselves against needing to handle any real multi-year transfer case. Once this CL goes in, we can start ignoring extendedRegistrationYears entirely because it'll always be 1 year, which makes the cleanup process easier. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=150212864 |
||
|---|---|---|
| .. | ||
| backup | ||
| batch | ||
| bigquery | ||
| braintree | ||
| builddefs | ||
| config | ||
| cron | ||
| dns | ||
| eclipse | ||
| env | ||
| export | ||
| flows | ||
| gcs | ||
| groups | ||
| idn | ||
| keyring | ||
| loadtest | ||
| mapreduce | ||
| model | ||
| module | ||
| monitoring | ||
| pricing | ||
| rdap | ||
| rde | ||
| request | ||
| security | ||
| storage/drive | ||
| tldconfig/idn | ||
| tmch | ||
| tools | ||
| ui | ||
| util | ||
| whois | ||
| xjc | ||
| xml | ||
| BUILD | ||
| repositories.bzl | ||