ICANN/DNSO
DNSO Mailling lists archives

[registrars]


<<< Chronological Index >>>    <<< Thread Index >>>

[registrars] crisp: an ietf working group



the Cross Registry Information Service
Protocol (crisp) working group chartered in june is now defining the
requirements of a protocol as a replacement of port :43 whois. The working
group is currently discussing the requirements for the protocols under
development.

the latest version of the requirements document is at
http://www.ietf.org/internet-drafts/draft-ietf-crisp-requirements-00.txt

some of the most interesting requirements effecting domain registrars
are below.

the biggest issue I see with the group is a lack of participation by
registrars as most of the authors of the documents are employees of the
VeriSign registry. It is important for Registrars to participate in the
development of protocols that define our industry.


-rick


 3.2.4 Domain Registrant Search

   The service MUST provide the capability of searching for registrants
   by exact name match or a reasonable name subset. The service MAY
   provide limits to the number of results from this search to
   alleviate performance or comply with Section 3.1.1. If the service
   limits the number of results from this search to alleviate
   performance, it MUST provide the client with a response indicating
   this condition. If the service limits the number of results from
   this search to comply with Section 3.1.1, it MUST NOT provide the
   client with a response indicating this condition.

   The service MUST provide a mechanism to distribute this search
   across all applicable domain registries and registrars. The service
   SHOULD have a means to narrow the scope of a search to a specific
   TLD. The service MUST be able to specify to the client an empty
   result set should the search yield no results.

3.2.7 Escrow Support

   The service MUST provide a means to escrow data of domain registrars
   to an escrow entity using a common schema. This escrow capability
   SHOULD be "off-line" and "out-of-band" from the normal operations of
   the service.


3.2.8 Authentication Distribution

   The service MUST be capable of allowing a centralized authority
   entity the means to distribute authentication information of
   entities accessing the service.



<<< Chronological Index >>>    <<< Thread Index >>>