Re: My personal comments on the requirements.

[Patrik Fältström <paf@cisco.com>]

At 13.49 -0500 00-12-22, AndrÈ Cormier wrote:
>  >  [5] The protocol MUST consider that the name server associated with a
>>   domain might not be registered in the same domain or even in a TLD for
>>   which the registry is authoritative.  This means that IP addresses for
>>   name servers whose parent domain exists in another TLD MUST be
>>   registered only in the registry that is authoritative for the TLD of
>>   the name server.  Glue records (DNS "A" records) MUST NOT be created
>>   for DNS NS records for which the registry is not authoritative.
>AC: I do not think this is protocol related. It will be the registry 
>application that
>AC: will create the DNS zone file and glue records. It should not be 
>state as a
>AC: requirement. I caan easily see that as a comment in the protocol 
>definition draft
>AC: and a pointer to a companion document for best current practices.

The problem with glue in some zones or registries which do not belong 
there but in a different zone is what happens when the IP address of 
those glues change. Should one owner of a nameserver remember to talk 
to _every_ registry and change the IP address, or just the one which 
the IP address really belong? If you say it is only a requirement of 
the zone that is generated, what is your thought of why the IP 
address need to be in the database of the registry? What happens if 
that IP address becomes out of date? I.e. if you are a registry, and 
have one Ip address in your database, and you by using DNS find a 
different IP address in DNS, which one will you trust (I hope the one 
in DNS) and why in that case do you need one in the database?

I need more arguments for why the IP address needs to be in more than 
one place, i.e. in the registry which really own the correct TLD for 
the NS, where the glue really should be.

Storing the same information in more than one place is generally (in 
my experience) a bad thing, and always leads to inconsistency between 
records.

    paf


-- 
Patrik Fältström <paf@cisco.com>       Internet Engineering Task Force
Area Director, Applications Area                   http://www.ietf.org
Phone: (Stockholm) +46-8-4494212            (San Jose) +1-408-525-0940
        PGP: 2DFC AAF6 16F0 F276 7843  2DC1 BC79 51D9 7D25 B8DC