RFC 3707: Cross Registry Internet Service Protocol (CRISP) Requirements
In plain English — editorial summary, not part of the RFC
Internet registries expose administrative and operational data via varying directory services. This document defines functional requirements for the directory services of domain registries and the common base requirements for extending the use of these services for other types of Internet registries. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3707
- Published
- February 2004
- Authors
- A. Newton
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 26
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3730Extensible Provisioning Protocol (EPP)Obsoleted
March 2004
- RFC 3731Extensible Provisioning Protocol (EPP) Domain Name MappingObsoleted
March 2004
- RFC 3732Extensible Provisioning Protocol (EPP) Host MappingObsoleted
March 2004
- RFC 3733Extensible Provisioning Protocol (EPP) Contact MappingObsoleted
March 2004
- RFC 3734Extensible Provisioning Protocol (EPP) Transport Over TCPObsoleted
March 2004
- RFC 3735Guidelines for Extending the Extensible Provisioning Protocol (EPP)Current
March 2004
- RFC 3744Web Distributed Authoring and Versioning (WebDAV) Access Control ProtocolCurrent
May 2004
- RFC 3752Open Pluggable Edge Services (OPES) Use Cases and Deployment ScenariosCurrent
April 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?