IETF Logo Mail Archive

[mif] Questions on MIF in vehicle environment

"Peng.yang.chn@gmail.com" <peng.yang.chn@gmail.com> Mon, 15 September 2014 11:08 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 F03431A0B04 for <mif@ietfa.amsl.com>; Mon, 15 Sep 2014 04:08:36 -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 c5a2BJ2UvaMV for <mif@ietfa.amsl.com>; Mon, 15 Sep 2014 04:08:35 -0700 (PDT)
Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4A261A0AFC for <mif@ietf.org>; Mon, 15 Sep 2014 04:08:35 -0700 (PDT)
Received: by mail-pa0-f48.google.com with SMTP id hz1so6240139pad.35 for <mif@ietf.org>; Mon, 15 Sep 2014 04:08:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:references:from:content-type:in-reply-to:message-id:date:to :content-transfer-encoding:mime-version; bh=iGSBDk7GP78ZE4402rKIgUakzKotgwBnHhxanN2Un58=; b=AuH943S1KfnNPWtj2TJ/qAiNNCGZ8eIiwXRJLb0Jr3Va8ZLl5L0FIAA7slTJcx05IG euSaKnL9eYbiXmzpzK5ZxekXeZy83V0Xwvwx64ljicpkUwUhFzIs6Q0wipRnzTUrvkkp lXmWTb+u8UMvD2FkEAy0X2qseiQTC5AoYrlG7vosWxhxbEpxwS17+Hm58o8IwqZYCZxx HAeu0kD/XCBlTV0R0dvX4V5dlbQrEkm1p/VCeFxtlLo2170yRa/cQtdWvtTu+R/Q0Bd/ RhoXVRInnicwlFuhmV+8gVbaimmvOF2kL9XEzi7d/pBn5Ub8L1crKfhe5Ol5j9fNorFR mFEg==
X-Received: by 10.66.222.132 with SMTP id qm4mr3948421pac.140.1410779315392; Mon, 15 Sep 2014 04:08:35 -0700 (PDT)
Received: from [192.168.1.100] ([114.247.10.153]) by mx.google.com with ESMTPSA id bq17sm11529504pac.47.2014.09.15.04.08.33 for <mif@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 15 Sep 2014 04:08:33 -0700 (PDT)
References: <20140830053510.14309.34501.idtracker@ietfa.amsl.com>
From: "Peng.yang.chn@gmail.com" <peng.yang.chn@gmail.com>
Content-Type: text/plain; charset="us-ascii"
X-Mailer: iPad Mail (11D257)
In-Reply-To: <20140830053510.14309.34501.idtracker@ietfa.amsl.com>
Message-Id: <A7E17052-A25F-4B04-8837-CFE65397634B@gmail.com>
Date: Mon, 15 Sep 2014 19:08:31 +0800
To: "mif@ietf.org" <mif@ietf.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Archived-At: http://mailarchive.ietf.org/arch/msg/mif/plUCCMLXsGs3kBYs67qOYuNDEkI
Subject: [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:08:37 -0000

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

v2.23.0 | Report a Bug | By Email