Re: [v6tc] Issue 1: Could we live with UDP encapsulation always on?

Pekka Savola <pekkas@netcore.fi> Fri, 17 December 2004 10:46 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04038; Fri, 17 Dec 2004 05:46:56 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfFm5-0008GC-Ny; Fri, 17 Dec 2004 05:55:53 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CfFXD-0004dr-CR; Fri, 17 Dec 2004 05:40:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CfFSu-0003N8-Mx for v6tc@megatron.ietf.org; Fri, 17 Dec 2004 05:36:04 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03234 for <v6tc@ietf.org>; Fri, 17 Dec 2004 05:36:02 -0500 (EST)
Received: from netcore.fi ([193.94.160.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfFbV-0007vg-TW for v6tc@ietf.org; Fri, 17 Dec 2004 05:44:59 -0500
Received: from localhost (pekkas@localhost) by netcore.fi (8.11.6/8.11.6) with ESMTP id iBHAZFR19934; Fri, 17 Dec 2004 12:35:17 +0200
Date: Fri, 17 Dec 2004 12:35:15 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: Jeroen Massar <jeroen@unfix.org>
Subject: Re: [v6tc] Issue 1: Could we live with UDP encapsulation always on?
In-Reply-To: <1103278369.25975.57.camel@firenze.zurich.ibm.com>
Message-ID: <Pine.LNX.4.61.0412171231230.19294@netcore.fi>
References: <6D2CE1A0-5011-11D9-81E4-00039358A080@sun.com> <1103278369.25975.57.camel@firenze.zurich.ibm.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: Alain Durand <Alain.Durand@sun.com>, v6tc@ietf.org
X-BeenThere: v6tc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: v6tc.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/v6tc>, <mailto:v6tc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/v6tc>
List-Post: <mailto:v6tc@ietf.org>
List-Help: <mailto:v6tc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/v6tc>, <mailto:v6tc-request@ietf.org?subject=subscribe>
Sender: v6tc-bounces@ietf.org
Errors-To: v6tc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb

>From Alain:
> Obviously the first thing to consider is the UDP overhead. When the 
> payload is large, there isn't much difference, but when it is small, 
> there is a non negligible impact.

What I'd be interested in knowing here is whether the typical UDP 
header compression algorithms fix this problem automatically in those 
deployments where the extra bytes are important.

On Fri, 17 Dec 2004, Jeroen Massar wrote:
> Byte-wise you could easily 'live' with UDP encaps btw. Especially as
> proto-41 is non-authenticated and very spoof sensitive, oh hmm so is the
> protocol which is proposed in the new draft. AYIYA, which looks somewhat
> quite like the proposed protocol, does not have this issue btw...
> With people downloading movies etc, do 3 bytes per packet extra hurt?

The assumption is that if you want to protect the payload, you'll want 
to use a real security mechanism -- this is not the place to 
(try to) invent one.

> Why is there a checksum in that newly proposed protocol anyway?
> There was a reason why checksumming was removed from the IPv6 headers ;)

It is the standard UDP checksum.  The first two lines are the UDP 
header.

> PS: The mailinglist archives don't work...

Thanks for pointing that out.  I'll raise it with the IETF 
secretariat.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

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