[ietf-provreg] References for Today's Host Object Discussion

"Hollenbeck, Scott" <shollenbeck@verisign.com> Thu, 20 March 2003 20:53 UTC

Received: from nic.cafax.se (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06112 for <provreg-archive@ietf.org>; Thu, 20 Mar 2003 15:53:52 -0500 (EST)
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.8/8.12.8) with ESMTP id h2KKgIx9023326 for <ietf-provreg-outgoing@nic.cafax.se>; Thu, 20 Mar 2003 21:42:18 +0100 (MET)
Received: by nic.cafax.se (8.12.8/8.12.8/Submit) id h2KKgI38023325 for ietf-provreg-outgoing; Thu, 20 Mar 2003 21:42:18 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from crow.verisign.com (crow.verisign.com [216.168.237.103]) by nic.cafax.se (8.12.8/8.12.8) with ESMTP id h2KKgGx9023320 for <ietf-provreg@cafax.se>; Thu, 20 Mar 2003 21:42:16 +0100 (MET)
Received: from vsvapostalgw3.prod.netsol.com (vsvapostalgw3.prod.netsol.com [10.170.12.61]) by crow.verisign.com (nsi_0.1/8.9.1) with ESMTP id PAA01292 for <ietf-provreg@cafax.se>; Thu, 20 Mar 2003 15:42:09 -0500 (EST)
Received: by vsvapostalgw3.prod.netsol.com with Internet Mail Service (5.5.2653.19) id <G93DNRL6>; Thu, 20 Mar 2003 15:39:14 -0500
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD603370873@vsvapostal3.prod.netsol.com>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>
Subject: [ietf-provreg] References for Today's Host Object Discussion
Date: Thu, 20 Mar 2003 15:39:13 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

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-