From crisp-bounces@ietf.org Fri Apr 21 04:18:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FWqqM-0005Ns-M0; Fri, 21 Apr 2006 04:18:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FWqqK-0005Nn-SB
	for crisp@ietf.org; Fri, 21 Apr 2006 04:18:20 -0400
Received: from smtp.denic.de ([81.91.161.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FWqqJ-0008Fd-DT
	for crisp@ietf.org; Fri, 21 Apr 2006 04:18:20 -0400
Received: from notes.denic.de ([192.168.0.77]) by smtp.denic.de with esmtp 
	id 1FWqqI-00073L-NJ; Fri, 21 Apr 2006 10:18:18 +0200
To: crisp@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.5 November 30, 2005
From: Marcos Sanz/Denic <sanz@denic.de>
Message-ID: <OF680C6E97.16161DB3-ONC1257157.002CFDD6-C1257157.002D9E72@notes.denic.de>
Date: Fri, 21 Apr 2006 10:18:17 +0200
X-MIMETrack: Serialize by Router on notes/Denic at 21.04.2006 10:18:18,
	Serialize complete at 21.04.2006 10:18:18
Content-Type: text/plain; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Subject: [Crisp] Nit in lwz-05
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

Dear list,

while implementing LWZ (yes, you heard it right ;-) we have realized that 
the figure in section 3 tags "payload descriptor" with "3..261" octets.

It should be "6..261" as of section 3.1.1

Best regards,
Marcos

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



From crisp-bounces@ietf.org Tue Apr 25 09:15:10 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FYNNc-0003TG-2R; Tue, 25 Apr 2006 09:15:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FYNNb-0003TA-38
	for crisp@ietf.org; Tue, 25 Apr 2006 09:14:59 -0400
Received: from zeke.ecotroph.net ([69.31.8.124])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FYNNZ-0007gH-Tb
	for crisp@ietf.org; Tue, 25 Apr 2006 09:14:59 -0400
Received: from [127.0.0.1] ([::ffff:208.50.38.5]) (AUTH: LOGIN anewton)
	by zeke.ecotroph.net with esmtp; Tue, 25 Apr 2006 09:13:51 -0400
	id 01588063.444E208F.00005BCD
Message-ID: <444E20D4.10502@hxr.us>
Date: Tue, 25 Apr 2006 09:15:00 -0400
From: Andrew Newton <andy@hxr.us>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: "Marcos Sanz/Denic" <sanz@denic.de>
Subject: Re: [Crisp] Nit in lwz-05
References: <OF680C6E97.16161DB3-ONC1257157.002CFDD6-C1257157.002D9E72@notes.denic.de>
In-Reply-To: <OF680C6E97.16161DB3-ONC1257157.002CFDD6-C1257157.002D9E72@notes.denic.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
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>
Errors-To: crisp-bounces@ietf.org

Marcos Sanz/Denic wrote:
> Dear list,
> 
> while implementing LWZ (yes, you heard it right ;-) we have realized that 
> the figure in section 3 tags "payload descriptor" with "3..261" octets.
> 
> It should be "6..261" as of section 3.1.1
> 
> Best regards,
> Marcos

Who keeps putting bugs in these documents? :)

-andy


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



From crisp-bounces@ietf.org Tue Apr 25 09:16:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FYNP8-0003uW-3d; Tue, 25 Apr 2006 09:16:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FYNP6-0003uR-Qk
	for crisp@ietf.org; Tue, 25 Apr 2006 09:16:32 -0400
Received: from zeke.hxr.us ([69.31.8.124] helo=zeke.ecotroph.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FYNP5-0007uI-Ku
	for crisp@ietf.org; Tue, 25 Apr 2006 09:16:32 -0400
Received: from [127.0.0.1] ([::ffff:208.50.38.5]) (AUTH: LOGIN anewton)
	by zeke.ecotroph.net with esmtp; Tue, 25 Apr 2006 09:15:25 -0400
	id 0158811B.444E20EE.00005C3A
Message-ID: <444E2131.4070805@hxr.us>
Date: Tue, 25 Apr 2006 09:16:33 -0400
From: Andrew Newton <andy@hxr.us>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: Alexander Mayrhofer <alexander.mayrhofer@enum.at>
Subject: Re: [Crisp] new status for DREG2
References: <6CEB55DE-2DD5-463B-BE15-145B241D8DCF@hxr.us>
	<44291355.4000508@enum.at>
In-Reply-To: <44291355.4000508@enum.at>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
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>
Errors-To: crisp-bounces@ietf.org

Alexander Mayrhofer wrote:
> Andrew Newton wrote:
>> I had a meeting with an sTLD operator last week where it was brought to
>> my attention that they would like to mark domains with a status
>> indicating compliance with regulations not directly related to the
>> actual domain registration process... as in, they have conducted a
>> compliance check and have found that a domain holder's web site meets
>> certain accessibility requirements or internationalization requirements,
>> etc...
>>
>> To do what they would like, I think we should add a <compliant:> and
>> <noncompliant> enhanced status to the base enhanced status set in
>> DREG2.  The substatus and related authority would indicate the type of
>> compliance.
> 
> That looks to me like some "validation status" - might be very similar to
> what is used in ENUM.
> 
> Any chance to recycly valdationEvents from EREG here?

We could, but that brings validation authorities into the picture as we 
have in EREG.  I don't think those types of things exist in this space.

-andy


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



From crisp-bounces@ietf.org Tue Apr 25 10:14:17 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FYOIy-0004sH-CO; Tue, 25 Apr 2006 10:14:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FYOIx-0004sB-OW
	for crisp@ietf.org; Tue, 25 Apr 2006 10:14:15 -0400
Received: from clone.registro.br ([200.160.2.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FYOIw-0002El-EN
	for crisp@ietf.org; Tue, 25 Apr 2006 10:14:15 -0400
Received: by clone.registro.br (Postfix, from userid 1000)
	id 3F7D82A559; Tue, 25 Apr 2006 11:14:12 -0300 (BRT)
Date: Tue, 25 Apr 2006 11:14:12 -0300
From: Frederico A C Neves <fneves@registro.br>
To: Andrew Newton <andy@hxr.us>
Subject: Re: [Crisp] Nit in lwz-05
Message-ID: <20060425141412.GA95476@registro.br>
Mail-Followup-To: Frederico A C Neves <fneves@registro.br>,
	Andrew Newton <andy@hxr.us>, Marcos Sanz/Denic <sanz@denic.de>,
	crisp@ietf.org
References: <OF680C6E97.16161DB3-ONC1257157.002CFDD6-C1257157.002D9E72@notes.denic.de>
	<444E20D4.10502@hxr.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <444E20D4.10502@hxr.us>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: Marcos Sanz/Denic <sanz@denic.de>, 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

We raised this privately to Andy when implementing our prototype.

On Tue, Apr 25, 2006 at 09:15:00AM -0400, Andrew Newton wrote:
> Marcos Sanz/Denic wrote:
> >Dear list,
> >
> >while implementing LWZ (yes, you heard it right ;-) we have realized that 
> >the figure in section 3 tags "payload descriptor" with "3..261" octets.
> >
> >It should be "6..261" as of section 3.1.1
> >
> >Best regards,
> >Marcos
> 
> Who keeps putting bugs in these documents? :)
> 

We :-)

For requests the range is "6..261", but for responses the value is 3.

So "6..261" would invalidate any response.

If possible the more correct version would be [ 3 or 6..261 ]

> -andy

Fred

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



From crisp-bounces@ietf.org Wed Apr 26 04:12:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FYf8O-0007CZ-N5; Wed, 26 Apr 2006 04:12:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FYf8N-0007CK-QO
	for crisp@ietf.org; Wed, 26 Apr 2006 04:12:27 -0400
Received: from smtp.denic.de ([81.91.161.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FYf8M-0005BF-I9
	for crisp@ietf.org; Wed, 26 Apr 2006 04:12:27 -0400
Received: from notes.denic.de ([192.168.0.77]) by smtp.denic.de with esmtp 
	id 1FYf8G-0005zR-75; Wed, 26 Apr 2006 10:12:20 +0200
In-Reply-To: <20060425141412.GA95476@registro.br>
To: crisp@ietf.org
Subject: Re: [Crisp] Nit in lwz-05
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.5 November 30, 2005
From: Marcos Sanz/Denic <sanz@denic.de>
Message-ID: <OFDEFAF1FD.0255A67E-ONC125715C.002BA649-C125715C.002D12AA@notes.denic.de>
Date: Wed, 26 Apr 2006 10:12:19 +0200
X-MIMETrack: Serialize by Router on notes/Denic at 26.04.2006 10:12:20,
	Serialize complete at 26.04.2006 10:12:20
Content-Type: text/plain; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
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

Fred,

> For requests the range is "6..261", but for responses the value is 3.
> 
> So "6..261" would invalidate any response.
> 
> If possible the more correct version would be [ 3 or 6..261 ]

You are right, but what about parenthesizing a bit so that it's clear 
lengths 4 and 5 are forbidden:

3 or [6..261]

The "problem" now is that no other range in the document has square 
brackets...

Regards,
Marcos

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



From crisp-bounces@ietf.org Thu Apr 27 09:35:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FZ6eI-0006rD-4j; Thu, 27 Apr 2006 09:35:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FZ6dL-0006JB-IQ
	for crisp@ietf.org; Thu, 27 Apr 2006 09:34:15 -0400
Received: from zeke.toscano.org ([69.31.8.124] helo=zeke.ecotroph.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FZ6OY-0004HC-OM
	for crisp@ietf.org; Thu, 27 Apr 2006 09:18:58 -0400
Received: from [10.0.1.104] ([::ffff:64.83.8.179])
	(AUTH: PLAIN anewton, TLS: TLSv1/SSLv3,128bits,RC4-SHA)
	by zeke.ecotroph.net with esmtp; Thu, 27 Apr 2006 09:17:52 -0400
	id 015880FD.4450C480.000061A7
In-Reply-To: <OFDEFAF1FD.0255A67E-ONC125715C.002BA649-C125715C.002D12AA@notes.denic.de>
References: <OFDEFAF1FD.0255A67E-ONC125715C.002BA649-C125715C.002D12AA@notes.denic.de>
Mime-Version: 1.0 (Apple Message framework v749.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <8C57A05C-D5E7-4D00-B297-DAFF75C74323@hxr.us>
Content-Transfer-Encoding: 7bit
From: Andrew Newton <andy@hxr.us>
Subject: Re: [Crisp] Nit in lwz-05
Date: Thu, 27 Apr 2006 09:18:56 -0400
To: "Marcos Sanz/Denic" <sanz@denic.de>
X-Mailer: Apple Mail (2.749.3)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
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>
Errors-To: crisp-bounces@ietf.org


On Apr 26, 2006, at 4:12 AM, Marcos Sanz/Denic wrote:

> Fred,
>
>> For requests the range is "6..261", but for responses the value is 3.
>>
>> So "6..261" would invalidate any response.
>>
>> If possible the more correct version would be [ 3 or 6..261 ]
>
> You are right, but what about parenthesizing a bit so that it's clear
> lengths 4 and 5 are forbidden:
>
> 3 or [6..261]
>
> The "problem" now is that no other range in the document has square
> brackets...

How about?

3 or 6..261 *

* In request packets, the payload descriptor can vary in length from  
6 to 261 octets (i.e. 6..261).  In response packets, the payload  
descriptor is always 3 octets.

-andy

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



From crisp-bounces@ietf.org Thu Apr 27 10:07:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FZ790-0001Xr-Fb; Thu, 27 Apr 2006 10:06:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FZ78z-0001SN-27
	for crisp@ietf.org; Thu, 27 Apr 2006 10:06:57 -0400
Received: from clone.registro.br ([200.160.2.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FZ78x-00070E-Ob
	for crisp@ietf.org; Thu, 27 Apr 2006 10:06:57 -0400
Received: by clone.registro.br (Postfix, from userid 1000)
	id 5099B2A422; Thu, 27 Apr 2006 11:06:50 -0300 (BRT)
Date: Thu, 27 Apr 2006 11:06:50 -0300
From: Frederico A C Neves <fneves@registro.br>
To: Andrew Newton <andy@hxr.us>
Subject: Re: [Crisp] Nit in lwz-05
Message-ID: <20060427140650.GF95476@registro.br>
Mail-Followup-To: Frederico A C Neves <fneves@registro.br>,
	Andrew Newton <andy@hxr.us>, Marcos Sanz/Denic <sanz@denic.de>,
	crisp@ietf.org
References: <OFDEFAF1FD.0255A67E-ONC125715C.002BA649-C125715C.002D12AA@notes.denic.de>
	<8C57A05C-D5E7-4D00-B297-DAFF75C74323@hxr.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8C57A05C-D5E7-4D00-B297-DAFF75C74323@hxr.us>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: Marcos Sanz/Denic <sanz@denic.de>, 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 Thu, Apr 27, 2006 at 09:18:56AM -0400, Andrew Newton wrote:
> 
> On Apr 26, 2006, at 4:12 AM, Marcos Sanz/Denic wrote:
> 
> >Fred,
> >
> >>For requests the range is "6..261", but for responses the value is 3.
> >>
> >>So "6..261" would invalidate any response.
> >>
> >>If possible the more correct version would be [ 3 or 6..261 ]
> >
> >You are right, but what about parenthesizing a bit so that it's clear
> >lengths 4 and 5 are forbidden:
> >
> >3 or [6..261]
> >
> >The "problem" now is that no other range in the document has square
> >brackets...
> 
> How about?
> 
> 3 or 6..261 *
> 
> * In request packets, the payload descriptor can vary in length from  
> 6 to 261 octets (i.e. 6..261).  In response packets, the payload  
> descriptor is always 3 octets.
> 
> -andy

It's unambiguous. Looks good to me.

Fred

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



