Re: EPP host renames

Actually, the RFC only says that this action is disallowed for external
hosts. For subordinate hosts, it's not well defined.

On Wed, Dec 19, 2012 at 1:44 PM, Francisco Obispo <[email protected]> wrote:

> well if another registrar is referencing the host you created, you're not
> supposed to allow the update:
>
> From RFC5732:
>
>    Host name changes can have an impact on associated objects that refer
>    to the host object.  A host name change SHOULD NOT require additional
>    updates of associated objects to preserve existing associations, with
>    one exception: changing an external host object that has associations
>    with objects that are sponsored by a different client.  Attempts to
>    update such hosts directly MUST fail with EPP error code 2305.  The
>    change can be provisioned by creating a new external host with a new
>    name and any needed new attributes, and subsequently updating the
>    other objects sponsored by the client.
>
>
>
> On Dec 19, 2012, at 10:41 AM, Seth Goldman <[email protected]> wrote:
>
> > I see. You're saying that the host object rename lets you work around
> the scenario where another registrar has a reference to one of your
> subordinate host objects. Otherwise, you're stuck in a scenario where you
> can't delete the domain until that other registrar removes its reference.
> Fair point, there's clearly no workaround for that.
>
> Francisco Obispo
> Director of Applications and Services - ISC
> email: [email protected]
> Phone: +1 650 423 1374 || INOC-DBA *3557* NOC
> PGP KeyID = B38DB1BE
>
>

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