mirror of
https://github.com/google/nomulus.git
synced 2025-08-03 16:32:11 +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
22 lines
777 B
XML
22 lines
777 B
XML
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
|
|
<response>
|
|
<result code="1001">
|
|
<msg>Command completed successfully; action pending</msg>
|
|
</result>
|
|
<resData>
|
|
<domain:trnData xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
|
|
<domain:name>fakesite.example</domain:name>
|
|
<domain:trStatus>pending</domain:trStatus>
|
|
<domain:reID>TheRegistrar</domain:reID>
|
|
<domain:reDate>2002-05-30T00:00:00Z</domain:reDate>
|
|
<domain:acID>NewRegistrar</domain:acID>
|
|
<domain:acDate>2002-06-04T00:00:00Z</domain:acDate>
|
|
<domain:exDate>2003-06-01T00:04:00Z</domain:exDate>
|
|
</domain:trnData>
|
|
</resData>
|
|
<trID>
|
|
<clTRID>ABC-12345</clTRID>
|
|
<svTRID>server-trid</svTRID>
|
|
</trID>
|
|
</response>
|
|
</epp>
|