[Crisp] RFC 3982 on IRIS: A Domain Registry (dreg) Type for the Internet Registry Information Service (IRIS)

rfc-editor@rfc-editor.org Mon, 10 January 2005 19:47 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16708 for <crisp-web-archive@ietf.org>; Mon, 10 Jan 2005 14:47:48 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Co5jg-0005lO-GI for crisp-web-archive@ietf.org; Mon, 10 Jan 2005 15:01:57 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Co5QD-0005u3-Ju; Mon, 10 Jan 2005 14:41:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CmifC-0006c8-9T; Thu, 06 Jan 2005 20:11:38 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11517; Thu, 6 Jan 2005 20:11:36 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cmis5-0003G0-8z; Thu, 06 Jan 2005 20:24:57 -0500
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j0717rQ24903; Thu, 6 Jan 2005 17:07:53 -0800 (PST)
Message-Id: <200501070107.j0717rQ24903@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 06 Jan 2005 17:07:53 -0800
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
X-Mailman-Approved-At: Mon, 10 Jan 2005 14:41:45 -0500
Cc: crisp@ietf.org, rfc-editor@rfc-editor.org
Subject: [Crisp] RFC 3982 on IRIS: A Domain Registry (dreg) Type for the Internet Registry Information Service (IRIS)
X-BeenThere: crisp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Cross Registry Information Service Protocol <crisp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/crisp>, <mailto:crisp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:crisp@ietf.org>
List-Help: <mailto:crisp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/crisp>, <mailto:crisp-request@ietf.org?subject=subscribe>
Sender: crisp-bounces@ietf.org
Errors-To: crisp-bounces@ietf.org
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813

A new Request for Comments is now available in online RFC libraries.


        RFC 3982

        Title:      IRIS:  A Domain Registry (dreg) Type for the
                    Internet Registry Information Service (IRIS)
        Author(s):  A. Newton, M. Sanz
        Status:     Standards Track
        Date:       January 2005
        Mailbox:    anewton@verisignlabs.com, sanz@denic.de
        Pages:      50
        Characters: 90901
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-crisp-iris-dreg-07.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3982.txt


This document describes an Internet Registry Information Service
(IRIS) registry schema for registered DNS information.  The schema
extends the necessary query and result operations of IRIS to provide
the functional information service needs for syntaxes and results used
by domain registries and registrars.

This document is a product of the Cross Registry Information Service
Protocol Working Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  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.

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.
ftp://ftp.isi.edu/in-notes/rfc3982.txt"><ftp://ftp.isi.edu/in-notes/rfc3982.txt>
_______________________________________________
Crisp mailing list
Crisp@ietf.org
https://www1.ietf.org/mailman/listinfo/crisp