To:
"Hollenbeck, Scott" <shollenbeck@verisign.com>
Cc:
"'Edward Lewis'" <edlewis@arin.net>, "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>
From:
Joe Abley <jabley@isc.org>
Date:
Sat, 5 Apr 2003 16:22:06 -0500
In-Reply-To:
<3CD14E451751BD42BA48AAA50B07BAD6033708BE@vsvapostal3.prod.netsol.com>
Sender:
owner-ietf-provreg@cafax.se
Subject:
Re: [ietf-provreg] References for Today's Host Object Discussion
Hey Scott, On Monday, Mar 31, 2003, at 08:17 Canada/Eastern, Hollenbeck, Scott wrote: >> Unless I am missing something, Scott, can you propose some text that >> would accommodate nameservers-as-attributes? Based on: >> >>> - Allowing a choice between name server host objects and >> name server domain >>> attributes. >>> http://www.cafax.se/ietf-provreg/maillist/2001-12/msg00024.html > > Sure. Here's what I have in mind: This looks good. It would be helpful to see the descriptive text you mentioned (and some example requests) to confirm that I'm understanding what you mean, exactly. There is one related issue that may deserve some thought. At the moment an address is required for a host record if the host is named under the apex of the registry. Where hosts are specified as attributes of domain objects, however, there is the opportunity to modify that rule; addresses can be required on hosts which are named under the domain in whose object they appear. So, for example, a domain object for "automagic.org" might contain host attributes for nameservers "buffoon.automagic.org", "ns1.flame.org" and "foo.something-else.com". Only the "buffoon.automagic.org" host would require addresses under the scheme outlined above. In the case of a registry which supports hosts-as-attributes, this (or something like it) seems like it would be necessary to avoid different domain objects containing conflicting addresses for hosts. Joe