To:
asbjorn.rrp@theglobalname.org
Cc:
ietf-provreg@cafax.se
From:
Patrick <patrick@gandi.net>
Date:
Mon, 29 Oct 2001 13:52:01 +0100
Content-Disposition:
inline
In-Reply-To:
<20011029124012.4204.qmail@nameplanet.aftonbladet.se>; from asbjorn.rrp@theglobalname.org on Mon, Oct 29, 2001 at 12:40:12PM -0000
Sender:
owner-ietf-provreg@cafax.se
User-Agent:
Mutt/1.2.5i
Subject:
Re: Domain as Nameserver
On Mon, Oct 29, 2001 at 12:40:12PM -0000, asbjorn.rrp@theglobalname.org took time to write: > Hi, > > in draft-ietf-provreg-epp-host-03.txt it states: > > <<This document assumes that host name objects have a subordinate > relationship to a superordinate domain name object. For example, host > name "ns1.example.com" has a subordinate relationship to domain name > "example.com". EPP actions (such as object transfers) that do not > preserve this relationship MUST be explicitly disallowed.>> > > Let's use the .INFO Registry in our example [1]: > > If someone registers example.INFO, the RegistrANT has full control over the example.INFO zone, and he can thus use the domain name itself as a nameserver if he wants to. > > Will EPP allows the RegistrANT to add example.INFO as a _nameserver_ in the Registry, or do .INFO nameserver have to be on the third level? As far as I have seem from experimentations, they do not, but they should (or at least it is not forbidden in the drafts, but they are doing many things not explained anywhere) Patrick.