Eric,
I'm raising this issue in the first place for two reasons:
1. The current NSI Registry implementation of NSI RRP does not allow
duplication of IP addresses. As Patrik noted, there is no restriction that
limits DNS A records to unique IP addresses, so I wanted to ensure that the
requirements for the GRRP reflect community consensus instead of blindly
carrying over earlier NSI RRP requirements.
2. Allowing duplication of IP addresses has an implicit impact on how
searches are performed and the kind of information returned as the results
of a successful search. For example, if we allow a registrar to delete a
name server by IP address, and that address is referred to by more than one
server name, should only one of the server names be deleted or should all of
them?
FWIW I'm leaning towards including requirements for query operations by IP
address but NOT for operations that modify data. Since server names are
still required to be unique, there's no risk of unintended collateral damage
when a server is <insert data modification op here> by name.
Scott Hollenbeck
Network Solutions, Inc. Registry
-----Original Message-----
From: Eric Brunner [mailto:brunner@world.std.com]
Sent: Thursday, June 29, 2000 10:31 AM
To: shollenb@netsol.com
Cc: rrp@nsiregistry.com
Subject: Re: [NSI-RRP] IP Address Uniqueness
Scott,
Lacking a motivation to subset DNS functionality, why this particular one
(A records)?
Where does a requirement that uniqueness in the names-to-addrs mapping exit?
The point is to provide a mechanism for distribution, with some properties,
not to assert some semantics for what is distributed, neh? Why do we care?
We're not wirebrushing content (or business practices).
Eric
---------
See http://www.nsiregistry.com/maillist/rrp/
for message archives and subscription management information.
This archive was generated by hypermail 2b29 : Mon Jul 03 2000 - 13:38:55 EDT