IETF Logo Mail Archive

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

Behcet Sarikaya <sarikaya2012@gmail.com> Wed, 22 April 2015 16:07 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 4FF501B36E5 for <dmm@ietfa.amsl.com>; Wed, 22 Apr 2015 09:07:14 -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 zK9WsNPBlLfd for <dmm@ietfa.amsl.com>; Wed, 22 Apr 2015 09:07:13 -0700 (PDT)
Received: from mail-lb0-x231.google.com (mail-lb0-x231.google.com [IPv6:2a00:1450:4010:c04::231]) (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 4E07E1ACE8E for <dmm@ietf.org>; Wed, 22 Apr 2015 09:06:11 -0700 (PDT)
Received: by lbbqq2 with SMTP id qq2so183852452lbb.3 for <dmm@ietf.org>; Wed, 22 Apr 2015 09:06:09 -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=up1YtU5YlT8oEme0eLMkO9npRGfPnmCChf+G3EkJOwk=; b=QdT73fN1WvmK5K2H+e8EIcWjaOf6m89o7ol3/kkpbYDrS7GE/g46zJZCd5bDWhtNVF Ht1bH/tZC793j6BmCdW7n4QIYzY7dIAwmfK2BscNoJfs502YkRNolF72m4+Ov3qvr/pt 4k7IlZHiaFV4E1/V1foCWCewQ0kc229YsYkhYgKwA/VOJBornBI7Y0B/TRXLimCUVM+V TaCGWD+np/7SI0Z0AD6PjUd/+s4slaW7fxiWZ3Ji011Lyc7OX8W1NHj3/QPYE+sgG7R6 Rz2p06Nn3BbU11KtErCN/HJWZlL3PDU2zpk60KCqNfbAOEkiHefesf91QjBKZgVlRYIi 58rQ==
MIME-Version: 1.0
X-Received: by 10.112.93.72 with SMTP id cs8mr25412997lbb.15.1429718769746; Wed, 22 Apr 2015 09:06:09 -0700 (PDT)
Received: by 10.114.74.225 with HTTP; Wed, 22 Apr 2015 09:06:09 -0700 (PDT)
In-Reply-To: <5536AB1E.6060507@gmail.com>
References: <551C0877.1060100@gmail.com> <552F4165.9020300@gmail.com> <5536AB1E.6060507@gmail.com>
Date: Wed, 22 Apr 2015 11:06:09 -0500
Message-ID: <CAC8QAcc6mDoBC6x9QJPsyrSv092Kv5b+LZCUgy_mFzJjk0OTFA@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/WRl2iTSQ8XjB-X35qvkMIf93xlU>
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: Wed, 22 Apr 2015 16:07:14 -0000

 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.

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

v2.23.0 | Report a Bug | By Email