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

Joe Abley <jabley@isc.org> Tue, 08 April 2003 18:48 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 OAA26053 for <provreg-archive@ietf.org>; Tue, 8 Apr 2003 14:48:17 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.9/8.12.9) with ESMTP id h38IadRN026245 for <ietf-provreg-outgoing@nic.cafax.se>; Tue, 8 Apr 2003 20:36:39 +0200 (MEST)
Received: by nic.cafax.se (8.12.9/8.12.9/Submit) id h38IadNC026244 for ietf-provreg-outgoing; Tue, 8 Apr 2003 20:36:39 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from buffoon.automagic.org (buffoon.automagic.org [208.185.30.208]) by nic.cafax.se (8.12.9/8.12.9) with SMTP id h38IabRN026239 for <ietf-provreg@cafax.se>; Tue, 8 Apr 2003 20:36:38 +0200 (MEST)
Received: (qmail 89866 invoked by uid 0); 8 Apr 2003 18:36:36 -0000
Received: from localhost.automagic.org (HELO isc.org) (root@127.0.0.1) by localhost.automagic.org with SMTP; 8 Apr 2003 18:36:36 -0000
Date: Tue, 08 Apr 2003 14:36:44 -0400
Subject: Re: [ietf-provreg] References for Today's Host Object Discussion
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v552)
Cc: 'Edward Lewis' <edlewis@arin.net>, "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>
From: Joe Abley <jabley@isc.org>
In-Reply-To: <5BEA6CDB196A4241B8BE129D309AA4AF10E635@vsvapostal8>
Message-Id: <0C0C40B4-69F1-11D7-BFDC-00039312C852@isc.org>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Tuesday, Apr 8, 2003, at 13:56 Canada/Eastern, Hollenbeck, Scott 
wrote:

>> 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.
>
> Text:
>
> "Name server hosts for domain delegation can be specified as either
> references to existing host objects or as domain attributes that 
> describe a
> host machine.  A server operator MUST use one name server 
> specification form
> consistently.  A server operator that announces support for host 
> objects
> MUST NOT allow domain attributes to describe a name server host 
> machine.  A
> server operator that does not announce support for host objects MUST 
> allow
> domain attributes to describe a name server host machine."
>
> The idea here is that it's a bad idea to allow some domain objects in a
> repository to reference host objects and others to use domain 
> attributes
> that describe a host machine.  Using one form consistently will make
> implementation and server management easier.
>
> [examples]

Cool, that's what I understood. That's all good.

I presume that text would slot into draft-ietf-provreg-epp-domain-06 
section 1.1 in some way (the corresponding section in 
draft-ietf-provreg-epp-host-06 could maybe stay as-is, since if you 
need the spec for host objects you're probably not running a server 
that uses host attributes on domain objects).

The domain mapping document should presumably inherit some text along 
the lines of section 2.5 in the host mapping document, to the effect 
that "When a host object is provisioned for use as a DNS name server, 
IP addresses SHOULD be required only as needed to generate DNS glue 
records."

Stronger text which says that IP addresses MUST only be present in host 
attributes if the host name is subordinate to the containing domain 
object name sounds like it is more than is required (and e.g. will not 
be compatible with the data in the NL registry, as per Jaap.


Joe