Re: Nameserver MUST HAVE IP

[Peter Eisenhauer <eisenhauer@schlund.de>]

See my previous posting with the example.

So name servers in the registry with "real" glue records (don't like the term
either) must be registered with ip addresses, the others could be handled like
name server outside the registry.

Then of course there must be checks, if the "glue" condition is valid if a
nameserver is registered or if a domain is updated...

I think the "Nameserver MUST be registered with ip address" is just too strong
for a generic requirement.


On Fri, Apr 06, 2001 at 09:33:57AM -0400, Hollenbeck, Scott wrote:
> >-----Original Message-----
> >From: Peter Eisenhauer [mailto:eisenhauer@schlund.de]
> >Sent: Friday, April 06, 2001 9:18 AM
> >To: ietf-provreg@cafax.se
> >Subject: Nameserver MUST HAVE IP
> >
> >
> >draft-ietf-provreg-grrp-reqs-01.txt:
> > "Name servers registered within the registry's authoritative TLDs MUST
> > be registered with a valid IPv4 or IPv6 address."
> >
> >I think this should be registry policy, not protocol requirement.
> >There are models in which IPs are not needed for *all* name 
> >servers inside the registry. The "MUST" excludes these solutions.
> 
> Could you provide an example of such a model and how it works?  I agree that
> it's not necessary for _all_ name servers to be registered with an address
> or addresses (such as when dealing with a name server from a
> non-authoritative TLD; the requirements deal with this situation), but I'd
> like to understand if you're suggesting that it should be OK to allow
> registration of ns1.foo.tld without addresses in the .tld registry, and what
> the .tld registry does with such a server.
> 
> <Scott/>

Mit freundlichen Gruessen,
Peter Eisenhauer

-- 
Peter Eisenhauer                        Schlund + Partner AG
Erbprinzenstrasse 4-12                  Tel: 0721/91374-0
76133 Karlsruhe                         E-Mail: eisenhauer@schlund.de