From crisp-bounces@ietf.org Wed Feb 01 06:09:44 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F4Frs-00030D-46; Wed, 01 Feb 2006 06:09:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F4Frq-0002zP-7K
	for crisp@megatron.ietf.org; Wed, 01 Feb 2006 06:09:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03306
	for <crisp@ietf.org>; Wed, 1 Feb 2006 06:08:06 -0500 (EST)
Received: from postman.ripe.net ([193.0.0.199])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F4G2x-0000LX-Ci
	for crisp@ietf.org; Wed, 01 Feb 2006 06:21:14 -0500
Received: by postman.ripe.net (Postfix, from userid 4008)
	id 60FC023EF9; Wed,  1 Feb 2006 12:09:10 +0100 (CET)
Received: from herring.ripe.net (herring.ripe.net [193.0.1.203])
	by postman.ripe.net (Postfix) with ESMTP id 7E41F23F18;
	Wed,  1 Feb 2006 12:09:09 +0100 (CET)
Received: from [193.0.1.17] (x17.ripe.net [193.0.1.17])
	by herring.ripe.net (Postfix) with ESMTP id 797CD2F598;
	Wed,  1 Feb 2006 12:09:09 +0100 (CET)
Message-ID: <43E096D5.1070503@ripe.net>
Date: Wed, 01 Feb 2006 12:09:09 +0100
From: Shane Kerr <shane@ripe.net>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051011)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: April Marine <April.Marine@nominum.com>
Subject: Re: [Crisp] IAB request re areg.iris.arpa
References: <20060131083832.U6964@shell-ng.nominum.com>
In-Reply-To: <20060131083832.U6964@shell-ng.nominum.com>
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=ISO-8859-1
X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00
X-RIPE-Spam-Status: N 0.000000 / -5.9
X-RIPE-Signature: 270435c9448fdd6de1a8aea205893f6a
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
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

The change makes sense to me.

April Marine wrote:

> The easiest way to check with y'all about this is merely to forward
> the email. Any issues we haven't thought of? Speak now....
>
> thanks!
> A (and G)
>
> ---------- Forwarded message ----------
> Date: Tue, 31 Jan 2006 10:43:25 -0500
> From: Andrew Newton <andy@hxr.us>
> To: Patrik F=E4ltstr=F6m <paf@cisco.com>
> Cc: April Marine <april.marine@nominum.com>, Ted Hardie
> <hardie@qualcomm.com>,
>     George Michaelson <ggm@apnic.net>, Leslie Daigle
> <leslie@thinkingcat.com>,
>     iana <iana@iana.org>, IAB <iab@ietf.org>
> Subject: Re: draft-ietf-crisp-iris-areg-13.txt
>
> Patrik,
>
> From your explanation, this sounds like a fairly reasonable thing.=20
> And quite honestly, I don't think anybody in the CRISP working group
> will object.  As for asking the working group, I guess that is a task
> for April and George.
>
> -andy
>
> On Jan 30, 2006, at 10:01 AM, Patrik F=E4ltstr=F6m wrote:
>
>> April, Andrew!
>>
>> I am, as one member of the IAB, reviewing the delegation request from
>> the IRIS wg, and I have only one small issue with it.
>>
>> The IAB do want to keep the arpa zone as "delegation only", and this
>> is why I ask the wg whether they would object to a change in the
>> delegation request.
>>
>> The proposal was to add a NAPTR with the owner areg-iris.arpa. This
>> implies either that we have the NAPTR in the arpa zone directly, or
>> that a delegation is made for areg-iris.arpa to a zone with the same
>> name where only the areg-iris.arpa NAPTR RR resides.
>>
>> Can you check with the wg whether they would accept a delegation of
>> the iris.arpa zone, and then have the areg.iris.arpa (note the '.'
>> between areg and iris.arpa) RR in that zone. That way potential other
>> records can be hosted in the same zone (iris.arpa) and new
>> delegations from arpa is not needed.
>>
>>    Regards, Patrik F=E4ltstr=F6m
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Crisp mailing list
>Crisp@ietf.org
>https://www1.ietf.org/mailman/listinfo/crisp
> =20
>


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



From crisp-bounces@ietf.org Thu Feb 09 15:50:09 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F7Ijx-00026J-Sb; Thu, 09 Feb 2006 15:50:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F7Ijr-00023M-Pu; Thu, 09 Feb 2006 15:50:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28851;
	Thu, 9 Feb 2006 15:48:20 -0500 (EST)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F7Iwj-00076G-4t; Thu, 09 Feb 2006 16:03:21 -0500
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1F7Ijq-0000LL-57; Thu, 09 Feb 2006 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1F7Ijq-0000LL-57@newodin.ietf.org>
Date: Thu, 09 Feb 2006 15:50:02 -0500
X-Spam-Score: 0.4 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: crisp@ietf.org
Subject: [Crisp] I-D ACTION:draft-ietf-crisp-iris-dchk-04.txt 
X-BeenThere: crisp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Cross Registry Information Service Protocol <crisp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/crisp>,
	<mailto:crisp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:crisp@ietf.org>
List-Help: <mailto:crisp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/crisp>,
	<mailto:crisp-request@ietf.org?subject=subscribe>
Sender: crisp-bounces@ietf.org
Errors-To: crisp-bounces@ietf.org

--NextPart

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

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

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

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


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

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-crisp-iris-dchk-04.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: <2006-2-9125256.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2006-2-9125256.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From crisp-bounces@ietf.org Thu Feb 09 15:50:21 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F7Ik9-0002Cf-HH; Thu, 09 Feb 2006 15:50:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F7Ijt-00023v-5n; Thu, 09 Feb 2006 15:50:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28859;
	Thu, 9 Feb 2006 15:48:21 -0500 (EST)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F7Iwj-00076K-7b; Thu, 09 Feb 2006 16:03:22 -0500
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1F7Ijq-0000Lm-At; Thu, 09 Feb 2006 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1F7Ijq-0000Lm-At@newodin.ietf.org>
Date: Thu, 09 Feb 2006 15:50:02 -0500
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: crisp@ietf.org
Subject: [Crisp] I-D ACTION:draft-ietf-crisp-iris-lwz-05.txt 
X-BeenThere: crisp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Cross Registry Information Service Protocol <crisp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/crisp>,
	<mailto:crisp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:crisp@ietf.org>
List-Help: <mailto:crisp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/crisp>,
	<mailto:crisp-request@ietf.org?subject=subscribe>
Sender: crisp-bounces@ietf.org
Errors-To: crisp-bounces@ietf.org

--NextPart

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

	Title		: A Lightweight UDP Transfer Protocol for the  the Internet Registry Information  Service
	Author(s)	: A. Newton
	Filename	: draft-ietf-crisp-iris-lwz-05.txt
	Pages		: 24
	Date		: 2006-2-9
	
This document describes a lightweight UDP transfer protocol for the
Internet Registry Information Service (IRIS).  This transfer protocol
uses a single packet for every request and response, and optionally
employs compression over the contents of the packet.

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

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


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

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-crisp-iris-lwz-05.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: <2006-2-9143405.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2006-2-9143405.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From crisp-bounces@ietf.org Thu Feb 09 15:50:25 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F7IkD-0002G4-Uk; Thu, 09 Feb 2006 15:50:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F7Ijt-00023x-8H; Thu, 09 Feb 2006 15:50:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28865;
	Thu, 9 Feb 2006 15:48:21 -0500 (EST)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F7Iwj-00076F-4w; Thu, 09 Feb 2006 16:03:22 -0500
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1F7Ijq-0000LT-70; Thu, 09 Feb 2006 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1F7Ijq-0000LT-70@newodin.ietf.org>
Date: Thu, 09 Feb 2006 15:50:02 -0500
X-Spam-Score: 0.4 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: crisp@ietf.org
Subject: [Crisp] I-D ACTION:draft-ietf-crisp-iris-common-transport-03.txt 
X-BeenThere: crisp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Cross Registry Information Service Protocol <crisp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/crisp>,
	<mailto:crisp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:crisp@ietf.org>
List-Help: <mailto:crisp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/crisp>,
	<mailto:crisp-request@ietf.org?subject=subscribe>
Sender: crisp-bounces@ietf.org
Errors-To: crisp-bounces@ietf.org

--NextPart

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

	Title		: A Common Schema for Internet Registry Information Service Transfer Protocols
	Author(s)	: A. Newton
	Filename	: draft-ietf-crisp-iris-common-transport-03.txt
	Pages		: 19
	Date		: 2006-2-9
	
This document describes an XML Schema for use by Internet Registry
   Information Service (IRIS) application transfer protocols that share
   common characteristics.  It describes common information about the
   transfer protocol, such as version, supported extensions, and
   supported security mechanisms.

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

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


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

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


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

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

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

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

Content-Type: text/plain
Content-ID: <2006-2-9130307.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2006-2-9130307.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From crisp-bounces@ietf.org Thu Feb 09 15:50:56 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F7Ikh-0002Oi-VH; Thu, 09 Feb 2006 15:50:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F7Ijt-00024P-R2; Thu, 09 Feb 2006 15:50:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28872;
	Thu, 9 Feb 2006 15:48:22 -0500 (EST)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1F7Iwj-00076H-5O; Thu, 09 Feb 2006 16:03:22 -0500
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1F7Ijq-0000Lb-92; Thu, 09 Feb 2006 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1F7Ijq-0000Lb-92@newodin.ietf.org>
Date: Thu, 09 Feb 2006 15:50:02 -0500
X-Spam-Score: 0.4 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: crisp@ietf.org
Subject: [Crisp] I-D ACTION:draft-ietf-crisp-iris-xpc-03.txt 
X-BeenThere: crisp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Cross Registry Information Service Protocol <crisp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/crisp>,
	<mailto:crisp-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:crisp@ietf.org>
List-Help: <mailto:crisp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/crisp>,
	<mailto:crisp-request@ietf.org?subject=subscribe>
Sender: crisp-bounces@ietf.org
Errors-To: crisp-bounces@ietf.org

--NextPart

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

	Title		: XML Pipelining with Chunks for the Information Registry Information Service
	Author(s)	: A. Newton
	Filename	: draft-ietf-crisp-iris-xpc-03.txt
	Pages		: 35
	Date		: 2006-2-9
	
This document describes a simple TCP transfer protocol for the
   Internet Registry Information Service (IRIS).  Data is transfered
   between clients and servers using chunks to achieve pipelining.

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

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


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

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


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

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

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

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

Content-Type: text/plain
Content-ID: <2006-2-9130552.I-D@ietf.org>

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

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

Content-Type: text/plain
Content-ID: <2006-2-9130552.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From crisp-bounces@ietf.org Fri Feb 10 04:46:24 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F7Ur9-0006AY-HA; Fri, 10 Feb 2006 04:46:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F7Ur5-0006A1-4W
	for crisp@megatron.ietf.org; Fri, 10 Feb 2006 04:46:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03807
	for <crisp@ietf.org>; Fri, 10 Feb 2006 04:44:25 -0500 (EST)
Received: from [193.80.224.123] (helo=kahua.nona.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F7V3s-0001tg-LU
	for crisp@ietf.org; Fri, 10 Feb 2006 04:59:33 -0500
Received: from [10.10.0.63] (nat.labs.nic.at [::ffff:83.136.33.3])
	(AUTH: PLAIN axelm, TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by pahula with esmtp; Fri, 10 Feb 2006 10:45:40 +0100
	id 0006C002.43EC60C4.00005FD1
Message-ID: <43EC60B2.6050801@enum.at>
Date: Fri, 10 Feb 2006 10:45:22 +0100
From: Alexander Mayrhofer <alexander.mayrhofer@enum.at>
Organization: enum.at GmbH
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: crisp@ietf.org, Andrew Newton <anewton@verisignlabs.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Content-Transfer-Encoding: 7bit
Cc: 
Subject: [Crisp] ENUM use cases for draft-ietf-crisp-iris-dchk-04.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

Hi,

i'm trying to apply certain ENUM use cases to the dchk-Draft, and would 
appreciate your opinions about them.

Contrary to "flat" domain registries (which means that they always operate 
on the same delegation levels [example.com vs. example2.com]), ENUM can have 
"overlapping" registrations. (eg. registries in countries with variable 
E.164 number lengths have to deal with delegation on different levels in the 
DNS tree).

Therefore, a domain name can not only be blocked by a exact match, but also 
by more/less specific label chains.

Same is true even in countries with closed numbering plans if an ENUM 
registry opts for number block type records, so that a single  record (be 
that a NS/CNAME style delegation, or a wildcard NAPTR record for "fat" 
registries) covers a whole range of numbers (eg. 100 numbers).

In both cases, a dchk query would not only need to consider the exact domain 
label, but rather more and less specifics as well, since they could prevent 
a registration of the domain in question.

eg. if the registry already contains a wildcard for *.1.2.3.4.e164.arpa, a 
dchk for 0.1.2.3.4.e164.arpa would need to indicate that the DNS space of 
this record is already occupied (same for eg. 2.3.4.e164.arpa), ideally 
pointing to the "blocking" domain object.

It could even become more complicated: Consider the case of a "fat" registry 
(which means that all NAPTRs are hold within the registry itself), where 
block allocations are represented by wildcard records, BUT numbers may be 
ported out from those blocks by the creation of more specific NAPTR records 
_within_ this block, even by other clients.

Example:

- Number block +43123 is represented in the registry by a NAPTR wildcard at 
*.3.2.1.3.4.e164.arpa (created by client A)
- client B checks for number +431234, because this number is to be ported 
out by a "more specific" NAPTR.
- dchk should indicate that there is already a less specific block, but, 
however, due to registry policy registration of the more specific number is 
nevertheless possible (or, not possible, depending even on more complicated 
policy).

So, i'd appreciate your input on the following questions:

- What status should be returned in case a domain name is blocked by a "more 
specific" or a "less specific" domain name?
   - for the case "registration not possible"
   - for the case "registration nevertheless possible"

- Which element would be used to return the "offending" domain in case of a 
"blocking" delegation: <domainVariant> does not exactly seem to fit 
(tailored for IDN?), <iris:seeAlso> seems to be a bit too generic for this...

- How can a registry indicate to a client that although the domain is 
question is "blocked" by a less specific record (eg. wildcard) it may be 
registered anyways (the "more complicated" case mentioned above)?

Please let me know if anything is unclear, and needs to be elaborated.

thanks,

Alex Mayrhofer
enum.at


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



From crisp-bounces@ietf.org Fri Feb 10 05:54:44 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F7VvI-0006Li-Jq; Fri, 10 Feb 2006 05:54:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F7VvF-0006KY-WF
	for crisp@megatron.ietf.org; Fri, 10 Feb 2006 05:54:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08152
	for <crisp@ietf.org>; Fri, 10 Feb 2006 05:52:58 -0500 (EST)
Received: from zeke.blacka.com ([69.31.8.124] helo=zeke.ecotroph.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F7W8E-0003x1-Vw
	for crisp@ietf.org; Fri, 10 Feb 2006 06:08:07 -0500
Received: from [10.0.1.105] ([::ffff:64.83.8.179])
	(AUTH: PLAIN anewton, SSL: TLSv1/SSLv3,128bits,RC4-SHA)
	by zeke.ecotroph.net with esmtp; Fri, 10 Feb 2006 05:53:45 -0500
	id 01588001.43EC70B9.00007805
In-Reply-To: <43EC60B2.6050801@enum.at>
References: <43EC60B2.6050801@enum.at>
Mime-Version: 1.0
Message-Id: <AD214F2D-5717-4845-8CD7-F6A92921BA95@hxr.us>
From: Andrew Newton <andy@hxr.us>
Subject: Re: [Crisp] ENUM use cases for draft-ietf-crisp-iris-dchk-04.txt
Date: Fri, 10 Feb 2006 05:54:15 -0500
To: Alexander Mayrhofer <alexander.mayrhofer@enum.at>
X-Mailer: Apple Mail (2.746.2)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
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>
Content-Type: multipart/mixed; boundary="===============0079114271=="
Sender: crisp-bounces@ietf.org
Errors-To: crisp-bounces@ietf.org

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--===============0079114271==
Content-Type: multipart/alternative;
	boundary="=_zeke.ecotroph.net-30727-1139568842-0001-2"

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--=_zeke.ecotroph.net-30727-1139568842-0001-2
Content-Type: text/plain; charset=us-ascii; delsp=yes; format=flowed
Content-Transfer-Encoding: 7bit

Hi Alex,

My comments in-line:

On Feb 10, 2006, at 4:45 AM, Alexander Mayrhofer wrote:
>
> eg. if the registry already contains a wildcard for *. 
> 1.2.3.4.e164.arpa, a dchk for 0.1.2.3.4.e164.arpa would need to  
> indicate that the DNS space of this record is already occupied  
> (same for eg. 2.3.4.e164.arpa), ideally pointing to the "blocking"  
> domain object.

I think we need to be careful with terminology here.  What can be put  
into DNS is a superset of what can be put into a DNS registration  
system.  A registry may not allow registrations at a level where  
there exists a wildcard, but that is not the case for DNS itself.

In forward domain registration systems, it is also not typical to  
allow a wildcard to block a registration.

> - What status should be returned in case a domain name is blocked  
> by a "more specific" or a "less specific" domain name?
>   - for the case "registration not possible"
>   - for the case "registration nevertheless possible"
>
> - Which element would be used to return the "offending" domain in  
> case of a "blocking" delegation: <domainVariant> does not exactly  
> seem to fit (tailored for IDN?), <iris:seeAlso> seems to be a bit  
> too generic for this...
>
> - How can a registry indicate to a client that although the domain  
> is question is "blocked" by a less specific record (eg. wildcard)  
> it may be registered anyways (the "more complicated" case mentioned  
> above)?
>
> Please let me know if anything is unclear, and needs to be elaborated.

I think the simple answer is that DCHK was not designed for this.   
The use case for DCHK is simple domain availability in the forward  
DNS . DCHK was originally introduced in the same draft with LWZ  
because the intent was to have a very fast service (we subsequently  
decoupled them draft-wise because of the confusion that they could  
only be used together).  It is a proper subset of DREG, and the  
intent is that registries could advertise the lightweight  
availability service in S-NAPTR on boxes different from the heavier  
weight DREG (this is a strategy that some domain registries use today).

Of course, there are ways to overload the semantics in DCHK to get  
what you want using things like the <other> status and <seeAlso>.   
But my feeling is that what you want is far enough from the forward  
domain availability check use case that using DCHK would work but it  
would not be pretty.  It sounds to me that you have outlined a good  
need for an ECHK or identified a new use case for EREG2.

-andy
--=_zeke.ecotroph.net-30727-1139568842-0001-2
Content-Type: text/html; charset=iso-8859-1
X-Mime-Autoconverted: from quoted-printable to quoted-printable by courier
	0.52.1
Content-Transfer-Encoding: quoted-printable

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; -kh=
tml-line-break: after-white-space; ">Hi Alex,<DIV><BR class=3D"khtml-blo=
ck-placeholder"></DIV><DIV>My comments in-line:</DIV><DIV><BR><DIV><DIV>=
On Feb 10, 2006, at 4:45 AM, Alexander Mayrhofer wrote:</DIV><BLOCKQUOTE=
 type=3D"cite"><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-=
bottom: 0px; margin-left: 0px; "><FONT class=3D"Apple-style-span" color=3D=
"#000000"><BR class=3D"khtml-block-placeholder"></FONT></DIV><DIV style=3D=
"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0p=
x; ">eg. if the registry already contains a wildcard for *.1.2.3.4.e164.=
arpa, a dchk for 0.1.2.3.4.e164.arpa would need to indicate that the DNS=
 space of this record is already occupied (same for eg. 2.3.4.e164.arpa)=
, ideally pointing to the "blocking" domain object.</DIV></BLOCKQUOTE><D=
IV><BR class=3D"khtml-block-placeholder"></DIV><DIV>I think we need to b=
e careful with terminology here.=A0 What can be put into DNS is a supers=
et of what can be put into a DNS registration system.=A0 A registry may =
not allow registrations at a level where there exists a wildcard, but th=
at is not the case for DNS itself.</DIV><DIV><BR class=3D"khtml-block-pl=
aceholder"></DIV><DIV>In forward domain registration systems, it is also=
 not typical to allow a wildcard to block a registration.</DIV><BR><BLOC=
KQUOTE type=3D"cite"><DIV style=3D"margin-top: 0px; margin-right: 0px; m=
argin-bottom: 0px; margin-left: 0px; ">- What status should be returned =
in case a domain name is blocked by a "more specific" or a "less specifi=
c" domain name?</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; m=
argin-bottom: 0px; margin-left: 0px; "><SPAN class=3D"Apple-converted-sp=
ace">=A0 </SPAN>- for the case "registration not possible"</DIV><DIV sty=
le=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-lef=
t: 0px; "><SPAN class=3D"Apple-converted-space">=A0 </SPAN>- for the cas=
e "registration nevertheless possible"</DIV><DIV style=3D"margin-top: 0p=
x; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; marg=
in-bottom: 0px; margin-left: 0px; ">- Which element would be used to ret=
urn the "offending" domain in case of a "blocking" delegation: &lt;domai=
nVariant&gt; does not exactly seem to fit (tailored for IDN?), &lt;iris:=
seeAlso&gt; seems to be a bit too generic for this...</DIV><DIV style=3D=
"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0p=
x; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-r=
ight: 0px; margin-bottom: 0px; margin-left: 0px; ">- How can a registry =
indicate to a client that although the domain is question is "blocked" b=
y a less specific record (eg. wildcard) it may be registered anyways (th=
e "more complicated" case mentioned above)?</DIV><DIV style=3D"margin-to=
p: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-hei=
ght: 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px;=
 margin-bottom: 0px; margin-left: 0px; ">Please let me know if anything =
is unclear, and needs to be elaborated.</DIV></BLOCKQUOTE></DIV><BR clas=
s=3D"khtml-block-placeholder"></DIV><DIV>I think the simple answer is th=
at DCHK was not designed for this.=A0 The use case for DCHK is simple do=
main availability in the forward DNS . DCHK was originally introduced in=
 the same draft with LWZ because the intent was to have a very fast serv=
ice (we subsequently decoupled them draft-wise because of the confusion =
that they could only be used together).=A0 It is a proper subset of DREG=
, and the intent is that registries could advertise the lightweight avai=
lability service in S-NAPTR on boxes different from the heavier weight D=
REG (this is a strategy that some domain registries use today).</DIV><DI=
V><BR class=3D"khtml-block-placeholder"></DIV><DIV>Of course, there are =
ways to overload the semantics in DCHK to get what you want using things=
 like the &lt;other&gt; status and &lt;seeAlso&gt;.=A0 But my feeling is=
 that what you want is far enough from the forward domain availability c=
heck use case that using DCHK would work but it would not be pretty.=A0 =
It sounds to me that you have outlined a good need for an ECHK or identi=
fied a new use case for EREG2.</DIV><DIV><BR class=3D"khtml-block-placeh=
older"></DIV><DIV>-andy</DIV></BODY></HTML>
--=_zeke.ecotroph.net-30727-1139568842-0001-2--


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

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

--===============0079114271==--




From crisp-bounces@ietf.org Fri Feb 10 11:17:12 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F7axM-0006u4-BA; Fri, 10 Feb 2006 11:17:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F7axK-0006tE-Vx
	for crisp@megatron.ietf.org; Fri, 10 Feb 2006 11:17:11 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03991
	for <crisp@ietf.org>; Fri, 10 Feb 2006 11:15:17 -0500 (EST)
Received: from mx3.nominet.org.uk ([213.248.199.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F7bAC-0006vt-38
	for crisp@ietf.org; Fri, 10 Feb 2006 11:30:29 -0500
Received: from staff.nominet.org.uk ([213.248.199.129])
	by mx3.nominet.org.uk with ESMTP; 10 Feb 2006 16:16:34 +0000
X-IronPort-AV: i="4.02,103,1139184000"; d="scan'208"; a="2746069:sNHT22103996"
Received: (from geoff@localhost)
	by staff.nominet.org.uk (8.12.9/8.12.9) id k1AGGYsc004885
	for crisp@ietf.org; Fri, 10 Feb 2006 16:16:34 GMT
Date: Fri, 10 Feb 2006 16:16:34 GMT
From: Geoffrey Sisson <geoff@nominet.org.uk>
Message-Id: <200602101616.k1AGGYsc004885@staff.nominet.org.uk>
To: crisp@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Subject: [Crisp] dchk-04, lwz-05 nits
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

Minor nits:

In dchk-04:

In the example in 3.1.1 the status is <activeAndAssigned/>, but
this should be <assignedAndActive/>

In lwz-05:

schemaLocation in Figure 5 contains "iris.xsd" but the one in Figure 6
contains "iris1.xsd".  Neither is correct or incorrect, but might be
better to have both the same.

Sorry I didn't see these before the recent revs. :(

Geoff

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



From crisp-bounces@ietf.org Fri Feb 10 11:28:05 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F7b7t-0005kq-Ka; Fri, 10 Feb 2006 11:28:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F7b7r-0005gn-Lv
	for crisp@megatron.ietf.org; Fri, 10 Feb 2006 11:28:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05389
	for <crisp@ietf.org>; Fri, 10 Feb 2006 11:26:09 -0500 (EST)
Received: from shell-ng.nominum.com ([81.200.64.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F7bKi-0007XW-Rc
	for crisp@ietf.org; Fri, 10 Feb 2006 11:41:22 -0500
Received: from shell-ng.nominum.com (shell-ng.nominum.com [81.200.64.181])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by shell-ng.nominum.com (Postfix) with ESMTP id B28D1568FA;
	Fri, 10 Feb 2006 08:27:37 -0800 (PST)
	(envelope-from amarine@nominum.com)
Date: Fri, 10 Feb 2006 08:27:37 -0800 (PST)
From: April Marine <April.Marine@nominum.com>
To: Geoffrey Sisson <geoff@nominet.org.uk>
Subject: Re: [Crisp] dchk-04, lwz-05 nits
In-Reply-To: <200602101616.k1AGGYsc004885@staff.nominet.org.uk>
Message-ID: <20060210082718.M22930@shell-ng.nominum.com>
References: <200602101616.k1AGGYsc004885@staff.nominet.org.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
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

wow, thanks for such a careful reading, *especially* at this point in the 
docs life!

April

On Fri, 10 Feb 2006, Geoffrey Sisson wrote:

> Minor nits:
>
> In dchk-04:
>
> In the example in 3.1.1 the status is <activeAndAssigned/>, but
> this should be <assignedAndActive/>
>
> In lwz-05:
>
> schemaLocation in Figure 5 contains "iris.xsd" but the one in Figure 6
> contains "iris1.xsd".  Neither is correct or incorrect, but might be
> better to have both the same.
>
> Sorry I didn't see these before the recent revs. :(
>
> Geoff
>
> _______________________________________________
> 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 Mon Feb 27 06:30:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FDga1-0008KH-JC; Mon, 27 Feb 2006 06:30:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FDga0-0008K9-L9
	for crisp@ietf.org; Mon, 27 Feb 2006 06:30:16 -0500
Received: from [216.151.193.226] (helo=cwhois1.completewhois.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FDgZz-0006db-6m
	for crisp@ietf.org; Mon, 27 Feb 2006 06:30:16 -0500
Received: from cwhois1.completewhois.com (localhost.localdomain [127.0.0.1])
	by cwhois1.completewhois.com (8.13.4/8.13.4) with ESMTP id
	k1RDIgwJ025381 for <crisp@ietf.org>; Mon, 27 Feb 2006 05:18:44 -0800
Received: from localhost (william@localhost)
	by cwhois1.completewhois.com (8.13.4/8.13.4/Submit) with ESMTP id
	k1RDIf75025298 for <crisp@ietf.org>; Mon, 27 Feb 2006 05:18:42 -0800
X-Authentication-Warning: cwhois1.completewhois.com: william owned process
	doing -bs
Date: Mon, 27 Feb 2006 05:18:41 -0800 (PST)
From: William Leibzon <william@completewhois.com>
To: CRISP WG <crisp@ietf.org>
Message-ID: <Pine.LNX.4.64.0602270503580.9385@cwhois1.completewhois.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Subject: [Crisp] IRIS-LWZ and security issues due to spoofed sources
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>
Errors-To: crisp-bounces@ietf.org


There have been a lot of discussions going on in the last few days
at NANOG and other dns operations lists that are related to issue of
public recursive dns servers being used way to amplify an attack:
  http://www.gossamer-threads.com/lists/nanog/users/89657
  http://lists.oarci.net/pipermail/dns-operations/2006-February/thread.html

The general description of the problem is that bad guys are sending
spoofed udp packets to servers in a way so that the servers would send 
data (to spoofed source) that is considerably larger then the original 
request - thus the amplification. For more information, you may want 
to read http://www.us-cert.gov/reading_room/DNS-recursion121605.pdf

Now it occurs to me that the same problem may also happen with those
using IRIS-LWZ UDP method as IRIS response is very likely to be larger 
then original request and thus there is a possibility of amplification.

So before its too late and IRIS-LWS draft is published as an RFC,
I think we need to have this possiblity documented in the Security 
Considerations section (which is rather small right now...) and try
to come up with some suggestions on how to deal with the problem when 
people want to run public IRIS server.

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



From crisp-bounces@ietf.org Mon Feb 27 06:51:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FDguH-0001aH-5O; Mon, 27 Feb 2006 06:51:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FDguG-0001a0-3U
	for crisp@ietf.org; Mon, 27 Feb 2006 06:51:12 -0500
Received: from [216.151.193.226] (helo=cwhois1.completewhois.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FDguE-0007Ey-K4
	for crisp@ietf.org; Mon, 27 Feb 2006 06:51:12 -0500
Received: from cwhois1.completewhois.com (localhost.localdomain [127.0.0.1])
	by cwhois1.completewhois.com (8.13.4/8.13.4) with ESMTP id
	k1RDddFi028044 for <crisp@ietf.org>; Mon, 27 Feb 2006 05:39:40 -0800
Received: from localhost (william@localhost)
	by cwhois1.completewhois.com (8.13.4/8.13.4/Submit) with ESMTP id
	k1RDddRK028041 for <crisp@ietf.org>; Mon, 27 Feb 2006 05:39:39 -0800
X-Authentication-Warning: cwhois1.completewhois.com: william owned process
	doing -bs
Date: Mon, 27 Feb 2006 05:39:39 -0800 (PST)
From: William Leibzon <william@completewhois.com>
To: CRISP WG <crisp@ietf.org>
Subject: Re: [Crisp] IRIS-LWZ and security issues due to spoofed sources
In-Reply-To: <Pine.LNX.4.64.0602270503580.9385@cwhois1.completewhois.com>
Message-ID: <Pine.LNX.4.64.0602270532250.9385@cwhois1.completewhois.com>
References: <Pine.LNX.4.64.0602270503580.9385@cwhois1.completewhois.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
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>
Errors-To: crisp-bounces@ietf.org


BTW - Don't assume that this is quite as much an issue for IRIS as it is
for DNS. While the problem is basicly the same, the number of IRIS servers
that are going to be run around this world is likely going to be several
orders of magnitude smaller then number of dns servers so really number of 
targets for miscreants to abuse would be very small and they would have to 
send lots of requests to each server to accomplish something.

So the issue would be for IRIS server operators is to know that spoofed 
pockets are possibility and this is something that miscreants can use for
amplification attack (so don't send too large a response to anonymous udp 
request) and deploy mechanisms that stop sending responses if too many
requests appear from particular source through IRIS-LWZ.

On Mon, 27 Feb 2006, William Leibzon wrote:

> There have been a lot of discussions going on in the last few days
> at NANOG and other dns operations lists that are related to issue of
> public recursive dns servers being used way to amplify an attack:
> http://www.gossamer-threads.com/lists/nanog/users/89657
> http://lists.oarci.net/pipermail/dns-operations/2006-February/thread.html
>
> The general description of the problem is that bad guys are sending
> spoofed udp packets to servers in a way so that the servers would send data 
> (to spoofed source) that is considerably larger then the original request - 
> thus the amplification. For more information, you may want to read 
> http://www.us-cert.gov/reading_room/DNS-recursion121605.pdf
>
> Now it occurs to me that the same problem may also happen with those
> using IRIS-LWZ UDP method as IRIS response is very likely to be larger then 
> original request and thus there is a possibility of amplification.
>
> So before its too late and IRIS-LWS draft is published as an RFC,
> I think we need to have this possiblity documented in the Security 
> Considerations section (which is rather small right now...) and try
> to come up with some suggestions on how to deal with the problem when people 
> want to run public IRIS server.
>
> ---
> 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 Mon Feb 27 08:08:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FDi6p-000680-Mj; Mon, 27 Feb 2006 08:08:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FDi6n-00067s-VN
	for crisp@ietf.org; Mon, 27 Feb 2006 08:08:13 -0500
Received: from postman.ripe.net ([193.0.0.199])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FDi6m-000115-Gl
	for crisp@ietf.org; Mon, 27 Feb 2006 08:08:13 -0500
Received: by postman.ripe.net (Postfix, from userid 4008)
	id EAC3C24115; Mon, 27 Feb 2006 14:08:11 +0100 (CET)
Received: from herring.ripe.net (herring.ripe.net [193.0.1.203])
	by postman.ripe.net (Postfix) with ESMTP id E71DA23EF4;
	Mon, 27 Feb 2006 14:08:10 +0100 (CET)
Received: from [193.0.1.17] (x17.ripe.net [193.0.1.17])
	by herring.ripe.net (Postfix) with ESMTP id DFB9A2F592;
	Mon, 27 Feb 2006 14:08:10 +0100 (CET)
Message-ID: <4402F9BA.6050903@ripe.net>
Date: Mon, 27 Feb 2006 14:08:10 +0100
From: Shane Kerr <shane@ripe.net>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051011)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: William Leibzon <william@completewhois.com>
Subject: Re: [Crisp] IRIS-LWZ and security issues due to spoofed sources
References: <Pine.LNX.4.64.0602270503580.9385@cwhois1.completewhois.com>
	<Pine.LNX.4.64.0602270532250.9385@cwhois1.completewhois.com>
In-Reply-To: <Pine.LNX.4.64.0602270532250.9385@cwhois1.completewhois.com>
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-RIPE-Spam-Level: 
X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00
X-RIPE-Spam-Status: N 0.000000 / -5.9
X-RIPE-Signature: d1e1eea1a18ea41251118bc60c4fdc21
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
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>
Errors-To: crisp-bounces@ietf.org

William,

I can only think of a couple of solutions, neither of which is very
attractive.

The first is to require that requestor packets be as big as or larger
than the response. This is bad for everyone involved, and requires that
the client know how big the response will/can be (this might be easy
with dchk, I don't know).

The second is to limit the responses, depending on client identifier.
For anonymous users this will have to be client IP address. AFAIK, all
Whois public servers do this now. This breaks down for IPv6: because
each user gets 2^80 different addresses (or at least 2^64), some sort of
aggregation is necessary unless your server can track that many
addresses. The problem with aggregation is punishing the wrong person,
leading to DoS attack against the service (imagine preventing an entire
university from querying the IRIS server by spoofing a lot of packets
from their network).

Since this is a general UDP problem, perhaps it makes sense to point to
another document for this problem. Is there such a thing?

--
Shane

William Leibzon wrote:

>
> BTW - Don't assume that this is quite as much an issue for IRIS as it is
> for DNS. While the problem is basicly the same, the number of IRIS
> servers
> that are going to be run around this world is likely going to be several
> orders of magnitude smaller then number of dns servers so really
> number of targets for miscreants to abuse would be very small and they
> would have to send lots of requests to each server to accomplish
> something.
>
> So the issue would be for IRIS server operators is to know that
> spoofed pockets are possibility and this is something that miscreants
> can use for
> amplification attack (so don't send too large a response to anonymous
> udp request) and deploy mechanisms that stop sending responses if too
> many
> requests appear from particular source through IRIS-LWZ.
>
> On Mon, 27 Feb 2006, William Leibzon wrote:
>
>> There have been a lot of discussions going on in the last few days
>> at NANOG and other dns operations lists that are related to issue of
>> public recursive dns servers being used way to amplify an attack:
>> http://www.gossamer-threads.com/lists/nanog/users/89657
>> http://lists.oarci.net/pipermail/dns-operations/2006-February/thread.html
>>
>>
>> The general description of the problem is that bad guys are sending
>> spoofed udp packets to servers in a way so that the servers would
>> send data (to spoofed source) that is considerably larger then the
>> original request - thus the amplification. For more information, you
>> may want to read
>> http://www.us-cert.gov/reading_room/DNS-recursion121605.pdf
>>
>> Now it occurs to me that the same problem may also happen with those
>> using IRIS-LWZ UDP method as IRIS response is very likely to be
>> larger then original request and thus there is a possibility of
>> amplification.
>>
>> So before its too late and IRIS-LWS draft is published as an RFC,
>> I think we need to have this possiblity documented in the Security
>> Considerations section (which is rather small right now...) and try
>> to come up with some suggestions on how to deal with the problem when
>> people want to run public IRIS server.
>


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



From crisp-bounces@ietf.org Mon Feb 27 09:46:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FDjde-0006jc-N2; Mon, 27 Feb 2006 09:46:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FDjdd-0006jU-3B
	for crisp@ietf.org; Mon, 27 Feb 2006 09:46:13 -0500
Received: from zeke.toscano.org ([69.31.8.124] helo=zeke.ecotroph.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FDjdZ-0004ud-Oq
	for crisp@ietf.org; Mon, 27 Feb 2006 09:46:13 -0500
Received: from [10.131.244.248] ([::ffff:216.168.239.87])
	(AUTH: PLAIN anewton, SSL: TLSv1/SSLv3,128bits,RC4-SHA)
	by zeke.ecotroph.net with esmtp; Mon, 27 Feb 2006 09:40:23 -0500
	id 01588071.44030F57.00003763
In-Reply-To: <4402F9BA.6050903@ripe.net>
References: <Pine.LNX.4.64.0602270503580.9385@cwhois1.completewhois.com>
	<Pine.LNX.4.64.0602270532250.9385@cwhois1.completewhois.com>
	<4402F9BA.6050903@ripe.net>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <40753247-0679-43EA-AF0D-2C5A35F5144A@hxr.us>
Content-Transfer-Encoding: 7bit
From: Andrew Newton <andy@hxr.us>
Subject: Re: [Crisp] IRIS-LWZ and security issues due to spoofed sources
Date: Mon, 27 Feb 2006 09:41:08 -0500
To: Shane Kerr <shane@ripe.net>
X-Mailer: Apple Mail (2.746.2)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: CRISP WG <crisp@ietf.org>, William Leibzon <william@completewhois.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>
Errors-To: crisp-bounces@ietf.org


On Feb 27, 2006, at 8:08 AM, Shane Kerr wrote:

> Since this is a general UDP problem, perhaps it makes sense to  
> point to
> another document for this problem. Is there such a thing?

That was gonna be my first question:  just how do they mitigate this  
with DNS?  Or DHCP?  Or anything else that uses UDP?  It seems BCP 78  
is applicable to this.

Also, I was under the assumption that an amplification attack  
resulted in an order of magnitude higher response.  In other words,  
if I send a 100 byte packet, the amplification is in hundreds of  
times higher bytes and usually across multiple packets.  Perhaps if  
we could get a pointer to the classic attack scenario that would help.

According to this:
http://www.lancs.ac.uk/postgrad/pissias/netsec/ddos/index.html
There really are two types of attacks: reflection attacks and  
amplification attacks.  As any interesting as reflection attacks are,  
they don't seem to be that much more gain than a direct attack.  The  
amplification attack usually yields a 300 to 400 times magnification,  
which I do not think IRIS would do.

More reading from CERT:
http://www.cert.org/incident_notes/IN-2000-04.html
The problem, it would seem, in the DNS world is a recursive name  
server configured to answer for anybody.  I don't think this is  
applicable to IRIS.

-andy

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



From crisp-bounces@ietf.org Mon Feb 27 09:58:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FDjpY-0005Ln-3B; Mon, 27 Feb 2006 09:58:32 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FDjpW-0005Ja-Ck
	for crisp@ietf.org; Mon, 27 Feb 2006 09:58:30 -0500
Received: from zeke.toscano.org ([69.31.8.124] helo=zeke.ecotroph.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FDjpV-0005GM-6e
	for crisp@ietf.org; Mon, 27 Feb 2006 09:58:30 -0500
Received: from [10.131.244.248] ([::ffff:216.168.239.87])
	(AUTH: PLAIN anewton, SSL: TLSv1/SSLv3,128bits,RC4-SHA)
	by zeke.ecotroph.net with esmtp; Mon, 27 Feb 2006 09:57:44 -0500
	id 01588063.44031368.00003AC6
In-Reply-To: <40753247-0679-43EA-AF0D-2C5A35F5144A@hxr.us>
References: <Pine.LNX.4.64.0602270503580.9385@cwhois1.completewhois.com>
	<Pine.LNX.4.64.0602270532250.9385@cwhois1.completewhois.com>
	<4402F9BA.6050903@ripe.net>
	<40753247-0679-43EA-AF0D-2C5A35F5144A@hxr.us>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <A2AB5551-5320-4D28-B42A-5C67B7617DA2@hxr.us>
Content-Transfer-Encoding: 7bit
From: Andrew Newton <andy@hxr.us>
Subject: Re: [Crisp] IRIS-LWZ and security issues due to spoofed sources
Date: Mon, 27 Feb 2006 09:58:31 -0500
To: CRISP WG <crisp@ietf.org>
X-Mailer: Apple Mail (2.746.2)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Cc: Shane Kerr <shane@ripe.net>, William Leibzon <william@completewhois.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>
Errors-To: crisp-bounces@ietf.org


On Feb 27, 2006, at 9:41 AM, Andrew Newton wrote:

> It seems BCP 78 is applicable to this.

Sorry.  BCP 38.
ftp://ftp.isi.edu/in-notes/rfc2827.txt

-andy

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



From crisp-bounces@ietf.org Mon Feb 27 10:01:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FDjrs-0006p2-Mp; Mon, 27 Feb 2006 10:00:56 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FDjrq-0006ol-9Z
	for crisp@ietf.org; Mon, 27 Feb 2006 10:00:55 -0500
Received: from [216.151.193.226] (helo=cwhois1.completewhois.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FDjrn-0005Lz-RN
	for crisp@ietf.org; Mon, 27 Feb 2006 10:00:54 -0500
Received: from cwhois1.completewhois.com (localhost.localdomain [127.0.0.1])
	by cwhois1.completewhois.com (8.13.4/8.13.4) with ESMTP id
	k1RGnIhV000917; Mon, 27 Feb 2006 08:49:18 -0800
Received: from localhost (william@localhost)
	by cwhois1.completewhois.com (8.13.4/8.13.4/Submit) with ESMTP id
	k1RGnIsa000913; Mon, 27 Feb 2006 08:49:18 -0800
X-Authentication-Warning: cwhois1.completewhois.com: william owned process
	doing -bs
Date: Mon, 27 Feb 2006 08:49:18 -0800 (PST)
From: William Leibzon <william@completewhois.com>
To: Andrew Newton <andy@hxr.us>
Subject: Re: [Crisp] IRIS-LWZ and security issues due to spoofed sources
In-Reply-To: <40753247-0679-43EA-AF0D-2C5A35F5144A@hxr.us>
Message-ID: <Pine.LNX.4.64.0602270837050.9385@cwhois1.completewhois.com>
References: <Pine.LNX.4.64.0602270503580.9385@cwhois1.completewhois.com>
	<Pine.LNX.4.64.0602270532250.9385@cwhois1.completewhois.com>
	<4402F9BA.6050903@ripe.net>
	<40753247-0679-43EA-AF0D-2C5A35F5144A@hxr.us>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
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>
Errors-To: crisp-bounces@ietf.org


On Mon, 27 Feb 2006, Andrew Newton wrote:

>
> On Feb 27, 2006, at 8:08 AM, Shane Kerr wrote:
>
>> Since this is a general UDP problem, perhaps it makes sense to point to
>> another document for this problem. Is there such a thing?
>
> That was gonna be my first question:  just how do they mitigate this with 
> DNS?  Or DHCP?  Or anything else that uses UDP?

They don't deal with it very well. But there are actually only few protocols
to which it is applicable since most protocols that use UDP would do it for
things like creating a data stream that is not subject to TCP retransmission.
In those cases real transmission does not begin until response is received
from originator - i.e. they simulate TCP in a way and do create a sort of
a session before larger amount of data is sent.

Where it is applicable is one-query request/response protocols which are
only few (most use TCP) such as DNS and DHCP. For DHCP the solution is 
simply that DHCP servers only  respond to requests from within local lan 
and not to whole world. For dns there is no good solution that everyone
likes - hence current set of discussions on how to deal with this issue
at operational mail lists.

> It seems BCP 78 is applicable to this.

You mean BCP 38 (RFC2827), right?

> Also, I was under the assumption that an amplification attack resulted in an 
> order of magnitude higher response.  In other words, if I send a 100 byte 
> packet, the amplification is in hundreds of times higher bytes and usually 
> across multiple packets.  Perhaps if we could get a pointer to the classic 
> attack scenario that would help.

Anything that is several times greater then what originator sent has an
amplification use potential. The highier the difference the more likely
it is that it would began tobe used for malicious reasons.

> According to this:
> http://www.lancs.ac.uk/postgrad/pissias/netsec/ddos/index.html
> There really are two types of attacks: reflection attacks and amplification 
> attacks.  As any interesting as reflection attacks are, they don't seem to be 
> that much more gain than a direct attack.  The amplification attack usually 
> yields a 300 to 400 times magnification, which I do not think IRIS would do.

Yes, 300 to 400 is too much and the reasons for abuse of dns right now is
exactly because it does offer potential for big amplication (not 300 to 
400 but with recursion, use of ANY and large txt records, it could get 
into 1:100 difference - which is more then good enough for attacker)

> More reading from CERT:
> http://www.cert.org/incident_notes/IN-2000-04.html
> The problem, it would seem, in the DNS world is a recursive name server 
> configured to answer for anybody.  I don't think this is applicable to IRIS.
>
> -andy
>
> _______________________________________________
> Crisp mailing list
> Crisp@ietf.org
> https://www1.ietf.org/mailman/listinfo/crisp

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



From crisp-bounces@ietf.org Mon Feb 27 10:17:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FDk8J-0006wa-05; Mon, 27 Feb 2006 10:17:55 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FDk8H-0006wR-RA
	for crisp@ietf.org; Mon, 27 Feb 2006 10:17:53 -0500
Received: from [216.151.193.226] (helo=cwhois1.completewhois.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FDk8G-000604-E8
	for crisp@ietf.org; Mon, 27 Feb 2006 10:17:53 -0500
Received: from cwhois1.completewhois.com (localhost.localdomain [127.0.0.1])
	by cwhois1.completewhois.com (8.13.4/8.13.4) with ESMTP id
	k1RH6MOJ001289; Mon, 27 Feb 2006 09:06:22 -0800
Received: from localhost (william@localhost)
	by cwhois1.completewhois.com (8.13.4/8.13.4/Submit) with ESMTP id
	k1RH6LXR001286; Mon, 27 Feb 2006 09:06:21 -0800
X-Authentication-Warning: cwhois1.completewhois.com: william owned process
	doing -bs
Date: Mon, 27 Feb 2006 09:06:21 -0800 (PST)
From: William Leibzon <william@completewhois.com>
To: Andrew Newton <andy@hxr.us>
Subject: Re: [Crisp] IRIS-LWZ and security issues due to spoofed sources
In-Reply-To: <Pine.LNX.4.64.0602270837050.9385@cwhois1.completewhois.com>
Message-ID: <Pine.LNX.4.64.0602270856470.9385@cwhois1.completewhois.com>
References: <Pine.LNX.4.64.0602270503580.9385@cwhois1.completewhois.com>
	<Pine.LNX.4.64.0602270532250.9385@cwhois1.completewhois.com>
	<4402F9BA.6050903@ripe.net>
	<40753247-0679-43EA-AF0D-2C5A35F5144A@hxr.us>
	<Pine.LNX.4.64.0602270837050.9385@cwhois1.completewhois.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
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>
Errors-To: crisp-bounces@ietf.org


On Mon, 27 Feb 2006, William Leibzon wrote:

> On Mon, 27 Feb 2006, Andrew Newton wrote:
>> 
>> On Feb 27, 2006, at 8:08 AM, Shane Kerr wrote:
>> 
>>> Since this is a general UDP problem, perhaps it makes sense to point to
>>> another document for this problem. Is there such a thing?
>> 
>> That was gonna be my first question:  just how do they mitigate this with 
>> DNS?  Or DHCP?  Or anything else that uses UDP?
>
> They don't deal with it very well. But there are actually only few protocols
> to which it is applicable since most protocols that use UDP would do it for
> things like creating a data stream that is not subject to TCP retransmission.
> In those cases real transmission does not begin until response is received
> from originator - i.e. they simulate TCP in a way and do create a sort of
> a session before larger amount of data is sent.
>
> Where it is applicable is one-query request/response protocols which are
> only few (most use TCP) such as DNS and DHCP. For DHCP the solution is 
> simply that DHCP servers only  respond to requests from within local 
> lan and not to whole world. For dns there is no good solution that 
> everyone likes - hence current set of discussions on how to deal with 
> this issue at operational mail lists.

Just so you know - in dns the recursion is being used as a way to cause 
responder to send back large data where it would normally not have done
it (this is kind-of poisoning) as there are only few sites that have 
large dns records and are good amplification potential as-is [this 
reminds me that I need to bring this issue up on DKIM since it is
going to introduce large dns records which as I said many times is
really not a good thing to have].

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



From crisp-bounces@ietf.org Tue Feb 28 18:50:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FEEbl-0008Ri-53; Tue, 28 Feb 2006 18:50:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FEEbT-0008Hq-UI; Tue, 28 Feb 2006 18:50:03 -0500
Received: from [156.154.16.129] (helo=cypress.neustar.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FEEbT-0005hq-2q; Tue, 28 Feb 2006 18:50:03 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by cypress.neustar.com (8.12.8/8.12.8) with ESMTP id k1SNo20e030662
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 28 Feb 2006 23:50:02 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1FEEbS-0006vi-FP; Tue, 28 Feb 2006 18:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1FEEbS-0006vi-FP@stiedprstage1.ietf.org>
Date: Tue, 28 Feb 2006 18:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: crisp@ietf.org
Subject: [Crisp] I-D ACTION:draft-ietf-crisp-iris-dreg2-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>
Errors-To: crisp-bounces@ietf.org

--NextPart

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

	Title		: Domain Registry Version 2 for the Internet        
                          Registry Information Service
	Author(s)	: A. Newton, F. Neves
	Filename	: draft-ietf-crisp-iris-dreg2-00.txt
	Pages		: 93
	Date		: 2006-2-28
	
   This document describes version 2 of the domain registration
   information schema for IRIS.  The schema extends the necessary query
   and result operations of IRIS to provide the functional information
   service needs for syntaxes and results used by domain registries and
   registrars.

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

ENCODING mime
FILE /internet-drafts/draft-ietf-crisp-iris-dreg2-00.txt

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

Content-Type: text/plain
Content-ID: <2006-2-28155617.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--




