Re: Followup: Restrictions on EPP host renames?

Seth,

My thoughts are included below prefixed with "JG-".

--

JG

[cid:F51AA9DF-E0A0-4AD0-8B87-490143317B81]

James Gould
Principal Software Engineer
[email protected]

703-948-3271 (Office)
12061 Bluemont Way
Reston, VA 20190
VerisignInc.com



From: Seth Goldman <[email protected]<mailto:[email protected]>>
Date: Wednesday, December 19, 2012 3:00 PM
To: EPP Provreg <[email protected]<mailto:[email protected]>>
Subject: [provreg] Followup: Restrictions on EPP host renames?

Ok, so it's clear to me that host object renames should be supported by our implementation. So I had some follow-up questions on the topic:

Can you rename a subordinate host object to be under a different domain? (e.g. ns1.example.com<http://ns1.example.com> to ns1.otherdomain.com<http://ns1.otherdomain.com>)

JG - Yes, as long as the client sponsors both example.com and otherdomain.com.

Can you rename an external host object to be subordinate? (e.g. ns1.example.org<http://ns1.example.org> to ns1.example.com<http://ns1.example.com>)

JG – Yes, as long as you add the IP addresses to ns1.example.org in the same same update, the client sponsors example.com, and there are no links of domains sponsored by other registrars per RFC 5732.

Can you rename a subordinate host object to be external? (e.g. ns1.example.com<http://ns1.example.com> to ns1.example.org<http://ns1.example.org>)

JG – Yes, as long as you remove the IP addresses in the same update and ns1.example.org does not already exist.

The RFC doesn't seem to say anything on these questions. Is this just a server defined policy? Or should are all of the above be allowed?

JG – This is up to your server policy.

_______________________________________________
provreg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/provreg