Browse Prior Art Database

Cross Registry Internet Service Protocol (CRISP) Requirements (RFC3707)

IP.com Disclosure Number: IPCOM000021757D
Original Publication Date: 2004-Feb-01
Included in the Prior Art Database: 2004-Feb-06
Document File: 27 page(s) / 53K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Newton: AUTHOR

Abstract

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 text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 7% of the total text.

Network Working Group A. Newton

Request for Comments: 3707 VeriSign, Inc.

Category: Informational February 2004

Cross Registry Internet Service Protocol (CRISP) Requirements

Status of this Memo

This memo provides information for the Internet community. It does

not specify an Internet standard of any kind. Distribution of this

memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2004). All Rights Reserved.

Abstract

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.

Table of Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.1. Background . . . . . . . . . . . . . . . . . . . . . . . 3

1.2. Requirements Scope . . . . . . . . . . . . . . . . . . . 3

1.3. Requirements Specification . . . . . . . . . . . . . . . 3

2. Internet Registry Communities . . . . . . . . . . . . . . . . 4

2.1. Domain Name System Registries . . . . . . . . . . . . . 4

2.1.1. Domain Registries . . . . . . . . . . . . . . . 4

2.1.2. Domain Registrars . . . . . . . . . . . . . . . 5

2.2. Other Registries . . . . . . . . . . . . . . . . . . . . 5

2.2.1. Regional Internet Registries . . . . . . . . . . 5

2.2.2. Local Internet Registries . . . . . . . . . . . 5

2.2.3. Internet Routing Registries . . . . . . . . . . 5

2.2.4. Incident Coordination Contact Registries . . . . 6

2.3. Implementers . . . . . . . . . . . . . . . . . . . . . . 6

2.4. End Users . . . . . . . . . . . . . . . . . . . . . . . 6

2.4.1. Internet Resource Registrants . . . . . . . . . 6

2.4.2. Service Providers and Network Operators . . . . 6

2.4.3. Intellectual Property Holders . . . . . . . . . 7

2.4.4. Law Enforcement . . . . . . . . . . . . . . . . 7

2.4.5. Certificate Authorities . . . . . . . . . . . . 7

2.4.6. DNS Users . . . . . . . . . . . . . . . . . . . 7

Newton Informational [Page 1]

RFC 3707 CRISP Requirements February 2004

2.4.7. Abusive Users . . . . . . . . . . . . . . . . . 7

2.5. Other Actors . . . . . . . . . . . . . . . . . . . . . . 8

3. Functional Requirements . . . . . . . . . . . . . . . . . . . 8

3.1. Base Functions . . . . . . . . . . . . . . . . . . . . . 8

3.1.1. Mining Prevention . . . . . . . . . . . . . . . 8

3.1.2. Minimal Technical Reinvention . . . . . . . . . 8

3.1.3. Standard and Extensible Schemas . . . . . . . . 9

3.1.4. Level of Access . . . . . . . . . . . . . . . . 9

3.1.5. Client Processing . . . . . . . . . . . . . . . 10

3.1.6. Entity Referencing . . . . . . . . . . . . . . . 10

3.1.7. Decentralization . . . . . . . . . . . . . . . . 10

3.1.8. Query of Access Permission . . . . . . . . . . . 11

3.1.9. Authentication Distribution . . . . . . . . . . 11

3.1.10. Base Error Responses . . . . . . . . . . . . . . 11

3.1.11. Query Distribution . . . . . . . . . . . . . . . 12

3.1.12....