From mailman-bounces@core3.amsl.com  Fri Feb  1 05:33:57 2008
Return-Path: <mailman-bounces@core3.amsl.com>
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 55B4E29580B
	for <ietfarch-crisp-archive@core3.amsl.com>; Fri,  1 Feb 2008 05:33:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.589
X-Spam-Level: 
X-Spam-Status: No, score=-2.589 tagged_above=-999 required=5 tests=[AWL=0.010,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id mo5UZIb06Asg
	for <ietfarch-crisp-archive@core3.amsl.com>;
	Fri,  1 Feb 2008 05:33:19 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B0612294884
	for <crisp-archive@megatron.ietf.org>; Fri,  1 Feb 2008 05:07:41 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: crisp-archive@megatron.ietf.org
X-No-Archive: yes
Message-ID: <mailman.11769.1201870980.31733.mailman@core3.amsl.com>
Date: Fri, 01 Feb 2008 05:03:00 -0800
Precedence: bulk
X-BeenThere: mailman@core3.amsl.com
X-Mailman-Version: 2.1.9
List-Id: <mailman.core3.amsl.com>
X-List-Administrivia: yes
Sender: mailman-bounces@core3.amsl.com
Errors-To: mailman-bounces@core3.amsl.com

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

http://www.ietf.org/mailman/options/crisp/crisp-archive%40megatron.ietf.org
From mailman-bounces@core3.amsl.com  Fri Feb  1 05:34:04 2008
Return-Path: <mailman-bounces@core3.amsl.com>
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 359EE28D5AB
	for <ietfarch-crisp-archive@core3.amsl.com>; Fri,  1 Feb 2008 05:33:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.589
X-Spam-Level: 
X-Spam-Status: No, score=-2.589 tagged_above=-999 required=5 tests=[AWL=0.010,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OsOv2X0KS9Bf
	for <ietfarch-crisp-archive@core3.amsl.com>;
	Fri,  1 Feb 2008 05:33:13 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0486E28D575
	for <crisp-archive@megatron.ietf.org>; Fri,  1 Feb 2008 05:07:27 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: crisp-archive@megatron.ietf.org
X-No-Archive: yes
Message-ID: <mailman.11769.1201870979.31726.mailman@core3.amsl.com>
Date: Fri, 01 Feb 2008 05:02:59 -0800
Precedence: bulk
X-BeenThere: mailman@core3.amsl.com
X-Mailman-Version: 2.1.9
List-Id: <mailman.core3.amsl.com>
X-List-Administrivia: yes
Sender: mailman-bounces@core3.amsl.com
Errors-To: mailman-bounces@core3.amsl.com

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

http://www.ietf.org/mailman/options/crisp/crisp-archive%40megatron.ietf.org
From crisp-bounces@ietf.org  Fri Feb  8 13:03:15 2008
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 657EC28C535;
	Fri,  8 Feb 2008 13:03:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id uINCLA5GXboI; Fri,  8 Feb 2008 13:03:14 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 74B3E28C54A;
	Fri,  8 Feb 2008 13:03:14 -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 67A8B28C3ED
	for <crisp@core3.amsl.com>; Fri,  8 Feb 2008 13:03:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id YiuctCgZpn4P for <crisp@core3.amsl.com>;
	Fri,  8 Feb 2008 13:03:12 -0800 (PST)
Received: from dukecmmtao02.coxmail.com (dukecmmtao02.coxmail.com
	[68.99.120.69]) by core3.amsl.com (Postfix) with ESMTP id 5831D28C54A
	for <crisp@ietf.org>; Fri,  8 Feb 2008 13:01:10 -0800 (PST)
Received: from ManRay ([68.4.188.194]) by dukecmmtao02.coxmail.com
	(InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP
	id <20080208210239.KXUV21469.dukecmmtao02.coxmail.com@ManRay>;
	Fri, 8 Feb 2008 16:02:39 -0500
From: "Carl Taswell" <ctaswell@telegenetics.net>
To: <crisp@ietf.org>
Date: Fri, 8 Feb 2008 13:02:33 -0800
Organization: Global TeleGenetics, Inc.
Message-ID: <004801c86a95$ed953870$c8bfa950$@net>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AchqleziPuU7/hisQoabkzUFH6qzjg==
Content-Language: en-us
Cc: shollenbeck@verisign.com, 'Andrew Newton' <andy@hxr.us>
Subject: [Crisp] Interaction between IRIS and EPP
X-BeenThere: crisp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ctaswell@telegenetics.net
List-Id: Cross Registry Information Service Protocol <crisp.ietf.org>
List-Unsubscribe: <http://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: <http://www.ietf.org/mailman/listinfo/crisp>,
	<mailto:crisp-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: crisp-bounces@ietf.org
Errors-To: crisp-bounces@ietf.org

I've inquired in the past about re-factoring the IRIS-based registries dreg,
areg, etc so that they all share a common format for contacts. If so, then I
need not reinvent the wheel and create yet another format for contacts in my
custom application registry that would be able to interact with all of the
other IRIS-based registries. 

Recently, I found that RFC4933 Extensible Provisioning Protocol (EPP)
Contact Mapping provides a detailed format for contacts. So my current
questions are:

1) Has there been any discussion of making IRIS-based registry contacts
interoperable with the EPP-based registry contacts? 

2) Has there been any discussion recommending best practice uses of IRIS
versus EPP and any interaction and interoperability?

Many thanks,

CT

-------------------------
Carl Taswell
Cel: 916-616-4939
Tel: 949-481-3121




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


From crisp-bounces@ietf.org  Thu Feb 28 16:32:15 2008
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


