[Crisp] RFC 5144 on A Domain Availability Check (DCHK) Registry Type for the Internet Registry Information Service (IRIS)

rfc-editor@rfc-editor.org Fri, 29 February 2008 00:32 UTC

Return-Path: <crisp-bounces@ietf.org>
X-Original-To: ietfarch-crisp-archive@core3.amsl.com
Delivered-To: ietfarch-crisp-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 05CD328C9A7; Thu, 28 Feb 2008 16:32:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.183
X-Spam-Level:
X-Spam-Status: No, score=-0.183 tagged_above=-999 required=5 tests=[AWL=-0.346, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, J_CHICKENPOX_93=0.6, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yZFOo4RdKsAc; Thu, 28 Feb 2008 16:31:54 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7F2E428C5CF; Thu, 28 Feb 2008 16:31:52 -0800 (PST)
X-Original-To: crisp@core3.amsl.com
Delivered-To: crisp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 412333A68A3; Thu, 28 Feb 2008 16:31:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qIag8HXqDi4a; Thu, 28 Feb 2008 16:31:44 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id DB29B28C237; Thu, 28 Feb 2008 16:31:44 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id 0A802117444; Thu, 28 Feb 2008 16:31:38 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20080229003138.0A802117444@bosco.isi.edu>
Date: Thu, 28 Feb 2008 16:31:38 -0800 (PST)
Cc: crisp@ietf.org, rfc-editor@rfc-editor.org
Subject: [Crisp] RFC 5144 on A Domain Availability Check (DCHK) Registry Type for the Internet Registry Information Service (IRIS)
X-BeenThere: crisp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Cross Registry Information Service Protocol <crisp.ietf.org>
List-Unsubscribe: <https://www.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://www.ietf.org/mailman/listinfo/crisp>, <mailto:crisp-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: crisp-bounces@ietf.org
Errors-To: crisp-bounces@ietf.org

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@arin.net, 
                    sanz@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@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.


The RFC Editor Team
USC/Information Sciences Institute

...


_______________________________________________
Crisp mailing list
Crisp@ietf.org
https://www.ietf.org/mailman/listinfo/crisp