Re: Regestry Identifiers

["Rick H. Wesson" <wessorh@ar.com>]

On Nov 17, 11:02am, Dave Crocker wrote:
> Rick H. Wesson wrote:
> >is it the perview of the IAHC to determine how a regestery manages
> >contact, domain, and name server handles? If so should some one write
> >a proposal on how these identifers are to be handled, or is this
> >up to each regestry operator.
>
> (just to show that IAHC participants are not monolithic in their/our
views...)
>
> 	1.  I'm not entirely sure I know what you mean by 'how a registry
> manages'.  Please clarify a bit.

I was asking if the IAHC was going to mandate that a regestry should
provide a security mechanism for their contact data (ie gardian) or
if the IAHC was going to leave things like this up to the individual
regestry. I also wanted to understand if the IAHC was going to define
the format of the data a regestry must manage. (ie how contact handles
will be created so that you will know what regestry "owns" that handle)

> Certainly one should not dictate internal operations details.

I was not suggesting that internal opperational details be defined but asking
if a certain level of "basic service" should be defined.

> 	2.  External aspects might well be subject to efforts at creating
> an integrated, global service.  I believe that the IETF would be
> appropriate for this only if there are technical questions, either
> involving the creation of new technology standards or in 'profiling' a
> collection of specifications into an integrated service for this purpose.
> My own thought is that the latter would be pretty nifty.

Would it be better to work out a common set of templates or is everybody
going to use the ones the InterNic uses. Would it not be better that an IETF
WG define these templates and write a public domain parser for them? I also
have lots of questions about the interoplation of contact handles. I wanted
to know if I should submit a proposal to the IAHC on the topic or persu the
creation of a IETF WG to deal with the subject.

I believe that regestries are going to have to look up a lot of
contact data contained by another regestry and I don't believe that (r)whois
is the appropiate method for doing this. I would like to see another standard
for an integrated regestry.


> 	3.  I'd guess that the IAHC will, in fact, want to specify a number
> of external aspects about registry information management, in response to
> public concerns over quality control and public information access.  At the
> moment, I have no idea what form or detail this is likely to take.

This is what my main question was about. The data management side of things
and weather these should be defined by the IAHC or within the perview
of an IETF process. I just don't want to waste my efforts tring to get
this into the IETF and then the IAHC make a paper on the same topic.


The situation I would like to avoid is the one where the ISP is confused
as to the procedures used to regester and manage data related to
    o requesting new domains
    o protecting others from using their name server w/o their approval.
    o notification of deleteing a domain.
    o domain modification.
    o where to get/send domain templates.

Thanks,

-Rick

-- 
Rick H. Wesson