Re: [mif] Questions on MIF in vehicle environment

<pierrick.seite@orange.com> Mon, 15 September 2014 11:17 UTC

Return-Path: <pierrick.seite@orange.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8354D1A0B0A for <mif@ietfa.amsl.com>; Mon, 15 Sep 2014 04:17:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.899
X-Spam-Level:
X-Spam-Status: No, score=-0.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jVCrtOVV7Y6V for <mif@ietfa.amsl.com>; Mon, 15 Sep 2014 04:17:32 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias244.francetelecom.com [80.12.204.244]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C45E21A0B07 for <mif@ietf.org>; Mon, 15 Sep 2014 04:17:31 -0700 (PDT)
Received: from omfeda07.si.francetelecom.fr (unknown [xx.xx.xx.200]) by omfeda14.si.francetelecom.fr (ESMTP service) with ESMTP id B0B8F2AC224; Mon, 15 Sep 2014 13:17:29 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfeda07.si.francetelecom.fr (ESMTP service) with ESMTP id 8C6AA1580C5; Mon, 15 Sep 2014 13:17:29 +0200 (CEST)
Received: from PEXCVZYM12.corporate.adroot.infra.ftgroup ([fe80::81f:1640:4749:5d13]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0195.001; Mon, 15 Sep 2014 13:17:29 +0200
From: pierrick.seite@orange.com
To: "Peng.yang.chn@gmail.com" <peng.yang.chn@gmail.com>, "mif@ietf.org" <mif@ietf.org>
Thread-Topic: [mif] Questions on MIF in vehicle environment
Thread-Index: AQHP0NVqUWh49f/QrU+ZYCWv6EGLWJwCCj+g
Date: Mon, 15 Sep 2014 11:17:28 +0000
Message-ID: <22970_1410779849_5416CAC9_22970_3051_1_81C77F07008CA24F9783A98CFD706F71142A0BA2@PEXCVZYM12.corporate.adroot.infra.ftgroup>
References: <20140830053510.14309.34501.idtracker@ietfa.amsl.com> <A7E17052-A25F-4B04-8837-CFE65397634B@gmail.com>
In-Reply-To: <A7E17052-A25F-4B04-8837-CFE65397634B@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.197.38.4]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.9.15.103022
Archived-At: http://mailarchive.ietf.org/arch/msg/mif/cqMOzszjS66ssLJRh7KUN4dqSSA
Subject: Re: [mif] Questions on MIF in vehicle environment
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif/>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Sep 2014 11:17:33 -0000

Hi Peny,

It would be worth to consider NEMO (RFC 3963) for your use-case; open source available here: http://www.umip.org/ 

Hope that helps,
Pierrick

>-----Message d'origine-----
>De : mif [mailto:mif-bounces@ietf.org] De la part de
>Peng.yang.chn@gmail.com
>Envoyé : lundi 15 septembre 2014 13:09
>À : mif@ietf.org
>Objet : [mif] Questions on MIF in vehicle environment
>
>Hi, Folks:
>
>It has been a long time since I posted something in this list last time.
>Recently, I am doing a project related to intelligent driving and maintenance,
>which may need the help from this list.
>Basically, one embedded HW platform will be put inside the vehicles. And,
>GSM, UMTS, WiFi have already been supported. In the near future, we will
>think of integrating TD-LTE and C2X modules.
>In this application scenario, quite a few sessions with diverse requirements on
>bandwidth, routing, security, jitter, and reliability should be supported. In the
>meantime, the connections are quite dynamic along the driving route. Our
>current NIC management function is not so optimized, and has some negative
>impact on the service quality.
>Is there any open-source MIF implementation could be available now days?
>And, our current HW is already very constrained in CPU/Mem resources, so
>that the implementation should be well optimized for ARM/Linux.
>
>Your help is greatly appreciated.
>BR
>Peny YANG
>_______________________________________________
>mif mailing list
>mif@ietf.org
>https://www.ietf.org/mailman/listinfo/mif

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.