From crisp-bounces@ietf.org Wed Jun 01 10:59:32 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DdUgu-0001LI-FL; Wed, 01 Jun 2005 10:59:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DdUgs-0001Ku-Fl
	for crisp@megatron.ietf.org; Wed, 01 Jun 2005 10:59:31 -0400
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 KAA23809
	for <crisp@ietf.org>; Wed, 1 Jun 2005 10:59:28 -0400 (EDT)
Received: from zak.hxr.us ([216.93.167.200] helo=zak.ecotroph.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DdV0h-00089Z-LT
	for crisp@ietf.org; Wed, 01 Jun 2005 11:20:00 -0400
Received: from [10.131.244.246] ([::ffff:216.168.239.87])
	(AUTH: PLAIN anewton, SSL: TLSv1/SSLv3,128bits,RC4-SHA)
	by zak.ecotroph.net with esmtp; Wed, 01 Jun 2005 10:59:24 -0400
	id 001F311C.429DCD4C.00002AA4
In-Reply-To: <046F43A8D79C794FA4733814869CDF07988384@dul1wnexmb01.vcorp.ad.vrsn.com>
References: <046F43A8D79C794FA4733814869CDF07988384@dul1wnexmb01.vcorp.ad.vrsn.com>
Mime-Version: 1.0 (Apple Message framework v730)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <EDA55B64-EC39-4123-8814-03A4DF3C5610@hxr.us>
Content-Transfer-Encoding: 7bit
From: Andrew Newton <andy@hxr.us>
Subject: Re: [Crisp] Last Call Comment: draft-ietf-crisp-iris-areg-11.txt
Date: Wed, 1 Jun 2005 10:59:22 -0400
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>
X-Mailer: Apple Mail (2.730)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Cc: Leslie Daigle <leslie@thinkingcat.com>, CRISP WG <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


On May 31, 2005, at 10:57 AM, Hollenbeck, Scott wrote:

> I agree with the progress.  Frankly, though, I'm afraid that
> outside-the-wg reviewers aren't going to know the context and have
> enough info to understand the choice.  That may well slow things down
> during IETF last call and/or IESG review.  A little bit of additional
> explanatory text may well help make it easier to move this document
> along without having to answer the same question again.

Suggested text to be appended to Section 9:

Motivation: The operational considerations for this NAPTR DNS  
assignment are described in Section 7.2.  The Number Resource  
Organization (NRO) is a formal, co-operative effort between all the  
Regional Internet Registries (RIRs), the managers of IP address space  
relevant to the protocol definitions in this document.

-andy

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



From crisp-bounces@ietf.org Wed Jun 01 11:23:38 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DdV4E-0008GM-RF; Wed, 01 Jun 2005 11:23:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DdV4C-0008GE-U4
	for crisp@megatron.ietf.org; Wed, 01 Jun 2005 11:23:37 -0400
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 LAA26195
	for <crisp@ietf.org>; Wed, 1 Jun 2005 11:23:33 -0400 (EDT)
Received: from falcon.verisign.com ([216.168.239.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DdVNz-00013R-1W
	for crisp@ietf.org; Wed, 01 Jun 2005 11:44:04 -0400
Received: from dul1wnexcn01.vcorp.ad.vrsn.com (dul1wnexcn01.vcorp.ad.vrsn.com
	[10.170.12.138])
	by falcon.verisign.com (8.12.10/8.12.10) with ESMTP id j51FG6oi019706; 
	Wed, 1 Jun 2005 11:16:06 -0400 (EDT)
Received: from dul1wnexmb01.vcorp.ad.vrsn.com ([10.170.12.134]) by
	dul1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 1 Jun 2005 11:23:13 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Crisp] Last Call Comment: draft-ietf-crisp-iris-areg-11.txt
Date: Wed, 1 Jun 2005 11:23:19 -0400
Message-ID: <046F43A8D79C794FA4733814869CDF079884A9@dul1wnexmb01.vcorp.ad.vrsn.com>
Thread-Topic: [Crisp] Last Call Comment: draft-ietf-crisp-iris-areg-11.txt
Thread-Index: AcVmuoNGN78xPK7wR+auvOK8HngrVAAAz5bw
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "Andrew Newton" <andy@hxr.us>
X-OriginalArrivalTime: 01 Jun 2005 15:23:13.0426 (UTC)
	FILETIME=[D390C720:01C566BD]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: quoted-printable
Cc: CRISP WG <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

> -----Original Message-----
> From: Andrew Newton [mailto:andy@hxr.us]=20
> Sent: Wednesday, June 01, 2005 10:59 AM
> To: Hollenbeck, Scott
> Cc: Leslie Daigle; CRISP WG
> Subject: Re: [Crisp] Last Call Comment:=20
> draft-ietf-crisp-iris-areg-11.txt
>=20
>=20
> On May 31, 2005, at 10:57 AM, Hollenbeck, Scott wrote:
>=20
> > I agree with the progress.  Frankly, though, I'm afraid that
> > outside-the-wg reviewers aren't going to know the context and have
> > enough info to understand the choice.  That may well slow=20
> things down
> > during IETF last call and/or IESG review.  A little bit of=20
> additional
> > explanatory text may well help make it easier to move this document
> > along without having to answer the same question again.
>=20
> Suggested text to be appended to Section 9:
>=20
> Motivation: The operational considerations for this NAPTR DNS =20
> assignment are described in Section 7.2.  The Number Resource =20
> Organization (NRO) is a formal, co-operative effort between all the =20
> Regional Internet Registries (RIRs), the managers of IP=20
> address space =20
> relevant to the protocol definitions in this document.

Works for me.

-Scott-

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



From crisp-bounces@ietf.org Sun Jun 05 18:35:13 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Df3i5-0008V1-JH; Sun, 05 Jun 2005 18:35:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Df3i3-0008Td-Io
	for crisp@megatron.ietf.org; Sun, 05 Jun 2005 18:35:11 -0400
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 SAA09720
	for <crisp@ietf.org>; Sun, 5 Jun 2005 18:35:08 -0400 (EDT)
Received: from [64.233.182.202] (helo=nproxy.gmail.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Df42l-0000hn-Jr
	for crisp@ietf.org; Sun, 05 Jun 2005 18:56:36 -0400
Received: by nproxy.gmail.com with SMTP id o25so787310nfa
	for <crisp@ietf.org>; Sun, 05 Jun 2005 15:35:00 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=bdvTPkryoL9bwWJO3tIciptiykbKii+8Jxw+LHRaVZwChycu45IjVpMixCDL1jdDqtNPWnZyy4JOSN4Au4GjVg33CT2BYjEpSHnx+2nVGvKRnvTYKIBXp2X6ggRQd4ohO8IuVelNqWNTcQguXE9iii+JS3i+sgWs8r65oIacGdw=
Received: by 10.48.1.19 with SMTP id 19mr57096nfa;
	Sun, 05 Jun 2005 15:35:00 -0700 (PDT)
Received: by 10.48.248.17 with HTTP; Sun, 5 Jun 2005 15:35:00 -0700 (PDT)
Message-ID: <487354f10506051535592fd536@mail.gmail.com>
Date: Mon, 6 Jun 2005 00:35:00 +0200
From: Robert Martin-Legene <rlegene@gmail.com>
To: CRISP WG <crisp@ietf.org>
Subject: Re: [Crisp] xpc-00
In-Reply-To: <78def96486af1f50c4756dca1b9c9931@hxr.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <200505021948.PAA25941@ietf.org>
	<487354f105051304317e721d2c@mail.gmail.com>
	<9e3522aa5fe0a1ec833faa465bfb43fd@hxr.us>
	<487354f1050519160738fe9cc1@mail.gmail.com>
	<5c3f85b9f172e2669a77d1ad04522093@hxr.us>
	<487354f1050520135510819650@mail.gmail.com>
	<78def96486af1f50c4756dca1b9c9931@hxr.us>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: quoted-printable
X-BeenThere: crisp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Robert Martin-Legene <rlegene@gmail.com>
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

A fortnight ago Andy wrote:
> we probably ought to define an error case
> that explicitly speaks to this.  Such as, "you have sent me an XML
> instance that is 900k long so far, perhaps you ought to get a hold of
> yourself".

That's basically what I wanted to get at. I just found it a logical
approach if the server could (possibly optionally, but recommended)
reveal it's tolerance in the Version-Info header, so a client would
know before hand if it's query would fail.

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



From crisp-bounces@ietf.org Wed Jun 08 15:49:08 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dg6Y0-0004y5-9g; Wed, 08 Jun 2005 15:49:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dg6Xv-0004xS-QP; Wed, 08 Jun 2005 15:49:03 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00453;
	Wed, 8 Jun 2005 15:49:01 -0400 (EDT)
Message-Id: <200506081949.PAA00453@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Wed, 08 Jun 2005 15:49:01 -0400
Cc: crisp@ietf.org
Subject: [Crisp] I-D ACTION:draft-ietf-crisp-iris-common-transport-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

--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 Common Schema for Internet Registry Information 
			  Service Transfer Protocols
	Author(s)	: A. Newton
	Filename	: draft-ietf-crisp-iris-common-transport-01.txt
	Pages		: 19
	Date		: 2005-6-8
	
This document describes an XML Schema for use by Internet Registry
   Information Service (IRIS) application transfer protocols that share
   common characteristics.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-crisp-iris-common-transport-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-common-transport-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-common-transport-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-6-8162151.I-D@ietf.org>

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

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

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


--OtherAccess--

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

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

--NextPart--






From crisp-bounces@ietf.org Wed Jun 08 15:49:40 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dg6YW-00052m-VP; Wed, 08 Jun 2005 15:49:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dg6YR-000524-Ug; Wed, 08 Jun 2005 15:49:36 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00506;
	Wed, 8 Jun 2005 15:49:34 -0400 (EDT)
Message-Id: <200506081949.PAA00506@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Wed, 08 Jun 2005 15:49:33 -0400
Cc: crisp@ietf.org
Subject: [Crisp] I-D ACTION:draft-ietf-crisp-iris-dchk-03.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

--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-03.txt
	Pages		: 17
	Date		: 2005-6-8
	
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-03.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-03.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-03.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-6-8162159.I-D@ietf.org>

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

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

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


--OtherAccess--

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

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

--NextPart--






From crisp-bounces@ietf.org Wed Jun 08 15:50:11 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dg6Z1-000559-Gh; Wed, 08 Jun 2005 15:50:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dg6Yx-00054X-Nx; Wed, 08 Jun 2005 15:50:07 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00544;
	Wed, 8 Jun 2005 15:50:05 -0400 (EDT)
Message-Id: <200506081950.PAA00544@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Wed, 08 Jun 2005 15:50:05 -0400
Cc: crisp@ietf.org
Subject: [Crisp] I-D ACTION:draft-ietf-crisp-iris-lwz-03.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

--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 Transfer Protocol for the  
			  the Internet Registry Information  Service
	Author(s)	: A. Newton
	Filename	: draft-ietf-crisp-iris-lwz-03.txt
	Pages		: 20
	Date		: 2005-6-8
	
This document describes a lightweight UDP transfer protocol 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-03.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-03.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-03.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-6-8162206.I-D@ietf.org>

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

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

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


--OtherAccess--

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

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

--NextPart--






From crisp-bounces@ietf.org Wed Jun 08 15:50:38 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dg6ZS-0005DO-Fp; Wed, 08 Jun 2005 15:50:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dg6ZO-0005Cb-C0; Wed, 08 Jun 2005 15:50:34 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00582;
	Wed, 8 Jun 2005 15:50:32 -0400 (EDT)
Message-Id: <200506081950.PAA00582@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Wed, 08 Jun 2005 15:50:32 -0400
Cc: crisp@ietf.org
Subject: [Crisp] I-D ACTION:draft-ietf-crisp-iris-xpc-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

--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		: XML Pipelining with Chunks for the Information Registry 
			  Information Service
	Author(s)	: A. Newton
	Filename	: draft-ietf-crisp-iris-xpc-01.txt
	Pages		: 33
	Date		: 2005-6-8
	
This document describes a simple TCP transfer protocol for the
   Internet Registry Information Service (IRIS).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-crisp-iris-xpc-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-xpc-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-xpc-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-6-8162213.I-D@ietf.org>

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

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

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


--OtherAccess--

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

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

--NextPart--






From crisp-bounces@ietf.org Fri Jun 10 15:14:18 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DgoxO-0007a4-36; Fri, 10 Jun 2005 15:14:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DgoxM-0007Xb-3T
	for crisp@megatron.ietf.org; Fri, 10 Jun 2005 15:14:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22083
	for <crisp@ietf.org>; Fri, 10 Jun 2005 15:14:14 -0400 (EDT)
Received: from zak.hxr.us ([216.93.167.200] helo=zak.ecotroph.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DgpJ4-0002r7-3V
	for crisp@ietf.org; Fri, 10 Jun 2005 15:36:43 -0400
Received: from [10.131.244.246] ([::ffff:216.168.239.87])
	(AUTH: PLAIN anewton, SSL: TLSv1/SSLv3,128bits,RC4-SHA)
	by zak.ecotroph.net with esmtp; Fri, 10 Jun 2005 15:14:11 -0400
	id 000FB87B.42A9E683.00007866
Mime-Version: 1.0 (Apple Message framework v730)
In-Reply-To: <20050527095027.P30742@shell-ng.nominum.com>
References: <20050527095027.P30742@shell-ng.nominum.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <230D97A6-0B64-4C8A-BE73-A27A9E72B603@hxr.us>
Content-Transfer-Encoding: 7bit
From: Andrew Newton <andy@hxr.us>
Subject: Re: [Crisp] last call draft-ietf-crisp-iris-areg-11.txt
Date: Fri, 10 Jun 2005 15:14:09 -0400
To: CRISP WG <crisp@ietf.org>
X-Mailer: Apple Mail (2.730)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit
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


On May 27, 2005, at 12:57 PM, April Marine wrote:

> WGLC will last till, oh, June 10.

Just in the nick of time...

Cathy Murphy and I have had a brief email exchange regarding  
inconsistencies between the areg xml schema and the descriptive  
text... basically small changes editorial changes.  However, she did  
raise one issue that I think is substantive:

> On Fri, 10 Jun 2005, Andrew Newton wrote:
>
>>
>>
>>> 3.1.10 - Why wasn't country code included as one of the common  
>>> search group elements? I thought it was supposed to be  
>>> searchable. *shrug* Just trying to make sure it wasn't an oversight.
>>>
>>
>> The thinking is that asking for all contacts in a specific country  
>> yields a result set so huge that it is probably useless... unless  
>> somebody is mining your data.
>>
>
> I suppose I was thinking more of an Org select by country code. It  
> is not an infrequent request on NANOG to ask for all the ISPs in a  
> particular region. In Africa or Asia where the countries are not  
> always as well developed, this might mean looking within a country  
> versus a city. However, we could always informally allow this in  
> our implementation. There is nothing that says it has to be in the  
> protocol.

We should probably add country.  For cases where it is inappropriate,  
an error can be returned.

-andy

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



From crisp-bounces@ietf.org Fri Jun 10 19:51:29 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DgtHd-0006LU-FZ; Fri, 10 Jun 2005 19:51:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DgtHb-0006Kt-W3
	for crisp@megatron.ietf.org; Fri, 10 Jun 2005 19:51:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25837
	for <crisp@ietf.org>; Fri, 10 Jun 2005 19:51:26 -0400 (EDT)
Received: from shell-ng.nominum.com ([81.200.64.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DgtdM-0004AT-BL
	for crisp@ietf.org; Fri, 10 Jun 2005 20:13:57 -0400
Received: by shell-ng.nominum.com (Postfix, from userid 10182)
	id DD622568AE; Fri, 10 Jun 2005 16:51:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by shell-ng.nominum.com (Postfix) with ESMTP id DBFDF568AD;
	Fri, 10 Jun 2005 16:51:00 -0700 (PDT)
	(envelope-from amarine@nominum.com)
Date: Fri, 10 Jun 2005 16:51:00 -0700 (PDT)
From: April Marine <April.Marine@nominum.com>
To: Andrew Newton <andy@hxr.us>
Subject: Re: [Crisp] last call draft-ietf-crisp-iris-areg-11.txt
In-Reply-To: <230D97A6-0B64-4C8A-BE73-A27A9E72B603@hxr.us>
Message-ID: <20050610164950.F94570@shell-ng.nominum.com>
References: <20050527095027.P30742@shell-ng.nominum.com>
	<230D97A6-0B64-4C8A-BE73-A27A9E72B603@hxr.us>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: CRISP WG <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

We can extend our timeline a day or two to allow for comments on this 
topic only. Thanks for the feedback given--some useful modifications came 
out of it!

April

On Fri, 10 Jun 2005, Andrew Newton wrote:

>
> On May 27, 2005, at 12:57 PM, April Marine wrote:
>
>> WGLC will last till, oh, June 10.
>
> Just in the nick of time...
>
> Cathy Murphy and I have had a brief email exchange regarding inconsistencies 
> between the areg xml schema and the descriptive text... basically small 
> changes editorial changes.  However, she did raise one issue that I think is 
> substantive:
>
>> On Fri, 10 Jun 2005, Andrew Newton wrote:
>> 
>>> 
>>> 
>>>> 3.1.10 - Why wasn't country code included as one of the common search 
>>>> group elements? I thought it was supposed to be searchable. *shrug* Just 
>>>> trying to make sure it wasn't an oversight.
>>>> 
>>> 
>>> The thinking is that asking for all contacts in a specific country yields 
>>> a result set so huge that it is probably useless... unless somebody is 
>>> mining your data.
>>> 
>> 
>> I suppose I was thinking more of an Org select by country code. It is not 
>> an infrequent request on NANOG to ask for all the ISPs in a particular 
>> region. In Africa or Asia where the countries are not always as well 
>> developed, this might mean looking within a country versus a city. However, 
>> we could always informally allow this in our implementation. There is 
>> nothing that says it has to be in the protocol.
>
> We should probably add country.  For cases where it is inappropriate, an 
> error can be returned.
>
> -andy
>
> _______________________________________________
> 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 Thu Jun 23 17:27:30 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DlZEQ-0005e9-M7; Thu, 23 Jun 2005 17:27:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DlZEP-0005e1-GO
	for crisp@megatron.ietf.org; Thu, 23 Jun 2005 17:27:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04437
	for <crisp@ietf.org>; Thu, 23 Jun 2005 17:27:27 -0400 (EDT)
Received: from zak.ecotroph.net ([216.93.167.200])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DlZcn-0006hj-Nu
	for crisp@ietf.org; Thu, 23 Jun 2005 17:52:43 -0400
Received: from [192.168.48.145] ([::ffff:212.202.97.146])
	(AUTH: PLAIN anewton, SSL: TLSv1/SSLv3,128bits,RC4-SHA)
	by zak.ecotroph.net with esmtp; Thu, 23 Jun 2005 17:27:24 -0400
	id 000FB875.42BB293C.000009DF
Mime-Version: 1.0 (Apple Message framework v730)
Content-Transfer-Encoding: 7bit
Message-Id: <6273F9F7-AE2E-4165-B8C3-7B43D1622367@hxr.us>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: CRISP WG <crisp@ietf.org>
From: Andrew Newton <andy@hxr.us>
Date: Thu, 23 Jun 2005 17:27:26 -0400
X-Mailer: Apple Mail (2.730)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit
Subject: [Crisp] a couple of issues with LWZ and XPC
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

Just to let everybody know, it appears that both the LWZ and XPC  
drafts will need at least one more spin around the block.

Based on feedback I've received off-line, it would appear that both  
LWZ and XPC need some more descriptive text regarding the intended  
message exchange pattern.  For LWZ, it would appear that the draft is  
not clear enough about the exchange being one UDP packet out, one UDP  
packet in, no session semantics, big desire to avoid fragmentation.   
For XPC, the draft is not clear enough about the response block being  
sent after the request block vs. interleaving request/response chunks.

Milena Caires has pointed out to me that neither XPC and LWZ mention  
which bits are most significant and that both drafts would appear to  
be counter to the convention setup by RFC 1166 (which becomes obvious  
when you look at the example).  This needs to be fixed.

Finally, the SASL example in XPC only shows a one octet length field  
for the SASL data when it suppose to be two octets.

-andy

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



From crisp-bounces@ietf.org Mon Jun 27 11:06:36 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DmvC0-0004iE-Q6; Mon, 27 Jun 2005 11:06:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DmvBy-0004i9-Nh
	for crisp@megatron.ietf.org; Mon, 27 Jun 2005 11:06:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00628
	for <crisp@ietf.org>; Mon, 27 Jun 2005 11:06:30 -0400 (EDT)
Received: from ppsw-0.csi.cam.ac.uk ([131.111.8.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dmvb2-0006wF-PS
	for crisp@ietf.org; Mon, 27 Jun 2005 11:32:34 -0400
X-Cam-SpamDetails: Not scanned
X-Cam-AntiVirus: No virus found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from c26.al.cl.cam.ac.uk ([128.232.110.76]:4568 helo=localhost)
	by ppsw-0.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.150]:465)
	with esmtps (TLSv1:DHE-RSA-AES256-SHA:256)
	id 1DmvBb-0004qt-2C (Exim 4.51) for crisp@ietf.org
	(return-path <kengo@elab.ic.i.u-tokyo.ac.jp>);
	Mon, 27 Jun 2005 16:06:11 +0100
Date: Mon, 27 Jun 2005 16:06:13 +0100
From: Nagahashi Kengo <kengo@elab.ic.i.u-tokyo.ac.jp>
To: crisp@ietf.org
Message-Id: <20050627160613.483b4e2d.kengo@elab.ic.i.u-tokyo.ac.jp>
X-Mailer: Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-unknown-freebsd4.10)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7bit
Subject: [Crisp] rreg draft
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

Hi,

We'll plan to submit revised rreg draft before ID cut-off.
Major changes in this draft is to add Motivation and Requirements.

Unlike areg and dreg, there is an argument which rreg does not well 
fit into iris framework. Our intention is to define requirements 
at first and then follow query/responce format on this requirements.

In this draft, it still remains query/responce but this might 
be better to remove it and define clear requiremens for routing registry.

any comments would be appreciate.

1.1 Motivation
  Our intention to apply  CRISP framework into Routing
  Registry is due to the current messy architecture 
  of routing registries.
  They  are scattered around the world but  neither hierarchical
  strcutre nor recursive look-up are 
  performed. This derives an inaccurate routing information
  in Routing Registry. 
  We have strong motivation to improve accuracy of the routing
  registries by introducing CRISP framework into routing registries.

  2 steps must be taken to improve the situation , (1) defines
  XML Schema for Routing Registry and (2)deploy CRISP enabled
  Routing Registry. 
  
  This document only focuses on the definition of XML schema for
  routing registries, and the deployment issues will be described
  in another document.

3. Requirements 
  
   Like other iris schema e.g. areg, dreg, routing registry should
   be defined XML schema which  comprises query and responce.

   The query and responce in routing registry is similer with 
   areg since main objective of routing registry is to manage
   prefix, autonomous system and contact information.
   
   The obvious difference with areg and rreg is that 
   rreg requries to handle routing policy schema 
   e.g. AS imports policy and exports policy.
   This routing policy schema is described by Routing Policy 
   Specification  Language (RPSL)[RPSL]. 
   Thus, rreg requires the routing policy handling defined 
   in RPSL.
   
   Since the routing registry are distributed without 
   strong relation, root resolution is a hard issue to solve. 
   One of straight forward solution is to decide the root 
   e.g. "rreg.nro.net" uniquely but it still requires to 
   discuss about it.


-kengo 

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



From crisp-bounces@ietf.org Mon Jun 27 11:56:52 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dmvye-0007of-HM; Mon, 27 Jun 2005 11:56:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dmvyd-0007oP-5r
	for crisp@megatron.ietf.org; Mon, 27 Jun 2005 11:56:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05373
	for <crisp@ietf.org>; Mon, 27 Jun 2005 11:56:48 -0400 (EDT)
Received: from zak.ecotroph.net ([216.93.167.200])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DmwNl-0000Ax-4g
	for crisp@ietf.org; Mon, 27 Jun 2005 12:22:52 -0400
Received: from [10.131.244.250] ([::ffff:216.168.239.87])
	(AUTH: PLAIN anewton, SSL: TLSv1/SSLv3,128bits,RC4-SHA)
	by zak.ecotroph.net with esmtp; Mon, 27 Jun 2005 11:56:43 -0400
	id 00113D6A.42C021BC.0000146A
In-Reply-To: <20050627160613.483b4e2d.kengo@elab.ic.i.u-tokyo.ac.jp>
References: <20050627160613.483b4e2d.kengo@elab.ic.i.u-tokyo.ac.jp>
Mime-Version: 1.0 (Apple Message framework v730)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <556712F6-801B-4589-93E4-5EEE8004B87E@hxr.us>
Content-Transfer-Encoding: 7bit
From: Andrew Newton <andy@hxr.us>
Subject: Re: [Crisp] rreg draft
Date: Mon, 27 Jun 2005 11:56:42 -0400
To: Nagahashi Kengo <kengo@elab.ic.i.u-tokyo.ac.jp>
X-Mailer: Apple Mail (2.730)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
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

Kengo,

As I observed the meeting and from my reading of the first version of  
the draft, it was hard to appreciate the difference between AREG and  
RREG.  My comments are inline:

On Jun 27, 2005, at 11:06 AM, Nagahashi Kengo wrote:
>    The obvious difference with areg and rreg is that
>    rreg requries to handle routing policy schema
>    e.g. AS imports policy and exports policy.
>    This routing policy schema is described by Routing Policy
>    Specification  Language (RPSL)[RPSL].
>    Thus, rreg requires the routing policy handling defined
>    in RPSL.

This is where you should probably concentrate your energy, in my  
opinion.  I was not able to determine how RREG was different from AREG.

If the difference really isn't in the type of data but instead of who  
is giving the data (a routing registry vs. an address registry), then  
this might need a little clarification.

>    Since the routing registry are distributed without
>    strong relation, root resolution is a hard issue to solve.
>    One of straight forward solution is to decide the root
>    e.g. "rreg.nro.net" uniquely but it still requires to
>    discuss about it.

I would not worry about tackling this yet.
Just my 2 cents.

-andy

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



From crisp-bounces@ietf.org Mon Jun 27 13:46:47 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dmxh1-000498-Iu; Mon, 27 Jun 2005 13:46:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dmxgz-00046y-Mg
	for crisp@megatron.ietf.org; Mon, 27 Jun 2005 13:46:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18085
	for <crisp@ietf.org>; Mon, 27 Jun 2005 13:46:43 -0400 (EDT)
Received: from ppsw-1.csi.cam.ac.uk ([131.111.8.131])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dmy69-0005Z2-T6
	for crisp@ietf.org; Mon, 27 Jun 2005 14:12:47 -0400
X-Cam-SpamDetails: Not scanned
X-Cam-AntiVirus: No virus found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from days.fitz.cam.ac.uk ([131.111.239.95]:2641 helo=localhost)
	by ppsw-1.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.151]:465)
	with esmtps (TLSv1:DHE-RSA-AES256-SHA:256)
	id 1Dmxgh-0000V1-5P (Exim 4.51) for crisp@ietf.org
	(return-path <kengo@elab.ic.i.u-tokyo.ac.jp>);
	Mon, 27 Jun 2005 18:46:27 +0100
Date: Mon, 27 Jun 2005 18:46:26 +0100
From: Nagahashi Kengo <kengo@elab.ic.i.u-tokyo.ac.jp>
To: crisp@ietf.org
Subject: Re: [Crisp] rreg draft
Message-Id: <20050627184626.52035041.kengo@elab.ic.i.u-tokyo.ac.jp>
In-Reply-To: <556712F6-801B-4589-93E4-5EEE8004B87E@hxr.us>
References: <20050627160613.483b4e2d.kengo@elab.ic.i.u-tokyo.ac.jp>
	<556712F6-801B-4589-93E4-5EEE8004B87E@hxr.us>
X-Mailer: Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-unknown-freebsd4.10)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7bit
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

Andy,

thanks for your quick input.
Yes, we need to more concentrate policy stuff in RREG. 
1st step to concentrate is to clarify requirements for
what we should need for policy stuff in RREG.
Anyway we need to give detailed description for policy 
stuff.
thanks again.

-kengo
  

On Mon, 27 Jun 2005 11:56:42 -0400
Andrew Newton <andy@hxr.us> wrote:

> Kengo,
> 
> As I observed the meeting and from my reading of the first version of  
> the draft, it was hard to appreciate the difference between AREG and  
> RREG.  My comments are inline:
> 
> On Jun 27, 2005, at 11:06 AM, Nagahashi Kengo wrote:
> >    The obvious difference with areg and rreg is that
> >    rreg requries to handle routing policy schema
> >    e.g. AS imports policy and exports policy.
> >    This routing policy schema is described by Routing Policy
> >    Specification  Language (RPSL)[RPSL].
> >    Thus, rreg requires the routing policy handling defined
> >    in RPSL.
> 
> This is where you should probably concentrate your energy, in my  
> opinion.  I was not able to determine how RREG was different from AREG.
> 
> If the difference really isn't in the type of data but instead of who  
> is giving the data (a routing registry vs. an address registry), then  
> this might need a little clarification.
> 
> >    Since the routing registry are distributed without
> >    strong relation, root resolution is a hard issue to solve.
> >    One of straight forward solution is to decide the root
> >    e.g. "rreg.nro.net" uniquely but it still requires to
> >    discuss about it.
> 
> I would not worry about tackling this yet.
> Just my 2 cents.
> 
> -andy
> 

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



