ICANN/GNSO GNSO Email List Archives


<<< Chronological Index >>>    <<< Thread Index >>>

[dow1-2tf] FW: RFC 3981 on IRIS: The Internet Registry Information Service (IRIS)Core Protocol

  • To: <dow1-2tf@xxxxxxxxx>
  • Subject: [dow1-2tf] FW: RFC 3981 on IRIS: The Internet Registry Information Service (IRIS)Core Protocol
  • From: "Neuman, Jeff" <Jeff.Neuman@xxxxxxxxxx>
  • Date: Thu, 6 Jan 2005 20:35:47 -0500
  • Sender: owner-dow1-2tf@xxxxxxxxxxxxxx
  • Thread-index: AcT0V3RRW0yUCXuBSDSWKNcBxO2TpQAAPvewAAAnc8A=
  • Thread-topic: RFC 3981 on IRIS: The Internet Registry Information Service (IRIS)Core Protocol


IRIS is officially an Internet Standard with RFC number 3981.  We will discuss 
this next week.

-----Original Message-----
From: ietf-announce-bounces@xxxxxxxx
[mailto:ietf-announce-bounces@xxxxxxxx]On Behalf Of
Sent: Thursday, January 06, 2005 8:06 PM
To: ietf-announce@xxxxxxxx
Cc: crisp@xxxxxxxx; rfc-editor@xxxxxxxxxxxxxx
Subject: RFC 3981 on IRIS: The Internet Registry Information Service
(IRIS)Core Protocol

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

        RFC 3981

        Title:      IRIS: The Internet Registry Information Service
                    (IRIS) Core Protocol
        Author(s):  A. Newton, M. Sanz
        Status:     Standards Track
        Date:       January 2005
        Mailbox:    anewton@xxxxxxxxxxxxxxxx, sanz@xxxxxxxx
        Pages:      52
        Characters: 101359
        Updates/Obsoletes/SeeAlso:    None

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

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

This document describes an application layer client-server protocol
for a framework to represent the query and result operations of
the information services of Internet registries.  Specified in the
Extensible Markup Language (XML), the protocol defines generic query
and result operations and a mechanism for extending these operations
for specific registry service needs.

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@xxxxxxxxx  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@xxxxxxxxxxxxxxx

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@xxxxxxxxxxxxxx with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@xxxxxxxxxxxxxx
        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@xxxxxxxxxxxxxxx  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@xxxxxxxxxxxxxxx  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.

Attachment: ATT462464.TXT
Description: ATT462464.TXT

Attachment: rfc3981.URL
Description: rfc3981.URL

IETF-Announce mailing list

<<< Chronological Index >>>    <<< Thread Index >>>