IETF Logo Mail Archive

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

Alain Durand <Alain.Durand@Sun.COM> Fri, 17 December 2004 09:56 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 EAA29349; Fri, 17 Dec 2004 04:56:04 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfEyq-0006pa-Uk; Fri, 17 Dec 2004 05:05:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CfEpE-0002mV-40; Fri, 17 Dec 2004 04:55:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CfEnF-0002Mm-SH for v6tc@megatron.ietf.org; Fri, 17 Dec 2004 04:53:01 -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 EAA29144 for <v6tc@ietf.org>; Fri, 17 Dec 2004 04:52:59 -0500 (EST)
Received: from brmea-mail-4.sun.com ([192.18.98.36]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfEvq-0006lL-A5 for v6tc@ietf.org; Fri, 17 Dec 2004 05:01:56 -0500
Received: from esunmail ([129.147.156.34]) by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id iBH9qudt028157 for <v6tc@ietf.org>; Fri, 17 Dec 2004 02:52:56 -0700 (MST)
Received: from xpa-fe2 (esunmail [129.147.156.34]) by edgemail1.Central.Sun.COM (iPlanet Messaging Server 5.2 HotFix 2.02 (built Oct 21 2004)) with ESMTP id <0I8V002XF247EG@edgemail1.Central.Sun.COM> for v6tc@ietf.org; Fri, 17 Dec 2004 02:52:56 -0700 (MST)
Received: from [192.168.1.4] ([83.113.94.83]) by mail.sun.net (iPlanet Messaging Server 5.2 HotFix 2.02 (built Oct 21 2004)) with ESMTPSA id <0I8V006L024544@mail.sun.net> for v6tc@ietf.org; Fri, 17 Dec 2004 02:52:55 -0700 (MST)
Date: Fri, 17 Dec 2004 01:52:56 -0800
From: Alain Durand <Alain.Durand@Sun.COM>
To: v6tc@ietf.org
Message-id: <6D2CE1A0-5011-11D9-81E4-00039358A080@sun.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.619)
Content-type: text/plain; charset=US-ASCII; format=flowed
Content-transfer-encoding: 7BIT
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7BIT
Subject: [v6tc] Issue 1: Could we live with UDP encapsulation always on?
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: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7BIT

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.

Another point to consider is that UDP encapsulation might force packets
to go to the slow path on the tunnel end-point unless special code is 
added
in the forwarding plane.

Also, IPv6/UDP/IPv4 has not generally been implemented so far, so we 
have
a deployment problem. Also, tons of PCs have now teredo, so there may 
be some
compatibility issues and/or some potential code to leverage.

Anything else to consider?

	- Alain.


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

v2.8.7 | Report a Bug | By Email