[Crisp] RFC 5144 on A Domain Availability Check (DCHK) Registry Type for the Internet Registry Information Service (IRIS)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Crisp] RFC 5144 on A Domain Availability Check (DCHK) Registry Type for the Internet Registry Information Service (IRIS)
A new Request for Comments is now available in online RFC libraries.
RFC 5144
Title: A Domain Availability Check (DCHK)
Registry Type for the Internet Registry
Information Service (IRIS)
Author: A. Newton, M. Sanz
Status: Standards Track
Date: February 2008
Mailbox: andy at arin.net,
sanz at denic.de
Pages: 17
Characters: 30063
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-crisp-iris-dchk-09.txt
URL: http://www.rfc-editor.org/rfc/rfc5144.txt
This document describes a lightweight domain availability service
using the Internet Registry Information Service (IRIS) framework and
the data model of the IRIS Domain Registry (DREG) service. [STANDARDS TRACK]
This document is a product of the Cross Registry Information Service Protocol Working Group of the IETF.
This is now a Proposed Standard Protocol.
STANDARDS TRACK: 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 at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at 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 at 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 at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
The RFC Editor Team
USC/Information Sciences Institute
...
_______________________________________________
Crisp mailing list
Crisp at ietf.org
https://www.ietf.org/mailman/listinfo/crisp
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.