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

Jeroen Massar <jeroen@unfix.org> Fri, 17 December 2004 11:48 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 GAA08324; Fri, 17 Dec 2004 06:48:26 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfGjc-0001QH-Mk; Fri, 17 Dec 2004 06:57:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CfGWr-0008Oh-0X; Fri, 17 Dec 2004 06:44:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CfGP4-0006KF-Cx for v6tc@megatron.ietf.org; Fri, 17 Dec 2004 06:36:10 -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 GAA07412 for <v6tc@ietf.org>; Fri, 17 Dec 2004 06:36:07 -0500 (EST)
Received: from noc.sixxs.net ([213.197.29.32] ident=postfix) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfGXg-00014x-41 for v6tc@ietf.org; Fri, 17 Dec 2004 06:45:05 -0500
Received: from localhost (localhost [127.0.0.1]) by noc.sixxs.net (Postfix) with ESMTP id 7CE862400C; Fri, 17 Dec 2004 12:35:58 +0100 (CET)
Received: from noc.sixxs.net ([127.0.0.1]) by localhost (noc [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 27573-05; Fri, 17 Dec 2004 12:35:57 +0100 (CET)
Received: from firenze.zurich.ibm.com (pat.zurich.ibm.com [195.176.20.45]) (using SSLv3 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by noc.sixxs.net (Postfix) with ESMTP id A89AB24008; Fri, 17 Dec 2004 12:35:57 +0100 (CET)
Subject: Re: [v6tc] Issue 1: Could we live with UDP encapsulation always on?
From: Jeroen Massar <jeroen@unfix.org>
To: Alain Durand <Alain.Durand@sun.com>
In-Reply-To: <A2C7FD38-501D-11D9-81E4-00039358A080@sun.com>
References: <6D2CE1A0-5011-11D9-81E4-00039358A080@sun.com> <1103278369.25975.57.camel@firenze.zurich.ibm.com> <Pine.LNX.4.61.0412171231230.19294@netcore.fi> <1103281912.25975.87.camel@firenze.zurich.ibm.com> <A2C7FD38-501D-11D9-81E4-00039358A080@sun.com>
Organization: Unfix
Date: Fri, 17 Dec 2004 12:35:53 +0100
Message-Id: <1103283353.25975.96.camel@firenze.zurich.ibm.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.2 (2.0.2-6)
X-Virus-Scanned: noc.sixxs.net - http://www.sixxs.net
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: 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>
Content-Type: multipart/mixed; boundary="===============1751368381=="
Sender: v6tc-bounces@ietf.org
Errors-To: v6tc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc

On Fri, 2004-12-17 at 03:20 -0800, Alain Durand wrote:
> On Dec 17, 2004, at 3:11 AM, Jeroen Massar wrote:
> > You mean eg dailup users? Do those still exist? Also G3 phones don't
> > have this issue either with UMTS and other goodies being deployed,
> > coming upto speeds of most lower DSL lines...
> 
> The issue is not so much speed but money. If there is a 7-10% overhead,
> this is not insignificant, regardless of bandwidth.

In general for 'office/home environments' aka webbrowsing and alike, it
seems the trend is that packet length distribution is that about 40% of
the packets is between the 0-400 size. the other 60% is in between
400-1200 with only relatively few packetlengths in tehe 1200-1400 range,
one will have a peak for the 1500 size, thus completely full packets.
On average, from the couple of graphs that I have I would estimate the
packetlength to be around 600 bytes/packet.

This is based on an ethernet (mtu=1500) environment though, thus the
peek at 1500 will move downwards, relative to the mtu size of the
environment. Also, when there is a high concentration of 'downloaders'
it might well be that that the packetsize distribution shifts almost
completely to the maximum mtu. All depends on the usage of the network
and if you count packets or octets as an importance.

There will always be some sort of overhead with encapsulation. But if
you are thinking of that, make a new protocol number which would make it
proto-41 or GRE, which did not work over NAT's.

> Please keep this discussion for the upcoming issue 3 thread:
> "Should some of this authentication mechanism "follow-on" after the 
> tunnel set-up phase as finished?"
> To keep the discussion focussed, I will only introduce one issue at a 
> time.

Ack, though if you want to minimize the header, you can't introduce any
of those parts anymore because the header is to small ;)

Greets,
 Jeroen

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