Re: [mif] Questions on MIF in vehicle environment

"Peng.yang.chn@gmail.com" <peng.yang.chn@gmail.com> Mon, 15 September 2014 11:31 UTC

Return-Path: <peng.yang.chn@gmail.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 476E91A0B71 for <mif@ietfa.amsl.com>; Mon, 15 Sep 2014 04:31:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.23
X-Spam-Level:
X-Spam-Status: No, score=-1.23 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_SORBS_WEB=0.77, SPF_PASS=-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 VKI5AxrV7TGE for <mif@ietfa.amsl.com>; Mon, 15 Sep 2014 04:31:48 -0700 (PDT)
Received: from mail-pd0-x235.google.com (mail-pd0-x235.google.com [IPv6:2607:f8b0:400e:c02::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A02B31A068E for <mif@ietf.org>; Mon, 15 Sep 2014 04:31:45 -0700 (PDT)
Received: by mail-pd0-f181.google.com with SMTP id w10so6093930pde.12 for <mif@ietf.org>; Mon, 15 Sep 2014 04:31:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=PEuTBlrdjG2B/vH8s5Hcv3L5vwInI9tZpiNCQXA3ROI=; b=CxvQHeGfFC1GNfccNvKVpAQs6cXVirdoBdqQCXhVBjra+j+27i9Uc4rgqAea/2eGqw QZlke3xI2aDAuVyUJfQnSSvKSmppYxoHsooBkFuGZoZ+UOhUL7YTUHL9vMVISKw/CJaD Sg9O85xAjEYsRGHWldHGjBQwq6MITG+fKLTHWNcPDdcvXlNAP/5X9wliff/8Cqf+yYar uD0gKUe3v38bkGHovGrf0qRGnk7jjTbuiMQbj9Y1lfZlmcrmRdrOu3npF9D1afsryq64 iWQLA6j9zOkeLsio1bxRAgeIHP6Gw9hCbfvzwlG+4vrax7XSTJqY13pi7qC3FxNHBLxB t2LQ==
X-Received: by 10.66.244.132 with SMTP id xg4mr34344441pac.64.1410780705234; Mon, 15 Sep 2014 04:31:45 -0700 (PDT)
Received: from [192.168.1.100] ([114.247.10.153]) by mx.google.com with ESMTPSA id y1sm11144193pbt.74.2014.09.15.04.31.43 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 15 Sep 2014 04:31:43 -0700 (PDT)
References: <20140830053510.14309.34501.idtracker@ietfa.amsl.com> <A7E17052-A25F-4B04-8837-CFE65397634B@gmail.com> <22970_1410779849_5416CAC9_22970_3051_1_81C77F07008CA24F9783A98CFD706F71142A0BA2@PEXCVZYM12.corporate.adroot.infra.ftgroup>
Mime-Version: 1.0 (1.0)
In-Reply-To: <22970_1410779849_5416CAC9_22970_3051_1_81C77F07008CA24F9783A98CFD706F71142A0BA2@PEXCVZYM12.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-Id: <746AC8FC-16F9-4049-A452-F93739C3F697@gmail.com>
X-Mailer: iPad Mail (11D257)
From: "Peng.yang.chn@gmail.com" <peng.yang.chn@gmail.com>
Date: Mon, 15 Sep 2014 19:31:41 +0800
To: "<pierrick.seite@orange.com>" <pierrick.seite@orange.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/mif/YG1EIrvuWGa7jUZk8yPeB-hiI94
Cc: "mif@ietf.org" <mif@ietf.org>
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:31:49 -0000

Hi, Pierrick:

Cool. Your help is greatly appreciated. I will let my man to check it. 

Many thanks
Regards,
Peny

发自我的 iPad

> 在 2014年9月15日,19:17,<pierrick.seite@orange.com> 写道:
> 
> 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.
>