Re: Domain object template

[Geert Jan de Groot <]

I have a couple of comments on this draft:

On Wed, 11 Jan 1995 09:41:16 +0100  Marten Terpstra wrote:
> Francis has made an update to the old domain object template. A draft
> version of his document is attached below. Please comment on this
> document, it should preferably be OK'ed at the coming RIPE meeting.
> This document is also available as:
> ftp://ftp.ripe.net/ripe/drafts/ripe-domain.{txt|ps}


> admin-c: The admin-c attribute contains the name or the  NIC
>          handle  of  the administrative contact person. This
>          is someone who will be contacted about  administra-
>          tive things such as domain registration etc.  A NIC
>          handle (if known) is preferred. Please do  not  use
>          formal  titles  like  'Dr', 'Prof' or 'Sir'. Do not
>          add full stops  between  names  or  initials.  This
>          value  should  be exactly the same as the attribute
>          in the person object  (see  further  below).   More
>          than  one  administrative  contact  person  can  be
>          specified, by simply repeating  the  attribute.  An
>          example of both the NIC handle and normal name use:
> 
>                  admin-c:  Daniel Karrenberg
>          or (preferred)
>                  admin-c:  DK58
> 
>          Status: mandatory, multiple lines allowed

I suggest to make mandatory that the administrative contact
should reside on the site itself. Assume that people have outsourced
the 'technical stuff' of their network, then it is likely that the
technical contact is someone belonging to another company, and
it might be difficult to get in touch with the holder of the 
domain itself because the address/phone number is different.

> nserver: The  nserver  attribute  contains   the   list   of
>          nameservers  for of this domain, primary first. The
>          format  is  fully  qualified  domain  name  without
>          trailing  "."  OR IP Address(es) of the nameserver.
>          Only one server should be described per  line.   An
>          example:
> 
>                  nserver: iraun1.IRA.UKA.DE
> 
>          Status: optional, multiple lines allowed

Can we please drop the possibility of allowing IP numbers here?
If one of the secondaries of your domain changes IP number, then
he has the nearly impossible task of finding all these outdated
references. Bind only allows hostnames here; I think it is a good
idea to restrict the database in the same way.

Also, we might add 'the first nserver listed is the primary for the zone'

> dom-net: The dom-net attribute contains the list of IP  net-
>          works  in  this  domain.  The format is dotted quad
>          including trailing 0s, extended formats defined  in
>          [1]  for range of IP address space are allowed.  An
>          example:
> 
>                  dom-net: 129.13.0.0 192.54.104.0
> 
>          Status: optional, multiple lines allowed

Can someone please explain why it is useful to record this?
Seems that this info might get outdated quickly as it isn't
related to the domain _name_.

Comments?

Geert Jan