Re: [dow1-2tf] FW: RFC 3981 on IRIS: The Internet Registry Information Service (IRIS)Core Protocol
The IETF Standard Track is a rather complicated and long lasting
exercise (which is under discussing if I'm correct). Every protocol
has do go through varies iterations before it will be moved from
the status "Internet Draft" to "Draft Standard". Once the protocol
reached this status the develpment has been finished and is waiting
for implementation and a proof of concept. Out of this perspective
you could argue that CRISP already reached a standard level. Please
keep in mind that IDN was only a "Draft Standard" as well as the
the ICANN "regulated" registries started to implement it.
Just my two cents,
Am 07.01.2005 schrieb Thomas Roessler:
> On 2005-01-06 20:35:47 -0500, Jeff Neuman wrote:
> > IRIS is officially an Internet Standard with RFC number 3981.
> That's not the case.
> IRIS has been published as a standards track RFC. This RFC is in the
> entry-level "proposed standard" state, i.e., at the lowest maturity
> level that a "standards track" protocol can have. The next maturity
> level will be "draft standard" (which requires two independent
> interoperable implementations); only after further experience has
> been gathered with the protocol, CRISP can become a formal Internet
> Many proposed standards never make it to standard state.
> See section 4.1 of <http://www.ietf.org/rfc/rfc2026.txt> for details
> on the IETF standards process.
> Thomas Roessler · Personal soap box at <http://log.does-not-exist.org/>.
> > -----Original Message-----
> > From: ietf-announce-bounces@xxxxxxxx
> > [mailto:ietf-announce-bounces@xxxxxxxx]On Behalf Of
> > rfc-editor@xxxxxxxxxxxxxx
> > 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.
(oo) /|\ A cow is not entirely full of
| |--/ | * milk some of it is hamburger!
w w w w