Re: Questions about containers

[Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>]

> Of course you are right that containers live in the registry. Therefore I
> could try to hide the existance of containers. 

How would you go about revealing their existance?

>                                            ... Unfortunately, there exists a
> whois service. ...

The whois mailing lists, either whois:43, or the !43 list, exist for whois-ish
issues. I've no idea what you see as a connection, err, container.

> BTW, some more comments, independent from the discussion above:
> 
> * the response to <domain:info> request does not disclose whether an attribute
> (e.g. host or contact) is derived from its container or whether it has been
> inserted directly into the domain. Even a comparison with its container would
> not reveal this information. That's bad.

Thanks. I'll look into this.

> * There's a big chance that an update of a container may render objects that a
> directly or indirectly linked to that container void, e.g. a domain defines by
> itself 12 name servers, and the the user attempts to add two name servers to a
> container of it, thereby exceeding the limit of 13 name servers. Reparenting
> objects and containers also has a big probability to fail as suddenly some
> required contacts may be missing. Of course, such attempts should result into
> an error. But the document does not describe how this is done. I think the way
> this is reported must be defined clearly, and all objects that would become
> void must be reported.

Ditto.

> * although I see some benefits in the container model, I am realizing slowly
> that it does not help to overcome my "single registrant - multiple registrars"
> and "registrar - reseller" problems in any way.

Really? I think the second problem is addressed by containers.

Eric