Registry lock - setting statuses on hosts

Hello,

At CIRA we are working through our approach to Registry Lock and are wondering what perspectives there are out there on the approach to setting of server statuses on hosts - i.e. the locking of hosts.

We are considering two main approaches:


1.       From the setting of a "domain lock" (serverUpdate, serverTransfer and serverDelete prohibited statuses set), automatically cascade the related host statuses (serverUpdate and serverDelete prohibited) to all host entities assigned (nameservers) to the domain in question.



2.       Separate the locking of domains and hosts into disparate transactions - i.e. one domain update transaction to set the domain server statuses followed by subsequent host update transactions to set server statuses on desired hosts.


Our main considerations here are balancing ease of use from a registrar's perspective vs differing too far from a consistent industry approach.

All feedback would be appreciated.

Thanks,
Stu

Stu Olmstead-Wilcox, Development Manager
Canadian Internet Registration Authority (CIRA)
Tel: (613) 237-5335 x265 | www.cira.ca |Twitter: @CIRASYSTEMS<http://twitter.com/CIRANEWS>
Trends, Commentary, Perspective.  Stay tuned to cirablog.ca<http://www.cirablog.ca/>

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