Kent,
I think you've hit on why I said "reducing the management problem" and not
"solving the management problem".
Though there may still be inter-registry issues with managing aliases, they
seem to reduce the intra-registry management problem. Assuming that aliases
must be unique within a registry I can now map all of the names associated
with a physical server to all of the addresses being used by that server in
a single object, and the address duplication issue within the registry goes
away.
Scott Hollenbeck
Network Solutions, Inc. Registry
-----Original Message-----
From: Kent Crispin [mailto:kent@songbird.com]
Sent: Friday, June 30, 2000 10:35 AM
To: rrp@nsiregistry.com
Subject: Re: [NSI-RRP] IP Address Uniqueness
On Fri, Jun 30, 2000 at 09:42:04AM -0400, Hollenbeck, Scott wrote:
> So, the problem with enforcing IP address uniqueness is that it introduces
a
> restriction that doesn't exist in the DNS. The problem with allowing
> registration of distinct name server objects that use IP addresses
> associated with other distinct name server objects is that you have the
same
> attribute data associated with multiple objects, making it more difficult
to
> manage the association of address to object.
>
> The aliasing suggestion I described appears to address both problems:
>
> 1. Each IP address is associated with only one name server object
(reducing
> the management problem), and
> 2. Each name server object can have multiple aliases (supporting the DNS
> data model).
Hmm. Maybe I'm even more dense than usual this morning...
I'm not sure how this solves anything. Haven't you just moved randy's
problem to the aliases? Don't we now have a management problem for
aliases? And if so, why bother with aliases?
-- Kent Crispin "Do good, and you'll be kent@songbird.com lonesome." -- Mark Twain --------- 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:42 EDT