To:
ietf-provreg@cafax.se
CC:
"Hollenbeck, Scott" <shollenbeck@verisign.com>, wessorh@ar.com
From:
Jens Wagner <jwagner@key-systems.net>
Date:
Tue, 06 Nov 2001 01:58:06 +0100
Sender:
owner-ietf-provreg@cafax.se
User-Agent:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.3) Gecko/20010803
Subject:
Re: "External" hosts in EPP
Hollenbeck, Scott wrote: >>-----Original Message----- >>From: Rick H Wesson [mailto:wessorh@ar.com] >>Sent: Monday, November 05, 2001 2:17 PM >>To: asbjorn.rrp@theglobalname.org >>Cc: ietf-provreg@cafax.se >>Subject: Re: "External" hosts in EPP >> >> >> >>asbjorn, >> >>another potential solution is to only requre host objects for hosts that >>require glue. in other words hosts outside the zone don't need a host >>object created. hosts inside the managed zone require a host object to be >>created and associated with the deligation. >> > >True, but this gets us back to the issue of losing the ability to change one >host object and having the change(s) reflected to all domains delegated to >the host. Do folks think that the benefit of the suggested change is >greater than the downside of having to perform host changes on a >domain-by-domain basis? > >I'm not trying to slam the suggestion (it could work quite well), I just >want to see a measure of interest in the trade-off. > >-Scott- > As long as the registry allows the registrars to rename out-of-zone hosts (based on the common f.c.f.s.) there will be a security issue regarding nameserver cybersquatting. I would prefer Rick's solution which removes this issue, even if it requires the registrar to implement one more foreach loop. Best regards, -jens