Re: [DMM] Call for adoption: draft-perkins-dmm-4283mnids-01

Behcet Sarikaya <sarikaya2012@gmail.com> Thu, 23 April 2015 17:11 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 D5C021ACDA7 for <dmm@ietfa.amsl.com>; Thu, 23 Apr 2015 10:11:46 -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 Y2SjOjeJ9ZWo for <dmm@ietfa.amsl.com>; Thu, 23 Apr 2015 10:11:45 -0700 (PDT)
Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (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 EA1571ACDBC for <dmm@ietf.org>; Thu, 23 Apr 2015 10:11:33 -0700 (PDT)
Received: by lbbzk7 with SMTP id zk7so18227278lbb.0 for <dmm@ietf.org>; Thu, 23 Apr 2015 10:11:32 -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=XdGok+txuIuQEAUzxHC8KyCBwbwENWdWK6UiR/L6SfA=; b=omjPDra+HPByCn+vsWcNXRurLtb3WlAC3eBeBJBrrjCEK2TpaU2YE0mwSw8i+AH2kB 0TlAE59wXoK5nVK5xkU7i6sH78gi5/MiIp7ZMqAf7Ax/8zR7S7w5OkvWGcFQLd4rso6O ixwXRWbJeBfJjO3oPos6x1jJUUcwIUThiVkiEg2Vxty+vz/iuyG0ko/kmixMurJdBPOk MYZjIe2QPEEn0XHnULmVA0zFlpDUzLLq2eewdD1xUXA9fcgcTN4pchj8rl2oImy7oGQr 4yYAJ2pM3B17BzyT/gy0/d1XilnzzMtmmPASMy1ho32lbRTu8DjO8hSdkcGwINomrwxy /U8Q==
MIME-Version: 1.0
X-Received: by 10.152.37.69 with SMTP id w5mr3317968laj.15.1429809092396; Thu, 23 Apr 2015 10:11:32 -0700 (PDT)
Received: by 10.114.74.225 with HTTP; Thu, 23 Apr 2015 10:11:32 -0700 (PDT)
In-Reply-To: <5537D047.5040502@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>
Date: Thu, 23 Apr 2015 12:11:32 -0500
Message-ID: <CAC8QAce+EQWWEc1PwE9sEOhsvMPS8kEGAd9g=av6swHYMUba-Q@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/hy9y-xeho6eOxyfajwsfOy8xIGg>
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: Thu, 23 Apr 2015 17:11:47 -0000

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?

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
>>
>>
>>
>
>