mirror of
https://github.com/google/nomulus.git
synced 2025-05-06 06:57:50 +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
15 lines
453 B
XML
15 lines
453 B
XML
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
|
|
<command>
|
|
<transfer op="request">
|
|
<domain:transfer
|
|
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
|
|
<domain:name>fakesite.example</domain:name>
|
|
<domain:period unit="y">1</domain:period>
|
|
<domain:authInfo>
|
|
<domain:pw>2fooBAR</domain:pw>
|
|
</domain:authInfo>
|
|
</domain:transfer>
|
|
</transfer>
|
|
<clTRID>ABC-12345</clTRID>
|
|
</command>
|
|
</epp>
|