From mailman-bounces@ietf.org  Sat Jan  1 05:40:24 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07170
	for <crisp-web-archive@ietf.org>; Sat, 1 Jan 2005 05:40:24 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ckgs5-0006nh-C9
	for crisp-web-archive@ietf.org; Sat, 01 Jan 2005 05:52:33 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ckg9l-0004P8-QT
	for crisp-web-archive@ietf.org; Sat, 01 Jan 2005 05:06:45 -0500
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-web-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.5115.1104573719.4100.mailman@lists.ietf.org>
Date: Sat, 01 Jan 2005 05:01:59 -0500
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit

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.

**********************************************************************

NOTE WELL:

Any submission to the IETF intended by the Contributor for publication
as all or part of an IETF Internet-Draft or RFC and any statement made
within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF
sessions, as well as written and electronic communications made at any
time or place, which are addressed to:

o the IETF plenary session, o any IETF working group or portion
thereof, o the IESG, or any member thereof on behalf of the IESG, o
the IAB or any member thereof on behalf of the IAB, o any IETF mailing
list, including the IETF list itself, any working group
  or design team list, or any other list functioning under IETF
auspices,
o the RFC Editor or the Internet-Drafts function

All IETF Contributions are subject to the rules of RFC 3667 and RFC
3668.

Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF Contributions in the context
of this notice.

Please consult RFC 3667 for details.

*******************************************************************************


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

Passwords for crisp-web-archive@ietf.org:

List                                     Password // URL
----                                     --------  
crisp@ietf.org                           awwuin    
https://www1.ietf.org/mailman/options/crisp/crisp-web-archive%40ietf.org


From crisp-bounces@ietf.org  Mon Jan 10 14:46:47 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16598
	for <crisp-web-archive@ietf.org>; Mon, 10 Jan 2005 14:46:46 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Co5ig-0005iZ-3W
	for crisp-web-archive@ietf.org; Mon, 10 Jan 2005 15:00:55 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Co5QD-0005tg-Ae; Mon, 10 Jan 2005 14:41:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cmibo-0005eV-KE; Thu, 06 Jan 2005 20:08:08 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11413;
	Thu, 6 Jan 2005 20:08:05 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cmiog-00039Q-4x; Thu, 06 Jan 2005 20:21:26 -0500
Received: from ISI.EDU (adma.isi.edu [128.9.160.239])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j0716JQ24475;
	Thu, 6 Jan 2005 17:06:19 -0800 (PST)
Message-Id: <200501070106.j0716JQ24475@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Thu, 06 Jan 2005 17:06:19 -0800
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
X-Mailman-Approved-At: Mon, 10 Jan 2005 14:41:45 -0500
Cc: crisp@ietf.org, rfc-editor@rfc-editor.org
Subject: [Crisp] RFC 3981 on IRIS: The Internet Registry Information Service
	(IRIS) Core Protocol
X-BeenThere: crisp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Cross Registry Information Service Protocol <crisp.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/crisp>,
	<mailto:crisp-request@ietf.org?subject=subscribe>
Sender: crisp-bounces@ietf.org
Errors-To: crisp-bounces@ietf.org
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a


--NextPart


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@verisignlabs.com, sanz@denic.de
        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@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.


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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <050106170441.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc3981

--OtherAccess
Content-Type: Message/External-body; name="rfc3981.txt"; site="ftp.isi.edu";
	access-type="anon-ftp"; directory="in-notes"

Content-Type: text/plain
Content-ID: <050106170441.RFC@RFC-EDITOR.ORG>


--OtherAccess--
--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--NextPart--



From crisp-bounces@ietf.org  Mon Jan 10 14:47:48 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16708
	for <crisp-web-archive@ietf.org>; Mon, 10 Jan 2005 14:47:48 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Co5jg-0005lO-GI
	for crisp-web-archive@ietf.org; Mon, 10 Jan 2005 15:01:57 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Co5QD-0005u3-Ju; Mon, 10 Jan 2005 14:41:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CmifC-0006c8-9T; Thu, 06 Jan 2005 20:11:38 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11517;
	Thu, 6 Jan 2005 20:11:36 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cmis5-0003G0-8z; Thu, 06 Jan 2005 20:24:57 -0500
Received: from ISI.EDU (adma.isi.edu [128.9.160.239])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j0717rQ24903;
	Thu, 6 Jan 2005 17:07:53 -0800 (PST)
Message-Id: <200501070107.j0717rQ24903@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Thu, 06 Jan 2005 17:07:53 -0800
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
X-Mailman-Approved-At: Mon, 10 Jan 2005 14:41:45 -0500
Cc: crisp@ietf.org, rfc-editor@rfc-editor.org
Subject: [Crisp] RFC 3982 on IRIS: A Domain Registry (dreg) Type for the
	Internet Registry Information Service (IRIS)
X-BeenThere: crisp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Cross Registry Information Service Protocol <crisp.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/crisp>,
	<mailto:crisp-request@ietf.org?subject=subscribe>
Sender: crisp-bounces@ietf.org
Errors-To: crisp-bounces@ietf.org
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813


--NextPart


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


        RFC 3982

        Title:      IRIS:  A Domain Registry (dreg) Type for the
                    Internet Registry Information Service (IRIS)
        Author(s):  A. Newton, M. Sanz
        Status:     Standards Track
        Date:       January 2005
        Mailbox:    anewton@verisignlabs.com, sanz@denic.de
        Pages:      50
        Characters: 90901
        Updates/Obsoletes/SeeAlso:    None

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

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


This document describes an Internet Registry Information Service
(IRIS) registry schema for registered DNS information.  The schema
extends the necessary query and result operations of IRIS to provide
the functional information service needs for syntaxes and results used
by domain registries and registrars.

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@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.


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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <050106170635.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc3982

--OtherAccess
Content-Type: Message/External-body; name="rfc3982.txt"; site="ftp.isi.edu";
	access-type="anon-ftp"; directory="in-notes"

Content-Type: text/plain
Content-ID: <050106170635.RFC@RFC-EDITOR.ORG>


--OtherAccess--
--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--NextPart--



From crisp-bounces@ietf.org  Mon Jan 10 14:48:32 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16766
	for <crisp-web-archive@ietf.org>; Mon, 10 Jan 2005 14:48:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Co5kP-0005mL-NA
	for crisp-web-archive@ietf.org; Mon, 10 Jan 2005 15:02:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Co5QD-0005uH-RO; Mon, 10 Jan 2005 14:41:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cmig3-0006fW-OX; Thu, 06 Jan 2005 20:12:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11565;
	Thu, 6 Jan 2005 20:12:30 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cmisw-0003Hv-OX; Thu, 06 Jan 2005 20:25:51 -0500
Received: from ISI.EDU (adma.isi.edu [128.9.160.239])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j0719XQ25237;
	Thu, 6 Jan 2005 17:09:33 -0800 (PST)
Message-Id: <200501070109.j0719XQ25237@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Thu, 06 Jan 2005 17:09:33 -0800
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
X-Mailman-Approved-At: Mon, 10 Jan 2005 14:41:45 -0500
Cc: crisp@ietf.org, rfc-editor@rfc-editor.org
Subject: [Crisp] RFC 3983 on Using the Internet Registry Information Service
	(IRIS) over the Blocks Extensible Exchange Protocol (BEEP)
X-BeenThere: crisp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Cross Registry Information Service Protocol <crisp.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/crisp>,
	<mailto:crisp-request@ietf.org?subject=subscribe>
Sender: crisp-bounces@ietf.org
Errors-To: crisp-bounces@ietf.org
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e


--NextPart


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


        RFC 3983

        Title:      Using the Internet Registry Information Service
                    (IRIS) over the Blocks Extensible Exchange
                    Protocol (BEEP)
        Author(s):  A. Newton, M. Sanz
        Status:     Standards Track
        Date:       January 2005
        Mailbox:    anewton@verisignlabs.com, sanz@denic.de
        Pages:      12
        Characters: 23466
        Updates/Obsoletes/SeeAlso:    None

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

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


This document specifies how to use the Blocks Extensible Exchange
Protocol (BEEP) as the application transport substrate for the
Internet Registry Information Service (IRIS).

This document is a product of the Cross Registry Information Service
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@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.


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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <050106170800.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc3983

--OtherAccess
Content-Type: Message/External-body; name="rfc3983.txt"; site="ftp.isi.edu";
	access-type="anon-ftp"; directory="in-notes"

Content-Type: text/plain
Content-ID: <050106170800.RFC@RFC-EDITOR.ORG>


--OtherAccess--
--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--NextPart--



From crisp-bounces@ietf.org  Mon Jan 10 14:48:58 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16787
	for <crisp-web-archive@ietf.org>; Mon, 10 Jan 2005 14:48:58 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Co5kn-0005mW-HB
	for crisp-web-archive@ietf.org; Mon, 10 Jan 2005 15:03:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Co5QE-0005uS-6X; Mon, 10 Jan 2005 14:41:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Co5BO-0003cD-6v; Mon, 10 Jan 2005 14:26:30 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15105;
	Mon, 10 Jan 2005 14:26:28 -0500 (EST)
From: rfc-editor@rfc-editor.org
Received: from [202.99.23.227] (helo=people.com.cn)
	by ietf-mx.ietf.org with smtp (Exim 4.33)
	id 1Co5Oz-0005CW-05; Mon, 10 Jan 2005 14:40:37 -0500
Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8)
	with SMTP id jm4a41e2d80d; Tue, 11 Jan 2005 03:28:13 +0800
Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8)
	with SMTP id jmd41de1965; Fri, 07 Jan 2005 09:27:36 +0800
Received: from megatron.ietf.org([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8)
	with SMTP id jm1141de51c5; Fri, 07 Jan 2005 09:27:36 +0800
Received: from megatron.ietf.org([132.151.6.71]) by people.com.cn(AIMC 2.9.5.8)
	with SMTP id AISP action; Fri, 07 Jan 2005 09:27:36 +0800
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cmifa-0006dz-Ga; Thu, 06 Jan 2005 20:12:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cmibo-0005eV-KE; Thu, 06 Jan 2005 20:08:08 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11413;
	Thu, 6 Jan 2005 20:08:05 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cmiog-00039Q-4x; Thu, 06 Jan 2005 20:21:26 -0500
Received: from ISI.EDU (adma.isi.edu [128.9.160.239])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j0716JQ24475;
	Thu, 6 Jan 2005 17:06:19 -0800 (PST)
Message-Id: <200501070106.j0716JQ24475@boreas.isi.edu>
To: ietf-announce@ietf.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Thu, 06 Jan 2005 17:06:19 -0800
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: ietf-announce-bounces@ietf.org
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: ietf-announce-bounces@ietf.org
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: rfc-editor@rfc-editor.org
X-Auto-Forward: jaglee@people.com.cn
 jag@kw.com.cn
X-Spam-Score: 0.4 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
X-Mailman-Approved-At: Mon, 10 Jan 2005 14:41:45 -0500
Cc: crisp@ietf.org, rfc-editor@rfc-editor.org
Subject: [Crisp] RFC 3981 on IRIS: The Internet Registry Information Service
	(IRIS) Core Protocol
X-BeenThere: crisp@ietf.org
List-Id: Cross Registry Information Service Protocol <crisp.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/crisp>,
	<mailto:crisp-request@ietf.org?subject=subscribe>
Sender: crisp-bounces@ietf.org
Errors-To: crisp-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 093efd19b5f651b2707595638f6c4003


--NextPart


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@verisignlabs.com, sanz@denic.de
        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@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.


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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <050106170441.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc3981

--OtherAccess
Content-Type: Message/External-body; name="rfc3981.txt"; site="ftp.isi.edu";
	access-type="anon-ftp"; directory="in-notes"

Content-Type: text/plain
Content-ID: <050106170441.RFC@RFC-EDITOR.ORG>


--OtherAccess--
--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--NextPart--




From crisp-bounces@ietf.org  Tue Jan 11 05:44:09 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10626
	for <crisp-web-archive@ietf.org>; Tue, 11 Jan 2005 05:44:09 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CoJjE-0001iM-95
	for crisp-web-archive@ietf.org; Tue, 11 Jan 2005 05:58:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CoJUA-0004xH-6y; Tue, 11 Jan 2005 05:42:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CoJSe-0004an-97
	for crisp@megatron.ietf.org; Tue, 11 Jan 2005 05:41:16 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10463
	for <crisp@ietf.org>; Tue, 11 Jan 2005 05:41:14 -0500 (EST)
Received: from postman.ripe.net ([193.0.0.199])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CoJgQ-0001eq-Gu
	for crisp@ietf.org; Tue, 11 Jan 2005 05:55:32 -0500
Received: by postman.ripe.net (Postfix, from userid 8)
	id A6BDD25A03; Tue, 11 Jan 2005 11:40:43 +0100 (CET)
Received: from birch.ripe.net (birch.ripe.net [193.0.1.96])
	by postman.ripe.net (Postfix) with ESMTP id ABF4C25A01
	for <crisp@ietf.org>; Tue, 11 Jan 2005 11:40:40 +0100 (CET)
Received: from x47.ripe.net (x47.ripe.net [193.0.1.47])
	by birch.ripe.net (8.12.10/8.11.6) with ESMTP id j0BAee8Q022079
	for <crisp@ietf.org>; Tue, 11 Jan 2005 11:40:40 +0100
Received: (from engin@localhost)
	by x47.ripe.net (8.12.10/8.12.6) id j0BAeefY004000
	for crisp@ietf.org; Tue, 11 Jan 2005 11:40:40 +0100
Date: Tue, 11 Jan 2005 11:40:40 +0100
From: Engin Gunduz <engin@ripe.net>
To: crisp@ietf.org
Subject: Re: [Crisp] RFC 3981 on IRIS: The Internet Registry Information
	Service (IRIS) Core Protocol
Message-ID: <20050111104040.GF15945@x47.ripe.net>
References: <200501070106.j0716JQ24475@boreas.isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-9
Content-Disposition: inline
In-Reply-To: <200501070106.j0716JQ24475@boreas.isi.edu>
User-Agent: Mutt/1.4.2.1i
X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_05
X-RIPE-Spam-Status: U 0.373394 / -3.7
X-RIPE-Signature: 2d09b72c7ded1046db983e44be981896
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
X-BeenThere: crisp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Cross Registry Information Service Protocol <crisp.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/crisp>,
	<mailto:crisp-request@ietf.org?subject=subscribe>
Sender: crisp-bounces@ietf.org
Errors-To: crisp-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1

Kudos to Andy and Marcos!

How do we proceed with AREG? We have two drafts for it,
draft-ietf-crisp-iris-areg-09 and draft-ietf-crisp-iris-areg-urires-00.

Do you think they are mature enough to be pushed forward?
-engin


On 2005-01-06 17:06:19 -0800, rfc-editor@rfc-editor.org wrote:
> 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@verisignlabs.com, sanz@denic.de
>         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@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.
> 
> 
> 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.


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

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


From crisp-bounces@ietf.org  Tue Jan 11 08:12:38 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21421
	for <crisp-web-archive@ietf.org>; Tue, 11 Jan 2005 08:12:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CoM2y-0004vx-Na
	for crisp-web-archive@ietf.org; Tue, 11 Jan 2005 08:26:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CoLhx-0001qf-Mq; Tue, 11 Jan 2005 08:05:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CoLaU-0000w4-A4
	for crisp@megatron.ietf.org; Tue, 11 Jan 2005 07:57:30 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19664
	for <crisp@ietf.org>; Tue, 11 Jan 2005 07:57:29 -0500 (EST)
Received: from smtp.denic.de ([81.91.161.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CoLoF-0004Ne-Vs
	for crisp@ietf.org; Tue, 11 Jan 2005 08:11:47 -0500
Received: from notes.denic.de ([192.168.0.77]) by smtp.denic.de with esmtp 
	id 1CoLZv-0005gI-Kf; Tue, 11 Jan 2005 13:56:55 +0100
In-Reply-To: <20050111104040.GF15945@x47.ripe.net>
To: crisp@ietf.org
Subject: Re: [Crisp] RFC 3981 on IRIS: The Internet Registry
	Information	Service (IRIS) Core Protocol
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003
From: Marcos Sanz/Denic <sanz@denic.de>
Message-ID: <OF51C940D2.D9C0FD0B-ONC1256F86.0046D512-C1256F86.00471DD7@notes.denic.de>
Date: Tue, 11 Jan 2005 13:56:47 +0100
X-MIMETrack: Serialize by Router on notes/Denic(Release 6.5.2|June 01, 2004) at
	11.01.2005 13:56:55, Serialize complete at 11.01.2005 13:56:55
Content-Type: text/plain; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
X-BeenThere: crisp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Cross Registry Information Service Protocol <crisp.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/crisp>,
	<mailto:crisp-request@ietf.org?subject=subscribe>
Sender: crisp-bounces@ietf.org
Errors-To: crisp-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25

Engin,

> How do we proceed with AREG? We have two drafts for it,
> draft-ietf-crisp-iris-areg-09 and draft-ietf-crisp-iris-areg-urires-00.
>
> Do you think they are mature enough to be pushed forward?

IMHO both documents are ready.

Regards,
Marcos

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


From crisp-bounces@ietf.org  Tue Jan 11 08:25:12 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22377
	for <crisp-web-archive@ietf.org>; Tue, 11 Jan 2005 08:25:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CoMF6-0005Fv-5c
	for crisp-web-archive@ietf.org; Tue, 11 Jan 2005 08:39:31 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CoLwM-0005Be-1V; Tue, 11 Jan 2005 08:20:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CoLrr-0004Tw-1w
	for crisp@megatron.ietf.org; Tue, 11 Jan 2005 08:15:27 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21778
	for <crisp@ietf.org>; Tue, 11 Jan 2005 08:15:25 -0500 (EST)
Received: from [64.151.105.12] (helo=zak.ecotroph.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CoM5K-000532-Uk
	for crisp@ietf.org; Tue, 11 Jan 2005 08:29:44 -0500
Received: from [10.0.1.2] ([::ffff:64.83.8.178])
	(AUTH: PLAIN anewton, SSL: TLSv1/SSLv3,128bits,RC4-SHA)
	by zak.ecotroph.net with esmtp; Tue, 11 Jan 2005 08:14:57 -0500
	id 000EB999.41E3D151.00002F31
Received-SPF: unknown (Address does not pass the Sender Policy Framework)
	SPF=HELO; sender=[10.0.1.2]; remoteip=::ffff:64.83.8.178;
	remotehost=; helo=[10.0.1.2]; receiver=zak.ecotroph.net;
Received-SPF: fail (Address does not pass the Sender Policy Framework)
	SPF=MAILFROM; sender=andy@hxr.us; remoteip=::ffff:64.83.8.178;
	remotehost=; helo=[10.0.1.2]; receiver=zak.ecotroph.net;
In-Reply-To: <OF51C940D2.D9C0FD0B-ONC1256F86.0046D512-C1256F86.00471DD7@notes.denic.de>
References: <OF51C940D2.D9C0FD0B-ONC1256F86.0046D512-C1256F86.00471DD7@notes.denic.de>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <C8AF650F-63D2-11D9-AC6B-000A95B3BA44@hxr.us>
Content-Transfer-Encoding: 7bit
From: Andrew Newton <andy@hxr.us>
Subject: Re: [Crisp] RFC 3981 on IRIS: The Internet Registry
	Information	Service (IRIS) Core Protocol
Date: Tue, 11 Jan 2005 08:14:54 -0500
To: "Marcos Sanz/Denic" <sanz@denic.de>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit
Cc: crisp@ietf.org
X-BeenThere: crisp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Cross Registry Information Service Protocol <crisp.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/crisp>,
	<mailto:crisp-request@ietf.org?subject=subscribe>
Sender: crisp-bounces@ietf.org
Errors-To: crisp-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit


On Jan 11, 2005, at 7:56 AM, Marcos Sanz/Denic wrote:

>> Do you think they are mature enough to be pushed forward?
>
> IMHO both documents are ready.

Agreed.

-andy


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


From crisp-bounces@ietf.org  Tue Jan 25 16:16:12 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08901
	for <crisp-web-archive@ietf.org>; Tue, 25 Jan 2005 16:16:11 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CtYJa-0000BB-Qb
	for crisp-web-archive@ietf.org; Tue, 25 Jan 2005 16:33:35 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CtXrK-0005hm-1A; Tue, 25 Jan 2005 16:04:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CtXnq-0003eI-Ka; Tue, 25 Jan 2005 16:00:46 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07172;
	Tue, 25 Jan 2005 16:00:44 -0500 (EST)
Message-Id: <200501252100.QAA07172@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 25 Jan 2005 16:00:44 -0500
Cc: crisp@ietf.org
Subject: [Crisp] I-D ACTION:draft-ietf-crisp-iris-lwz-01.txt
X-BeenThere: crisp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Cross Registry Information Service Protocol <crisp.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/crisp>,
	<mailto:crisp-request@ietf.org?subject=subscribe>
Sender: crisp-bounces@ietf.org
Errors-To: crisp-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Cross Registry Information Service Protocol Working Group of the IETF.

	Title		: A Lightweight UDP Transport for the  the Internet 
			  Registry Information  Service
	Author(s)	: A. Newton
	Filename	: draft-ietf-crisp-iris-lwz-01.txt
	Pages		: 17
	Date		: 2005-1-25
	
This document describes a lightweight UDP transport for the Internet
   Registry Information Service (IRIS).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-crisp-iris-lwz-01.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-crisp-iris-lwz-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-crisp-iris-lwz-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2005-1-25163201.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-crisp-iris-lwz-01.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-crisp-iris-lwz-01.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-1-25163201.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--NextPart--





From crisp-bounces@ietf.org  Fri Jan 28 15:58:28 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12662
	for <crisp-web-archive@ietf.org>; Fri, 28 Jan 2005 15:58:28 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CudTh-0007wL-9R
	for crisp-web-archive@ietf.org; Fri, 28 Jan 2005 16:16:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CudBS-00005D-TE; Fri, 28 Jan 2005 15:57:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CudAd-000852-92; Fri, 28 Jan 2005 15:56:47 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12503;
	Fri, 28 Jan 2005 15:56:45 -0500 (EST)
Message-Id: <200501282056.PAA12503@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Fri, 28 Jan 2005 15:56:45 -0500
Cc: crisp@ietf.org
Subject: [Crisp] I-D ACTION:draft-ietf-crisp-iris-dchk-02.txt
X-BeenThere: crisp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Cross Registry Information Service Protocol <crisp.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/crisp>,
	<mailto:crisp-request@ietf.org?subject=subscribe>
Sender: crisp-bounces@ietf.org
Errors-To: crisp-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Cross Registry Information Service Protocol Working Group of the IETF.

	Title		: A Domain Availability Check (dchk)  Registry Type 
			  for the Internet Registry Information  Service (IRIS)
	Author(s)	: A. Newton
	Filename	: draft-ietf-crisp-iris-dchk-02.txt
	Pages		: 16
	Date		: 2005-1-28
	
This document describes a lightweight domain availability service
   using the IRIS framework and the data model of the IRIS Domain
   Registry service.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-crisp-iris-dchk-02.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-crisp-iris-dchk-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-crisp-iris-dchk-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2005-1-28152521.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-crisp-iris-dchk-02.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-crisp-iris-dchk-02.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-1-28152521.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--NextPart--





