[nemo] Requirement of a Car Manufacturer for real MIPv6 large deployments (IPv4 NAT traversal feature)
LASNIER-REDDAN Edouard <Edouard.Lasnier-Reddan@renault.com> Wed, 01 June 2005 14:57 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DdUey-00012J-Vn; Wed, 01 Jun 2005 10:57:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DaF30-0003Ee-1h; Mon, 23 May 2005 11:40:54 -0400
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 LAA06402; Mon, 23 May 2005 11:40:51 -0400 (EDT)
Received: from xenia3-in0.renault.fr ([193.194.133.17] helo=xenia3.mc2.renault.fr) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DaFKz-0000Jm-Nj; Mon, 23 May 2005 11:59:30 -0400
Received: from univers4.mc2.renault.fr (univers4-in0.mc2.renault.fr [10.210.68.9]) by xenia3.mc2.renault.fr (8.13.1/8.13.1) with ESMTP id j4NFej9C028255; Mon, 23 May 2005 17:40:45 +0200 (MEST)
Received: from hepatite1.mc2.renault.fr (hepatite1.mc2.renault.fr [10.210.68.19]) by univers4.mc2.renault.fr (8.13.4/8.13.4) with SMTP id j4NFeXAD014342; Mon, 23 May 2005 17:40:33 +0200 (MEST)
Received: from univers3-in0.mc2.renault.fr(10.210.68.1) by hepatite1.mc2.renault.fr via csmap id be9f74cc_cba0_11d9_8377_0002b3cb50ff_12410; Mon, 23 May 2005 17:38:43 +0200 (CEST)
Received: from su356aos (su356aos.mc2.renault.fr [138.21.107.59]) by univers3.mc2.renault.fr (8.13.1/8.13.1) with ESMTP id j4NFboWZ026089; Mon, 23 May 2005 17:37:50 +0200 (MEST)
Received: from su358aos (su358aos.mc2.renault.fr [138.21.107.206]) by wsmtp54.mc2.renault.fr (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IGY00J3U8R250@wsmtp54.mc2.renault.fr>; Mon, 23 May 2005 17:37:50 +0200 (MEST)
Received: from FR20016868 ([10.230.213.114]) by wsmtpin57.mc2.renault.fr (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with SMTP id <0IGY00MD08R2KL@wsmtpin57.mc2.renault.fr>; Mon, 23 May 2005 17:37:50 +0200 (MEST)
Date: Mon, 23 May 2005 17:37:41 +0200
From: LASNIER-REDDAN Edouard <Edouard.Lasnier-Reddan@renault.com>
To: mip6@ietf.org, nemo@ietf.org
Message-id: <02b701c55fad$5b8f3520$72d5e60a@corp.noxiane.net>
Organization: Renault
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
Content-type: multipart/mixed; boundary="Boundary_(ID_13UhgGNevmVhLRQsXXC+KA)"
X-Priority: 3
X-MSMail-priority: Normal
X-Scanned-By: MIMEDefang 2.44
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0770535483960d190d4a0d020e7060bd
X-Mailman-Approved-At: Wed, 01 Jun 2005 10:57:30 -0400
Cc: HORKAY Francois <francois.horkay@renault.com>
Subject: [nemo] Requirement of a Car Manufacturer for real MIPv6 large deployments (IPv4 NAT traversal feature)
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: NEMO Working Group <nemo.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>, <mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nemo@ietf.org>
List-Help: <mailto:nemo-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nemo>, <mailto:nemo-request@ietf.org?subject=subscribe>
Sender: nemo-bounces@ietf.org
Errors-To: nemo-bounces@ietf.org
Dear NEMO WG participants, The car manufacturer RENAULT is involved in several research projects dealing with IP mobility since 2001. One of our major achievements was the RENAULT Laguna "IPv6 Car", supporting Mobile IPv6. This telematic concept car received the "Murai Award" in 2003 in Tokyo for its capability to support GPRS (2G European cellular network) / Wifi vertical handover, using Mobile IPv6 with IPv4 NAT traversal feature (the NAT traversal function, called "DOORS", was developed by Cisco Systems, it did provide efficient results and is compatible with our deployment constraints for further commercial exploitations). Mobile IPv6 is considered by the car manufacturers as a key technology for the deployment of next generation Telematic services, such as remote diagnosis, fleet management, etc. This trend has been confirmed by the current work of the research project GST - Global System for Telematics, in which RENAULT, BMW, DAIMLER CHRYSLER, FIAT and many other actors of the Telematic Industry work on standardization convergence : IPv6 is now part of the core specification for a European standard for telematics, mainly because of its mobility features. If it is agreed by the automotive industry that IPv6 paves the future of the telematic market, the existing constraints on the deployment of Mobile IPv6 makes the finalization of the standard very sensitive: 1. For the car manufacturers, Mobile IPv6 will have to be deployed soon on top of existing cellular networks, such as GPRS, EDGE or UMTS, all based on IPv4. In order to remain independent from the mobile telecom operator, it is mandatory to deploy Mobile IPv6 with a NAT traversal support. Deploying MIPv6 without a NAT traversal feature would be a non sense: if the car manufacturers have to setup technical agreements with the mobile telecom operators to deploy MIPv6, then many other solutions can be considered, and MIPv6 leads to a situation of dependence toward the mobile telecom operators, which is not acceptable. MIPv6 should not limit the possible business models : it should enable the actors of the value chain to define their business model, and in this MIPv6 context, it means that MIPv6 should be flexible and not compel the Home Agent to be directly connected to the Internet. 2. Having NAT traversal feature is a required feature but the technical solution defined at the IETF should take into consideration the deployment constraints. In the next 18 months, MIPv6 will be mainly deployed for pilot experiments, for validation before a wider deployment. In this context, the Home Agent is in many cases in existing small networks dedicated to pilot experiments initially designed for IPv4, with NAT boxes on the Internet interface. This constraint is a fact, and is valid for many projects. 3. On a long term perspective, the car manufacturers - or any actors from the telematic industry supplying IP mobility support for the cars - will deploy MIPv6 on their enterprise networks. Those networks are secured, designed for IPv4, and most probably the Home Agent will not be directly interfaced with the Internet, it will be a secured equipment in the core of the network, behind NATs. This problem is in fact very common as enterprise networks are connected to the Internet behind NATs in general. If the deployment of Mobile IPv6 requires re-designing the car manufacturers networks because security policies and existing NAT features are not supported, then Mobile IPv6 will remain a beautiful idea that no company will be able to deploy. Mobile IPv6 should support multiple IPv4 Network Address Translation (in the access networks, and in front of the Home network). The Home Agent may be deployed on IPv4 networks behind NAT access to the Internet. I have currently several industrial projects for which I could deploy MIPv6 _for real_ if the IPv4 NAT traversal would be normalized and enable Home Agent to be connected to the internet behind NATs and other boxes. Edouard LASNIER REDDAN, Telecom Solution for Telematics, RENAULT, on May 2nd, 2005 ************** Cordialement / Best Regards / Mit Freundlichen Grüssen Edouard Lasnier Reddan. edouard.lasnier-reddan@renault.com Office : + 33 (0)1 76 84 71 93 / Fax : + 33 (0)1 76 84 91 16 RENAULT 13 avenue Paul Langevin / API : FR EQV NOV 3 32 92359 Le Plessis Robinson Cedex France
- [nemo] Requirement of a Car Manufacturer for real… LASNIER-REDDAN Edouard