RE: [nc-whois] Fw: [dnssac] I-D ACTION:draft-ietf-crisp-requirements-01.txt (fwd)

["Abel Wisman" <abel@able-towers.com>]

Sound good to me, though I keep emphasizing, IF it ever gets done :)


Abel

And yes yes, I am working on those stats Kristy :))

A


-----Original Message-----
From: owner-nc-whois@dnso.org [mailto:owner-nc-whois@dnso.org] On Behalf
Of Ram Mohan
Sent: 09 October 2002 15:42
To: Kristy McKee
Cc: nc-whois@dnso.org
Subject: Re: [nc-whois] Fw: [dnssac] I-D
ACTION:draft-ietf-crisp-requirements-01.txt (fwd)


kristy,
happy to contribute :)

my suggestions as below:

<modified_paragraph>

Verisign is working with the IETF to develop a new Cross Registry
Information Service Protocol (a.k.a. CRISP) to improve or replace port
43 access to WHOIS data.

This new CRISP protocol attempts to define methods by which the
directory services of domain registries and the common base requirements
for extending the use of these services for other types of Internet
registries.  Although CRISP is not a centralized repository for Whois
data, upon adoption by registries and registrars, it would enable
Centralized Public Access by formalizing a uniform interface to the
WHOIS data, aiding the Task Force's focus on Uniformity and Consistency.

CRISP, upon adoption, may provide new ability for role-based access to
WHOIS information (for example, the Technical Contact level might permit
access to information relevant to networking, while the Billing Contact
level might permit access to information relevant to the needs of
finance, and so on).

CRISP may take many years to develop, implement and be universally
adopted, and is unlikely to be available as a short-term solution. In
the long run, however, it may help to address many of the concerns with
respect to a universally searchable Whois service.

The Task Force recommends to all interested parties to participate in
the IETF process, in order to provide sufficient guidance to ensure that
WHOIS in the future can be uniformly accessible and searchable.

</modified_paragraph>

-ram
--------------------------------------------------------
Ram Mohan
Vice President, Business Operations
Afilias.INFO
p: +1-215-706-5700; f: +1-215-706-5701
e: rmohan@afilias.info
--------------------------------------------------------

----- Original Message -----
From: "Kristy McKee" <k@widgital.com>
To: "Ram Mohan" <rmohan@afilias.info>
Cc: <nc-whois@dnso.org>
Sent: Monday, October 07, 2002 4:07 PM
Subject: Re: [nc-whois] Fw: [dnssac] I-D
ACTION:draft-ietf-crisp-requirements-01.txt (fwd)


> Ram, since you brought it up.
>
> I need a little assistance with a paragraph from WG3's report:
>
> <paragraph>
>
> With hope of fulfilling the universal Whois covenants included in 
> appendix W of Verisign's .com Registry agreement with ICANN, they are 
> working with the IETF to develop a new protocol (named CRISP) to 
> improve or replace
port
> 43 access to whois data.
>
> Although CRISP is not a centralized repository for Whois data, it 
> would enable Centralized Public Access by they way it interfaces with 
> that data.
>
> It might work more like a web crawler who identifies the location of 
> desired information, collects and returns it.
>
> It is a bit fancier than this however and should allow for more 
> controls, the CRISP solution will enable different levels of access to

> whois data by different types of users.
>
> For example, the Technical Contact level might permit access to
information
> relevant to networking, while the Intellectual Property Contact level
might
> permit access to information relevant to the needs of IP holders, and 
> so
on.
>
> CRISP may take many years to develop and implement. For that reason, 
> it is unlikely to be available as a short-term solution. In the long 
> run, however, it may help to address many of the concerns of the Task 
> Force Survey respondents with respect to a universal Whois service.
>
> </paragraph>
>
> <references>
>
> uWho:  http://uwho.verisignlabs.com/
> CRISP:  http://www.ietf.org/html.charters/crisp-charter.html
> Appendix W:  http://uwho.verisignlabs.com/com.html
>
> </references>
>