From crisp-bounces@ietf.org  Thu Feb 10 18:26:02 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 SAA07304
	for <crisp-web-archive@ietf.org>; Thu, 10 Feb 2005 18:26:02 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CzO1L-0006ar-LK
	for crisp-web-archive@ietf.org; Thu, 10 Feb 2005 18:46:51 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CzNYo-0006Gy-A2; Thu, 10 Feb 2005 18:17:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CzNRe-0002JG-Cu
	for crisp@megatron.ietf.org; Thu, 10 Feb 2005 18:09:58 -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 SAA04885
	for <crisp@ietf.org>; Thu, 10 Feb 2005 18:09:55 -0500 (EST)
Received: from [64.151.105.12] (helo=zak.ecotroph.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CzNlj-00062N-SC
	for crisp@ietf.org; Thu, 10 Feb 2005 18:30:45 -0500
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; Thu, 10 Feb 2005 18:09:56 -0500
	id 000E434E.420BE9C4.00004707
Mime-Version: 1.0 (Apple Message framework v619)
Content-Transfer-Encoding: 7bit
Message-Id: <DF91D469-7BB8-11D9-BC8F-000D9358DFD8@hxr.us>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: crisp@ietf.org
From: Andrew Newton <andy@hxr.us>
Date: Thu, 10 Feb 2005 18:09:53 -0500
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Subject: [Crisp] draft-newton-crisp-iris-xpc-00.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.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit

Hola crispy critters,

I've recently submitted a new draft 
(draft-newton-crisp-iris-xpc-00.txt) about a new TCP transport-binding. 
  It is complimentary in structure to the LWZ draft.  Here's the URI: 
http://www.ietf.org/internet-drafts/draft-newton-crisp-iris-xpc-00.txt

I've already received one private comment regarding it.  In summary, 
the suggestion was to eliminate the raw TCP aspect and strictly use 
TLS, having clients specify SSL_NULL_WITH_NULL_NULL cipher suite when 
no encryption is needed.  The thought is that this reduces complexity 
and will not be that big of an overhead for servers considering it is 
desirable to have most traffic flow over UDP (LWZ) when no auth is 
needed.

As usual, thoughts and comments are welcome.

-andy


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


From crisp-bounces@ietf.org  Thu Feb 10 18:40:13 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 SAA08660
	for <crisp-web-archive@ietf.org>; Thu, 10 Feb 2005 18:40:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CzOF4-0006wr-K9
	for crisp-web-archive@ietf.org; Thu, 10 Feb 2005 19:01:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CzNty-0004U1-56; Thu, 10 Feb 2005 18:39:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CzNqk-0003RY-Hd
	for crisp@megatron.ietf.org; Thu, 10 Feb 2005 18:35:54 -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 SAA08153
	for <crisp@ietf.org>; Thu, 10 Feb 2005 18:35:51 -0500 (EST)
Received: from mint.apnic.net ([202.12.29.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CzOAn-0006pe-Oi
	for crisp@ietf.org; Thu, 10 Feb 2005 18:56:41 -0500
Received: from apnic.net (garlic.apnic.net [202.12.29.224])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mint.apnic.net (Postfix) with ESMTP id 634B2D5F2D;
	Fri, 11 Feb 2005 09:26:45 +1000 (EST)
Date: Fri, 11 Feb 2005 09:35:18 +1000
From: George Michaelson <ggm@apnic.net>
To: Andrew Newton <andy@hxr.us>
Subject: Re: [Crisp] draft-newton-crisp-iris-xpc-00.txt
Message-ID: <20050211093518.002c49b9@garlic.apnic.net>
In-Reply-To: <DF91D469-7BB8-11D9-BC8F-000D9358DFD8@hxr.us>
References: <DF91D469-7BB8-11D9-BC8F-000D9358DFD8@hxr.us>
Organization: APNIC Pty Ltd
X-Mailer: Sylpheed-Claws 1.0.1 (GTK+ 1.2.10; i386--netbsdelf)
X-Fruit-Of-The-Month-Club: persimmon
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
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: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: 7bit


is there a risk that users will be lulled into a false sense of security
e2e if the transport 'claims' to be TLS, but is using a null crypto?

Otherwise, its a rational choice I guess, and avoids the issue of having to
think about two transport platforms.

-G

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


From crisp-bounces@ietf.org  Thu Feb 10 20:57:39 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 UAA17820
	for <crisp-web-archive@ietf.org>; Thu, 10 Feb 2005 20:57:39 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CzQO5-00017D-5l
	for crisp-web-archive@ietf.org; Thu, 10 Feb 2005 21:18:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CzQ2d-0001pt-TR; Thu, 10 Feb 2005 20:56:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CzQ25-0001VJ-Ls
	for crisp@megatron.ietf.org; Thu, 10 Feb 2005 20:55:45 -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 UAA17746
	for <crisp@ietf.org>; Thu, 10 Feb 2005 20:55:44 -0500 (EST)
Received: from [64.151.105.12] (helo=zak.ecotroph.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CzQMC-00015F-L2
	for crisp@ietf.org; Thu, 10 Feb 2005 21:16:33 -0500
Received: from [10.0.1.3] ([::ffff:64.83.8.178])
	(AUTH: PLAIN anewton, SSL: TLSv1/SSLv3,128bits,RC4-SHA)
	by zak.ecotroph.net with esmtp; Thu, 10 Feb 2005 20:55:42 -0500
	id 001B7DA8.420C109E.00005978
In-Reply-To: <20050211093518.002c49b9@garlic.apnic.net>
References: <DF91D469-7BB8-11D9-BC8F-000D9358DFD8@hxr.us>
	<20050211093518.002c49b9@garlic.apnic.net>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <07C81EDB-7BD0-11D9-BC8F-000D9358DFD8@hxr.us>
Content-Transfer-Encoding: 7bit
From: Andrew Newton <andy@hxr.us>
Subject: Re: [Crisp] draft-newton-crisp-iris-xpc-00.txt
Date: Thu, 10 Feb 2005 20:55:39 -0500
To: George Michaelson <ggm@apnic.net>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
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: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit


On Feb 10, 2005, at 6:35 PM, George Michaelson wrote:

>
> is there a risk that users will be lulled into a false sense of 
> security
> e2e if the transport 'claims' to be TLS, but is using a null crypto?

I'm thinking that perhaps the advice in the draft is to use the null 
cipher suit unless the user explicitly asks for encryption or plain 
passwords are being used.  And to avoid what you have mentioned, 
clients should be instructed to differentiate between TLS with 
encryption and TLS without encryption.

> Otherwise, its a rational choice I guess, and avoids the issue of 
> having to
> think about two transport platforms.

Yup.  Less admin trivia (ACLs on border routers, firewall rules, etc... 
) too.

-andy


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


From crisp-bounces@ietf.org  Tue Feb 15 15:35:05 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 PAA09142
	for <crisp-web-archive@ietf.org>; Tue, 15 Feb 2005 15:35:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D19kd-0000eu-AE
	for crisp-web-archive@ietf.org; Tue, 15 Feb 2005 15:56:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D19GO-0004zq-RJ; Tue, 15 Feb 2005 15:25:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D197j-00005U-7u
	for crisp@megatron.ietf.org; Tue, 15 Feb 2005 15:16:43 -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 PAA06335
	for <crisp@ietf.org>; Tue, 15 Feb 2005 15:16:41 -0500 (EST)
Received: from shell-ng.nominum.com ([81.200.64.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D19So-0008Ps-DV
	for crisp@ietf.org; Tue, 15 Feb 2005 15:38:31 -0500
Received: by shell-ng.nominum.com (Postfix, from userid 10182)
	id 6A83156838; Tue, 15 Feb 2005 12:16:07 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by shell-ng.nominum.com (Postfix) with ESMTP id 688DB56835;
	Tue, 15 Feb 2005 12:16:07 -0800 (PST)
	(envelope-from amarine@nominum.com)
Date: Tue, 15 Feb 2005 12:16:07 -0800 (PST)
From: April Marine <April.Marine@nominum.com>
To: CRISP WG <crisp@ietf.org>
Message-ID: <20050215121201.P40811@shell-ng.nominum.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: April Marine <april.marine@nominum.com>, Ted Hardie <hardie@qualcomm.com>,
        George Michaelson <ggm@apnic.net>
Subject: [Crisp] Working Group Last Call on AREG docs
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: 9182cfff02fae4f1b6e9349e01d62f32

This is the official Working Group Last Call for the following two docs. 
The first has been discussed extensively; the second was a spinoff created 
after the last meeting.

Please send comments to the mailing list. This two week last call will end 
on March 1 with the hope that, if needed, the docs can be spun and sent to 
the IESG shortly after the March meeting (where feedback can be 
discussed).

thanks!
April and George


IRIS - An Address Registry (areg) Type for the Internet Registry
Information Service
draft-ietf-crisp-iris-areg-09.txt

IRIS - URI Resolution for AREG Type for the Internet Registry
Information Service
draft-ietf-crisp-iris-areg-urires-00.txt

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


From crisp-bounces@ietf.org  Tue Feb 15 18:14:23 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 SAA26250
	for <crisp-web-archive@ietf.org>; Tue, 15 Feb 2005 18:14:23 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1CEq-0004zm-2L
	for crisp-web-archive@ietf.org; Tue, 15 Feb 2005 18:36:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1Bqn-0006h1-Fp; Tue, 15 Feb 2005 18:11:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D1Bow-00066c-PU
	for crisp@megatron.ietf.org; Tue, 15 Feb 2005 18:09: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 SAA25344
	for <crisp@ietf.org>; Tue, 15 Feb 2005 18:09:28 -0500 (EST)
Received: from mint.apnic.net ([202.12.29.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1CA3-0004qc-VU
	for crisp@ietf.org; Tue, 15 Feb 2005 18:31:21 -0500
Received: from apnic.net (garlic.apnic.net [202.12.29.224])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mint.apnic.net (Postfix) with ESMTP id 3FD04D5F31
	for <crisp@ietf.org>; Wed, 16 Feb 2005 08:59:54 +1000 (EST)
Date: Wed, 16 Feb 2005 09:08:56 +1000
From: George Michaelson <ggm@apnic.net>
To: crisp@ietf.org
Message-ID: <20050216090856.11157de7@garlic.apnic.net>
Organization: APNIC Pty Ltd
X-Mailer: Sylpheed-Claws 1.0.1 (GTK+ 1.2.10; i386--netbsdelf)
X-Fruit-Of-The-Month-Club: persimmon
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit
Subject: [Crisp] new draft for consideration by WG:
 draft-kengo-crisp-iris-rreg-00.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.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit


Kengo Nagahashi, Tomoya Yoshida and Kuniaki Kondo have submitted a draft
IRIS routing registry proposal:

	Title		: IRIS - A Routing Registry (rreg) Type for the Internet 
 			  Registry Information Service
 	Author(s)	: K. Nagahashi, et al.
 	Filename	: draft-kengo-crisp-iris-rreg-00.txt
 	Pages		: 61
 	Date		: 2005-2-14
 	

Available from the usual places but notably:

	http://www.ietf.org/internet-drafts/draft-kengo-crisp-iris-rreg-00.txt

I'd like to thank them for this submission, and ask the WG to read the
draft and consider it for possible WG adoption.  This would complete the
set of current WHOIS dependent services and make CRISP a much more complete
activity.

If we have time, why don't we discuss this in Minneapolis?

Many thanks for your submission guys!

-George

-- 
George Michaelson       |  APNIC                 
Email: ggm@apnic.net    |  PO Box 2131 Milton
Phone: +61 7 3858 3150  |  QLD 4064 Australia    
  Fax: +61 7 3858 3199  |  http://www.apnic.net  

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


From crisp-bounces@ietf.org  Tue Feb 15 20:52:25 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 UAA12632
	for <crisp-web-archive@ietf.org>; Tue, 15 Feb 2005 20:52:25 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1Ehm-0000wx-Jr
	for crisp-web-archive@ietf.org; Tue, 15 Feb 2005 21:14:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1ELT-0000ta-7p; Tue, 15 Feb 2005 20:51:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D1EIt-00081O-Tw
	for crisp@megatron.ietf.org; Tue, 15 Feb 2005 20:48:36 -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 UAA12300
	for <crisp@ietf.org>; Tue, 15 Feb 2005 20:48:34 -0500 (EST)
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1Ee2-0000pV-Ii
	for crisp@ietf.org; Tue, 15 Feb 2005 21:10:27 -0500
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by numenor.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id
	j1G1lqhP013694
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 15 Feb 2005 17:47:52 -0800 (PST)
Received: from [24.23.128.154] (vpn-10-50-16-92.qualcomm.com [10.50.16.92])
	by crowley.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id
	j1G1lmBf023737; Tue, 15 Feb 2005 17:47:49 -0800 (PST)
Mime-Version: 1.0
Message-Id: <p06210205be3854c35e39@[24.23.128.154]>
In-Reply-To: <20050215121201.P40811@shell-ng.nominum.com>
References: <20050215121201.P40811@shell-ng.nominum.com>
Date: Tue, 15 Feb 2005 17:41:07 -0800
To: April Marine <April.Marine@nominum.com>, CRISP WG <crisp@ietf.org>
From: Ted Hardie <hardie@qualcomm.com>
Subject: Re: [Crisp] Working Group Last Call on AREG docs
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-PMX-Version: 4.7.0.111621
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: April Marine <april.marine@nominum.com>, George Michaelson <ggm@apnic.net>
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: a7d6aff76b15f3f56fcb94490e1052e4

I am a bit confused here.  The urires doc does not seem to have
been updated since the working group meeting in which (I thought)
we agreed not to include  iris.nro.net as a default top.  Can I have
pointers to the working group discussion where that was changed?
			thanks,
				Ted




At 12:16 PM -0800 2/15/05, April Marine wrote:
>This is the official Working Group Last Call for the following two 
>docs. The first has been discussed extensively; the second was a 
>spinoff created after the last meeting.
>
>Please send comments to the mailing list. This two week last call 
>will end on March 1 with the hope that, if needed, the docs can be 
>spun and sent to the IESG shortly after the March meeting (where 
>feedback can be discussed).
>
>thanks!
>April and George
>
>
>IRIS - An Address Registry (areg) Type for the Internet Registry
>Information Service
>draft-ietf-crisp-iris-areg-09.txt
>
>IRIS - URI Resolution for AREG Type for the Internet Registry
>Information Service
>draft-ietf-crisp-iris-areg-urires-00.txt
>
>_______________________________________________
>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 Feb 15 21:45:25 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 VAA19941
	for <crisp-web-archive@ietf.org>; Tue, 15 Feb 2005 21:45:25 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1FX5-0002zK-5o
	for crisp-web-archive@ietf.org; Tue, 15 Feb 2005 22:07:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1F2d-0004OJ-2Q; Tue, 15 Feb 2005 21:35:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D1Erd-0001DA-1R
	for crisp@megatron.ietf.org; Tue, 15 Feb 2005 21:24: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 VAA16522
	for <crisp@ietf.org>; Tue, 15 Feb 2005 21:24:27 -0500 (EST)
Received: from dml-gw.dml.com ([211.1.161.129]
	helo=ken2-vmware.hongo.wide.ad.jp)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1FCm-0001vV-ST
	for crisp@ietf.org; Tue, 15 Feb 2005 21:46:21 -0500
Received: from ken2-vmware.hongo.wide.ad.jp (localhost [127.0.0.1])
	by ken2-vmware.hongo.wide.ad.jp (8.11.6/8.11.6) with SMTP id
	j1G2Nin01072; Wed, 16 Feb 2005 11:23:44 +0900 (JST)
	(envelope-from kengo@elab.ic.i.u-tokyo.ac.jp)
Date: Wed, 16 Feb 2005 11:23:44 +0900
From: Nagahashi Kengo <kengo@elab.ic.i.u-tokyo.ac.jp>
To: crisp@ietf.org
Subject: Re: [Crisp] new draft for consideration by WG:
	draft-kengo-crisp-iris-rreg-00.txt
Message-Id: <20050216112344.3499216f.kengo@elab.ic.i.u-tokyo.ac.jp>
In-Reply-To: <20050216090856.11157de7@garlic.apnic.net>
References: <20050216090856.11157de7@garlic.apnic.net>
Organization: The University of Tokyo
X-Mailer: Sylpheed version 0.8.0 (GTK+ 1.2.10; i386-unknown-freebsd4.5)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: 7bit
Cc: yoshida@ocn.ad.jp, kuniaki@inetcore.com
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: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit


thanks for pushing.
We hope we have a short discussion in Minneapolis.
Any comments would be appreciate.

-kengo



On Wed, 16 Feb 2005 09:08:56 +1000
George Michaelson <ggm@apnic.net> wrote:

> 
> Kengo Nagahashi, Tomoya Yoshida and Kuniaki Kondo have submitted a draft
> IRIS routing registry proposal:
> 
> 	Title		: IRIS - A Routing Registry (rreg) Type for the Internet 
>  			  Registry Information Service
>  	Author(s)	: K. Nagahashi, et al.
>  	Filename	: draft-kengo-crisp-iris-rreg-00.txt
>  	Pages		: 61
>  	Date		: 2005-2-14
>  	
> 
> Available from the usual places but notably:
> 
> 	http://www.ietf.org/internet-drafts/draft-kengo-crisp-iris-rreg-00.txt
> 
> I'd like to thank them for this submission, and ask the WG to read the
> draft and consider it for possible WG adoption.  This would complete the
> set of current WHOIS dependent services and make CRISP a much more complete
> activity.
> 
> If we have time, why don't we discuss this in Minneapolis?
> 
> Many thanks for your submission guys!
> 
> -George
> 
> -- 
> George Michaelson       |  APNIC                 
> Email: ggm@apnic.net    |  PO Box 2131 Milton
> Phone: +61 7 3858 3150  |  QLD 4064 Australia    
>   Fax: +61 7 3858 3199  |  http://www.apnic.net  
> 
> _______________________________________________
> 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  Wed Feb 16 07:10: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 HAA00410
	for <crisp-web-archive@ietf.org>; Wed, 16 Feb 2005 07:10:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1OMA-0001jr-6F
	for crisp-web-archive@ietf.org; Wed, 16 Feb 2005 07:32:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1NvN-00047Y-1S; Wed, 16 Feb 2005 07:04:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D1Nlc-0001Oj-Mp
	for crisp@megatron.ietf.org; Wed, 16 Feb 2005 06:54:54 -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 GAA28914
	for <crisp@ietf.org>; Wed, 16 Feb 2005 06:54:49 -0500 (EST)
Received: from postman.ripe.net ([193.0.0.199])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1O6r-0001JG-MX
	for crisp@ietf.org; Wed, 16 Feb 2005 07:16:50 -0500
Received: by postman.ripe.net (Postfix, from userid 8)
	id EADC0242E4; Wed, 16 Feb 2005 12:54:20 +0100 (CET)
Received: from birch.ripe.net (birch.ripe.net [193.0.1.96])
	by postman.ripe.net (Postfix) with ESMTP
	id E750F249EF; Wed, 16 Feb 2005 12:54:19 +0100 (CET)
Received: from [193.0.1.17] (x17.ripe.net [193.0.1.17])
	by birch.ripe.net (8.12.10/8.11.6) with ESMTP id j1GBsJet007027;
	Wed, 16 Feb 2005 12:54:19 +0100
Message-ID: <4213346B.9050604@ripe.net>
Date: Wed, 16 Feb 2005 12:54:19 +0100
From: Shane Kerr <shane@ripe.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913
X-Accept-Language: en, nl
MIME-Version: 1.0
To: Ted Hardie <hardie@qualcomm.com>
Subject: Re: [Crisp] Working Group Last Call on AREG docs
References: <20050215121201.P40811@shell-ng.nominum.com>
	<p06210205be3854c35e39@[24.23.128.154]>
In-Reply-To: <p06210205be3854c35e39@[24.23.128.154]>
X-Enigmail-Version: 0.90.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00
X-RIPE-Spam-Status: N 0.000000 / -5.9
X-RIPE-Signature: 5eb718578b72e3718e83de2936ef6866
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7bit
Cc: April Marine <April.Marine@nominum.com>, CRISP WG <crisp@ietf.org>,
        George Michaelson <ggm@apnic.net>
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: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: 7bit

Ted,

IIRC, we agreed not to include iris.nro.net in the areg document, and rather 
to put it into a separate document, the urires document.

The idea was to separate the schema & protocol definition from the service 
resolution (I think it was your idea, Ted).

Ted Hardie wrote:
> I am a bit confused here.  The urires doc does not seem to have
> been updated since the working group meeting in which (I thought)
> we agreed not to include  iris.nro.net as a default top.  Can I have
> pointers to the working group discussion where that was changed?
>             thanks,
>                 Ted
> 
> 
> 
> 
> At 12:16 PM -0800 2/15/05, April Marine wrote:
> 
>> This is the official Working Group Last Call for the following two 
>> docs. The first has been discussed extensively; the second was a 
>> spinoff created after the last meeting.
>>
>> Please send comments to the mailing list. This two week last call will 
>> end on March 1 with the hope that, if needed, the docs can be spun and 
>> sent to the IESG shortly after the March meeting (where feedback can 
>> be discussed).
>>
>> thanks!
>> April and George
>>
>>
>> IRIS - An Address Registry (areg) Type for the Internet Registry
>> Information Service
>> draft-ietf-crisp-iris-areg-09.txt
>>
>> IRIS - URI Resolution for AREG Type for the Internet Registry
>> Information Service
>> draft-ietf-crisp-iris-areg-urires-00.txt
>>
>> _______________________________________________
>> 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


-- 
Shane Kerr
RIPE NCC

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


From crisp-bounces@ietf.org  Wed Feb 16 14:48:11 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 OAA10562
	for <crisp-web-archive@ietf.org>; Wed, 16 Feb 2005 14:48:11 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1VUz-00070P-Nh
	for crisp-web-archive@ietf.org; Wed, 16 Feb 2005 15:10:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1TWN-0000bJ-CP; Wed, 16 Feb 2005 13:03:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D1Rtx-0004DF-50
	for crisp@megatron.ietf.org; Wed, 16 Feb 2005 11:19:45 -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 LAA08929
	for <crisp@ietf.org>; Wed, 16 Feb 2005 11:19:42 -0500 (EST)
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1SFE-00045l-8P
	for crisp@ietf.org; Wed, 16 Feb 2005 11:41:44 -0500
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by ithilien.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id
	j1GGIweD015436; Wed, 16 Feb 2005 08:18:58 -0800 (PST)
Received: from [24.23.128.154] (vpn-10-50-0-15.qualcomm.com [10.50.0.15])
	by sabrina.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id
	j1GGIsJr007883; Wed, 16 Feb 2005 08:18:55 -0800 (PST)
Mime-Version: 1.0
Message-Id: <p06210202be39203c0eed@[24.23.128.154]>
In-Reply-To: <4213346B.9050604@ripe.net>
References: <20050215121201.P40811@shell-ng.nominum.com>
	<p06210205be3854c35e39@[24.23.128.154]> <4213346B.9050604@ripe.net>
Date: Wed, 16 Feb 2005 08:18:54 -0800
To: Shane Kerr <shane@ripe.net>
From: Ted Hardie <hardie@qualcomm.com>
Subject: Re: [Crisp] Working Group Last Call on AREG docs
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-PMX-Version: 4.7.0.111621
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: April Marine <April.Marine@nominum.com>, CRISP WG <crisp@ietf.org>,
        George Michaelson <ggm@apnic.net>
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: 3002fc2e661cd7f114cb6bae92fe88f1

At 12:54 PM +0100 2/16/05, Shane Kerr wrote:
>Ted,
>
>IIRC, we agreed not to include iris.nro.net in the areg document, 
>and rather to put it into a separate document, the urires document.
>
>The idea was to separate the schema & protocol definition from the 
>service resolution (I think it was your idea, Ted).

I do think I suggested that. I thought I also suggested that we
leave the top as "subject to client configuration", so that the document
did not enshrine a particular domain name.  My reasoning for this
was that it would be better to build clients capable of configuration
on this point rather than having a hard-coded the address; during a DDoS attack
on iris.nro.net, to give a small example, the ability to re-point at
an active mirror or different system is valuable.  I also remember
vividly how long the SRI machines got whois queries after things
functionally changed.  That name is enshrined in RFC 954, which
didn't get updated to remove that kind of detail until Leslie took
it on RFC 3912, and that was probably part of the reason the
stream ran on so long.  I suspect April remembers this even better
than I do.

Moving the top level name to a different document *does* make it
much easier to rev, but I do wonder if that is enough.

Speaking only as a young geezer,
				Ted

>Ted Hardie wrote:
>>I am a bit confused here.  The urires doc does not seem to have
>>been updated since the working group meeting in which (I thought)
>>we agreed not to include  iris.nro.net as a default top.  Can I have
>>pointers to the working group discussion where that was changed?
>>             thanks,
>>                 Ted
>>
>>
>>
>>
>>At 12:16 PM -0800 2/15/05, April Marine wrote:
>>
>>>This is the official Working Group Last Call for the following two 
>>>docs. The first has been discussed extensively; the second was a 
>>>spinoff created after the last meeting.
>>>
>>>Please send comments to the mailing list. This two week last call 
>>>will end on March 1 with the hope that, if needed, the docs can be 
>>>spun and sent to the IESG shortly after the March meeting (where 
>>>feedback can be discussed).
>>>
>>>thanks!
>>>April and George
>>>
>>>
>>>IRIS - An Address Registry (areg) Type for the Internet Registry
>>>Information Service
>>>draft-ietf-crisp-iris-areg-09.txt
>>>
>>>IRIS - URI Resolution for AREG Type for the Internet Registry
>>>Information Service
>>>draft-ietf-crisp-iris-areg-urires-00.txt
>>>
>>>_______________________________________________
>>>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
>
>
>--
>Shane Kerr
>RIPE NCC


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


From crisp-bounces@ietf.org  Wed Feb 16 15:04:37 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 PAA13822
	for <crisp-web-archive@ietf.org>; Wed, 16 Feb 2005 15:04:34 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1Vko-0007z8-2H
	for crisp-web-archive@ietf.org; Wed, 16 Feb 2005 15:26:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1UzJ-00087H-JF; Wed, 16 Feb 2005 14:37:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D1T5H-0006wx-2y
	for crisp@megatron.ietf.org; Wed, 16 Feb 2005 12:35: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 MAA01028
	for <crisp@ietf.org>; Wed, 16 Feb 2005 12:35:24 -0500 (EST)
Received: from shell-ng.nominum.com ([81.200.64.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1TQS-0002sW-Pw
	for crisp@ietf.org; Wed, 16 Feb 2005 12:57:28 -0500
Received: by shell-ng.nominum.com (Postfix, from userid 10182)
	id 620E256881; Wed, 16 Feb 2005 09:34:52 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by shell-ng.nominum.com (Postfix) with ESMTP id 602D55687E;
	Wed, 16 Feb 2005 09:34:52 -0800 (PST)
	(envelope-from amarine@nominum.com)
Date: Wed, 16 Feb 2005 09:34:52 -0800 (PST)
From: April Marine <April.Marine@nominum.com>
To: Ted Hardie <hardie@qualcomm.com>
Subject: Re: [Crisp] Working Group Last Call on AREG docs
In-Reply-To: <p06210202be39203c0eed@[24.23.128.154]>
Message-ID: <20050216093218.L31535@shell-ng.nominum.com>
References: <20050215121201.P40811@shell-ng.nominum.com>
	<p06210205be3854c35e39@[24.23.128.154]> <4213346B.9050604@ripe.net>
	<p06210202be39203c0eed@[24.23.128.154]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 093efd19b5f651b2707595638f6c4003

I looked at the minutes (which, thanks to Kim Davies, were quite clear on 
what we said). My memory was we were going to do the doc as done, but
it could be open for interpretation:

------------
from minutes:

There is a concern that the IESG will not be happy with having a
specific host hardcoded in the specification.

George Michaelson stated he felt uncomfortable with having a host in the
specification, and would be tempted not to specify the server selection
process as a defacto one will likely naturally emerge anyway.

Scott Hollenbeck echoed this feeling that it didn't seem right to
include a hostname.

Ted Hardie said you could always submit the draft with the reference in,
but the IESG may remove it. He said he saw the advantage of having a
single root to manage the referral process, but some people may want to
set up other services outside this one. He noted that an effort had
recently concluded on pulling operational things out of the WHOIS
specification, making it a purely technical. He believed it could be
appropriate to publish a second document that documented NRO's role in
bootstrapping searches, as it doesn't build a dependency into the
protocol on a single root.

-------------

The minutes also say that I said we should take this to the list, which 
unfortunately, I don't think I ever really did. So I guess we are having 
that conversation now. :)


April


On Wed, 16 Feb 2005, Ted Hardie wrote:

> At 12:54 PM +0100 2/16/05, Shane Kerr wrote:
>> Ted,
>> 
>> IIRC, we agreed not to include iris.nro.net in the areg document, and 
>> rather to put it into a separate document, the urires document.
>> 
>> The idea was to separate the schema & protocol definition from the service 
>> resolution (I think it was your idea, Ted).
>
> I do think I suggested that. I thought I also suggested that we
> leave the top as "subject to client configuration", so that the document
> did not enshrine a particular domain name.  My reasoning for this
> was that it would be better to build clients capable of configuration
> on this point rather than having a hard-coded the address; during a DDoS 
> attack
> on iris.nro.net, to give a small example, the ability to re-point at
> an active mirror or different system is valuable.  I also remember
> vividly how long the SRI machines got whois queries after things
> functionally changed.  That name is enshrined in RFC 954, which
> didn't get updated to remove that kind of detail until Leslie took
> it on RFC 3912, and that was probably part of the reason the
> stream ran on so long.  I suspect April remembers this even better
> than I do.
>
> Moving the top level name to a different document *does* make it
> much easier to rev, but I do wonder if that is enough.
>
> Speaking only as a young geezer,
> 				Ted
>
>> Ted Hardie wrote:
>>> I am a bit confused here.  The urires doc does not seem to have
>>> been updated since the working group meeting in which (I thought)
>>> we agreed not to include  iris.nro.net as a default top.  Can I have
>>> pointers to the working group discussion where that was changed?
>>>             thanks,
>>>                 Ted
>>> 
>>> 
>>> 
>>> 
>>> At 12:16 PM -0800 2/15/05, April Marine wrote:
>>> 
>>>> This is the official Working Group Last Call for the following two docs. 
>>>> The first has been discussed extensively; the second was a spinoff 
>>>> created after the last meeting.
>>>> 
>>>> Please send comments to the mailing list. This two week last call will 
>>>> end on March 1 with the hope that, if needed, the docs can be spun and 
>>>> sent to the IESG shortly after the March meeting (where feedback can be 
>>>> discussed).
>>>> 
>>>> thanks!
>>>> April and George
>>>> 
>>>> 
>>>> IRIS - An Address Registry (areg) Type for the Internet Registry
>>>> Information Service
>>>> draft-ietf-crisp-iris-areg-09.txt
>>>> 
>>>> IRIS - URI Resolution for AREG Type for the Internet Registry
>>>> Information Service
>>>> draft-ietf-crisp-iris-areg-urires-00.txt
>>>> 
>>>> _______________________________________________
>>>> 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
>> 
>> 
>> --
>> Shane Kerr
>> RIPE NCC
>

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


From crisp-bounces@ietf.org  Wed Feb 16 21:13:29 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 VAA25781
	for <crisp-web-archive@ietf.org>; Wed, 16 Feb 2005 21:13:29 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1bVw-0002e7-Gm
	for crisp-web-archive@ietf.org; Wed, 16 Feb 2005 21:35:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1b6o-0001qz-4C; Wed, 16 Feb 2005 21:09:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D1b5U-0001Oo-RW
	for crisp@megatron.ietf.org; Wed, 16 Feb 2005 21:08:17 -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 VAA25509
	for <crisp@ietf.org>; Wed, 16 Feb 2005 21:08:13 -0500 (EST)
Received: from jens241.inetcore.com ([202.33.8.241] helo=gw.inetcore.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1bQp-0002YN-IB
	for crisp@ietf.org; Wed, 16 Feb 2005 21:30:20 -0500
Received: from kuniaki (dhcp224.inetcore.com [192.168.0.224])
	by gw.inetcore.com (Postfix) with ESMTP id B3B551D1D4E;
	Thu, 17 Feb 2005 11:03:30 +0900 (JST)
To: crisp@ietf.org
Subject: FW: Re: [Crisp] new draft for consideration by WG:
	draft-kengo-crisp-iris-rreg-00.txt
From: Kuniaki Kondo <kuniaki@bugest.net>
References: <200502171051.FDC81298.LJBOVJL@inetcore.com>
Message-Id: <200502171108.GBE00046.JLJOVBL@bugest.net>
X-Mailer: Winbiff [Version 2.50 beta11]
X-Accept-Language: ja,en
Date: Thu, 17 Feb 2005 11:08:11 +0900
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: yoshida@ocn.ad.jp
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: 92df29fa99cf13e554b84c8374345c17

Hi, All

>thanks for pushing.
>We hope we have a short discussion in Minneapolis.
>Any comments would be appreciate.

 Especially, we are considering what queries are usefull for this
 service. It's written in section 3.1 'Query Derivatives'.

 If you have any request or comment, please let me know.

 Thanks.


>
>-kengo
>
>
>
>On Wed, 16 Feb 2005 09:08:56 +1000
>George Michaelson <ggm@apnic.net> wrote:
>
>> 
>> Kengo Nagahashi, Tomoya Yoshida and Kuniaki Kondo have submitted a draft
>> IRIS routing registry proposal:
>> 
>> 	Title		: IRIS - A Routing Registry (rreg) Type for the Internet 
>>  			  Registry Information Service
>>  	Author(s)	: K. Nagahashi, et al.
>>  	Filename	: draft-kengo-crisp-iris-rreg-00.txt
>>  	Pages		: 61
>>  	Date		: 2005-2-14
>>  	
>> 
>> Available from the usual places but notably:
>> 
>> 	http://www.ietf.org/internet-drafts/draft-kengo-crisp-iris-rreg-00.txt
>> 
>> I'd like to thank them for this submission, and ask the WG to read the
>> draft and consider it for possible WG adoption.  This would complete the
>> set of current WHOIS dependent services and make CRISP a much more complete
>> activity.
>> 
>> If we have time, why don't we discuss this in Minneapolis?
>> 
>> Many thanks for your submission guys!
>> 
>> -George
>> 
>> -- 
>> George Michaelson       |  APNIC                 
>> Email: ggm@apnic.net    |  PO Box 2131 Milton
>> Phone: +61 7 3858 3150  |  QLD 4064 Australia    
>>   Fax: +61 7 3858 3199  |  http://www.apnic.net  
>> 
>> _______________________________________________
>> Crisp mailing list
>> Crisp@ietf.org
>> https://www1.ietf.org/mailman/listinfo/crisp
>> 

Kuniaki KONDO - Intec NetCore, Inc.
Kuniaki@iNetCore.Com - http://inetcore.com/
NATS Project - http://www.nats-project.org/
$B%$%Y%s%H(BML - http://www.bugest.net/event-ml.html


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


From crisp-bounces@ietf.org  Thu Feb 17 05:53:29 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 FAA06619
	for <crisp-web-archive@ietf.org>; Thu, 17 Feb 2005 05:53:29 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1jdE-0007FR-OQ
	for crisp-web-archive@ietf.org; Thu, 17 Feb 2005 06:15:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1jFu-0007IE-SA; Thu, 17 Feb 2005 05:51:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D1j9j-0004oP-US
	for crisp@megatron.ietf.org; Thu, 17 Feb 2005 05:45:12 -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 FAA05744
	for <crisp@ietf.org>; Thu, 17 Feb 2005 05:45:09 -0500 (EST)
Received: from postman.ripe.net ([193.0.0.199])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1jV9-0006zl-V3
	for crisp@ietf.org; Thu, 17 Feb 2005 06:07:21 -0500
Received: by postman.ripe.net (Postfix, from userid 8)
	id 8040A25FFC; Thu, 17 Feb 2005 11:44:39 +0100 (CET)
Received: from birch.ripe.net (birch.ripe.net [193.0.1.96])
	by postman.ripe.net (Postfix) with ESMTP
	id E9A6625F91; Thu, 17 Feb 2005 11:44:37 +0100 (CET)
Received: from [193.0.1.17] (x17.ripe.net [193.0.1.17])
	by birch.ripe.net (8.12.10/8.11.6) with ESMTP id j1HAibet007381;
	Thu, 17 Feb 2005 11:44:37 +0100
Message-ID: <42147595.4030203@ripe.net>
Date: Thu, 17 Feb 2005 11:44:37 +0100
From: Shane Kerr <shane@ripe.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913
X-Accept-Language: en, nl
MIME-Version: 1.0
To: Ted Hardie <hardie@qualcomm.com>
Subject: Re: [Crisp] Working Group Last Call on AREG docs
References: <20050215121201.P40811@shell-ng.nominum.com>
	<p06210205be3854c35e39@[24.23.128.154]> <4213346B.9050604@ripe.net>
	<p06210202be39203c0eed@[24.23.128.154]>
In-Reply-To: <p06210202be39203c0eed@[24.23.128.154]>
X-Enigmail-Version: 0.90.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00
X-RIPE-Spam-Status: N 0.000000 / -5.9
X-RIPE-Signature: e6d6df02a01b16abf8dc9e1607545522
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: 7bit
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Content-Transfer-Encoding: 7bit

Ted Hardie wrote:
> At 12:54 PM +0100 2/16/05, Shane Kerr wrote:
> 
>> Ted,
>>
>> IIRC, we agreed not to include iris.nro.net in the areg document, and 
>> rather to put it into a separate document, the urires document.
>>
>> The idea was to separate the schema & protocol definition from the 
>> service resolution (I think it was your idea, Ted).
> 
> 
> I do think I suggested that. I thought I also suggested that we
> leave the top as "subject to client configuration", so that the document
> did not enshrine a particular domain name.  My reasoning for this
> was that it would be better to build clients capable of configuration
> on this point rather than having a hard-coded the address; during a DDoS 
> attack
> on iris.nro.net, to give a small example, the ability to re-point at
> an active mirror or different system is valuable.  I also remember
> vividly how long the SRI machines got whois queries after things
> functionally changed.  That name is enshrined in RFC 954, which
> didn't get updated to remove that kind of detail until Leslie took
> it on RFC 3912, and that was probably part of the reason the
> stream ran on so long.  I suspect April remembers this even better
> than I do.
> 
> Moving the top level name to a different document *does* make it
> much easier to rev, but I do wonder if that is enough.

I guess my question is:

- How does someone attempting to write a client know where to start looking?

A more general question is:

- In IRIS, where do I start my resolution process?

In IRIS, the answer is: at the top.

For DREG, this is at the top of the DNS.

For EREG, I am guessing this is also at the top of the DNS.

For AREG, there is no direct mapping (or indirect in some cases) between the 
data being searched for and a domain name. Rather than force the AREG to use 
DNS, an alternate top needs to be defined. The easiest way seemed to be... 
IRIS.NRO.NET.

I think the requirements are a directory service that has a natural mapping 
from number ranges. Neither DNS nor LDAP really has that, but I feel that 
IRIS *does*, once you have gotten around the tricky problem of where to 
*start* the lookup process.

-- 
Shane Kerr
RIPE NCC

p.s. I haven't looked at RREG, so I don't know where it starts.

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


From crisp-bounces@ietf.org  Thu Feb 17 15:33:57 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 PAA02217
	for <crisp-web-archive@ietf.org>; Thu, 17 Feb 2005 15:33:57 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1sh2-0006nT-9k
	for crisp-web-archive@ietf.org; Thu, 17 Feb 2005 15:56:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1qbK-0007px-N7; Thu, 17 Feb 2005 13:42:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D1nyj-0000M2-3a
	for crisp@megatron.ietf.org; Thu, 17 Feb 2005 10:54:09 -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 KAA09780
	for <crisp@ietf.org>; Thu, 17 Feb 2005 10:54:07 -0500 (EST)
Received: from [64.151.105.12] (helo=zak.ecotroph.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1oKB-0007gn-OA
	for crisp@ietf.org; Thu, 17 Feb 2005 11:16:21 -0500
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; Thu, 17 Feb 2005 10:54:01 -0500
	id 000B4204.4214BE1A.00007538
Mime-Version: 1.0 (Apple Message framework v619.2)
In-Reply-To: <42147595.4030203@ripe.net>
References: <20050215121201.P40811@shell-ng.nominum.com>
	<p06210205be3854c35e39@[24.23.128.154]> <4213346B.9050604@ripe.net>
	<p06210202be39203c0eed@[24.23.128.154]> <42147595.4030203@ripe.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <1a430b65bdeceda79b33937bf7fe9ed6@hxr.us>
Content-Transfer-Encoding: 7bit
From: Andrew Newton <andy@hxr.us>
Subject: Re: [Crisp] Working Group Last Call on AREG docs
Date: Thu, 17 Feb 2005 10:53:59 -0500
To: CRISP WG <crisp@ietf.org>
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit


On Feb 17, 2005, at 5:44 AM, Shane Kerr wrote:

> where do I start my resolution process?

start at 0.0.0.0 until you get to 255.255.255.255.  :)

> For AREG, there is no direct mapping (or indirect in some cases) 
> between the data being searched for and a domain name. Rather than 
> force the AREG to use DNS, an alternate top needs to be defined. The 
> easiest way seemed to be... IRIS.NRO.NET.

I think it is a good idea to have the draft suggest to implementors to 
make the AREG top a configuration option... and to also suggest the 
default should be IRIS.NRO.NET.  Indeed, there will be people 10 or 15 
years from now who will query that name long after it has changed to 
IRIS.SUPER-NRO.NET just like there are people who never update their 
DNS hints file.  Unless we plan on having this updated everytime MS 
Windows Update executes, I see no way around it.

-andy


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


From crisp-bounces@ietf.org  Thu Feb 17 18:47: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 SAA25972
	for <crisp-web-archive@ietf.org>; Thu, 17 Feb 2005 18:47:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1viQ-0004sA-4a
	for crisp-web-archive@ietf.org; Thu, 17 Feb 2005 19:09:51 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1uZZ-0008GA-Ps; Thu, 17 Feb 2005 17:56:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D1uEj-0007Ga-1j
	for crisp@megatron.ietf.org; Thu, 17 Feb 2005 17:35:05 -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 RAA18267
	for <crisp@ietf.org>; Thu, 17 Feb 2005 17:35:00 -0500 (EST)
Received: from mx.alices-registry.com ([69.59.189.34])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1uaC-0002yJ-PM
	for crisp@ietf.org; Thu, 17 Feb 2005 17:57:18 -0500
Received: by mx.alices-registry.com (Postfix, from userid 1012)
	id 5A5E914804F; Thu, 17 Feb 2005 14:54:46 -0800 (PST)
Received: from [192.168.1.10] (dsl081-069-028.sfo1.dsl.speakeasy.net
	[64.81.69.28])
	by mx.alices-registry.com (Postfix) with ESMTP id 910A114804F;
	Thu, 17 Feb 2005 14:54:41 -0800 (PST)
Message-ID: <42151BFB.4010900@ar.com>
Date: Thu, 17 Feb 2005 14:34:35 -0800
From: Rick Wesson <wessorh@ar.com>
User-Agent: Mozilla Thunderbird 0.8 (X11/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Andrew Newton <andy@hxr.us>
Subject: Re: [Crisp] Working Group Last Call on AREG docs
References: <20050215121201.P40811@shell-ng.nominum.com>	<p06210205be3854c35e39@[24.23.128.154]>
	<4213346B.9050604@ripe.net>	<p06210202be39203c0eed@[24.23.128.154]>
	<42147595.4030203@ripe.net>
	<1a430b65bdeceda79b33937bf7fe9ed6@hxr.us>
In-Reply-To: <1a430b65bdeceda79b33937bf7fe9ed6@hxr.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on mx1.ar.com
X-Spam-Status: No, hits=0.0 required=3.0 tests=none autolearn=no version=2.60
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit


just a clarification question....

Why must contacts have their address associated with an organization, 
there appears no capability to have a contact with any address 
information of their own. The slippry slope is that only number 
deligations can be made to organizations.

is my logic flawed? any education would be much appreciated.

-rick






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


From crisp-bounces@ietf.org  Thu Feb 17 18:59:42 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 SAA27345
	for <crisp-web-archive@ietf.org>; Thu, 17 Feb 2005 18:59:42 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1vuB-0005Dr-Vt
	for crisp-web-archive@ietf.org; Thu, 17 Feb 2005 19:22:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1vIf-0003OE-Bp; Thu, 17 Feb 2005 18:43:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D1uM4-0003vj-V3
	for crisp@megatron.ietf.org; Thu, 17 Feb 2005 17:42:40 -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 RAA19634
	for <crisp@ietf.org>; Thu, 17 Feb 2005 17:42:38 -0500 (EST)
Received: from [64.151.105.12] (helo=zak.ecotroph.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1uhb-0003NM-Me
	for crisp@ietf.org; Thu, 17 Feb 2005 18:04:56 -0500
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; Thu, 17 Feb 2005 17:42:38 -0500
	id 00207834.42151DDE.0000377D
In-Reply-To: <42151BFB.4010900@ar.com>
References: <20050215121201.P40811@shell-ng.nominum.com>	<p06210205be3854c35e39@[24.23.128.154]>
	<4213346B.9050604@ripe.net>	<p06210202be39203c0eed@[24.23.128.154]>
	<42147595.4030203@ripe.net>
	<1a430b65bdeceda79b33937bf7fe9ed6@hxr.us> <42151BFB.4010900@ar.com>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <033d7a606a9140067439840ef330627b@hxr.us>
Content-Transfer-Encoding: 7bit
From: Andrew Newton <andy@hxr.us>
Subject: Re: [Crisp] Working Group Last Call on AREG docs
Date: Thu, 17 Feb 2005 17:42:36 -0500
To: Rick Wesson <wessorh@ar.com>
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: 7bit
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit


On Feb 17, 2005, at 5:34 PM, Rick Wesson wrote:

> is my logic flawed? any education would be much appreciated.

I think it is simply that none of the RIRs have their databases modeled 
that way.  The addresses are with the organization, not the contact.

-andy


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


From crisp-bounces@ietf.org  Thu Feb 17 19:57:44 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 TAA03763
	for <crisp-web-archive@ietf.org>; Thu, 17 Feb 2005 19:57:44 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D1woO-00078u-51
	for crisp-web-archive@ietf.org; Thu, 17 Feb 2005 20:20:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D1w8a-0005wB-DA; Thu, 17 Feb 2005 19:36:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D1vnm-0007EK-5R
	for crisp@megatron.ietf.org; Thu, 17 Feb 2005 19:15:22 -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 TAA29392
	for <crisp@ietf.org>; Thu, 17 Feb 2005 19:15:19 -0500 (EST)
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1w9J-0005lK-Jt
	for crisp@ietf.org; Thu, 17 Feb 2005 19:37:39 -0500
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by ithilien.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id
	j1I0EfeD011360; Thu, 17 Feb 2005 16:14:41 -0800 (PST)
Received: from [24.23.128.154] (vpn-10-50-0-72.qualcomm.com [10.50.0.72])
	by crowley.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id
	j1I0EaBf006018; Thu, 17 Feb 2005 16:14:38 -0800 (PST)
Mime-Version: 1.0
Message-Id: <p06210209be3ae16cf384@[24.23.128.154]>
In-Reply-To: <42147595.4030203@ripe.net>
References: <20050215121201.P40811@shell-ng.nominum.com>
	<p06210205be3854c35e39@[24.23.128.154]> <4213346B.9050604@ripe.net>
	<p06210202be39203c0eed@[24.23.128.154]> <42147595.4030203@ripe.net>
Date: Thu, 17 Feb 2005 16:14:35 -0800
To: Shane Kerr <shane@ripe.net>
From: Ted Hardie <hardie@qualcomm.com>
Subject: Re: [Crisp] Working Group Last Call on AREG docs
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-PMX-Version: 4.7.0.111621
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f

At 11:44 AM +0100 2/17/05, Shane Kerr wrote:
>I guess my question is:
>
>- How does someone attempting to write a client know where to start looking?

And I guess this is the disconnect.  Why is this done at client write time,
rather than at client configuration time?

>A more general question is:
>
>- In IRIS, where do I start my resolution process?
>
>In IRIS, the answer is: at the top.

I guess that this is also a question for me.  Given the referral
mechanism, does it have to be "the top", or can it be anyone
willing to give you a referral?  For data which relates to
a hierarchy, starting at the top of the hierarchy ensures
that the person you're talking to knows at least how to
give the referral to the next level.  For data which is not
inherently hierarchical, is this still true?  Right now,
if I understand it correctly, if I ask ARIN about something
that is undelegated, it sends me to IANA; if I ask about
something delegated to RIPE, it sends me to RIPE.
If we don't enshrine iris.nro.net in the document, could
the RIRs not operationally decide whether they would
refer to each other directly or via iris.nro.net?

Again, just another bozo thinking about the problem,
			regards,
				Ted


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


From crisp-bounces@ietf.org  Fri Feb 18 04:34: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 EAA09913
	for <crisp-web-archive@ietf.org>; Fri, 18 Feb 2005 04:34:57 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D24sz-0002a6-0O
	for crisp-web-archive@ietf.org; Fri, 18 Feb 2005 04:57:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D24UI-0006Hd-OA; Fri, 18 Feb 2005 04:31:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D24P3-0003a6-3X
	for crisp@megatron.ietf.org; Fri, 18 Feb 2005 04:26:25 -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 EAA09030
	for <crisp@ietf.org>; Fri, 18 Feb 2005 04:26:23 -0500 (EST)
Received: from postman.ripe.net ([193.0.0.199])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D24kf-0002Km-AI
	for crisp@ietf.org; Fri, 18 Feb 2005 04:48:46 -0500
Received: by postman.ripe.net (Postfix, from userid 8)
	id AF57126ABE; Fri, 18 Feb 2005 10:25:52 +0100 (CET)
Received: from birch.ripe.net (birch.ripe.net [193.0.1.96])
	by postman.ripe.net (Postfix) with ESMTP
	id C6DD826AB3; Fri, 18 Feb 2005 10:25:51 +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 j1I9Ppet022790;
	Fri, 18 Feb 2005 10:25:51 +0100
Received: (from engin@localhost)
	by x47.ripe.net (8.12.10/8.12.6) id j1I9PpDa030339;
	Fri, 18 Feb 2005 10:25:51 +0100
Date: Fri, 18 Feb 2005 10:25:51 +0100
From: Engin Gunduz <engin@ripe.net>
To: Ted Hardie <hardie@qualcomm.com>
Subject: Re: [Crisp] Working Group Last Call on AREG docs
Message-ID: <20050218092551.GB29677@x47.ripe.net>
References: <20050215121201.P40811@shell-ng.nominum.com>
	<p06210205be3854c35e39@[24.23.128.154]> <4213346B.9050604@ripe.net>
	<p06210202be39203c0eed@[24.23.128.154]> <42147595.4030203@ripe.net>
	<p06210209be3ae16cf384@[24.23.128.154]>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-9
Content-Disposition: inline
In-Reply-To: <p06210209be3ae16cf384@[24.23.128.154]>
User-Agent: Mutt/1.4.2.1i
X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00
X-RIPE-Spam-Status: N 0.000000 / -5.9
X-RIPE-Signature: f90ce38b878486615f2befb9f40333b3
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: Shane Kerr <shane@ripe.net>, 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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0

On 2005-02-17 16:14:35 -0800, Ted Hardie wrote:
> At 11:44 AM +0100 2/17/05, Shane Kerr wrote:
> >I guess my question is:
> >
> >- How does someone attempting to write a client know where to start 
> >looking?
> 
> And I guess this is the disconnect.  Why is this done at client write time,
> rather than at client configuration time?
> 
> >A more general question is:
> >
> >- In IRIS, where do I start my resolution process?
> >
> >In IRIS, the answer is: at the top.
> 
> I guess that this is also a question for me.  Given the referral
> mechanism, does it have to be "the top", or can it be anyone
> willing to give you a referral?  For data which relates to
> a hierarchy, starting at the top of the hierarchy ensures
> that the person you're talking to knows at least how to
> give the referral to the next level.  For data which is not
> inherently hierarchical, is this still true?  Right now,
> if I understand it correctly, if I ask ARIN about something
> that is undelegated, it sends me to IANA; if I ask about
> something delegated to RIPE, it sends me to RIPE.
> If we don't enshrine iris.nro.net in the document, could
> the RIRs not operationally decide whether they would
> refer to each other directly or via iris.nro.net?

Why not.  But when the RIRs do not send the clients to IANA
and start sending them to each other, there is likely to be data 
synchronisation problems (each RIR must have an up-to-date
allocation map, otherwise the path that client will take will
be longer than required).

For the document: I think the idea was that, we needed something simple
to start with, and when have more experience with referral mechanism,
we can come up with a refined document.
-engin

> Again, just another bozo thinking about the problem,
> 			regards,
> 				Ted
> 
> 
> _______________________________________________
> Crisp mailing list
> Crisp@ietf.org
> https://www1.ietf.org/mailman/listinfo/crisp

-- 
Engin Gunduz
RIPE NCC Software Engineering Department


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


From crisp-bounces@ietf.org  Fri Feb 18 07:22:40 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 HAA24611
	for <crisp-web-archive@ietf.org>; Fri, 18 Feb 2005 07:22:40 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D27VK-0006Z2-3t
	for crisp-web-archive@ietf.org; Fri, 18 Feb 2005 07:45:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D278b-0001dR-HU; Fri, 18 Feb 2005 07:21:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D275P-0000ZU-2x
	for crisp@megatron.ietf.org; Fri, 18 Feb 2005 07:18:19 -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 HAA24312
	for <crisp@ietf.org>; Fri, 18 Feb 2005 07:18:16 -0500 (EST)
Received: from falcon.verisign.com ([216.168.239.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D27R3-0006UK-1U
	for crisp@ietf.org; Fri, 18 Feb 2005 07:40:42 -0500
Received: from dul1wnexcn02.vcorp.ad.vrsn.com (dul1wnexcn02.vcorp.ad.vrsn.com
	[10.170.12.139])
	by falcon.verisign.com (8.12.10/8.12.10) with ESMTP id j1ICCVop026387; 
	Fri, 18 Feb 2005 07:12:31 -0500 (EST)
Received: from dul1wnexmb01.vcorp.ad.vrsn.com ([10.170.12.134]) by
	dul1wnexcn02.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 18 Feb 2005 07:17:46 -0500
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Subject: RE: [Crisp] Working Group Last Call on AREG docs
Date: Fri, 18 Feb 2005 07:17:45 -0500
Message-ID: <046F43A8D79C794FA4733814869CDF07327F67@dul1wnexmb01.vcorp.ad.vrsn.com>
Thread-Topic: [Crisp] Working Group Last Call on AREG docs
Thread-Index: AcUVnSKX9mkUnpqsQHunFA3rEC7wdQAFj6tQ
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "Engin Gunduz" <engin@ripe.net>
X-OriginalArrivalTime: 18 Feb 2005 12:17:46.0682 (UTC)
	FILETIME=[DAF621A0:01C515B3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: quoted-printable

> For the document: I think the idea was that, we needed=20
> something simple
> to start with, and when have more experience with referral mechanism,
> we can come up with a refined document.

One of the issues with this approach is that the early "simple"
implementations tend to be very difficult to dislodge once they've been
deployed.  "start with" often ends up being "live with for a long time".

-Scott-

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


From crisp-bounces@ietf.org  Fri Feb 18 08:13:51 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 IAA29103
	for <crisp-web-archive@ietf.org>; Fri, 18 Feb 2005 08:13:51 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D28Io-0007rx-Gv
	for crisp-web-archive@ietf.org; Fri, 18 Feb 2005 08:36:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D27ss-0007uU-QP; Fri, 18 Feb 2005 08:09:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D27nD-0005iJ-4T
	for crisp@megatron.ietf.org; Fri, 18 Feb 2005 08:03:35 -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 IAA27733
	for <crisp@ietf.org>; Fri, 18 Feb 2005 08:03:34 -0500 (EST)
Received: from [64.151.105.12] (helo=zak.ecotroph.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D288r-0007XS-Fl
	for crisp@ietf.org; Fri, 18 Feb 2005 08:25:58 -0500
Received: from [10.0.1.4] ([::ffff:64.83.8.178])
	(AUTH: PLAIN anewton, SSL: TLSv1/SSLv3,128bits,RC4-SHA)
	by zak.ecotroph.net with esmtp; Fri, 18 Feb 2005 08:03:31 -0500
	id 0020784C.4215E7A4.0000210A
In-Reply-To: <046F43A8D79C794FA4733814869CDF07327F67@dul1wnexmb01.vcorp.ad.vrsn.com>
References: <046F43A8D79C794FA4733814869CDF07327F67@dul1wnexmb01.vcorp.ad.vrsn.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <79F5DF7E-81AD-11D9-B82D-000A95B3BA44@hxr.us>
Content-Transfer-Encoding: 7bit
From: Andrew Newton <andy@hxr.us>
Subject: Re: [Crisp] Working Group Last Call on AREG docs
Date: Fri, 18 Feb 2005 08:03:25 -0500
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Cc: CRISP WG <crisp@ietf.org>, Engin Gunduz <engin@ripe.net>
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: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit


On Feb 18, 2005, at 7:17 AM, Hollenbeck, Scott wrote:

>> For the document: I think the idea was that, we needed
>> something simple
>> to start with, and when have more experience with referral mechanism,
>> we can come up with a refined document.
>
> One of the issues with this approach is that the early "simple"
> implementations tend to be very difficult to dislodge once they've been
> deployed.

And ones that are overly complex tend to never be deployed.

We have been looking at this for sometime now and have not found 
anything more palatable.

-andy


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


From crisp-bounces@ietf.org  Fri Feb 18 08:36:01 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 IAA01479
	for <crisp-web-archive@ietf.org>; Fri, 18 Feb 2005 08:36:01 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D28eE-0008U4-AE
	for crisp-web-archive@ietf.org; Fri, 18 Feb 2005 08:58:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D28Ar-0005Il-Qt; Fri, 18 Feb 2005 08:28:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D281F-0002Iu-Sm
	for crisp@megatron.ietf.org; Fri, 18 Feb 2005 08:18:05 -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 IAA29488
	for <crisp@ietf.org>; Fri, 18 Feb 2005 08:18:04 -0500 (EST)
Received: from eagle.verisign.com ([216.168.239.70])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D28Mu-0007xi-96
	for crisp@ietf.org; Fri, 18 Feb 2005 08:40:29 -0500
Received: from dul1wnexcn02.vcorp.ad.vrsn.com (dul1wnexcn02.vcorp.ad.vrsn.com
	[10.170.12.139])
	by eagle.verisign.com (8.12.10/8.12.10) with ESMTP id j1ID9iYo009574;
	Fri, 18 Feb 2005 08:09:44 -0500 (EST)
Received: from dul1wnexmb01.vcorp.ad.vrsn.com ([10.170.12.134]) by
	dul1wnexcn02.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 18 Feb 2005 08:17:32 -0500
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Subject: RE: [Crisp] Working Group Last Call on AREG docs
Date: Fri, 18 Feb 2005 08:17:31 -0500
Message-ID: <046F43A8D79C794FA4733814869CDF07327F68@dul1wnexmb01.vcorp.ad.vrsn.com>
Thread-Topic: [Crisp] Working Group Last Call on AREG docs
Thread-Index: AcUVukJK2wLGncaqTSu1lCouaywvuQAAF+EQ
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "Andrew Newton" <andy@hxr.us>
X-OriginalArrivalTime: 18 Feb 2005 13:17:32.0746 (UTC)
	FILETIME=[346C12A0:01C515BC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: quoted-printable

> >> For the document: I think the idea was that, we needed
> >> something simple
> >> to start with, and when have more experience with referral=20
> mechanism,
> >> we can come up with a refined document.
> >
> > One of the issues with this approach is that the early "simple"
> > implementations tend to be very difficult to dislodge once=20
> they've been
> > deployed.
>=20
> And ones that are overly complex tend to never be deployed.
>=20
> We have been looking at this for sometime now and have not found=20
> anything more palatable.

You made quite a leap from "simple" to "overly complex".  I won't
disagree with your assessment, but it only makes sense if the only
options available are "simple" and "overly complex".

Could you help me understand why anything other than a hard-wired server
name falls into the category of "overly complex"?  There's no text in
the document to describe the situation as far as I can tell.  I didn't
see anything other than this:

"The client SHOULD start every query from the IRIS server iris.nro.net
and follow the referrals to find the authoritative server to actually
query."

Justification would be helpful.  Given the very complete description of
referrals in other IRIS documents, the lack of text explaining why a
referral won't work here is somewhat mystifying to me.

-Scott-

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


From crisp-bounces@ietf.org  Fri Feb 18 09:52:18 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 JAA08993
	for <crisp-web-archive@ietf.org>; Fri, 18 Feb 2005 09:52:18 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D29q7-0002A9-M6
	for crisp-web-archive@ietf.org; Fri, 18 Feb 2005 10:14:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D29I4-0006I9-8C; Fri, 18 Feb 2005 09:39:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D298z-0002LL-Nq
	for crisp@megatron.ietf.org; Fri, 18 Feb 2005 09:30:09 -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 JAA06328
	for <crisp@ietf.org>; Fri, 18 Feb 2005 09:30:08 -0500 (EST)
Received: from postman.ripe.net ([193.0.0.199])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D29Uf-0001QC-BW
	for crisp@ietf.org; Fri, 18 Feb 2005 09:52:33 -0500
Received: by postman.ripe.net (Postfix, from userid 8)
	id 2701426B7E; Fri, 18 Feb 2005 15:29:38 +0100 (CET)
Received: from birch.ripe.net (birch.ripe.net [193.0.1.96])
	by postman.ripe.net (Postfix) with ESMTP
	id 3105726AAF; Fri, 18 Feb 2005 15:29:37 +0100 (CET)
Received: from [193.0.1.17] (x17.ripe.net [193.0.1.17])
	by birch.ripe.net (8.12.10/8.11.6) with ESMTP id j1IETaet010611;
	Fri, 18 Feb 2005 15:29:37 +0100
Message-ID: <4215FBD0.5030709@ripe.net>
Date: Fri, 18 Feb 2005 15:29:36 +0100
From: Shane Kerr <shane@ripe.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913
X-Accept-Language: en, nl
MIME-Version: 1.0
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>
Subject: Re: [Crisp] Working Group Last Call on AREG docs
References: <046F43A8D79C794FA4733814869CDF07327F68@dul1wnexmb01.vcorp.ad.vrsn.com>
In-Reply-To: <046F43A8D79C794FA4733814869CDF07327F68@dul1wnexmb01.vcorp.ad.vrsn.com>
X-Enigmail-Version: 0.90.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00
X-RIPE-Spam-Status: N 0.000000 / -5.9
X-RIPE-Signature: bbfee4492b97ced1f3e5a24e472cf25c
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: 7bit
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: 7bit

Hollenbeck, Scott wrote:
>>>>For the document: I think the idea was that, we needed
>>>>something simple
>>>>to start with, and when have more experience with referral 
>>
>>mechanism,
>>
>>>>we can come up with a refined document.
>>>
>>>One of the issues with this approach is that the early "simple"
>>>implementations tend to be very difficult to dislodge once 
>>
>>they've been
>>
>>>deployed.
>>
>>And ones that are overly complex tend to never be deployed.
>>
>>We have been looking at this for sometime now and have not found 
>>anything more palatable.
> 
> 
> You made quite a leap from "simple" to "overly complex".  I won't
> disagree with your assessment, but it only makes sense if the only
> options available are "simple" and "overly complex".
> 
> Could you help me understand why anything other than a hard-wired server
> name falls into the category of "overly complex"?  There's no text in
> the document to describe the situation as far as I can tell.  I didn't
> see anything other than this:
> 
> "The client SHOULD start every query from the IRIS server iris.nro.net
> and follow the referrals to find the authoritative server to actually
> query."
> 
> Justification would be helpful.  Given the very complete description of
> referrals in other IRIS documents, the lack of text explaining why a
> referral won't work here is somewhat mystifying to me.

I don't understand. A referral from where? I'm not trying to be sarcastic or 
anything, but the only option I see other than telling coders where to start 
their referral process is not to tell them anything.

Perhaps:

"Users SHOULD use http://www.google.com/ to search for an appropriate web 
page with information about what IRIS server to configure for AREG server 
location."

Okay, maybe I'm being a little sarcastic now. ;)

-- 
Shane Kerr
RIPE NCC

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


From crisp-bounces@ietf.org  Fri Feb 18 09:53:34 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 JAA09248
	for <crisp-web-archive@ietf.org>; Fri, 18 Feb 2005 09:53:34 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D29rM-0002Dv-2F
	for crisp-web-archive@ietf.org; Fri, 18 Feb 2005 10:16:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D29Ip-0006NW-RX; Fri, 18 Feb 2005 09:40:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D29Ak-00038h-Jj
	for crisp@megatron.ietf.org; Fri, 18 Feb 2005 09:31:58 -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 JAA06549
	for <crisp@ietf.org>; Fri, 18 Feb 2005 09:31:57 -0500 (EST)
Received: from clone.registro.br ([200.160.2.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D29WQ-0001UJ-7g
	for crisp@ietf.org; Fri, 18 Feb 2005 09:54:22 -0500
Received: by clone.registro.br (Postfix, from userid 1000)
	id EE31C2A467; Fri, 18 Feb 2005 12:31:21 -0200 (BRST)
Date: Fri, 18 Feb 2005 12:31:21 -0200
From: Frederico A C Neves <fneves@registro.br>
To: CRISP WG <crisp@ietf.org>
Subject: Re: [Crisp] Working Group Last Call on AREG docs
Message-ID: <20050218143121.GG42119@registro.br>
References: <20050215121201.P40811@shell-ng.nominum.com>
	<p06210205be3854c35e39@[24.23.128.154]> <4213346B.9050604@ripe.net>
	<p06210202be39203c0eed@[24.23.128.154]> <42147595.4030203@ripe.net>
	<1a430b65bdeceda79b33937bf7fe9ed6@hxr.us> <42151BFB.4010900@ar.com>
	<033d7a606a9140067439840ef330627b@hxr.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <033d7a606a9140067439840ef330627b@hxr.us>
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
Content-Transfer-Encoding: quoted-printable
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: b2809b6f39decc6de467dcf252f42af1
Content-Transfer-Encoding: quoted-printable

On Thu, Feb 17, 2005 at 05:42:36PM -0500, Andrew Newton wrote:
>=20
> On Feb 17, 2005, at 5:34 PM, Rick Wesson wrote:
>=20
> >is my logic flawed? any education would be much appreciated.
>=20
> I think it is simply that none of the RIRs have their databases modeled=
=20
> that way.  The addresses are with the organization, not the contact.
>=20

Ops... if this is true (I'll check the draft) we have a problem.

The RIRs actually have a mixed contact/Address model,

RIPE+APNIC only have contacts with their respective addresses, what
they don't have is actually the organization [1]. Sometimes they use
the "descr" attribute on the inetnum obj to embed addresses [2].

ARIN+LACNIC have contacts with their respective addresses, and
organization, with address too. [3]

The protocol should support both models with the use of optional
objects.

Fred

[1]
 > whois -h whois.ripe.net 193.0.0.193
 ...
 inetnum:      193.0.0.0 - 193.0.7.255
 netname:      RIPE-NCC
 descr:        RIPE Network Coordination Centre
 descr:        Amsterdam, Netherlands
 remarks:      Used for RIPE NCC infrastructure.
 country:      NL
 admin-c:      AMR68-RIPE
 admin-c:      RDK-RIPE
 tech-c:       OPS4-RIPE
 status:       ASSIGNED PI
 mnt-by:       RIPE-NCC-MNT
 mnt-lower:    RIPE-NCC-MNT
 changed:      mally@ripe.net 20030522
 source:       RIPE
 ...
 person:       Andrei M. Robachevsky
 address:      RIPE Network Coordination Centre (NCC)
 address:      Singel 258
 address:      NL-1016 AB Amsterdam
 address:      Netherlands
 phone:        +31-20-535-4444
 fax-no:       +31-20-535-4445
 e-mail:       xxxx@xxxx.xxx
 nic-hdl:      AMR68-RIPE
 mnt-by:       RIPE-NCC-MNT
 changed:      xxxx@xxxx.xxx 20001016
 source:       RIPE
 ... =20


[2]
 > whois -h whois.apnic.net 202.12.29.20
 ...
 inetnum:      202.12.28.0 - 202.12.29.255
 netname:      APNIC-AP
 descr:        Asia Pacific Network Information Center, Pty. Ltd.
 descr:        Level 1 - 33 Park Road.
 descr:        Milton QLD 4064
 descr:        Australia
 country:      AU
 admin-c:      AIC1-AP
 tech-c:       NO4-AP
 mnt-by:       APNIC-HM
 changed:      technical@apnic.net 19980918
 status:       ASSIGNED PORTABLE
 source:       APNIC
 ...
 person:       APNIC Network Operations
 address:      Level 1
 address:      33 Park Road
 address:      Milton QLD 4064
 country:      AU
 phone:        +61 7 3858 3100
 fax-no:       +61 7 3858 3199
 e-mail:       technical@apnic.net
 nic-hdl:      NO4-AP
 remarks:      Administrator for APNIC Network Operations
 notify:       dbmon@apnic.net
 mnt-by:       MAINT-APNIC-AP
 changed:      technical@apnic.net 19981111
 changed:      hostmaster@apnic.net 20020211
 source:       APNIC


[3]
 > whois -h whois.lacnic.net 200.160.0.0
 ...
 inetnum:     200.128/9
 status:      allocated
 owner:       Comite Gestor da Internet no Brasil
 ownerid:     BR-CGIN-LACNIC
 responsible: Frederico A C Neves
 address:     Av. das Na=E7=F5es Unidas, 11541, 7=B0 andar
 address:     04578-000 - S=E3o Paulo - SP
 country:     BR
 phone:       +55 11 9119-0304 []
 owner-c:     CGB
 tech-c:      CGB
 inetrev:     200.128/9
 nserver:     A.DNS.BR
 nsstat:      20050217 AA
 nslastaa:    20050217
 ...
 nic-hdl:     CGB
 person:      Comite Gestor da Internet no Brasil
 e-mail:      blkadm@NIC.BR
 address:     Av. das Na=E7=F5es Unidas, 11541, 7=B0 andar
 address:     04578-000 - S=E3o Paulo - SP
 country:     BR
 phone:       +55 19 9119-0304 []
 created:     20020902
 changed:     20020902
 ...

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


From crisp-bounces@ietf.org  Fri Feb 18 09:59:33 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 JAA10268
	for <crisp-web-archive@ietf.org>; Fri, 18 Feb 2005 09:59:33 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D29x8-0002T9-Eo
	for crisp-web-archive@ietf.org; Fri, 18 Feb 2005 10:21:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D29aP-0004wR-PQ; Fri, 18 Feb 2005 09:58:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D29NO-0008Ue-Ls
	for crisp@megatron.ietf.org; Fri, 18 Feb 2005 09:45:02 -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 JAA07933
	for <crisp@ietf.org>; Fri, 18 Feb 2005 09:45:01 -0500 (EST)
Received: from eagle.verisign.com ([216.168.239.70])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D29j1-0001qK-VG
	for crisp@ietf.org; Fri, 18 Feb 2005 10:07:27 -0500
Received: from dul1wnexcn02.vcorp.ad.vrsn.com (dul1wnexcn02.vcorp.ad.vrsn.com
	[10.170.12.139])
	by eagle.verisign.com (8.12.10/8.12.10) with ESMTP id j1IEadYo012972;
	Fri, 18 Feb 2005 09:36:39 -0500 (EST)
Received: from dul1wnexmb01.vcorp.ad.vrsn.com ([10.170.12.134]) by
	dul1wnexcn02.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 18 Feb 2005 09:44:27 -0500
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Subject: RE: [Crisp] Working Group Last Call on AREG docs
Date: Fri, 18 Feb 2005 09:44:26 -0500
Message-ID: <046F43A8D79C794FA4733814869CDF07327F6B@dul1wnexmb01.vcorp.ad.vrsn.com>
Thread-Topic: [Crisp] Working Group Last Call on AREG docs
Thread-Index: AcUVxkn6eensOdKhTXWoWzX8ZLwrGwAAK62A
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "Shane Kerr" <shane@ripe.net>
X-OriginalArrivalTime: 18 Feb 2005 14:44:27.0738 (UTC)
	FILETIME=[58CCB3A0:01C515C8]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: quoted-printable

> I don't understand. A referral from where? I'm not trying to=20
> be sarcastic or=20
> anything, but the only option I see other than telling coders=20
> where to start=20
> their referral process is not to tell them anything.

How about whatever "nearby" IRIS AREG server they happen to know about?

My point in suggesting that more text is needed is that the AREG
document says nothing about why AREG resolution differs from the
resolution process described in other documents.  Why are the AREG and
DREG situations different?  DREG includes a very detailed description of
the resolution process in section 6.  AREG includes two sentences.  If
there is a reason that one must start with a specific server the
document really ought to explain why that's the case.

BTW, the document currently says that one "SHOULD start every query from
the IRIS server iris.nro.net".  So what happens if the client doesn't?

-Scott-

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


From crisp-bounces@ietf.org  Fri Feb 18 10:29: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 KAA15946
	for <crisp-web-archive@ietf.org>; Fri, 18 Feb 2005 10:29:24 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D2AQ1-0003aJ-Fy
	for crisp-web-archive@ietf.org; Fri, 18 Feb 2005 10:51:50 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D29rw-0004QK-6F; Fri, 18 Feb 2005 10:16:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D29cR-0006Wd-Fs
	for crisp@megatron.ietf.org; Fri, 18 Feb 2005 10:00:35 -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 KAA10469
	for <crisp@ietf.org>; Fri, 18 Feb 2005 10:00:33 -0500 (EST)
Received: from smtp2.arin.net ([192.149.252.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D29y6-0002V7-EW
	for crisp@ietf.org; Fri, 18 Feb 2005 10:22:59 -0500
Received: by smtp2.arin.net (Postfix, from userid 5003)
	id 8254014461B; Fri, 18 Feb 2005 10:00:25 -0500 (EST)
Received: from mercury.arin.net (mercury.arin.net [192.149.252.131])
	by smtp2.arin.net (Postfix) with ESMTP id F1FBA144619
	for <crisp@ietf.org>; Fri, 18 Feb 2005 10:00:24 -0500 (EST)
Received: from caesium (caesium.arin.net [192.136.136.36])
	by mercury.arin.net (Postfix) with ESMTP id EC7B11FECE
	for <crisp@ietf.org>; Fri, 18 Feb 2005 10:00:24 -0500 (EST)
From: "Tim Christensen" <timc@arin.net>
To: "'CRISP WG'" <crisp@ietf.org>
Subject: RE: [Crisp] Working Group Last Call on AREG docs
Date: Fri, 18 Feb 2005 10:00:18 -0500
Message-ID: <000901c515ca$928453d0$248888c0@arin.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
In-Reply-To: <20050218143121.GG42119@registro.br>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Importance: Normal
X-Spam-Checker-Version: SpamAssassin 2.63-arin1 (2004-01-11) on smtp2.arin.net
X-Spam-Status: No, hits=-6.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=2.63-arin1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit



> -----Original Message-----
> From: crisp-bounces@ietf.org [mailto:crisp-bounces@ietf.org] 
> On Behalf Of Frederico A C Neves
> Subject: Re: [Crisp] Working Group Last Call on AREG docs
> 
> On Thu, Feb 17, 2005 at 05:42:36PM -0500, Andrew Newton wrote:
> > 
> > On Feb 17, 2005, at 5:34 PM, Rick Wesson wrote:
> > 
> > >is my logic flawed? any education would be much appreciated.
> > 
> > I think it is simply that none of the RIRs have their databases 
> > modeled
> > that way.  The addresses are with the organization, not the contact.
> > 
> 
> Ops... if this is true (I'll check the draft) we have a problem.
> 
> The RIRs actually have a mixed contact/Address model,
> 
> RIPE+APNIC only have contacts with their respective addresses, what
> they don't have is actually the organization [1]. Sometimes 
> they use the "descr" attribute on the inetnum obj to embed 
> addresses [2].
> 
> ARIN+LACNIC have contacts with their respective addresses, and
> organization, with address too. [3]

Correct, ARIN associates addresses with both organizations and with
contacts.

> The protocol should support both models with the use of 
> optional objects.

Agreed.  As I mentioned briefly to Andy late last night I'll go check the
draft too.

Tim



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


From crisp-bounces@ietf.org  Fri Feb 18 11:02:56 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 LAA24899
	for <crisp-web-archive@ietf.org>; Fri, 18 Feb 2005 11:02:55 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D2AwU-0006NQ-I2
	for crisp-web-archive@ietf.org; Fri, 18 Feb 2005 11:25:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D29sV-0004ep-RW; Fri, 18 Feb 2005 10:17:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D29gM-00080o-H9
	for crisp@megatron.ietf.org; Fri, 18 Feb 2005 10:04: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 KAA11183
	for <crisp@ietf.org>; Fri, 18 Feb 2005 10:04:36 -0500 (EST)
Received: from [64.151.105.12] (helo=zak.ecotroph.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2A21-0002fI-RC
	for crisp@ietf.org; Fri, 18 Feb 2005 10:27:03 -0500
Received: from [10.0.1.3] ([::ffff:64.83.8.178])
	(AUTH: PLAIN anewton, SSL: TLSv1/SSLv3,128bits,RC4-SHA)
	by zak.ecotroph.net with esmtp; Fri, 18 Feb 2005 10:04:32 -0500
	id 0020783F.42160400.00002F11
In-Reply-To: <046F43A8D79C794FA4733814869CDF07327F68@dul1wnexmb01.vcorp.ad.vrsn.com>
References: <046F43A8D79C794FA4733814869CDF07327F68@dul1wnexmb01.vcorp.ad.vrsn.com>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <c77e69452d040f86373f26b9a910b982@hxr.us>
Content-Transfer-Encoding: 7bit
From: Andrew Newton <andy@hxr.us>
Subject: Re: [Crisp] Working Group Last Call on AREG docs
Date: Fri, 18 Feb 2005 10:04:30 -0500
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit


On Feb 18, 2005, at 8:17 AM, Hollenbeck, Scott wrote:

> You made quite a leap from "simple" to "overly complex".  I won't
> disagree with your assessment, but it only makes sense if the only
> options available are "simple" and "overly complex".

Sorry.  One day I will learn not to write email before my first morning 
coffee.

> Could you help me understand why anything other than a hard-wired 
> server
> name falls into the category of "overly complex"?  There's no text in
> the document to describe the situation as far as I can tell.  I didn't
> see anything other than this:

First, I agree that it should be a configurable default, not 
hard-wired.  I believe this is almost what Ted was saying (he just said 
"configurable", I say "configurable default").

> "The client SHOULD start every query from the IRIS server iris.nro.net
> and follow the referrals to find the authoritative server to actually
> query."
>
> Justification would be helpful.  Given the very complete description of
> referrals in other IRIS documents, the lack of text explaining why a
> referral won't work here is somewhat mystifying to me.

First, the well-known top still uses referrals (its not a centralized 
DB).  But what you are suggesting is a highly, coordinated referral 
mesh, which to me seems like overkill at the moment.  Additionally, it 
still does not solve the exact problem of "where do I start?".  Having 
software implementors and users assume an entry point seems to be the 
same problem only spread out over a larger number of nodes.

-andy


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


From crisp-bounces@ietf.org  Fri Feb 18 11:18: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 LAA29383
	for <crisp-web-archive@ietf.org>; Fri, 18 Feb 2005 11:18:48 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D2BBq-0007sM-U6
	for crisp-web-archive@ietf.org; Fri, 18 Feb 2005 11:41:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D29sr-0005GA-Pf; Fri, 18 Feb 2005 10:17:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D29ip-0000GB-Ch
	for crisp@megatron.ietf.org; Fri, 18 Feb 2005 10:07:11 -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 KAA11798
	for <crisp@ietf.org>; Fri, 18 Feb 2005 10:07:09 -0500 (EST)
Received: from postman.ripe.net ([193.0.0.199])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2A4V-0002jx-LL
	for crisp@ietf.org; Fri, 18 Feb 2005 10:29:36 -0500
Received: by postman.ripe.net (Postfix, from userid 8)
	id 2F82626CAA; Fri, 18 Feb 2005 16:06:32 +0100 (CET)
Received: from birch.ripe.net (birch.ripe.net [193.0.1.96])
	by postman.ripe.net (Postfix) with ESMTP
	id 4D7B626CAE; Fri, 18 Feb 2005 16:06:31 +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 j1IF6Vet023066;
	Fri, 18 Feb 2005 16:06:31 +0100
Received: (from engin@localhost)
	by x47.ripe.net (8.12.10/8.12.6) id j1IF6V0l030653;
	Fri, 18 Feb 2005 16:06:31 +0100
Date: Fri, 18 Feb 2005 16:06:31 +0100
From: Engin Gunduz <engin@ripe.net>
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>
Subject: Re: [Crisp] Working Group Last Call on AREG docs
Message-ID: <20050218150630.GD25988@x47.ripe.net>
References: <046F43A8D79C794FA4733814869CDF07327F68@dul1wnexmb01.vcorp.ad.vrsn.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-9
Content-Disposition: inline
In-Reply-To: <046F43A8D79C794FA4733814869CDF07327F68@dul1wnexmb01.vcorp.ad.vrsn.com>
User-Agent: Mutt/1.4.2.1i
X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00
X-RIPE-Spam-Status: N 0.000002 / -5.9
X-RIPE-Signature: c3d5eccfb62d94fd185fa86f78f2a3b7
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: CRISP WG <crisp@ietf.org>, Andrew Newton <andy@hxr.us>
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: 52f7a77164458f8c7b36b66787c853da

On 2005-02-18 08:17:31 -0500, Hollenbeck, Scott wrote:
> > >> For the document: I think the idea was that, we needed
> > >> something simple
> > >> to start with, and when have more experience with referral 
> > mechanism,
> > >> we can come up with a refined document.
> > >
> > > One of the issues with this approach is that the early "simple"
> > > implementations tend to be very difficult to dislodge once 
> > they've been
> > > deployed.
> > 
> > And ones that are overly complex tend to never be deployed.
> > 
> > We have been looking at this for sometime now and have not found 
> > anything more palatable.
> 
> You made quite a leap from "simple" to "overly complex".  I won't
> disagree with your assessment, but it only makes sense if the only
> options available are "simple" and "overly complex".
> 
> Could you help me understand why anything other than a hard-wired server
> name falls into the category of "overly complex"?  There's no text in
> the document to describe the situation as far as I can tell.  I didn't
> see anything other than this:
> 
> "The client SHOULD start every query from the IRIS server iris.nro.net
> and follow the referrals to find the authoritative server to actually
> query."
> 
> Justification would be helpful.  Given the very complete description of
> referrals in other IRIS documents, the lack of text explaining why a
> referral won't work here is somewhat mystifying to me.

The document does not say referral will not work.
Referral _will_ work. The problem is to figure out where to start from.

For DREG, the solution is to find the starting point from DNS records.
This is possible because there is a natural link between domain registration
data and DNS data.

Using DNS is problematic for AREG as there is no trivial link between
DNS data and address registration.  Yes, there is reverse DNS tree but
it is not trivial to find the starting point of referral in the
reverse DNS.  And reverse DNS can be useful only for IP address registration
data. For autonomous system numbers, there is nothing in the DNS
at all.

-engin

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

-- 
Engin Gunduz
RIPE NCC Software Engineering Department

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


From crisp-bounces@ietf.org  Fri Feb 18 11:24:14 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 LAA01155
	for <crisp-web-archive@ietf.org>; Fri, 18 Feb 2005 11:24:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D2BH6-0008Mq-PM
	for crisp-web-archive@ietf.org; Fri, 18 Feb 2005 11:46:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D29tq-0005Vm-Io; Fri, 18 Feb 2005 10:18:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D29qK-0003fB-Se
	for crisp@megatron.ietf.org; Fri, 18 Feb 2005 10:14:56 -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 KAA13775
	for <crisp@ietf.org>; Fri, 18 Feb 2005 10:14:55 -0500 (EST)
Received: from [64.151.105.12] (helo=zak.ecotroph.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2ABy-0003Am-BC
	for crisp@ietf.org; Fri, 18 Feb 2005 10:37:21 -0500
Received: from [10.0.1.3] ([::ffff:64.83.8.178])
	(AUTH: PLAIN anewton, SSL: TLSv1/SSLv3,128bits,RC4-SHA)
	by zak.ecotroph.net with esmtp; Fri, 18 Feb 2005 10:14:51 -0500
	id 0020783F.4216066C.0000306F
In-Reply-To: <20050218143121.GG42119@registro.br>
References: <20050215121201.P40811@shell-ng.nominum.com>
	<p06210205be3854c35e39@[24.23.128.154]> <4213346B.9050604@ripe.net>
	<p06210202be39203c0eed@[24.23.128.154]> <42147595.4030203@ripe.net>
	<1a430b65bdeceda79b33937bf7fe9ed6@hxr.us> <42151BFB.4010900@ar.com>
	<033d7a606a9140067439840ef330627b@hxr.us>
	<20050218143121.GG42119@registro.br>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <a17ef5b0f27ae5627c284d738d58657c@hxr.us>
Content-Transfer-Encoding: 7bit
From: Andrew Newton <andy@hxr.us>
Subject: Re: [Crisp] Working Group Last Call on AREG docs
Date: Fri, 18 Feb 2005 10:14:49 -0500
To: Frederico A C Neves <fneves@registro.br>
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit


On Feb 18, 2005, at 9:31 AM, Frederico A C Neves wrote:

> The protocol should support both models with the use of optional
> objects.

I think this is easily enough done in one of two ways:
1) just put the address elements in the contact result as optional 
(RIPE,APNIC will never use them, ARIN,LACNIC will never use the ones in 
the organization result-- I assume)
2) create a separate address result that each may refer to as a 
temporary reference (temporary on the assumption that there is no 
full-fledged address object in the DB).

#1 is slightly more work for clients, #2 is slightly more work for 
servers.  And I do mean slightly in both cases because neither is a big 
deal.

Personally, I like #2 because it seems more normalized, but I could go 
either way.

-andy


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


From crisp-bounces@ietf.org  Fri Feb 18 11:53: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 LAA06086
	for <crisp-web-archive@ietf.org>; Fri, 18 Feb 2005 11:53:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D2BjY-0001NS-W6
	for crisp-web-archive@ietf.org; Fri, 18 Feb 2005 12:16:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D2B1T-0001iV-HP; Fri, 18 Feb 2005 11:30:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D2AIZ-0006X2-1O
	for crisp@megatron.ietf.org; Fri, 18 Feb 2005 10:44:07 -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 KAA18944
	for <crisp@ietf.org>; Fri, 18 Feb 2005 10:44:05 -0500 (EST)
Received: from postman.ripe.net ([193.0.0.199])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2AeF-0004S6-C1
	for crisp@ietf.org; Fri, 18 Feb 2005 11:06:31 -0500
Received: by postman.ripe.net (Postfix, from userid 8)
	id 9B3DF26CCD; Fri, 18 Feb 2005 16:43:35 +0100 (CET)
Received: from birch.ripe.net (birch.ripe.net [193.0.1.96])
	by postman.ripe.net (Postfix) with ESMTP
	id D35AC26CC5; Fri, 18 Feb 2005 16:43:34 +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 j1IFhYet002385;
	Fri, 18 Feb 2005 16:43:34 +0100
Received: (from engin@localhost)
	by x47.ripe.net (8.12.10/8.12.6) id j1IFhYkI032000;
	Fri, 18 Feb 2005 16:43:34 +0100
Date: Fri, 18 Feb 2005 16:43:34 +0100
From: Engin Gunduz <engin@ripe.net>
To: Rick Wesson <wessorh@ar.com>
Subject: Re: [Crisp] Working Group Last Call on AREG docs
Message-ID: <20050218154334.GE25988@x47.ripe.net>
References: <20050215121201.P40811@shell-ng.nominum.com>
	<p06210205be3854c35e39@[24.23.128.154]> <4213346B.9050604@ripe.net>
	<p06210202be39203c0eed@[24.23.128.154]> <42147595.4030203@ripe.net>
	<1a430b65bdeceda79b33937bf7fe9ed6@hxr.us> <42151BFB.4010900@ar.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-9
Content-Disposition: inline
In-Reply-To: <42151BFB.4010900@ar.com>
User-Agent: Mutt/1.4.2.1i
X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00
X-RIPE-Spam-Status: N 0.136372 / -5.9
X-RIPE-Signature: dcc430c35b4dfae599667182b6e4e7d2
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: CRISP WG <crisp@ietf.org>, Andrew Newton <andy@hxr.us>
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: 93238566e09e6e262849b4f805833007

On 2005-02-17 14:34:35 -0800, Rick Wesson wrote:
> just a clarification question....
> 
> Why must contacts have their address associated with an organization, 
> there appears no capability to have a contact with any address 
> information of their own. 

This must be an oversight of mine. Contacts must have address field
indeed, like organisations.

Thanks for catching this...
-engin

> The slippry slope is that only number 
> deligations can be made to organizations.
> 
> is my logic flawed? any education would be much appreciated.
> 
> -rick

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


From crisp-bounces@ietf.org  Fri Feb 18 12:11:06 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 MAA08491
	for <crisp-web-archive@ietf.org>; Fri, 18 Feb 2005 12:11:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D2C0R-00026B-54
	for crisp-web-archive@ietf.org; Fri, 18 Feb 2005 12:33:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D2BFC-0001Ms-15; Fri, 18 Feb 2005 11:44:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D2Amf-0004Ck-HQ
	for crisp@megatron.ietf.org; Fri, 18 Feb 2005 11:15:13 -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 LAA28436
	for <crisp@ietf.org>; Fri, 18 Feb 2005 11:15:11 -0500 (EST)
Received: from clone.registro.br ([200.160.2.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2B8L-0007V5-6I
	for crisp@ietf.org; Fri, 18 Feb 2005 11:37:38 -0500
Received: by clone.registro.br (Postfix, from userid 1000)
	id 906E82A4E3; Fri, 18 Feb 2005 14:14:39 -0200 (BRST)
Date: Fri, 18 Feb 2005 14:14:39 -0200
From: Frederico A C Neves <fneves@registro.br>
To: CRISP WG <crisp@ietf.org>
Subject: Re: [Crisp] Working Group Last Call on AREG docs
Message-ID: <20050218161439.GJ42119@registro.br>
References: <046F43A8D79C794FA4733814869CDF07327F6B@dul1wnexmb01.vcorp.ad.vrsn.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <046F43A8D79C794FA4733814869CDF07327F6B@dul1wnexmb01.vcorp.ad.vrsn.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
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: 8b30eb7682a596edff707698f4a80f7d

On Fri, Feb 18, 2005 at 09:44:26AM -0500, Hollenbeck, Scott wrote:
> > I don't understand. A referral from where? I'm not trying to 
> > be sarcastic or 
> > anything, but the only option I see other than telling coders 
> > where to start 
> > their referral process is not to tell them anything.
> 
> How about whatever "nearby" IRIS AREG server they happen to know about?
> 
> My point in suggesting that more text is needed is that the AREG
> document says nothing about why AREG resolution differs from the
> resolution process described in other documents.  Why are the AREG and
> DREG situations different?  DREG includes a very detailed description of
> the resolution process in section 6.  AREG includes two sentences.  If
> there is a reason that one must start with a specific server the
> document really ought to explain why that's the case.
> 
> BTW, the document currently says that one "SHOULD start every query from
> the IRIS server iris.nro.net".  So what happens if the client doesn't?

AFAIK, only the collection of the RIRs, NRO, has auth and should be
authoritative for the main tree initial references. Because of ERX and
NIRs even IANA doesn't have all the top tree info.

If we don't start top-down on a specific IRIS server, NRO will still
need to publish this info on a regular basis and IRIS servers owners
will need to keep this info up to date. This is a trade off, we start
with a well known server name that could be anycasted etc.... to
protect it from DDOS etc... or we'll start with a similar root info
(OOB) as in DNS and people will start to have servers with this
information not up to date. The former is less suitable to non-uniform
responses.

Fred

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


From crisp-bounces@ietf.org  Fri Feb 18 12:14:07 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 MAA09132
	for <crisp-web-archive@ietf.org>; Fri, 18 Feb 2005 12:14:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D2C3O-0002He-ID
	for crisp-web-archive@ietf.org; Fri, 18 Feb 2005 12:36:35 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D2BMR-0006ee-AB; Fri, 18 Feb 2005 11:52:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D2B0r-0000z2-VO
	for crisp@megatron.ietf.org; Fri, 18 Feb 2005 11:29:54 -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 LAA02095
	for <crisp@ietf.org>; Fri, 18 Feb 2005 11:29:50 -0500 (EST)
Received: from falcon.verisign.com ([216.168.239.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2BMX-0000AS-IP
	for crisp@ietf.org; Fri, 18 Feb 2005 11:52:17 -0500
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 j1IGO4op009512; 
	Fri, 18 Feb 2005 11:24:04 -0500 (EST)
Received: from dul1wnexmb01.vcorp.ad.vrsn.com ([10.170.12.134]) by
	dul1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 18 Feb 2005 11:29:19 -0500
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Subject: RE: [Crisp] Working Group Last Call on AREG docs
Date: Fri, 18 Feb 2005 11:29:19 -0500
Message-ID: <046F43A8D79C794FA4733814869CDF07327F70@dul1wnexmb01.vcorp.ad.vrsn.com>
Thread-Topic: [Crisp] Working Group Last Call on AREG docs
Thread-Index: AcUVyyyYI7tbqk42TNGU4wxBSDBskwAC4SJw
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "Andrew Newton" <andy@hxr.us>
X-OriginalArrivalTime: 18 Feb 2005 16:29:20.0197 (UTC)
	FILETIME=[FF65BF50:01C515D6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: quoted-printable

> First, the well-known top still uses referrals (its not a centralized=20
> DB).  But what you are suggesting is a highly, coordinated referral=20
> mesh, which to me seems like overkill at the moment. =20
> Additionally, it=20
> still does not solve the exact problem of "where do I=20
> start?".  Having=20
> software implementors and users assume an entry point seems to be the=20
> same problem only spread out over a larger number of nodes.

I think this was your *second* point, Andy.  ;-)

What I'm suggesting is that the AREG resolution document should include
text to explain the technical limitation that requires a well-known
starting point. That could include a description of why a "highly,
coordinated referral mesh" won't work.

-Scott-

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


From crisp-bounces@ietf.org  Fri Feb 18 12:16:50 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 MAA09436
	for <crisp-web-archive@ietf.org>; Fri, 18 Feb 2005 12:16:49 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D2C61-0002NA-Sm
	for crisp-web-archive@ietf.org; Fri, 18 Feb 2005 12:39:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D2BTh-0000xb-5U; Fri, 18 Feb 2005 11:59:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D2B58-00030z-8t
	for crisp@megatron.ietf.org; Fri, 18 Feb 2005 11:34:18 -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 LAA02623
	for <crisp@ietf.org>; Fri, 18 Feb 2005 11:34:16 -0500 (EST)
Received: from smtp2.arin.net ([192.149.252.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2BQn-0000O2-Us
	for crisp@ietf.org; Fri, 18 Feb 2005 11:56:43 -0500
Received: by smtp2.arin.net (Postfix, from userid 5003)
	id 8CBC5144643; Fri, 18 Feb 2005 11:34:13 -0500 (EST)
Received: from mercury.arin.net (mercury.arin.net [192.149.252.131])
	by smtp2.arin.net (Postfix) with ESMTP id 06F80144631
	for <crisp@ietf.org>; Fri, 18 Feb 2005 11:34:13 -0500 (EST)
Received: from caesium (caesium.arin.net [192.136.136.36])
	by mercury.arin.net (Postfix) with ESMTP id 05E011FEC6
	for <crisp@ietf.org>; Fri, 18 Feb 2005 11:34:13 -0500 (EST)
From: "Tim Christensen" <timc@arin.net>
To: "'CRISP WG'" <crisp@ietf.org>
Subject: RE: [Crisp] Working Group Last Call on AREG docs
Date: Fri, 18 Feb 2005 11:34:05 -0500
Message-ID: <001301c515d7$ac57bbf0$248888c0@arin.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
In-Reply-To: <a17ef5b0f27ae5627c284d738d58657c@hxr.us>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Importance: Normal
X-Spam-Checker-Version: SpamAssassin 2.63-arin1 (2004-01-11) on smtp2.arin.net
X-Spam-Status: No, hits=-6.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=2.63-arin1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit

> -----Original Message-----
> From: crisp-bounces@ietf.org [mailto:crisp-bounces@ietf.org] 
> On Behalf Of Andrew Newton
> Subject: Re: [Crisp] Working Group Last Call on AREG docs
> 
> On Feb 18, 2005, at 9:31 AM, Frederico A C Neves wrote:
> 
> > The protocol should support both models with the use of optional 
> > objects.
> 
> I think this is easily enough done in one of two ways:
> 1) just put the address elements in the contact result as optional 
> (RIPE,APNIC will never use them, ARIN,LACNIC will never use 
> the ones in 
> the organization result-- I assume)

Not a safe assumption. For ARIN, addresses are mandatory elements of both
Orgs and Contacts.
ARIN would use both.  (Not that this answer affects your #1 suggestion per
se)

> 2) create a separate address result that each may refer to as a 
> temporary reference (temporary on the assumption that there is no 
> full-fledged address object in the DB).

It seems more normalized, yes, but it's also somewhat more cumbersome given
that address overlap among multiple Orgs or Contacts is quite a bit less
than you might think.  There is not much address commonality, even among
contacts who work for the registered org, because things like mail stops,
suite numbers, etc. make them different.

> #1 is slightly more work for clients, #2 is slightly more work for 
> servers.  And I do mean slightly in both cases because 
> neither is a big 
> deal.
> 
> Personally, I like #2 because it seems more normalized, but I 
> could go 
> either way.

I'm rather ambivalent as to which method is used, but the ability should
exist.

Tim



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


From crisp-bounces@ietf.org  Fri Feb 18 12:18:40 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 MAA09577
	for <crisp-web-archive@ietf.org>; Fri, 18 Feb 2005 12:18:40 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D2C7n-0002Q4-4e
	for crisp-web-archive@ietf.org; Fri, 18 Feb 2005 12:41:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D2BTo-00013W-8d; Fri, 18 Feb 2005 11:59:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D2B93-0003rq-Vg
	for crisp@megatron.ietf.org; Fri, 18 Feb 2005 11:38:22 -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 LAA03183
	for <crisp@ietf.org>; Fri, 18 Feb 2005 11:38:19 -0500 (EST)
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2BUk-0000U2-0N
	for crisp@ietf.org; Fri, 18 Feb 2005 12:00:47 -0500
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by ithilien.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id
	j1IGbkeD010508; Fri, 18 Feb 2005 08:37:46 -0800 (PST)
Received: from [24.23.128.154] (vpn-10-50-16-36.qualcomm.com [10.50.16.36])
	by sabrina.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id
	j1IGbgJr023377; Fri, 18 Feb 2005 08:37:44 -0800 (PST)
Mime-Version: 1.0
Message-Id: <p06210207be3bc8b847c9@[24.23.128.154]>
In-Reply-To: <c77e69452d040f86373f26b9a910b982@hxr.us>
References: <046F43A8D79C794FA4733814869CDF07327F68@dul1wnexmb01.vcorp.ad.vrsn.com>
	<c77e69452d040f86373f26b9a910b982@hxr.us>
Date: Fri, 18 Feb 2005 08:37:41 -0800
To: Andrew Newton <andy@hxr.us>,
        "Hollenbeck, Scott" <shollenbeck@verisign.com>
From: Ted Hardie <hardie@qualcomm.com>
Subject: Re: [Crisp] Working Group Last Call on AREG docs
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-PMX-Version: 4.7.0.111621
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b

At 10:04 AM -0500 2/18/05, Andrew Newton wrote:
>>"The client SHOULD start every query from the IRIS server iris.nro.net
>>and follow the referrals to find the authoritative server to actually
>>query."
>>
>>Justification would be helpful.  Given the very complete description of
>>referrals in other IRIS documents, the lack of text explaining why a
>>referral won't work here is somewhat mystifying to me.
>
>First, the well-known top still uses referrals (its not a 
>centralized DB).  But what you are suggesting is a highly, 
>coordinated referral mesh, which to me seems like overkill at the 
>moment.  Additionally, it still does not solve the exact problem of 
>"where do I start?".  Having software implementors and users assume 
>an entry point seems to be the same problem only spread out over a 
>larger number of nodes.

But I'm not sure a highly coordinated mesh is the only other choice. 
If a client
starts any place and asks for something that is not known locally, that place
can always give a referral to a well-known "top"; if they have other 
data, great, but
if not things aren't lost.   That means the number of places the 
"top" has to be
updated goes from "every client" to "every referrer" when a change is needed.
And the client can *still* be pointed at the top if the person doing the
configuration prefers it that way.

I think there will be a number of users who are sufficiently focused on
one region and task that they would be able to point their clients at
that RIR's IRIS server and go on their merry way.  I have not idea, though,
whether that number is small, some, lots, most, or almost all.  Any data
that we can bring to bear on that point?
			regards,
				Ted

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


From crisp-bounces@ietf.org  Fri Feb 18 13:36:34 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 NAA19598
	for <crisp-web-archive@ietf.org>; Fri, 18 Feb 2005 13:36:34 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D2DLC-0004ms-IT
	for crisp-web-archive@ietf.org; Fri, 18 Feb 2005 13:59:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D2Cf9-0006d1-KD; Fri, 18 Feb 2005 13:15:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D2CSc-0001va-ET
	for crisp@megatron.ietf.org; Fri, 18 Feb 2005 13:02: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 NAA14468
	for <crisp@ietf.org>; Fri, 18 Feb 2005 13:02:35 -0500 (EST)
Received: from mx.alices-registry.com ([69.59.189.34])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2CoJ-0003qX-DK
	for crisp@ietf.org; Fri, 18 Feb 2005 13:25:04 -0500
Received: by mx.alices-registry.com (Postfix, from userid 1012)
	id 4C32C14804F; Fri, 18 Feb 2005 10:22:35 -0800 (PST)
Received: from [192.168.1.10] (dsl081-069-028.sfo1.dsl.speakeasy.net
	[64.81.69.28])
	by mx.alices-registry.com (Postfix) with ESMTP id 0C21814804F
	for <crisp@ietf.org>; Fri, 18 Feb 2005 10:22:30 -0800 (PST)
Message-ID: <42162DA6.1070707@ar.com>
Date: Fri, 18 Feb 2005 10:02:14 -0800
From: Rick Wesson <wessorh@ar.com>
User-Agent: Mozilla Thunderbird 0.8 (X11/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: CRISP WG <crisp@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on mx1.ar.com
X-Spam-Status: No, hits=0.0 required=3.0 tests=none autolearn=no version=2.60
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2870a44b67ee17965ce5ad0177e150f4
Content-Transfer-Encoding: 7bit
Subject: [Crisp] staring points
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: 30ac594df0e66ffa5a93eb4c48bcb014
Content-Transfer-Encoding: 7bit

could the IANA publish a welk-nown list of starting points as SRV 
records under the .int tld?

-rick

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


From crisp-bounces@ietf.org  Fri Feb 18 14:22:50 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 OAA28014
	for <crisp-web-archive@ietf.org>; Fri, 18 Feb 2005 14:22:50 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D2E3x-0006cq-0P
	for crisp-web-archive@ietf.org; Fri, 18 Feb 2005 14:45:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D2DQn-0007Ks-Nu; Fri, 18 Feb 2005 14:04:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D2DBk-0000af-3j
	for crisp@megatron.ietf.org; Fri, 18 Feb 2005 13:49: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 NAA21460
	for <crisp@ietf.org>; Fri, 18 Feb 2005 13:49:15 -0500 (EST)
Received: from [64.151.105.12] (helo=zak.ecotroph.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2DXP-0005C3-8x
	for crisp@ietf.org; Fri, 18 Feb 2005 14:11:42 -0500
Received: from [10.0.1.4] ([::ffff:64.83.8.178])
	(AUTH: PLAIN anewton, SSL: TLSv1/SSLv3,128bits,RC4-SHA)
	by zak.ecotroph.net with esmtp; Fri, 18 Feb 2005 13:49:10 -0500
	id 0020707E.421638A6.00005166
In-Reply-To: <001301c515d7$ac57bbf0$248888c0@arin.net>
References: <001301c515d7$ac57bbf0$248888c0@arin.net>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <C4D78B2C-81DD-11D9-BF36-000A95B3BA44@hxr.us>
Content-Transfer-Encoding: 7bit
From: Andrew Newton <andy@hxr.us>
Subject: Re: [Crisp] Working Group Last Call on AREG docs
Date: Fri, 18 Feb 2005 13:49:07 -0500
To: "Tim Christensen" <timc@arin.net>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit


On Feb 18, 2005, at 11:34 AM, Tim Christensen wrote:

> It seems more normalized, yes, but it's also somewhat more cumbersome 
> given
> that address overlap among multiple Orgs or Contacts is quite a bit 
> less
> than you might think.  There is not much address commonality, even 
> among
> contacts who work for the registered org, because things like mail 
> stops,
> suite numbers, etc. make them different.

Good point.  So #1 is probably best.

-andy


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


From crisp-bounces@ietf.org  Fri Feb 18 14:48:39 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 OAA02129
	for <crisp-web-archive@ietf.org>; Fri, 18 Feb 2005 14:48:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D2ESt-0007c7-VC
	for crisp-web-archive@ietf.org; Fri, 18 Feb 2005 15:11:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D2Dmd-0006vt-RX; Fri, 18 Feb 2005 14:27:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D2DfT-0003yv-KC
	for crisp@megatron.ietf.org; Fri, 18 Feb 2005 14:20:00 -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 OAA27715
	for <crisp@ietf.org>; Fri, 18 Feb 2005 14:19:57 -0500 (EST)
Received: from bartok.nlnetlabs.nl ([213.154.224.50])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2E1B-0006Xi-9L
	for crisp@ietf.org; Fri, 18 Feb 2005 14:42:25 -0500
Received: from bartok.nlnetlabs.nl (localhost.nlnetlabs.nl [127.0.0.1])
	by bartok.nlnetlabs.nl (8.13.1/8.13.1) with ESMTP id j1IJJeou060010;
	Fri, 18 Feb 2005 20:19:40 +0100 (CET)
	(envelope-from jaap@bartok.nlnetlabs.nl)
Message-Id: <200502181919.j1IJJeou060010@bartok.nlnetlabs.nl>
To: Rick Wesson <wessorh@ar.com>
Subject: Re: [Crisp] staring points 
In-reply-to: Your message of Fri, 18 Feb 2005 10:02:14 -0800.
	<42162DA6.1070707@ar.com> 
Date: Fri, 18 Feb 2005 20:19:40 +0100
From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c


    could the IANA publish a welk-nown list of starting points as SRV 
    records under the .int tld?

Since it is infrastructure, something under .arpa is likely more
appropriate.

	jaap

PS. Hi Rick!

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


From crisp-bounces@ietf.org  Fri Feb 18 15:17: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 PAA07454
	for <crisp-web-archive@ietf.org>; Fri, 18 Feb 2005 15:17:09 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D2EuX-0000oc-OA
	for crisp-web-archive@ietf.org; Fri, 18 Feb 2005 15:39:37 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D2EXe-0007xb-Rm; Fri, 18 Feb 2005 15:15:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D2EQ1-0003TG-IT
	for crisp@megatron.ietf.org; Fri, 18 Feb 2005 15:08:05 -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 PAA04995
	for <crisp@ietf.org>; Fri, 18 Feb 2005 15:08:03 -0500 (EST)
Received: from mx.alices-registry.com ([69.59.189.34])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2EkT-000056-SB
	for crisp@ietf.org; Fri, 18 Feb 2005 15:29:15 -0500
Received: by mx.alices-registry.com (Postfix, from userid 1012)
	id 5203C148048; Fri, 18 Feb 2005 12:26:45 -0800 (PST)
Received: from [192.168.1.10] (dsl081-069-028.sfo1.dsl.speakeasy.net
	[64.81.69.28])
	by mx.alices-registry.com (Postfix) with ESMTP id 8A610148048;
	Fri, 18 Feb 2005 12:26:40 -0800 (PST)
Message-ID: <42164ABE.7080300@ar.com>
Date: Fri, 18 Feb 2005 12:06:22 -0800
From: Rick Wesson <wessorh@ar.com>
User-Agent: Mozilla Thunderbird 0.8 (X11/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jaap Akkerhuis <jaap@NLnetLabs.nl>
Subject: Re: [Crisp] staring points
References: <200502181919.j1IJJeou060010@bartok.nlnetlabs.nl>
In-Reply-To: <200502181919.j1IJJeou060010@bartok.nlnetlabs.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on mx1.ar.com
X-Spam-Status: No, hits=0.0 required=3.0 tests=none autolearn=no version=2.60
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit

Jaap,

thanks, yes, .arpa is more appropiate. How do you feel about publishing 
hints via SRV records? Would that be appropiate mechanism for pointing 
out the "top" of the tree?

-rick

Jaap Akkerhuis wrote:

>    could the IANA publish a welk-nown list of starting points as SRV 
>    records under the .int tld?
>
>Since it is infrastructure, something under .arpa is likely more
>appropriate.
>
>	jaap
>
>PS. Hi Rick!
>
>_______________________________________________
>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  Fri Feb 18 15:24: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 PAA08672
	for <crisp-web-archive@ietf.org>; Fri, 18 Feb 2005 15:24:09 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D2F1I-00011K-Nn
	for crisp-web-archive@ietf.org; Fri, 18 Feb 2005 15:46:37 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D2EXl-00080C-B6; Fri, 18 Feb 2005 15:16:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D2EQB-0003Yb-2B
	for crisp@megatron.ietf.org; Fri, 18 Feb 2005 15:08:15 -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 PAA05113
	for <crisp@ietf.org>; Fri, 18 Feb 2005 15:08:12 -0500 (EST)
Received: from cliffie.verisignlabs.com ([65.201.175.9]
	helo=mail.verisignlabs.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2EgG-0008Ik-9T
	for crisp@ietf.org; Fri, 18 Feb 2005 15:24:52 -0500
Received: from [192.168.0.108] ([::ffff:68.232.102.88])
	(AUTH: PLAIN leslie, TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by mail.verisignlabs.com with esmtp; Fri, 18 Feb 2005 15:01:53 -0500
	id 0057405B.421649B1.000017C3
Received-SPF: unknown (Address does not pass the Sender Policy Framework)
	SPF=HELO; sender=[192.168.0.108]; remoteip=::ffff:68.232.102.88;
	remotehost=; helo=[192.168.0.108];
	receiver=mail.verisignlabs.com;
Received-SPF: none (Address does not pass the Sender Policy Framework)
	SPF=MAILFROM; sender=leslie@thinkingcat.com;
	remoteip=::ffff:68.232.102.88; remotehost=; helo=[192.168.0.108];
	receiver=mail.verisignlabs.com;
Message-ID: <42164997.3020708@thinkingcat.com>
Date: Fri, 18 Feb 2005 15:01:27 -0500
From: Leslie Daigle <leslie@thinkingcat.com>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Rick Wesson <wessorh@ar.com>
Subject: Re: [Crisp] staring points
References: <42162DA6.1070707@ar.com>
In-Reply-To: <42162DA6.1070707@ar.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: 7bit
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit


Nice try; wrong tld... ;-)  The IETF decamped from  .int, and
we now use .arpa for such needs.

So, yes, SNAPTR could be used (like in DREG); areg-iris.arpa
could include appropriate NAPTR records to hand off to the
appropriate server (e.g., iris.nro.net).  As part of its
caretaking of the standard, the IETF/IAB would undertake
to make sure IANA kept its DNS up to date for areg-iris.arpa.
(It's not like it's going to be highly volatile!).

That speaks to the "enshrined location of the top AREG server"
issue; it solves some of the issues with it.

There still seems to be a question about whether there should
be a unique "top" to AREG, or whether that should be configurable
in the client.  That doesn't preclude the possibility of having
some conventionally known good/best starting places,  such as
iris.nro.net.

It's the latter that I recall Ted calling for during the
meeting (and seems to be captured in the minutes).  However,
the current AREG URI document doesn't seem to make the
distinction -- it suggests (practically) that there is one
top, and that it is located at iris.nro.net.

For myself, I think either the document should be clearer
that is *one* possible starting point and clients should be
configurable to allow others, or it should suggest
how to find the current "top" at any given time (other
than enshrining a host name).

BTW, both the AREG and AREG-URI document seem to be
registering the AREG1 namespace:

       urn:ietf:params:xml:ns:areg1

(i.e., duplicated iana considerations).

Leslie.

Rick Wesson wrote:
> could the IANA publish a welk-nown list of starting points as SRV 
> records under the .int tld?
> 
> -rick
> 
> _______________________________________________
> 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  Fri Feb 18 18:39:16 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 SAA21971
	for <crisp-web-archive@ietf.org>; Fri, 18 Feb 2005 18:39:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D2I4B-0006RL-9Z
	for crisp-web-archive@ietf.org; Fri, 18 Feb 2005 19:01:48 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D2HGZ-0004jx-6S; Fri, 18 Feb 2005 18:10:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D2Fot-0002UK-35
	for crisp@megatron.ietf.org; Fri, 18 Feb 2005 16:37:51 -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 QAA25542
	for <crisp@ietf.org>; Fri, 18 Feb 2005 16:37:48 -0500 (EST)
Received: from cwhois1.completewhois.com ([216.151.192.222]
	helo=mail.completewhois.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2GAc-0006Wf-BE
	for crisp@ietf.org; Fri, 18 Feb 2005 17:00:18 -0500
Received: by mail.completewhois.com (Postfix, from userid 500)
	id EFCB818B38; Fri, 18 Feb 2005 13:49:15 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by mail.completewhois.com (Postfix) with ESMTP
	id E68474C490; Fri, 18 Feb 2005 13:49:15 -0800 (PST)
Date: Fri, 18 Feb 2005 13:49:15 -0800 (PST)
From: William Leibzon <william@completewhois.com>
To: Tim Christensen <timc@arin.net>
Subject: RE: [Crisp] Working Group Last Call on AREG docs
In-Reply-To: <001301c515d7$ac57bbf0$248888c0@arin.net>
Message-ID: <Pine.LNX.4.60.0502181334450.13597@cwhois1.completewhois.com>
References: <001301c515d7$ac57bbf0$248888c0@arin.net>
MIME-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
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>
Content-Type: multipart/mixed; boundary="===============1330055130=="
Sender: crisp-bounces@ietf.org
Errors-To: crisp-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--===============1330055130==
Content-Type: MULTIPART/signed;
	BOUNDARY="-1747394880-49940603-1108763355=:13597";
	protocol="application/x-pkcs7-signature"; micalg=sha1

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---1747394880-49940603-1108763355=:13597
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed


On Fri, 18 Feb 2005, Tim Christensen wrote:

>> 2) create a separate address result that each may refer to as a
>> temporary reference (temporary on the assumption that there is no
>> full-fledged address object in the DB).
>
> It seems more normalized, yes, but it's also somewhat more cumbersome given
> that address overlap among multiple Orgs or Contacts is quite a bit less
> than you might think.  There is not much address commonality, even among
> contacts who work for the registered org, because things like mail stops,
> suite numbers, etc. make them different.
>
>> #1 is slightly more work for clients, #2 is slightly more work for
>> servers.  And I do mean slightly in both cases because
>> neither is a big deal.

Having one central address database table is indeed correct approach for
normalizing database schema, but its going to be a pain building interface
for it (for users to be able to refer to address object).

What we could instead is to have contact be considered to linked to
organization object. Right now they are already linked as you may notice,
but its in different way as contacts are responsible for certain roles 
within the organization or roles for netobjects, here I'm talking about 
linking for purposes of showing that contact works for organizaiton, but 
he may not necesserily be responsible for any function of that organization
and may instead be reponsible for something as contractor working for 
another company. Having this link would automaticly mean that contact 
would have address coming from organization object.

Implementation wise this means address is gone from contact and instead
optional organization id is added and those that need address will have
to have organization object created. For large organization, it should
be possible to add suborg under its main org (a division or specific
office).

Note: I'm unsure how well this complexity will work for RIPE and others
as I'm also a lot more familiar with how arin structured its database,
but I suppose it will just mean that for RIPE & APNIC, orgid for contact 
will always be NULL, which isn't too difficult.

---
William Leibzon
   mailto: william@completewhois.com
Anti-Spam and Email Security Research Worksite:
   http://www.elan.net/~william/emailsecurity/
Whois & DNS Network Investigation Tools:
   http://www.completewhois.com
---1747394880-49940603-1108763355=:13597
Content-Type: APPLICATION/x-pkcs7-signature; name="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Disposition: attachment; filename="smime.p7s"
Content-Transfer-Encoding: BASE64

MIIEWgYJKoZIhvcNAQcCoIIESzCCBEcCAQExCzAJBgUrDgMCGgUAMAsGCSqG
SIb3DQEHAaCCAl8wggJbMIIBxKADAgECAgMMcrUwDQYJKoZIhvcNAQEEBQAw
YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQ
dHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJ
c3N1aW5nIENBMB4XDTA0MDYwNTA5NDI0MVoXDTA1MDYwNTA5NDI0MVowSzEf
MB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEoMCYGCSqGSIb3DQEJ
ARYZd2lsbGlhbUBjb21wbGV0ZXdob2lzLmNvbTCBnzANBgkqhkiG9w0BAQEF
AAOBjQAwgYkCgYEAxU1TG0vg2fYJeZ2TZ7cFst7hHB/83aN00wQS1cmKBpDA
q3UgvHfcnltbJqmM0+Wfr35P7RDKGjCvqZTS6sDhXeEUDE1OgdwHsYv62TUr
y94CQMVu6cctH3T+ajzQ9m1NmR0AT+uYQK7hwwcz70PB6T2troUUlcxFon+H
1jB1t1ECAwEAAaM2MDQwJAYDVR0RBB0wG4EZd2lsbGlhbUBjb21wbGV0ZXdo
b2lzLmNvbTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUAA4GBACxJJGcY
lC9YU8SQWQBr/lzwwk9coMdLKs7YsqcroT12o0UT+AKO+5Ec4VPE7OfBvz66
5w1sz41oAlZM2JggwDSJ8NeYCpLxUxk/1wx1BclPGuedYsRm7NO5CCQP4IO7
qlwgTwBkfkrLeadbUf9MMuOjURVwTKfVkT6qfX8bvbqzMYIBwzCCAb8CAQEw
aTBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcg
KFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWls
IElzc3VpbmcgQ0ECAwxytTAJBgUrDgMCGgUAoIGxMBgGCSqGSIb3DQEJAzEL
BgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA1MDIxODIxNDkxNVowIwYJ
KoZIhvcNAQkEMRYEFMl4cFj5nb/WPD1VNpUwcHAaPGE3MFIGCSqGSIb3DQEJ
DzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMC
AgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMA0GCSqGSIb3DQEBAQUABIGA
M6VMbibHR0rs/4s/rmpT4p6XRgGIFfKJH9LG4usd73G14vbjPjZf0QaZOxwi
HINouW9miaXAdT9p3Rhb5F/40/DyxUId55niKzK0+kuDUnUZI+75J7g2m5Be
pyelb2vFuks+1+4k+G/ZU5rF6YWEjdvy0GzeuLKSyc8RcVLraK8=

---1747394880-49940603-1108763355=:13597--


--===============1330055130==
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

--===============1330055130==--



From crisp-bounces@ietf.org  Fri Feb 18 18:59:50 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 SAA27502
	for <crisp-web-archive@ietf.org>; Fri, 18 Feb 2005 18:59:50 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D2IO5-0008Ij-Tt
	for crisp-web-archive@ietf.org; Fri, 18 Feb 2005 19:22:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D2HM3-0002eU-HQ; Fri, 18 Feb 2005 18:16:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D2GYu-0006rF-N1
	for crisp@megatron.ietf.org; Fri, 18 Feb 2005 17:25:24 -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 RAA11325
	for <crisp@ietf.org>; Fri, 18 Feb 2005 17:25:22 -0500 (EST)
Received: from smtp2.arin.net ([192.149.252.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2Gub-0003Jg-C6
	for crisp@ietf.org; Fri, 18 Feb 2005 17:47:52 -0500
Received: by smtp2.arin.net (Postfix, from userid 5003)
	id CC968144633; Fri, 18 Feb 2005 17:25:17 -0500 (EST)
Received: from mercury.arin.net (mercury.arin.net [192.149.252.131])
	by smtp2.arin.net (Postfix) with ESMTP id 2674B14462A
	for <crisp@ietf.org>; Fri, 18 Feb 2005 17:25:17 -0500 (EST)
Received: from caesium (caesium.arin.net [192.136.136.36])
	by mercury.arin.net (Postfix) with ESMTP id 1BC631FEC6
	for <crisp@ietf.org>; Fri, 18 Feb 2005 17:25:17 -0500 (EST)
From: "Tim Christensen" <timc@arin.net>
To: "'CRISP WG'" <crisp@ietf.org>
Subject: RE: [Crisp] Working Group Last Call on AREG docs
Date: Fri, 18 Feb 2005 17:25:09 -0500
Message-ID: <001501c51608$b776c1d0$248888c0@arin.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
In-Reply-To: <Pine.LNX.4.60.0502181334450.13597@cwhois1.completewhois.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Importance: Normal
X-Spam-Checker-Version: SpamAssassin 2.63-arin1 (2004-01-11) on smtp2.arin.net
X-Spam-Status: No, hits=-6.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=2.63-arin1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Content-Transfer-Encoding: 7bit

> -----Original Message-----
> From: William Leibzon [mailto:william@completewhois.com] 
> Subject: RE: [Crisp] Working Group Last Call on AREG docs
> 
> On Fri, 18 Feb 2005, Tim Christensen wrote:
> 
> >> 2) create a separate address result that each may refer to as a 
> >> temporary reference (temporary on the assumption that there is no 
> >> full-fledged address object in the DB).
> >
> > It seems more normalized, yes, but it's also somewhat more 
> cumbersome 
> > given that address overlap among multiple Orgs or Contacts 
> is quite a 
> > bit less than you might think.  There is not much address 
> commonality, 
> > even among contacts who work for the registered org, because things 
> > like mail stops, suite numbers, etc. make them different.
> >
> >> #1 is slightly more work for clients, #2 is slightly more work for 
> >> servers.  And I do mean slightly in both cases because 
> neither is a 
> >> big deal.
> 
> Having one central address database table is indeed correct 
> approach for normalizing database schema, but its going to be 
> a pain building interface for it (for users to be able to 
> refer to address object).
> 
> What we could instead is to have contact be considered to 
> linked to organization object. Right now they are already 
> linked as you may notice, but its in different way as 
> contacts are responsible for certain roles 
> within the organization or roles for netobjects, here I'm 
> talking about 
> linking for purposes of showing that contact works for 
> organizaiton, but 
> he may not necesserily be responsible for any function of 
> that organization and may instead be reponsible for something 
> as contractor working for 
> another company. Having this link would automaticly mean that contact 
> would have address coming from organization object.

I am not in support of this suggestion.

If a contact is not responsible for any functions in the organization, why
would the contact's information even exist in this directory service?  I
have a hard time seeing this protocol expanding to "phone book" purposes,
both in functional terms and in scale.  There are other ways to do that
already.

> Implementation wise this means address is gone from contact 
> and instead optional organization id is added and those that 
> need address will have to have organization object created. 
> For large organization, it should be possible to add suborg 
> under its main org (a division or specific office).

This has the unfortunate side effect of forcing all
"independent-contractor-Ipjockeys" to register their organization in order
to have an address for their contact information.  There are contacts which
are not employees of the organization for which they are a contact, and
furthermore the contact's own organization (IP-management-R-us, let's say)
does not have a registered org itself (because it doesn't have any number
resources to register).

I am strongly against constraining address to only an Org and then somehow
having to kludge through orgs to establish contact addresses.

Tim



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


From crisp-bounces@ietf.org  Fri Feb 18 20:24:41 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 UAA07268
	for <crisp-web-archive@ietf.org>; Fri, 18 Feb 2005 20:24:40 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D2JiB-0003Dj-5I
	for crisp-web-archive@ietf.org; Fri, 18 Feb 2005 20:47:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D2Is0-0001B7-Tp; Fri, 18 Feb 2005 19:53:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D2IbU-0008Qv-QS
	for crisp@megatron.ietf.org; Fri, 18 Feb 2005 19:36:12 -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 TAA01487
	for <crisp@ietf.org>; Fri, 18 Feb 2005 19:36:10 -0500 (EST)
Received: from cwhois1.completewhois.com ([216.151.192.222]
	helo=mail.completewhois.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2IxF-00017R-UX
	for crisp@ietf.org; Fri, 18 Feb 2005 19:58:42 -0500
Received: by mail.completewhois.com (Postfix, from userid 500)
	id BB7F1189E6; Fri, 18 Feb 2005 16:47:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by mail.completewhois.com (Postfix) with ESMTP
	id B6F3A4C490; Fri, 18 Feb 2005 16:47:47 -0800 (PST)
Date: Fri, 18 Feb 2005 16:47:47 -0800 (PST)
From: William Leibzon <william@completewhois.com>
To: Tim Christensen <timc@arin.net>
Subject: RE: [Crisp] Working Group Last Call on AREG docs
In-Reply-To: <001501c51608$b776c1d0$248888c0@arin.net>
Message-ID: <Pine.LNX.4.60.0502181618260.19700@cwhois1.completewhois.com>
References: <001501c51608$b776c1d0$248888c0@arin.net>
MIME-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365
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>
Content-Type: multipart/mixed; boundary="===============1684839636=="
Sender: crisp-bounces@ietf.org
Errors-To: crisp-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d16ce744298aacf98517bc7c108bd198

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--===============1684839636==
Content-Type: MULTIPART/signed;
	BOUNDARY="-1747394880-1190171566-1108774067=:19700";
	protocol="application/x-pkcs7-signature"; micalg=sha1

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---1747394880-1190171566-1108774067=:19700
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed


On Fri, 18 Feb 2005, Tim Christensen wrote:

>> On Fri, 18 Feb 2005, Tim Christensen wrote:
>>
>> Having one central address database table is indeed correct
>> approach for normalizing database schema, but its going to be
>> a pain building interface for it (for users to be able to
>> refer to address object).
>>
>> What we could instead is to have contact be considered to
>> linked to organization object. Right now they are already
>> linked as you may notice, but its in different way as
>> contacts are responsible for certain roles
>> within the organization or roles for netobjects, here I'm
>> talking about
>> linking for purposes of showing that contact works for
>> organizaiton, but
>> he may not necesserily be responsible for any function of
>> that organization and may instead be reponsible for something
>> as contractor working for
>> another company. Having this link would automaticly mean that contact
>> would have address coming from organization object.
>
> I am not in support of this suggestion.
>
> If a contact is not responsible for any functions in the organization, why
> would the contact's information even exist in this directory service?

<sarcasm>
Thanks for deleting CWHOIS-ARIN contact because of not being associated 
with any organization. Guess that it was there for different purpose as 
documented at http://www.sixxs.net/tools/brs/ was not of concern to ARIN...
</sarcasm>

To the point, as I noted, he maybe responsble, but work for one organization
(or himself) but at the same time have technical role as contact for different
organization (contractor relationship is an example). And same contact can 
easily have roles at more then one organization also, so link to ORG from 
contact would establish what his primarily organization is but it IS NOT 
the same as link from ORG or NETBLOCK as the contacts are currently used.

> I have a hard time seeing this protocol expanding to "phone book" 
> purposes, both in functional terms and in scale.  There are other ways 
> to do that already.

Whois is in fact a phone-book for network registration data already.
Also since address is to be optional, the contact can enter or not,
so its no different then now or with direct address in contact table.

>> Implementation wise this means address is gone from contact
>> and instead optional organization id is added and those that
>> need address will have to have organization object created.
>> For large organization, it should be possible to add suborg
>> under its main org (a division or specific office).
>
> This has the unfortunate side effect of forcing all
> "independent-contractor-Ipjockeys" to register their organization in order
> to have an address for their contact information.

So, what's a problem especially if address is optional? And they can have 
organization as personal name too if they want, they are quite many orgs
like that in ARIN db as is now.

> There are contacts which are not employees of the organization for which 
> they are a contact

Exactly, this way they can be contact for one organization and optionally
indicate by means of ORGID what organization they are really employed by.

> ,and furthermore the contact's own organization (IP-management-R-us, 
> let's say) does not have a registered org itself (because it doesn't 
> have any number resources to register).
>
> I am strongly against constraining address to only an Org and then somehow
> having to kludge through orgs to establish contact addresses.

Its not a cludge. And I can assure you that 99+% of people looking for
contact data ARE NOT looking for physical address and only want to see
email address and phone (as they get it with netblock whois currently).
In fact, I'd not be surprised if direct queries for contact in ARIN are
in the ratio of 1:1000 (or more) to queries for netblock and that
direct queries for ORG may even be more common then for contact.

---
William Leibzon
   mailto: william@completewhois.com
Anti-Spam and Email Security Research Worksite:
   http://www.elan.net/~william/emailsecurity/
Whois & DNS Network Investigation Tools:
   http://www.completewhois.com
---1747394880-1190171566-1108774067=:19700
Content-Type: APPLICATION/x-pkcs7-signature; name="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Disposition: attachment; filename="smime.p7s"
Content-Transfer-Encoding: BASE64

MIIEWgYJKoZIhvcNAQcCoIIESzCCBEcCAQExCzAJBgUrDgMCGgUAMAsGCSqG
SIb3DQEHAaCCAl8wggJbMIIBxKADAgECAgMMcrUwDQYJKoZIhvcNAQEEBQAw
YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQ
dHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJ
c3N1aW5nIENBMB4XDTA0MDYwNTA5NDI0MVoXDTA1MDYwNTA5NDI0MVowSzEf
MB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEoMCYGCSqGSIb3DQEJ
ARYZd2lsbGlhbUBjb21wbGV0ZXdob2lzLmNvbTCBnzANBgkqhkiG9w0BAQEF
AAOBjQAwgYkCgYEAxU1TG0vg2fYJeZ2TZ7cFst7hHB/83aN00wQS1cmKBpDA
q3UgvHfcnltbJqmM0+Wfr35P7RDKGjCvqZTS6sDhXeEUDE1OgdwHsYv62TUr
y94CQMVu6cctH3T+ajzQ9m1NmR0AT+uYQK7hwwcz70PB6T2troUUlcxFon+H
1jB1t1ECAwEAAaM2MDQwJAYDVR0RBB0wG4EZd2lsbGlhbUBjb21wbGV0ZXdo
b2lzLmNvbTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUAA4GBACxJJGcY
lC9YU8SQWQBr/lzwwk9coMdLKs7YsqcroT12o0UT+AKO+5Ec4VPE7OfBvz66
5w1sz41oAlZM2JggwDSJ8NeYCpLxUxk/1wx1BclPGuedYsRm7NO5CCQP4IO7
qlwgTwBkfkrLeadbUf9MMuOjURVwTKfVkT6qfX8bvbqzMYIBwzCCAb8CAQEw
aTBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcg
KFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWls
IElzc3VpbmcgQ0ECAwxytTAJBgUrDgMCGgUAoIGxMBgGCSqGSIb3DQEJAzEL
BgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA1MDIxOTAwNDc0N1owIwYJ
KoZIhvcNAQkEMRYEFODp+UhN8HBXGiJX8aPYotdYbc+KMFIGCSqGSIb3DQEJ
DzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMC
AgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMA0GCSqGSIb3DQEBAQUABIGA
TOIj94ciyndJxD/qmMgLIrf9eQrWzyZNWZr9AtyNs7GdScTi4jYfpgmEJbgg
TPf9o+WjZcQXsRA6qlGuvU5gCiIYVicl1XAAn5SDXaviy9SC6OixTr/q10sy
tAZpzJbiUwvlLceui4O3IoApNpJExt+2q0f/XMTHor/KoL8fU6Y=

---1747394880-1190171566-1108774067=:19700--


--===============1684839636==
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

--===============1684839636==--



From crisp-bounces@ietf.org  Mon Feb 21 06:06: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 GAA11504
	for <crisp-web-archive@ietf.org>; Mon, 21 Feb 2005 06:06:09 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D3BkW-0005Vo-Hd
	for crisp-web-archive@ietf.org; Mon, 21 Feb 2005 06:29:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D3Awv-0005x5-1J; Mon, 21 Feb 2005 05:37:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D3AJu-00073S-Ox
	for crisp@megatron.ietf.org; Mon, 21 Feb 2005 04:57: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 EAA05664
	for <crisp@ietf.org>; Mon, 21 Feb 2005 04:57:31 -0500 (EST)
Received: from postman.ripe.net ([193.0.0.199])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3Ag5-0003l1-FP
	for crisp@ietf.org; Mon, 21 Feb 2005 05:20:33 -0500
Received: by postman.ripe.net (Postfix, from userid 8)
	id 830B924937; Mon, 21 Feb 2005 10:56:57 +0100 (CET)
Received: from birch.ripe.net (birch.ripe.net [193.0.1.96])
	by postman.ripe.net (Postfix) with ESMTP
	id AA35B24687; Mon, 21 Feb 2005 10:56:56 +0100 (CET)
Received: from [193.0.1.17] (x17.ripe.net [193.0.1.17])
	by birch.ripe.net (8.12.10/8.11.6) with ESMTP id j1L9uuet009835;
	Mon, 21 Feb 2005 10:56:56 +0100
Message-ID: <4219B068.3090900@ripe.net>
Date: Mon, 21 Feb 2005 10:56:56 +0100
From: Shane Kerr <shane@ripe.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913
X-Accept-Language: en, nl
MIME-Version: 1.0
To: Leslie Daigle <leslie@thinkingcat.com>
Subject: Re: [Crisp] staring points
References: <42162DA6.1070707@ar.com> <42164997.3020708@thinkingcat.com>
In-Reply-To: <42164997.3020708@thinkingcat.com>
X-Enigmail-Version: 0.90.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00
X-RIPE-Spam-Status: N 0.000000 / -5.9
X-RIPE-Signature: 907289cb82b6db19b0fc5cb0de266275
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: 7bit
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Content-Transfer-Encoding: 7bit

Leslie Daigle wrote:
> 
> Nice try; wrong tld... ;-)  The IETF decamped from  .int, and
> we now use .arpa for such needs.
> 
> So, yes, SNAPTR could be used (like in DREG); areg-iris.arpa
> could include appropriate NAPTR records to hand off to the
> appropriate server (e.g., iris.nro.net).  As part of its
> caretaking of the standard, the IETF/IAB would undertake
> to make sure IANA kept its DNS up to date for areg-iris.arpa.
> (It's not like it's going to be highly volatile!).
> 
> That speaks to the "enshrined location of the top AREG server"
> issue; it solves some of the issues with it.

While I understand that this is probably politically easier to do, we're 
really talking about moving the "enshrined location of the top AREG server" 
into the DNS. Saying, "start at areg-iris.arpa" isn't really that different 
from saying "start at iris.nro.net", except that the IAB runs it and not the 
NRO.

Which is not to say that I'm opposed to this, I just think we shouldn't kid 
ourselves about what the solution really adds.

> There still seems to be a question about whether there should
> be a unique "top" to AREG, or whether that should be configurable
> in the client.  That doesn't preclude the possibility of having
> some conventionally known good/best starting places,  such as
> iris.nro.net.
 >
> It's the latter that I recall Ted calling for during the
> meeting (and seems to be captured in the minutes).  However,
> the current AREG URI document doesn't seem to make the
> distinction -- it suggests (practically) that there is one
> top, and that it is located at iris.nro.net.
> 
> For myself, I think either the document should be clearer
> that is *one* possible starting point and clients should be
> configurable to allow others, or it should suggest
> how to find the current "top" at any given time (other
> than enshrining a host name).

I don't think anybody thinks that clients should be prevented from having 
their initial query location configured on their side. Clients could even 
have a set of starting points depending on what AREG information they are 
looking for.

But... one of the reasons that the RIRs are so interested in IRIS is because 
clients have to configure these starting points today!

The main reason to want a unique "top" to AREG is that it is actually how 
number management works today - the same as DREG. Clients that follow the 
hierarchy from the top will get the "best" information possible, at least 
from a global view.

I can envision any number of scenerios where a top-down approach is not 
complete. For example, at a university it might make more sense to try a 
local AREG query first. Likewise at an exchange point each ISP peering there 
may provide an AREG server with detailed information to their peers. But I 
am fairly sure these are the exception, and nothing prevents clients from 
taking advantage of knowledge about the local network environment.

I hope the latest draft that Engin submitted over the weekend is clear 
enough to meet the desire for flexibility and having a well-defined default.

-- 
Shane Kerr
RIPE NCC

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


From crisp-bounces@ietf.org  Mon Feb 21 22:04:53 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 WAA22211
	for <crisp-web-archive@ietf.org>; Mon, 21 Feb 2005 22:04:53 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D3QiS-0006yr-IM
	for crisp-web-archive@ietf.org; Mon, 21 Feb 2005 22:28:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D3M51-000102-S5; Mon, 21 Feb 2005 17:31:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D3KAx-0001T2-Ey; Mon, 21 Feb 2005 15:29:03 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11379;
	Mon, 21 Feb 2005 15:29:01 -0500 (EST)
Message-Id: <200502212029.PAA11379@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Mon, 21 Feb 2005 15:29:01 -0500
Cc: crisp@ietf.org
Subject: [Crisp] I-D ACTION:draft-ietf-crisp-iris-areg-10.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: cf3becbbd6d1a45acbe2ffd4ab88bdc2

--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		: IRIS - An Address Registry (areg) Type for the Internet 
			  Registry Information Service
	Author(s)	: A. Newton, et al.
	Filename	: draft-ietf-crisp-iris-areg-10.txt
	Pages		: 61
	Date		: 2005-2-21
	
This document describes an IRIS registry schema for IP address and
   Autonomous System Number 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
   Internet Protocol address registries.

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

ENCODING mime
FILE /internet-drafts/draft-ietf-crisp-iris-areg-10.txt

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

Content-Type: text/plain
Content-ID: <2005-2-21151320.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  Mon Feb 21 22:20:56 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 WAA23639
	for <crisp-web-archive@ietf.org>; Mon, 21 Feb 2005 22:20:56 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D3Qxz-0007QF-GT
	for crisp-web-archive@ietf.org; Mon, 21 Feb 2005 22:44:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D3M54-00010O-HL; Mon, 21 Feb 2005 17:31:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D3KBD-0001VK-SC; Mon, 21 Feb 2005 15:29:19 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11406;
	Mon, 21 Feb 2005 15:29:18 -0500 (EST)
Message-Id: <200502212029.PAA11406@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Mon, 21 Feb 2005 15:29:18 -0500
Cc: crisp@ietf.org
Subject: [Crisp] I-D ACTION:draft-ietf-crisp-iris-areg-urires-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		: IRIS - URI Resolution for AREG Type for the Internet Registry Information Service
	Author(s)	: E. Gunduz
	Filename	: draft-ietf-crisp-iris-areg-urires-01.txt
	Pages		: 11
	Date		: 2005-2-21
	
This document describes a URI Resolution method for the IRIS registry
   schema for IP address and Autonomous System Number information.

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

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

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

Content-Type: text/plain
Content-ID: <2005-2-21151327.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  Wed Feb 23 22:18: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 WAA23747
	for <crisp-web-archive@ietf.org>; Wed, 23 Feb 2005 22:18:28 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D49t3-0004lW-Li
	for crisp-web-archive@ietf.org; Wed, 23 Feb 2005 22:42:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D3klI-0005vw-C9; Tue, 22 Feb 2005 19:52:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D3MiZ-0007Ed-Hf
	for crisp@megatron.ietf.org; Mon, 21 Feb 2005 18:11:55 -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 SAA27169
	for <crisp@ietf.org>; Mon, 21 Feb 2005 18:11:47 -0500 (EST)
Received: from mx.alices-registry.com ([69.59.189.34])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3N4r-00086a-Dj
	for crisp@ietf.org; Mon, 21 Feb 2005 18:34:57 -0500
Received: by mx.alices-registry.com (Postfix, from userid 1012)
	id 81CB0148048; Mon, 21 Feb 2005 15:32:22 -0800 (PST)
Received: from [192.168.1.10] (dsl081-069-028.sfo1.dsl.speakeasy.net
	[64.81.69.28])
	by mx.alices-registry.com (Postfix) with ESMTP id 50F31148048;
	Mon, 21 Feb 2005 15:32:16 -0800 (PST)
Message-ID: <421A6A96.7020400@ar.com>
Date: Mon, 21 Feb 2005 15:11:18 -0800
From: Rick Wesson <wessorh@ar.com>
User-Agent: Mozilla Thunderbird 0.8 (X11/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: William Leibzon <william@completewhois.com>
Subject: Re: [Crisp] Working Group Last Call on AREG docs
References: <001301c515d7$ac57bbf0$248888c0@arin.net>
	<Pine.LNX.4.60.0502181334450.13597@cwhois1.completewhois.com>
In-Reply-To: <Pine.LNX.4.60.0502181334450.13597@cwhois1.completewhois.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on mx1.ar.com
X-Spam-Status: No, hits=0.0 required=3.0 tests=none autolearn=no version=2.60
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Content-Transfer-Encoding: 7bit
Cc: Tim Christensen <timc@arin.net>, "'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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Content-Transfer-Encoding: 7bit


William,

Having s single IrisContact which has attributes of isRole, and 
isOrganization would be simpler than seporate objects for contact and 
organizations. Simply removing organization and adding a new attribute 
to contact whould be the best normalization of this schema.

-rick


William Leibzon wrote:

>
> On Fri, 18 Feb 2005, Tim Christensen wrote:
>
>>> 2) create a separate address result that each may refer to as a
>>> temporary reference (temporary on the assumption that there is no
>>> full-fledged address object in the DB).
>>
>>
>> It seems more normalized, yes, but it's also somewhat more cumbersome 
>> given
>> that address overlap among multiple Orgs or Contacts is quite a bit less
>> than you might think.  There is not much address commonality, even among
>> contacts who work for the registered org, because things like mail 
>> stops,
>> suite numbers, etc. make them different.
>>
>>> #1 is slightly more work for clients, #2 is slightly more work for
>>> servers.  And I do mean slightly in both cases because
>>> neither is a big deal.
>>
>
> Having one central address database table is indeed correct approach for
> normalizing database schema, but its going to be a pain building 
> interface
> for it (for users to be able to refer to address object).
>
> What we could instead is to have contact be considered to linked to
> organization object. Right now they are already linked as you may notice,
> but its in different way as contacts are responsible for certain roles 
> within the organization or roles for netobjects, here I'm talking 
> about linking for purposes of showing that contact works for 
> organizaiton, but he may not necesserily be responsible for any 
> function of that organization
> and may instead be reponsible for something as contractor working for 
> another company. Having this link would automaticly mean that contact 
> would have address coming from organization object.
>
> Implementation wise this means address is gone from contact and instead
> optional organization id is added and those that need address will have
> to have organization object created. For large organization, it should
> be possible to add suborg under its main org (a division or specific
> office).
>
> Note: I'm unsure how well this complexity will work for RIPE and others
> as I'm also a lot more familiar with how arin structured its database,
> but I suppose it will just mean that for RIPE & APNIC, orgid for 
> contact will always be NULL, which isn't too difficult.
>
> ---
> William Leibzon
>   mailto: william@completewhois.com
> Anti-Spam and Email Security Research Worksite:
>   http://www.elan.net/~william/emailsecurity/
> Whois & DNS Network Investigation Tools:
>   http://www.completewhois.com
>
>------------------------------------------------------------------------
>
>_______________________________________________
>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 Feb 24 13:25: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 NAA26347
	for <crisp-web-archive@ietf.org>; Thu, 24 Feb 2005 13:25:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1D4O34-0006Gj-7F
	for crisp-web-archive@ietf.org; Thu, 24 Feb 2005 13:49:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D4Nfl-0006gk-Jj; Thu, 24 Feb 2005 13:25:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D4Nfk-0006gZ-D9
	for crisp@megatron.ietf.org; Thu, 24 Feb 2005 13:25:12 -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 NAA26326
	for <crisp@ietf.org>; Thu, 24 Feb 2005 13:25:09 -0500 (EST)
Received: from cliffie.verisignlabs.com ([65.201.175.9]
	helo=mail.verisignlabs.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4O2h-0006Fn-8d
	for crisp@ietf.org; Thu, 24 Feb 2005 13:48:55 -0500
Received: from [10.131.244.197] ([::ffff:216.168.239.87])
	(AUTH: PLAIN leslie, TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by mail.verisignlabs.com with esmtp; Thu, 24 Feb 2005 13:25:03 -0500
	id 00574339.421E1BFF.00005943
Received-SPF: unknown (Address does not pass the Sender Policy Framework)
	SPF=HELO; sender=[10.131.244.197];
	remoteip=::ffff:216.168.239.87; remotehost=;
	helo=[10.131.244.197]; receiver=mail.verisignlabs.com;
Received-SPF: none (Address does not pass the Sender Policy Framework)
	SPF=MAILFROM; sender=leslie@thinkingcat.com;
	remoteip=::ffff:216.168.239.87; remotehost=;
	helo=[10.131.244.197]; receiver=mail.verisignlabs.com;
Message-ID: <421E1BE6.3000506@thinkingcat.com>
Date: Thu, 24 Feb 2005 13:24:38 -0500
From: Leslie Daigle <leslie@thinkingcat.com>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Shane Kerr <shane@ripe.net>
Subject: Re: [Crisp] staring points
References: <42162DA6.1070707@ar.com> <42164997.3020708@thinkingcat.com>
	<4219B068.3090900@ripe.net>
In-Reply-To: <4219B068.3090900@ripe.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Content-Transfer-Encoding: 7bit
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Content-Transfer-Encoding: 7bit


Having read the revised version...

No, I don't think you're hearing what I'm saying.

I'm saying that:

	. if this *spec* defines a TOP starting point, then
	  make it a *name* not a *location*, so that it
	  can be updated over time (that's the NAPTR shim,
	  and I propose that areg-iris.arpa is a reasonable
	  place to host it).

	. if this *spec* does not define a single TOP starting
	  point, it is quite reasonable to separately define
	  the RIR's operational, authoritative AREG service
	  with a publicized well known TOP (iris.nro.net,
	  if you like).  That can be described & published as a
	  CRISP WG document (or maybe even as part of this
	  document, once you get the separation of concepts down).

I'm not really trying to advocate either way, I just think
it should be made clearer which the WG wants.

Right now, the document mixes the two:  you SHOULD start from
one defined top, although you MAY do whatever else you please.
That doesn't really leave room for developing other equivalently
weighted strategies (e.g., "local AREG -- you SHOULD start at
areg-iris.yourisp.net", or some such rot), which makes it
seem like a single TOP. OTOH, the fact that you can do anything
else means that it's not really a single TOP.  Pick!

Leslie.


	



Shane Kerr wrote:
> Leslie Daigle wrote:
> 
>>
>> Nice try; wrong tld... ;-)  The IETF decamped from  .int, and
>> we now use .arpa for such needs.
>>
>> So, yes, SNAPTR could be used (like in DREG); areg-iris.arpa
>> could include appropriate NAPTR records to hand off to the
>> appropriate server (e.g., iris.nro.net).  As part of its
>> caretaking of the standard, the IETF/IAB would undertake
>> to make sure IANA kept its DNS up to date for areg-iris.arpa.
>> (It's not like it's going to be highly volatile!).
>>
>> That speaks to the "enshrined location of the top AREG server"
>> issue; it solves some of the issues with it.
> 
> 
> While I understand that this is probably politically easier to do, we're 
> really talking about moving the "enshrined location of the top AREG 
> server" into the DNS. Saying, "start at areg-iris.arpa" isn't really 
> that different from saying "start at iris.nro.net", except that the IAB 
> runs it and not the NRO.
> 
> Which is not to say that I'm opposed to this, I just think we shouldn't 
> kid ourselves about what the solution really adds.
> 
>> There still seems to be a question about whether there should
>> be a unique "top" to AREG, or whether that should be configurable
>> in the client.  That doesn't preclude the possibility of having
>> some conventionally known good/best starting places,  such as
>> iris.nro.net.
> 
>  >
> 
>> It's the latter that I recall Ted calling for during the
>> meeting (and seems to be captured in the minutes).  However,
>> the current AREG URI document doesn't seem to make the
>> distinction -- it suggests (practically) that there is one
>> top, and that it is located at iris.nro.net.
>>
>> For myself, I think either the document should be clearer
>> that is *one* possible starting point and clients should be
>> configurable to allow others, or it should suggest
>> how to find the current "top" at any given time (other
>> than enshrining a host name).
> 
> 
> I don't think anybody thinks that clients should be prevented from 
> having their initial query location configured on their side. Clients 
> could even have a set of starting points depending on what AREG 
> information they are looking for.
> 
> But... one of the reasons that the RIRs are so interested in IRIS is 
> because clients have to configure these starting points today!
> 
> The main reason to want a unique "top" to AREG is that it is actually 
> how number management works today - the same as DREG. Clients that 
> follow the hierarchy from the top will get the "best" information 
> possible, at least from a global view.
> 
> I can envision any number of scenerios where a top-down approach is not 
> complete. For example, at a university it might make more sense to try a 
> local AREG query first. Likewise at an exchange point each ISP peering 
> there may provide an AREG server with detailed information to their 
> peers. But I am fairly sure these are the exception, and nothing 
> prevents clients from taking advantage of knowledge about the local 
> network environment.
> 
> I hope the latest draft that Engin submitted over the weekend is clear 
> enough to meet the desire for flexibility and having a well-defined 
> default.
> 

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


