To:
ietf-provreg@cafax.se
From:
Urs Eppenberger <urs.eppenberger@switch.ch>
Date:
Thu, 08 Feb 2001 14:02:41 +0100
Content-Disposition:
inline
In-Reply-To:
<DF737E620579D411A8E400D0B77E671D7505BC@regdom-ex01.prod.netsol.com>
Sender:
owner-ietf-provreg@cafax.se
Subject:
RE: draft-hollenbeck-grrp-reqs-06 [Was Re: Interim Meeting]
--On Mittwoch, 7. Februar 2001 10:26 Uhr -0500 "Hollenbeck, Scott" <shollenbeck@verisign.com> wrote: > [11] The protocol MUST provide services to manage name servers associated > with multiple domains. No name server data SHOULD exist in the registry > without an associated parent domain. The first sentence is OK. It talks about protocol level. The second sentence is about what a registry is allowed to store, and this does not make sense here. At SWITCH we register nameserver objects without checking if they are 'used'. We register the corresponding IP addresses and a contact person. (Often fetching the e-mail address from the SOA record does not help in case of misconfigurations, because e-mail just does not work anymore. For this we keep a more or less complete set of contact information for the hostmaster of the nameserver. He is the owner of the object and has the right to change attribute values like IP adresses.) We allow certain changes at a specific date, for example the replacement of nameservers for a domain. For this you need to register the nameservers first, without the connection to the domain. And at the agreed date the old nameserver are replaced. Therefore to require that 'no nameservers SHOULD exist' does not make sense for me. Urs.