From nobody Fri Sep 12 17:25:16 2014 Return-Path: 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 58ED81A0126; Fri, 12 Sep 2014 17:25:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 hsRGyoeH4Db4; Fri, 12 Sep 2014 17:25:10 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BB1331A0115; Fri, 12 Sep 2014 17:25:10 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.6.2.p6 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140913002510.1248.65570.idtracker@ietfa.amsl.com> Date: Fri, 12 Sep 2014 17:25:10 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/mif/RcouL1A9kX07KJWUzfP6GVRUzkQ Cc: mif@ietf.org Subject: [mif] I-D Action: draft-ietf-mif-mpvd-arch-04.txt X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.15 List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Sep 2014 00:25:12 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multiple Interfaces Working Group of the IETF. Title : Multiple Provisioning Domain Architecture Author : Dmitry Anipko Filename : draft-ietf-mif-mpvd-arch-04.txt Pages : 23 Date : 2014-09-12 Abstract: This document is a product of the work of the MIF Architecture Design team. It outlines a solution framework for some of the issues experienced by nodes that can be attached to multiple networks simultaneously. The framework defines the concept of a Provisioning Domain (PvD) which is a a consistent set of network configuration information. PvD aware nodes learn PvD specific information from the networks they are attached to and / or other sources. PvDs are used to enable separation and configuration consistency in presence of multiple concurrent connections. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-mif-mpvd-arch/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-mif-mpvd-arch-04 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-mif-mpvd-arch-04 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Fri Sep 12 17:30:17 2014 Return-Path: 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 2B0B31A0164 for ; Fri, 12 Sep 2014 17:30:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.902 X-Spam-Level: X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham 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 fUY_U3yDB-RT for ; Fri, 12 Sep 2014 17:30:13 -0700 (PDT) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0737.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:737]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24CEB1A0167 for ; Fri, 12 Sep 2014 17:30:13 -0700 (PDT) Received: from SN2PR03MB077.namprd03.prod.outlook.com (10.255.175.153) by SN2PR03MB080.namprd03.prod.outlook.com (10.255.175.156) with Microsoft SMTP Server (TLS) id 15.0.1029.10; Sat, 13 Sep 2014 00:29:49 +0000 Received: from SN2PR03MB077.namprd03.prod.outlook.com ([169.254.2.129]) by SN2PR03MB077.namprd03.prod.outlook.com ([169.254.2.129]) with mapi id 15.00.1029.000; Sat, 13 Sep 2014 00:29:49 +0000 From: Dmitry Anipko To: MIF Mailing List Thread-Topic: [mif] I-D Action: draft-ietf-mif-mpvd-arch-04.txt Thread-Index: AQHPzulGBmQyfQ8P6Uq1tPgY5gTOqJv+NYSg Date: Sat, 13 Sep 2014 00:29:48 +0000 Message-ID: <0ba69fa8ee2840a6bb89f8a9b6a34873@SN2PR03MB077.namprd03.prod.outlook.com> References: <20140913002510.1248.65570.idtracker@ietfa.amsl.com> In-Reply-To: <20140913002510.1248.65570.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [2001:4898:80e0:ee43::2] x-microsoft-antispam: BCL:0;PCL:0;RULEID:;UriScan:; x-forefront-prvs: 03333C607F x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(199003)(13464003)(189002)(377424004)(377454003)(90102001)(85306004)(2656002)(108616004)(64706001)(230783001)(77982001)(86362001)(4396001)(80022001)(46102001)(76482001)(15975445006)(107886001)(110136001)(20776003)(107046002)(79102001)(97736003)(21056001)(106116001)(105586002)(19580395003)(83322001)(31966008)(19580405001)(106356001)(77096002)(81342001)(81542001)(86612001)(54356999)(76176999)(85852003)(87936001)(74502001)(101416001)(74316001)(76576001)(92566001)(95666004)(15202345003)(99286002)(99396002)(50986999)(74662001)(83072002)(33646002)(24736002)(3826002); DIR:OUT; SFP:1102; SCL:1; SRVR:SN2PR03MB080; H:SN2PR03MB077.namprd03.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: microsoft.onmicrosoft.com Archived-At: http://mailarchive.ietf.org/arch/msg/mif/cewxYHHM4tBnJX8xpW9hCHeFpc0 Subject: [mif] FW: I-D Action: draft-ietf-mif-mpvd-arch-04.txt X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Sep 2014 00:30:15 -0000 This revision includes changes suggested by Ian Farrer per language review = (thanks Ian!), and list of contributors as provided by the WG chairs. Thank you. -----Original Message----- From: mif [mailto:mif-bounces@ietf.org] On Behalf Of internet-drafts@ietf.o= rg Sent: Friday, September 12, 2014 5:25 PM To: i-d-announce@ietf.org Cc: mif@ietf.org Subject: [mif] I-D Action: draft-ietf-mif-mpvd-arch-04.txt A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Multiple Interfaces Working Group of the = IETF. Title : Multiple Provisioning Domain Architecture Author : Dmitry Anipko Filename : draft-ietf-mif-mpvd-arch-04.txt Pages : 23 Date : 2014-09-12 Abstract: This document is a product of the work of the MIF Architecture Design team. It outlines a solution framework for some of the issues experienced by nodes that can be attached to multiple networks simultaneously. The framework defines the concept of a Provisioning Domain (PvD) which is a a consistent set of network configuration information. PvD aware nodes learn PvD specific information from the networks they are attached to and / or other sources. PvDs are used to enable separation and configuration consistency in presence of multiple concurrent connections. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-mif-mpvd-arch/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-mif-mpvd-arch-04 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mif-mpvd-arch-04 Please note that it may take a couple of minutes from the time of submissio= n until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ mif mailing list mif@ietf.org https://www.ietf.org/mailman/listinfo/mif From nobody Mon Sep 15 01:11:01 2014 Return-Path: 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 1385E1A0126 for ; Mon, 15 Sep 2014 01:11:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham 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 PBsIllwwCTD1 for ; Mon, 15 Sep 2014 01:10:57 -0700 (PDT) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B34181A011F for ; Mon, 15 Sep 2014 01:10:56 -0700 (PDT) Received: from [192.168.1.158] ([62.225.30.139]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0MV6EP-1Xqt193n3N-00YTVd; Mon, 15 Sep 2014 10:10:54 +0200 From: Ian Farrer Content-Type: multipart/alternative; boundary="Apple-Mail=_4C32B843-824F-4F1B-87FA-2AB4F918208A" Message-Id: <7B7DEF3E-8339-4E7C-9C92-410DCF2250F8@gmx.com> Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Date: Mon, 15 Sep 2014 10:10:53 +0200 References: <20140913002510.1248.65570.idtracker@ietfa.amsl.com> <0ba69fa8ee2840a6bb89f8a9b6a34873@SN2PR03MB077.namprd03.prod.outlook.com> To: Dmitry Anipko , MIF Mailing List In-Reply-To: <0ba69fa8ee2840a6bb89f8a9b6a34873@SN2PR03MB077.namprd03.prod.outlook.com> X-Mailer: Apple Mail (2.1878.6) X-Provags-ID: V03:K0:guUpI4oGUZSq05ykIbwdOTlyMYNYBhda1MZnSgq9bpAXf30d1ys ykf8XKZmHLhM17Gfb6YcjMeHxQbq1tOCfOLfjoBkphdAV/iPclB2t0ypAi+b/XbwWBK3Eu1 GPZlSwE0GCTuPHkCaE7eCtt03VjD4FPMZePL3k1EjMBV3Sckybp6HDNUbzXN10sDxgwBK9i SDxXJV/QUjn+gTDO4hHxg== X-UI-Out-Filterresults: notjunk:1; Archived-At: http://mailarchive.ietf.org/arch/msg/mif/lqDTiTNQF-sv1ZZp947dSsiWc-s Subject: Re: [mif] I-D Action: draft-ietf-mif-mpvd-arch-04.txt X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 08:11:00 -0000 --Apple-Mail=_4C32B843-824F-4F1B-87FA-2AB4F918208A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Hi, One additional question that arose whilst I was reviewing the document = is from the end of P1 in section 3.4: One way this could be accomplished is by using a DHCPv6 ORO containing = the PvDs that are of interest. The configuration source can then respond with only the requested = information. I think that the language here is incorrect. The ORO is a list of option = codes and this doesn=92t have any way of including specific PvDs (unless = each PvD was defined as a DHCP option in its own right, which seems = unworkable). I guess that the real intension here is to have a new DHCP = option which carries information about requested/available PvDs, and for = the client to include the option code for this in the ORO.=20 If so, proposed new text: One way this could be accomplished is by using a new DHCPv6 option = containing the PvDs that are of interest. The configuration source can then respond with only the requested = information. Cheers, Ian On 13 Sep 2014, at 02:29, Dmitry Anipko = wrote: > This revision includes changes suggested by Ian Farrer per language = review (thanks Ian!), and list of contributors as provided by the WG = chairs. >=20 > Thank you. >=20 > -----Original Message----- > From: mif [mailto:mif-bounces@ietf.org] On Behalf Of = internet-drafts@ietf.org > Sent: Friday, September 12, 2014 5:25 PM > To: i-d-announce@ietf.org > Cc: mif@ietf.org > Subject: [mif] I-D Action: draft-ietf-mif-mpvd-arch-04.txt >=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts = directories. > This draft is a work item of the Multiple Interfaces Working Group of = the IETF. >=20 > Title : Multiple Provisioning Domain Architecture > Author : Dmitry Anipko > Filename : draft-ietf-mif-mpvd-arch-04.txt > Pages : 23 > Date : 2014-09-12 >=20 > Abstract: > This document is a product of the work of the MIF Architecture = Design > team. It outlines a solution framework for some of the issues > experienced by nodes that can be attached to multiple networks > simultaneously. The framework defines the concept of a Provisioning > Domain (PvD) which is a a consistent set of network configuration > information. PvD aware nodes learn PvD specific information from = the > networks they are attached to and / or other sources. PvDs are used > to enable separation and configuration consistency in presence of > multiple concurrent connections. >=20 >=20 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-mif-mpvd-arch/ >=20 > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-mif-mpvd-arch-04 >=20 > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mif-mpvd-arch-04 >=20 >=20 > Please note that it may take a couple of minutes from the time of = submission until the htmlized version and diff are available at = tools.ietf.org. >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > mif mailing list > mif@ietf.org > https://www.ietf.org/mailman/listinfo/mif >=20 > _______________________________________________ > mif mailing list > mif@ietf.org > https://www.ietf.org/mailman/listinfo/mif --Apple-Mail=_4C32B843-824F-4F1B-87FA-2AB4F918208A Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252
Hi,

One additional = question that arose whilst I was reviewing the document is from the end = of P1 in section 3.4:

One way =
this could be accomplished is by using a DHCPv6 ORO containing the PvDs =
that are of interest.
The configuration source can =
then respond with only the requested =
information.

I think that the language = here is incorrect. The ORO is a list of option codes and this doesn=92t = have any way of including specific PvDs (unless each PvD was defined as = a DHCP option in its own right, which seems unworkable). I guess that = the real intension here is to have a new DHCP option which carries = information about requested/available PvDs, and for the client to = include the option code for this in the = ORO. 

If so, proposed new = text:

One way this =
could be accomplished is by using a new DHCPv6 option containing the =
PvDs that are of interest.
The configuration =
source can then respond with only the requested =
information.

Cheers,
Ian


On 13 Sep 2014, at 02:29, Dmitry = Anipko <Dmitry.Anipko@microsoft.com> wrote:

This revision includes changes suggested by Ian Farrer per = language review (thanks Ian!), and list of contributors as provided by = the WG chairs.

Thank you.

-----Original = Message-----
From: mif [mailto:mif-bounces@ietf.org] On = Behalf Of internet-drafts@ietf.org
S= ent: Friday, September 12, 2014 5:25 PM
To: i-d-announce@ietf.org
Cc: = mif@ietf.org
Subject: [mif] I-D = Action: draft-ietf-mif-mpvd-arch-04.txt


A New Internet-Draft = is available from the on-line Internet-Drafts directories.
This = draft is a work item of the Multiple Interfaces Working Group of the = IETF.

       Title =           : Multiple = Provisioning Domain Architecture
=        Author =          : Dmitry = Anipko
= Filename        : = draft-ietf-mif-mpvd-arch-04.txt
Pages =           : = 23
= Date =            : = 2014-09-12

Abstract:
  This document is a product = of the work of the MIF Architecture Design
  team. =  It outlines a solution framework for some of the issues
=   experienced by nodes that can be attached to multiple = networks
  simultaneously.  The framework defines the = concept of a Provisioning
  Domain (PvD) which is a a = consistent set of network configuration
  information. =  PvD aware nodes learn PvD specific information from the
=   networks they are attached to and / or other sources. =  PvDs are used
  to enable separation and = configuration consistency in presence of
  multiple = concurrent connections.


The IETF datatracker status page for = this draft is:
https:= //datatracker.ietf.org/doc/draft-ietf-mif-mpvd-arch/

There's = also a htmlized version available = at:
http://tools.ietf.org/html/draft-ietf-mif-mpvd-arch-04

A = diff from the previous version is available = at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mif-mpvd-arch-04
<= br>
Please note that it may take a couple of minutes from the time of = submission until the htmlized version and diff are available at = tools.ietf.org.

Internet-Drafts are also available by anonymous = FTP = at:
ftp://ftp.ietf.org/internet-drafts/

________________________= _______________________
mif mailing = list
mif@ietf.org
https://www.ietf.org/mailman/listinfo/mif

_= ______________________________________________
mif mailing = list
mif@ietf.org
https://www.ietf.org/mailman/listinfo/mif

= --Apple-Mail=_4C32B843-824F-4F1B-87FA-2AB4F918208A-- From nobody Mon Sep 15 04:08:39 2014 Return-Path: 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 ; 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 ; 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 ; Mon, 15 Sep 2014 04:08:35 -0700 (PDT) Received: by mail-pa0-f48.google.com with SMTP id hz1so6240139pad.35 for ; 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 (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" Content-Type: text/plain; charset=us-ascii X-Mailer: iPad Mail (11D257) In-Reply-To: <20140830053510.14309.34501.idtracker@ietfa.amsl.com> Message-Id: Date: Mon, 15 Sep 2014 19:08:31 +0800 To: "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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 11:08:37 -0000 Hi, Folks:=20 It has been a long time since I posted something in this list last time.=20 Recently, I am doing a project related to intelligent driving and maintenanc= e, which may need the help from this list.=20 Basically, one embedded HW platform will be put inside the vehicles. And, GS= M, UMTS, WiFi have already been supported. In the near future, we will think= of integrating TD-LTE and C2X modules.=20 In this application scenario, quite a few sessions with diverse requirements= on bandwidth, routing, security, jitter, and reliability should be supporte= d. In the meantime, the connections are quite dynamic along the driving rout= e. Our current NIC management function is not so optimized, and has some neg= ative impact on the service quality.=20 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 t= he implementation should be well optimized for ARM/Linux.=20 Your help is greatly appreciated.=20 BR Peny YANG= From nobody Mon Sep 15 04:17:35 2014 Return-Path: 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 ; 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 ; 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 ; 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: To: "Peng.yang.chn@gmail.com" , "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> In-Reply-To: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 sourc= e available here: http://www.umip.org/=20 Hope that helps, Pierrick >-----Message d'origine----- >De=A0: mif [mailto:mif-bounces@ietf.org] De la part de >Peng.yang.chn@gmail.com >Envoy=E9=A0: lundi 15 septembre 2014 13:09 >=C0=A0: mif@ietf.org >Objet=A0: [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 maintena= nce, >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 requiremen= ts 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 confiden= tielles 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 el= ectroniques 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 inf= ormation 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 dele= te 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. From nobody Mon Sep 15 04:31:51 2014 Return-Path: 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 ; 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 ; 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 ; Mon, 15 Sep 2014 04:31:45 -0700 (PDT) Received: by mail-pd0-f181.google.com with SMTP id w10so6093930pde.12 for ; 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 (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> <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" Date: Mon, 15 Sep 2014 19:31:41 +0800 To: "" Archived-At: http://mailarchive.ietf.org/arch/msg/mif/YG1EIrvuWGa7jUZk8yPeB-hiI94 Cc: "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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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.=20 Many thanks Regards, Peny =E5=8F=91=E8=87=AA=E6=88=91=E7=9A=84 iPad > =E5=9C=A8 2014=E5=B9=B49=E6=9C=8815=E6=97=A5=EF=BC=8C19:17=EF=BC=8C =E5=86=99=E9=81=93=EF=BC=9A >=20 > Hi Peny, >=20 > It would be worth to consider NEMO (RFC 3963) for your use-case; open sour= ce available here: http://www.umip.org/=20 >=20 > Hope that helps, > Pierrick >=20 >> -----Message d'origine----- >> De : mif [mailto:mif-bounces@ietf.org] De la part de >> Peng.yang.chn@gmail.com >> Envoy=C3=A9 : lundi 15 septembre 2014 13:09 >> =C3=80 : mif@ietf.org >> Objet : [mif] Questions on MIF in vehicle environment >>=20 >> Hi, Folks: >>=20 >> 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 mainten= ance, >> 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 requireme= nts 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 negativ= e >> 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. >>=20 >> Your help is greatly appreciated. >> BR >> Peny YANG >> _______________________________________________ >> mif mailing list >> mif@ietf.org >> https://www.ietf.org/mailman/listinfo/mif >=20 > __________________________________________________________________________= _______________________________________________ >=20 > Ce message et ses pieces jointes peuvent contenir des informations confide= ntielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez rec= u ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages e= lectroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou= falsifie. Merci. >=20 > This message and its attachments may contain confidential or privileged in= formation 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 del= ete 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. >=20 From nobody Mon Sep 15 05:38:23 2014 Return-Path: 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 2CC2B1A0322 for ; Mon, 15 Sep 2014 05:38:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.999 X-Spam-Level: X-Spam-Status: No, score=-0.999 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, 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 1YPv-jCCNXN1 for ; Mon, 15 Sep 2014 05:38:20 -0700 (PDT) Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E1AF1A0311 for ; Mon, 15 Sep 2014 05:38:20 -0700 (PDT) Received: by mail-pa0-f46.google.com with SMTP id kq14so6344619pab.5 for ; Mon, 15 Sep 2014 05:38:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=WYcfbCpc0z0opFMT6qZFGEzXw//Bp0FMKXRpKby/hVk=; b=ohcAd3/RcwVmIz6hUUWyuPwuDAbffFPgRPjKQYMptl4i0VMcPxPRXWMeOT1koXmE41 YfFa/WnbuNzhIBC+AWdrBHaiyiut6WDLttSyglzgMz/TFoUgb/b7oDxWUgDntO9tQnr7 Uw/yvC2oJGtxsGdJUVH6bpZr6qdoppnntkb0kIC6fzBlbfggvrxm7BXl//wO8mFgdaoX 8wlVwSck/Xoj3iWiUTKkA4hRTUS0OHbDJs+/ckYgnn+PTWPXvpzcC9jU6fhmfR7oquOD 27qfjygRGRvLbK5IakWNTC1d8WeC1xinoxQ2jrttp0rcMswssefrXu4Y6GI/kGQhuZPf vPqw== X-Received: by 10.70.127.238 with SMTP id nj14mr5479433pdb.156.1410784700005; Mon, 15 Sep 2014 05:38:20 -0700 (PDT) Received: from [192.168.0.104] ([203.230.193.47]) by mx.google.com with ESMTPSA id ps1sm11312006pdb.73.2014.09.15.05.38.17 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 15 Sep 2014 05:38:19 -0700 (PDT) Content-Type: multipart/alternative; boundary="Apple-Mail=_CB873D45-CFA8-48BB-94B7-03164FD3AB5D" Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Jong-Hyouk Lee In-Reply-To: <746AC8FC-16F9-4049-A452-F93739C3F697@gmail.com> Date: Mon, 15 Sep 2014 21:38:16 +0900 Message-Id: <7B0516F2-3707-45D4-96C5-D4BE4CDAB67D@gmail.com> References: <20140830053510.14309.34501.idtracker@ietfa.amsl.com> <22970_1410779849_5416CAC9_22970_3051_1_81C77F07008CA24F9783A98CFD706F71142A0BA2@PEXCVZYM12.corporate.adroot.infra.ftgroup> <746AC8FC-16F9-4049-A452-F93739C3F697@gmail.com> To: "Peng.yang.chn@gmail.com" X-Mailer: Apple Mail (2.1878.6) Archived-At: http://mailarchive.ietf.org/arch/msg/mif/8Cpahp3q9xdwOrH9A1XJZAUoJ6U Cc: "mif@ietf.org" , Thierry Ernst 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 12:38:22 -0000 --Apple-Mail=_CB873D45-CFA8-48BB-94B7-03164FD3AB5D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Peny, you might be interested in https://project.inria.fr/itssv6/=20 -- Jong-Hyouk Lee, living somewhere between /dev/null and /dev/random Protocol Engineering Lab., Sangmyung University #email: jonghyouk@gmail.com #webpage: https://sites.google.com/site/hurryon On Sep 15, 2014, at 8:31 PM, Peng.yang.chn@gmail.com = wrote: > Hi, Pierrick: >=20 > Cool. Your help is greatly appreciated. I will let my man to check it.=20= >=20 > Many thanks > Regards, > Peny >=20 > =E5=8F=91=E8=87=AA=E6=88=91=E7=9A=84 iPad >=20 >> =E5=9C=A8 2014=E5=B9=B49=E6=9C=8815=E6=97=A5=EF=BC=8C19:17=EF=BC=8C =E5=86=99=E9=81=93=EF=BC=9A >>=20 >> Hi Peny, >>=20 >> It would be worth to consider NEMO (RFC 3963) for your use-case; open = source available here: http://www.umip.org/=20 >>=20 >> Hope that helps, >> Pierrick >>=20 >>> -----Message d'origine----- >>> De : mif [mailto:mif-bounces@ietf.org] De la part de >>> Peng.yang.chn@gmail.com >>> Envoy=C3=A9 : lundi 15 septembre 2014 13:09 >>> =C3=80 : mif@ietf.org >>> Objet : [mif] Questions on MIF in vehicle environment >>>=20 >>> Hi, Folks: >>>=20 >>> 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. >>>=20 >>> Your help is greatly appreciated. >>> BR >>> Peny YANG >>> _______________________________________________ >>> mif mailing list >>> mif@ietf.org >>> https://www.ietf.org/mailman/listinfo/mif >>=20 >> = __________________________________________________________________________= _______________________________________________ >>=20 >> 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. >>=20 >> 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. >>=20 >=20 > _______________________________________________ > mif mailing list > mif@ietf.org > https://www.ietf.org/mailman/listinfo/mif --Apple-Mail=_CB873D45-CFA8-48BB-94B7-03164FD3AB5D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Peny, = you might be interested in https://project.inria.fr/itssv6/=  
--
Jong-Hyouk Lee, living somewhere between /dev/null and = /dev/random
Protocol Engineering Lab., = Sangmyung University

#email: jonghyouk@gmail.com
#webpage:&n= bsp;https://sites.google.com/si= te/hurryon

On Sep 15, 2014, at 8:31 PM, Peng.yang.chn@gmail.com = <peng.yang.chn@gmail.com> = wrote:

Hi, Pierrick:

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

Many = thanks
Regards,
Peny

=E5=8F=91=E8=87=AA=E6=88=91=E7=9A=84 = iPad

=E5=9C=A8 = 2014=E5=B9=B49=E6=9C=8815=E6=97=A5=EF=BC=8C19:17=EF=BC=8C<pierrick.seite@orange.com>= ; =E5=86=99=E9=81=93=EF=BC=9A

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
Env= oy=C3=A9 : lundi 15 septembre 2014 13:09
=C3=80 : = 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.


_____________________________________________= __
mif mailing list
mif@ietf.org
https://www.ietf.org/mail= man/listinfo/mif

= --Apple-Mail=_CB873D45-CFA8-48BB-94B7-03164FD3AB5D-- From nobody Mon Sep 15 07:21:46 2014 Return-Path: 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 EDFA11A0368 for ; Mon, 15 Sep 2014 07:21:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.283 X-Spam-Level: X-Spam-Status: No, score=-1.283 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham 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 PopNnxJLY67d for ; Mon, 15 Sep 2014 07:21:42 -0700 (PDT) Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E3AA1A0339 for ; Mon, 15 Sep 2014 07:21:42 -0700 (PDT) Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id s8FELecJ003031 for ; Mon, 15 Sep 2014 16:21:40 +0200 Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 41DBB205821 for ; Mon, 15 Sep 2014 16:22:11 +0200 (CEST) Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 3A7762057BC for ; Mon, 15 Sep 2014 16:22:11 +0200 (CEST) Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id s8FELWMK002602 for ; Mon, 15 Sep 2014 16:21:40 +0200 Message-ID: <5416F5EC.2080307@gmail.com> Date: Mon, 15 Sep 2014 16:21:32 +0200 From: Alexandru Petrescu User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: mif@ietf.org References: <20140830053510.14309.34501.idtracker@ietfa.amsl.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Archived-At: http://mailarchive.ietf.org/arch/msg/mif/cGvyfz0U_8CalTjljD62wh0TaS0 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 14:21:45 -0000 Le 15/09/2014 13:08, Peng.yang.chn@gmail.com a écrit : > 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 Hello, It all depends of which particular functionality is needed in realizing this intelligent driving and maintenance, and at which layer. At the software driver level, open-source software exists for most NICs on the market. There are also some less open sources for 802.11p drivers (which one can call C2X). At the networking layer, almost everything needed is available as open-source: IPv4 and IPv6 stacks in linux, umip.org implementation of Mobile IPv6, dynamics implementation of Mobile IPv4, NAT masquerading in the kernel for IPv4 and IPv6, DHCPv4 and DHCPv6 clients, relays and servers. At the application layer, there is very little available as open source. These applications are developped very quickly in rapid development environments such as java, remote procedure calls, eclipse and more. The tools to develop such application software _are_ open source - it is the same as for desktop environments. Along these lines I saw recent announcements: BMW CarIT, Automotive Grade Android, Xen hypervisor, GENIVI, Apple CarPlay, Google Auto Link (ask Jeremiah Foster). In terms of making connections reliable to the vehicle- there is nothing available as open source either. This is software depending to a large extent to the behaviour of particular chipsets and telecom operators' networks. There is a big challenge to start connections very quickly (engine start plus 5 seconds) and to maintain connections up during long time while the vehicle moves across large areas). Alex > _______________________________________________ mif mailing list > mif@ietf.org https://www.ietf.org/mailman/listinfo/mif > > From nobody Mon Sep 15 16:25:49 2014 Return-Path: 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 AD8B91A0027; Mon, 15 Sep 2014 16:25:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 dp4zJFzqHEbq; Mon, 15 Sep 2014 16:25:44 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 972F11A0011; Mon, 15 Sep 2014 16:25:44 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.6.2.p6 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140915232544.11515.90413.idtracker@ietfa.amsl.com> Date: Mon, 15 Sep 2014 16:25:44 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/mif/95yQMCa8lqO3SpWLE8xG2zAfkLw Cc: mif@ietf.org Subject: [mif] I-D Action: draft-ietf-mif-mpvd-arch-05.txt X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.15 List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2014 23:25:45 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multiple Interfaces Working Group of the IETF. Title : Multiple Provisioning Domain Architecture Author : Dmitry Anipko Filename : draft-ietf-mif-mpvd-arch-05.txt Pages : 23 Date : 2014-09-15 Abstract: This document is a product of the work of the MIF Architecture Design team. It outlines a solution framework for some of the issues experienced by nodes that can be attached to multiple networks simultaneously. The framework defines the concept of a Provisioning Domain (PvD) which is a a consistent set of network configuration information. PvD aware nodes learn PvD specific information from the networks they are attached to and / or other sources. PvDs are used to enable separation and configuration consistency in presence of multiple concurrent connections. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-mif-mpvd-arch/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-mif-mpvd-arch-05 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-mif-mpvd-arch-05 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Wed Sep 17 12:26:55 2014 Return-Path: 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 519D61A0ACD; Wed, 17 Sep 2014 12:26:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 fiQO5P-pomAo; Wed, 17 Sep 2014 12:26:48 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C32C91A0B03; Wed, 17 Sep 2014 12:26:46 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.6.2.p6 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140917192646.32390.140.idtracker@ietfa.amsl.com> Date: Wed, 17 Sep 2014 12:26:46 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/mif/1CNCQpkzM4XmhEKhNLBHcH4YG0M Cc: mif@ietf.org Subject: [mif] I-D Action: draft-ietf-mif-mpvd-arch-06.txt X-BeenThere: mif@ietf.org X-Mailman-Version: 2.1.15 List-Id: Multiple Interface Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2014 19:26:51 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multiple Interfaces Working Group of the IETF. Title : Multiple Provisioning Domain Architecture Author : Dmitry Anipko Filename : draft-ietf-mif-mpvd-arch-06.txt Pages : 23 Date : 2014-09-17 Abstract: This document is a product of the work of the MIF Architecture Design team. It outlines a solution framework for some of the issues experienced by nodes that can be attached to multiple networks simultaneously. The framework defines the concept of a Provisioning Domain (PvD) which is a a consistent set of network configuration information. PvD aware nodes learn PvD specific information from the networks they are attached to and / or other sources. PvDs are used to enable separation and configuration consistency in presence of multiple concurrent connections. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-mif-mpvd-arch/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-mif-mpvd-arch-06 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-mif-mpvd-arch-06 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/