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

Frederico A C Neves <fneves@registro.br> Wed, 09 April 2003 00:51 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 UAA10087 for <provreg-archive@ietf.org>; Tue, 8 Apr 2003 20:51:27 -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 h390fCRN029578 for <ietf-provreg-outgoing@nic.cafax.se>; Wed, 9 Apr 2003 02:41:12 +0200 (MEST)
Received: by nic.cafax.se (8.12.9/8.12.9/Submit) id h390fC7S029577 for ietf-provreg-outgoing; Wed, 9 Apr 2003 02:41:12 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from clone.registro.br (clone.registro.br [200.160.2.4]) by nic.cafax.se (8.12.9/8.12.9) with ESMTP id h390fARN029572 for <ietf-provreg@cafax.se>; Wed, 9 Apr 2003 02:41:11 +0200 (MEST)
Received: by clone.registro.br (Postfix, from userid 1000) id 5D8E89299; Tue, 8 Apr 2003 21:41:09 -0300 (BRT)
Date: Tue, 08 Apr 2003 21:41:09 -0300
From: Frederico A C Neves <fneves@registro.br>
To: ietf-provreg@cafax.se
Subject: Re: [ietf-provreg] References for Today's Host Object Discussion
Message-ID: <20030409004109.GB2276@registro.br>
References: <5BEA6CDB196A4241B8BE129D309AA4AF10E635@vsvapostal8>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <5BEA6CDB196A4241B8BE129D309AA4AF10E635@vsvapostal8>
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk

Scott,

On Tue, Apr 08, 2003 at 01:56:29PM -0400, 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.
> 

This text is perfect for .br and solves all the problems I've tried to
explain at SF. If this moves forward we'll not need to use an
extension describing a different domain mapping or another crude hack,
so I'm all in favor of this.

> Example host object references:
> 
> <domain:ns>
>   <domain:hostObj>ns1.example.com</domain:hostObj>
>   <domain:hostObj>ns1.example.net</domain:hostObj>
> </domain:ns>
> 
> Example domain attributes that describe host machines:
> 
> <domain:ns>
>   <domain:hostAttr>
>     <domain:hostName>ns1.example.com</domain:hostName>
>   </domain:hostAttr>

Here there is a missing <domain:hostAttr> or I'm misunderstanding
something ?

>     <domain:hostName>ns1.example.net</domain:hostName>
>     <domain:hostAddr ip="v4">192.0.2.2</domain:hostAddr>
>   </domain:hostAttr>
> </domain:ns>
> 
> Ed: so when can we move forward with document edits for this and the privacy
> proposal?
> 
> -Scott-

Fred