[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
Date: Thu, 20 Mar 2003 15:39:13 -0500
Sender: owner-ietf-provreg@cafax.se
Subject: [ietf-provreg] References for Today's Host Object Discussion

After today's meeting some people asked me for a reference to an earlier
discussion about host objects being used as name servers.  For those of you
who weren't there, we talked a little bit about the history of why we have
an object concept for name server hosts.  Part of the ensuing discussion
touched on all of the options that have been discussed over the last few
years, including:

- Host objects for all name servers.
(This is a simplified expression of what we have in the documents now)

- Host objects for only in-zone hosts, with external hosts specified as
domain object attributes.
http://www.cafax.se/ietf-provreg/maillist/2002-11/msg00008.html

- Allowing a choice between name server host objects and name server domain
attributes.
http://www.cafax.se/ietf-provreg/maillist/2001-12/msg00024.html

I've included references to the list archives where I've been able to find
them.  What did we ever do before google came along...

For what it's worth, I kind of like the last option (or something like it)
as something to consider for the next version of the protocol.  We've heard
a lot of comments from people having issues with host objects as name
servers; maybe we can eliminate the issues if we allow a choice.

-Scott-

Home | Date list | Subject list