2.1.3 Cross Registry Information Service Protocol (crisp)

NOTE: This charter is a snapshot of the 65th IETF Meeting in Dallas, TX USA. It may now be out-of-date.

Last Modified: 2005-10-04

Chair(s):

April Marine <april.marine@nominum.com>
George Michaelson <ggm@apnic.net>

Applications Area Director(s):

Ted Hardie <hardie@qualcomm.com>
Scott Hollenbeck <sah@428cobrajet.net>

Applications Area Advisor:

Ted Hardie <hardie@qualcomm.com>

Mailing Lists:

General Discussion: crisp@ietf.org
To Subscribe: https://www1.ietf.org/mailman/listinfo/crisp
Archive: http://www.ietf.org/mail-archive/web/crisp/index.html

Description of Working Group:

In the standard operation of Internet systems, various labels and data
are managed globally -- domain names, IPv4 and IPv6 addresses,
etc. From time to time, for operational and administrative purposes,
users of the Internet need to be able to find and access registered
nformation associated with those labels.

The CRISP (Cross-Registry Information Service Protocol) WG will
define a standard mechanism that can be used for:

- finding authoritative information associated with a label,

- a protocol to transport queries and responses for accessing that
information,

- a first profile (schema & queries) to support commonly-required
queries for domain registration information,

- a second profile (schema & queries) to support commonly-required
queries for numbering resource information. ("numbering resources"
is used to refer to IP addresses and ASNs)

The WG will strive to preserve an extensible architecture so that the
work possibly be useful in the future to other types of registries
beyond those specifically considered by the group.


Specific topics that are NOT goals of this WG are:

- Backwards compatibility with existing administrative directory
services such as WHOIS.

- Provisioning of data into registry or registrar systems. CRISP
provides a uniform access to and view of data that may be held in
disparate backend servers.

The CRISP service definition will define:

- a standard mechanism that can be used to determine the
authoritative server(s) for information about a given label

- a single mandatory to implement protocol for transporting
application queries and responses, including

- expression of input query

- expression of result sets

- standard expression of error conditions

- authentication and verification of data integrity

- specific data types and queries to be supported in the
supported registry services.

Deliverables:

- Requirements document as an Informational RFC. (previously
submitted)

- First draft of protocol (use) specification. (previously submitted)

- First draft of domain registration administrative directory
services required schema element specification. (previously submitted)

- Document specifying a new protocol, or the use of an existing one,
for providing CRISP service (application transport).

- Document specifying required schema elements and queries for domain
registration administrative directory queries.

- Document specifying required schema elements and queries for
numbering resources registration administrative directory queries.

Goals and Milestones:

Done  Submit requirements document as an Informational RFC
Done  Submit first draft of protocol (use) specification
Done  Submit first draft of domain registration administrative directory services required schema element specification.
Done  Submit revised protocol (use) specification document as Proposed Standard
Done  Submit revised draft of domain registration administrative directory services required schema element specification as Proposed Standard.
Done  Submit first draft of IP address registration administrative directory services required schema element specification
Done  Submit revised draft of IP address registration administrative directory services required schema element specification as Proposed Standard
Jan 2006  Submit the following drafts for IESG review (Proposed Standards)
Jan 2006  A Domain Availability Check (dchk) Registry Type for the Internet Registry Information Service (IRIS) (Submit to IESG review for Proposed Standard)
Jan 2006  A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service (Submit to IESG review for Proposed Standard)
Jan 2006  A Common Schema for Internet Registry Information Service Transfer Protocols (Submit to IESG review for Proposed Standard)
Jan 2006  XML Pipelining with Chunks for the Information Registry Information Service (Submit to IESG review for Proposed Standard)

Internet-Drafts:

  • draft-ietf-crisp-iris-areg-13.txt
  • draft-ietf-crisp-iris-dchk-04.txt
  • draft-ietf-crisp-iris-lwz-05.txt
  • draft-ietf-crisp-iris-common-transport-03.txt
  • draft-ietf-crisp-iris-xpc-03.txt
  • draft-ietf-crisp-iris-dreg2-00.txt

    Request For Comments:

    RFCStatusTitle
    RFC3707 I Cross Registry Internet Service Protocol (CRISP) Requirements
    RFC3981 Standard IRIS - The Internet Registry Information Service (IRIS) Core Protocol
    RFC3982 Standard IRIS - A Domain Registry (dreg) Type for the Internet Registry Information Service
    RFC3983 Standard IRIS - Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP)

    Meeting Minutes


    Slides

    None received.