Re: Followup: Restrictions on EPP host renames?

On Thu, Dec 20, 2012 at 12:57 AM, Michael Young <[email protected]> wrote:

> And change the nature of any other in zone domains association to the host
> object from internal to external host
>
> That could turn into a heavy mass function. I'd hate to make a client side
> mistake in submitting that type of transaction request - ouch
>
> Michael Young
>
> M:647-289-1220
>
> On 2012-12-19, at 15:43, Francisco Obispo <[email protected]> wrote:
>
> > The whole change would have to live inside its own transaction, that is:
> >
> > -remove ip addresses
> > -change the host name (cascade)
> > -check constraints before commit
> >
> >
> >
> >
> > On Dec 19, 2012, at 12:41 PM, Michael Young <[email protected]> wrote:
> >
> >> No how would you handle existing glue records that are now not allowed?
>


 Exactly. This is a huge mine field. You don't know if the client didn't
expect the glue to move to the new name.

I find the rars always expect the most obscure possible interpretation you
didn't cater for. ;) The only sane option imho is to reject with a 2306 or
similar error for renaming subordinates.

Ed.

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