To:
"Hollenbeck, Scott" <shollenbeck@verisign.com>
Cc:
"'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>
From:
Joe Abley <jabley@isc.org>
Date:
Mon, 24 Mar 2003 00:59:39 -0500
In-Reply-To:
<3CD14E451751BD42BA48AAA50B07BAD603370873@vsvapostal3.prod.netsol.com>
Sender:
owner-ietf-provreg@cafax.se
Subject:
Re: [ietf-provreg] References for Today's Host Object Discussion
On Thursday, Mar 20, 2003, at 15:39 Canada/Eastern, Hollenbeck, Scott wrote: > - 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. Thanks for posting that link; I have been hearing similar comments for some time, and I hadn't realised the issue had already been considered. Eliminating the requirement to support host objects would make EPP a viable prospect for several registries that I have talked to recently. I wonder whether it might be reasonable to accommodate the non-host-object case in the current spec before it is shipped for proposed standard. This doesn't seem like it would be a major change to the text, and the impact on existing implementations seems small (zero, maybe) considering that the spec would not change for registries which choose to include host objects. I would be happy to contribute text if this sounds like a reasonable approach. Joe