Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service' to Proposed Standard (draft-ietf-crisp-iris-lwz)

Harald Alvestrand <harald@alvestrand.no> Wed, 16 August 2006 21:01 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GDSWI-0004Jd-Ug; Wed, 16 Aug 2006 17:01:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GDSWH-0004JV-Mx for ietf@ietf.org; Wed, 16 Aug 2006 17:01:45 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GDFtd-0002cY-PM for ietf@ietf.org; Wed, 16 Aug 2006 03:33:01 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GDFhW-0004MS-Di for ietf@ietf.org; Wed, 16 Aug 2006 03:20:33 -0400
Received: from localhost (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id BF3E92596CA; Wed, 16 Aug 2006 09:18:39 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03067-01; Wed, 16 Aug 2006 09:18:34 +0200 (CEST)
Received: from [127.0.0.1] (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 781022596C7; Wed, 16 Aug 2006 09:18:34 +0200 (CEST)
Message-ID: <44E2C737.8000402@alvestrand.no>
Date: Wed, 16 Aug 2006 00:20:23 -0700
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Thunderbird 1.5.0.4 (X11/20060516)
MIME-Version: 1.0
To: Andrew Newton <andy@hxr.us>
References: <E1GCknR-0004hD-Jt@stiedprstage1.ietf.org> <44E1D050.F9A@xyzzy.claranet.de> <44E1EAEF.3030505@hxr.us>
In-Reply-To: <44E1EAEF.3030505@hxr.us>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: -2.5 (--)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: ietf@ietf.org
Subject: Re: Last Call: 'A Lightweight UDP Transfer Protocol for the the Internet Registry Information Service' to Proposed Standard (draft-ietf-crisp-iris-lwz)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

Andrew Newton wrote:
>> 3 - Why is LWZ limited to UDP, desperately trying to solve
>>     various size issues with delated XML and other tricks ?
>
> TCP is handled by XPC and BEEP.  But for very short and quick answers 
> (and lots of them, such as domain availability checks) UDP is better.  
> Don't know what you mean by tricks, but the deflation is optional.
my congestion control alarm went off.

after reviewing the document, it's still ringing.

There's nothing in the document that says "if you want to send 4000 
requests, and 70 out of the first 100 get lost, you should slow down 
your sending rate to that server".

The word "retransmit" does not occur in the document.
The word "packet loss" does not occur in the document.
The word "congestion" does not occur in the document.

4000-byte UDP packets will have 3x the drop rate of 1500-byte UDP 
packets. So retransmissions are more likely than with DNS over the same 
wire. I can't envision an implementation of this that wouldn't 
retransmit. So guidance is needed.

Using UDP is fine, but I regard this specification as incomplete.

                       Harald





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