RFC 3707 on Cross Registry Internet Service Protocol (CRISP) Requirements
rfc-editor@rfc-editor.org Fri, 06 February 2004 19:07 UTC
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09683 for <ietf-announce-archive@odin.ietf.org>; Fri, 6 Feb 2004 14:07:33 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 1ApBB0-0000ir-UO for ietf-announce-list@asgard.ietf.org; Fri, 06 Feb 2004 13:58:06 -0500
Received: from ietf.org ([10.27.2.28]) by asgard.ietf.org with esmtp (Exim 4.14) id 1ApB9q-0000dt-D6 for all-ietf@asgard.ietf.org; Fri, 06 Feb 2004 13:56:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09296 for <all-ietf@ietf.org>; Fri, 6 Feb 2004 13:56:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1ApB9p-0002sB-00 for all-ietf@ietf.org; Fri, 06 Feb 2004 13:56:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ApB8y-0002p8-00 for all-ietf@ietf.org; Fri, 06 Feb 2004 13:56:00 -0500
Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 1ApB8L-0002mU-00 for all-ietf@ietf.org; Fri, 06 Feb 2004 13:55:21 -0500
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i16ItLk26268; Fri, 6 Feb 2004 10:55:21 -0800 (PST)
Message-Id: <200402061855.i16ItLk26268@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3707 on Cross Registry Internet Service Protocol (CRISP) Requirements
Cc: rfc-editor@rfc-editor.org, ietf-not43@lists.verisignlabs.com
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 06 Feb 2004 10:55:20 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=-9.2 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60
Sender: owner-ietf-announce@ietf.org
Precedence: bulk
A new Request for Comments is now available in online RFC libraries. RFC 3707 Title: Cross Registry Internet Service Protocol (CRISP) Requirements Author(s): A. Newton Status: Informational Date: February 2004 Mailbox: anewton@verisignlabs.com; anewton@ecotroph.net Pages: 26 Characters: 52411 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-crisp-requirements-06.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3707.txt 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 document is a product of the Cross Registry Information Service Protocol Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.