Re: [DMM] Call for adoption: draft-perkins-dmm-4283mnids-01
Behcet Sarikaya <sarikaya2012@gmail.com> Fri, 24 April 2015 19:30 UTC
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9BD51B3185 for <dmm@ietfa.amsl.com>; Fri, 24 Apr 2015 12:30:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=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 ulCzNNw9cFIs for <dmm@ietfa.amsl.com>; Fri, 24 Apr 2015 12:30:57 -0700 (PDT)
Received: from mail-la0-x22e.google.com (mail-la0-x22e.google.com [IPv6:2a00:1450:4010:c03::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54D531B29E2 for <dmm@ietf.org>; Fri, 24 Apr 2015 12:30:55 -0700 (PDT)
Received: by laat2 with SMTP id t2so42407177laa.1 for <dmm@ietf.org>; Fri, 24 Apr 2015 12:30:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=kUwXrF9p/8UMBBltTFYP+vO7GTSvGatMPBTnS67YAk8=; b=A4PS3/fs07UxeXkHE9RyGuVkGT43/NqVkRkbjJUPYY0KLzTW4GZcQzMgwDvgItp04S Ko44QlWcam+VInxoFiauRj/gV5QyvOfJ7Dtpsxr32vbZb2RcpR1LQb8s7+/4u+RTUpCN pc00Pl7qTd6PQGPWPgMPa6kT142zpSE+C3ksvXeVaWPDylvNq0oeruvSETjpHYHFTcfv x4h96aB3aI7F2VMNpVm6MyanBF9b4fGKas0gCjXfj+u+NY5LSXwW459BJj+m9Ha7PV+E CGH00I/4vcoc/IJ4ULTF5y8Q+GIZaBvYMcAI95eC7rxhLVsjCZImKq7R3Q1BRYHmsTHs qPLA==
MIME-Version: 1.0
X-Received: by 10.112.181.68 with SMTP id du4mr7931662lbc.11.1429903853831; Fri, 24 Apr 2015 12:30:53 -0700 (PDT)
Received: by 10.114.74.225 with HTTP; Fri, 24 Apr 2015 12:30:53 -0700 (PDT)
In-Reply-To: <5539FE54.2030103@gmail.com>
References: <551C0877.1060100@gmail.com> <552F4165.9020300@gmail.com> <5536AB1E.6060507@gmail.com> <CAC8QAcc6mDoBC6x9QJPsyrSv092Kv5b+LZCUgy_mFzJjk0OTFA@mail.gmail.com> <5537D047.5040502@gmail.com> <CAC8QAce+EQWWEc1PwE9sEOhsvMPS8kEGAd9g=av6swHYMUba-Q@mail.gmail.com> <5539FE54.2030103@gmail.com>
Date: Fri, 24 Apr 2015 14:30:53 -0500
Message-ID: <CAC8QAcf_WyHWF1GY9m9fsaQPMT0_eH5MsRyo9Fzm9jppZJ2PPg@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/dmm/_-yH0anTnbsD42h7MuORbL_G540>
Cc: sofiane.imadali@gmail.com, Basavaraj Patil <bpatil1@gmail.com>, "dmm@ietf.org" <dmm@ietf.org>
Subject: Re: [DMM] Call for adoption: draft-perkins-dmm-4283mnids-01
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Apr 2015 19:30:58 -0000
On Fri, Apr 24, 2015 at 3:27 AM, Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote: > Le 23/04/2015 19:11, Behcet Sarikaya a écrit : >> >> On Wed, Apr 22, 2015 at 11:45 AM, Alexandru Petrescu >> <alexandru.petrescu@gmail.com> wrote: >>> >>> Le 22/04/2015 18:06, Behcet Sarikaya a écrit : >>>> >>>> >>>> Hi Alex, >>>> >>>> On Tue, Apr 21, 2015 at 2:55 PM, Alexandru Petrescu >>>> <alexandru.petrescu@gmail.com> wrote: >>>>> >>>>> >>>>> Le 16/04/2015 06:58, Jouni Korhonen a écrit : >>>>>> >>>>>> >>>>>> >>>>>> Folks, >>>>>> >>>>>> The adoption call for this I-D has ended. There is a clear concensus >>>>>> to >>>>>> adopt the I-D as a working group item. >>>>> >>>>> >>>>> >>>>> >>>>> I support its adoption. >>>>> >>>>> We have been working with an identifier specific to automobiles to use >>>>> to >>>>> realize access control. Identifying an entire set of IP nodes deployed >>>>> in a >>>>> vehicle is different than identifying an end-user like address@realm. >>>>> >>>>> We looked for such an identifier and believe the VIN (Vehicle >>>>> Identification >>>>> Number) be a good candidate. >>>>> >>>>> One would consider using one type, like type 40, to encode the VIN or >>>>> parts >>>>> of it, into an MN-ID. >>>>> >>>>> The questions to the group are the following: >>>>> - is VIN considered private information? (in deployments it is private >>>>> to a certain extent, but publicly avaliable to cameras or in public >>>>> databases to another extent). >>>>> - is the MN-ID type 40 ok for it. >>>>> - is one type sufficient or should there be subtypes. >>>> >>>> >>>> >>>> What is your model here in providing Internet access to the car? >>>> As you may know, operators in US are deploying systems that connect >>>> the car to their LTE network upstream and downstream is the passengers >>>> in the car that access over Wi-Fi. >>>> With LTE, you get mobility support which is based on fixed anchoring. >>>> I cc'ed to Raj who works on these types of technologies. >>>> The ID there is the IMSI. I don't think vin is used. >>> >>> >>> >>> The model of Internet access to the cars for cars currently on market in >>> Europe is the same - the LTE technology is used, using the IMSI as an >>> identifier. However, that does not use MN-ID, is only IPv4, is not WiFi >>> and >>> does not resist to cellular generation upgrades to 5G and beyond. >> >> >> I don't understand the handover scenario. I think you are mixing the >> car and the passengers in the car. >> LTE is available on a large geography, why should you handover the >> upstream traffic to Wi-Fi? > > > When the car arrives home it connects to the WiFi available in home, thus > handing over from LTE. This is a sold use-case at e.g. Tesla. The WiFi > hotspot can be the one deployed in-house, in-garage, or the WiFi offered by > the electrical recharging stations. > Even if the is the case then 3GPP developed a lot of things on accessing non-3GPP networks like Wi-Fi. I think line-id is used instead of IMSI? Behcet > Other manufacturers propose scenarios in which car's WiFi antenna switches > from being an in-car hotspot to being a Client to outside wifi. > > Some consider 802.11p (wifi for vehicles) to be deployed along highways and > cars to perform handovers between these 802.11p access points. > > Next time on highway scan for WiFi - one is surprised by the number of > hotspots driving around, even though often they use portals. > > There are many commercially considered scenarios involving WiFi handovers > for cars. > > Alex > > >> >> Behcet >>> >>> >>> Newer models will feature IPv6 in addition to IPv4, WiFi handover from >>> LTE >>> to house's hotspot, continuous sessions, and over-the-air software update >>> for cheap upgradeability to future generation 5G and beyond. >>> >>> In this context it is hard to imagine IMSI will be there for a long time >>> in >>> a given car, and a more permanent identifier is needed. >>> >>> To Raj - is LTE considering other kinds of identifiers for access control >>> (other than IMSI) for vehicular environments, like V2X? >>> >>> Alex >>> >>> >>> >>>> >>>> Regards, >>>> >>>> Behcet >>>>> >>>>> >>>>> >>>>> Yours, >>>>> >>>>> Alex >>>>> >>>>> >>>>>> >>>>>> - Jouni & Dapeng >>>>>> >>>>>> 4/1/2015, 8:02 AM, Jouni Korhonen kirjoitti: >>>>>>> >>>>>>> >>>>>>> >>>>>>> Folks, >>>>>>> >>>>>>> This emails starts a two week call for the I-D >>>>>>> draft-perkins-dmm-4283mnids-01 >>>>>>> to confirm the aadoption s a DMM WG document. The call ends April >>>>>>> 15th >>>>>>> EOB PST. >>>>>>> >>>>>>> Express your support or opposition to the mailing list. During the >>>>>>> IETF92 meeting we got 7 voices for the adoption so at least the same >>>>>>> amount supporting emails should be expected. >>>>>>> >>>>>>> - Jouni & Dapeng >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> dmm mailing list >>>>>> dmm@ietf.org >>>>>> https://www.ietf.org/mailman/listinfo/dmm >>>>>> >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> dmm mailing list >>>>> dmm@ietf.org >>>>> https://www.ietf.org/mailman/listinfo/dmm >>>> >>>> >>>> >>>> >>> >>> >> >> > >
- [DMM] Call for adoption: draft-perkins-dmm-4283mn… Jouni Korhonen
- Re: [DMM] Call for adoption: draft-perkins-dmm-42… Sri Gundavelli (sgundave)
- Re: [DMM] Call for adoption: draft-perkins-dmm-42… Lyle Bertz
- Re: [DMM] Call for adoption: draft-perkins-dmm-42… Jouni Korhonen
- Re: [DMM] Call for adoption: draft-perkins-dmm-42… pierrick.seite
- Re: [DMM] Call for adoption: draft-perkins-dmm-42… Jong-Hyouk Lee
- Re: [DMM] Call for adoption: draft-perkins-dmm-42… Marco Liebsch
- [DMM] =?utf-8?Q?=E5=9B=9E=E5=A4=8D=EF=BC=9A_?=Cal… Dapeng Liu
- Re: [DMM] Call for adoption: draft-perkins-dmm-42… Jouni Korhonen
- Re: [DMM] Call for adoption: draft-perkins-dmm-42… Alexandru Petrescu
- Re: [DMM] Call for adoption: draft-perkins-dmm-42… Charlie Perkins
- Re: [DMM] Call for adoption: draft-perkins-dmm-42… Behcet Sarikaya
- Re: [DMM] Call for adoption: draft-perkins-dmm-42… Alexandru Petrescu
- Re: [DMM] Call for adoption: draft-perkins-dmm-42… Behcet Sarikaya
- Re: [DMM] Call for adoption: draft-perkins-dmm-42… Charlie Perkins
- Re: [DMM] Call for adoption: draft-perkins-dmm-42… Alexandru Petrescu
- Re: [DMM] Call for adoption: draft-perkins-dmm-42… Templin, Fred L
- Re: [DMM] Call for adoption: draft-perkins-dmm-42… Behcet Sarikaya
- Re: [DMM] Call for adoption: draft-perkins-dmm-42… Behcet Sarikaya
- Re: [DMM] Call for adoption: draft-perkins-dmm-42… Alexandru Petrescu
- Re: [DMM] Call for adoption: draft-perkins-dmm-42… Alexandru Petrescu