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

Charlie Perkins <charles.perkins@earthlink.net> Tue, 21 April 2015 20:55 UTC

Return-Path: <charles.perkins@earthlink.net>
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 2A8AD1B2B2B for <dmm@ietfa.amsl.com>; Tue, 21 Apr 2015 13:55:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] 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 DLOF1REt3scd for <dmm@ietfa.amsl.com>; Tue, 21 Apr 2015 13:55:44 -0700 (PDT)
Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) by ietfa.amsl.com (Postfix) with ESMTP id 82AE71A8FD2 for <dmm@ietf.org>; Tue, 21 Apr 2015 13:55:44 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=WMT650vHG7sTcCrfjClKL1OH+nK8oVB4hTC9+0OyqVJLSYnYwI36Tm9qxwAIYhmr; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [107.1.141.74] (helo=[192.168.252.133]) by elasmtp-curtail.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1YkfCp-00033g-MM; Tue, 21 Apr 2015 16:55:43 -0400
Message-ID: <5536B94B.2090800@earthlink.net>
Date: Tue, 21 Apr 2015 13:55:39 -0700
From: Charlie Perkins <charles.perkins@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: dmm@ietf.org
References: <551C0877.1060100@gmail.com> <552F4165.9020300@gmail.com> <5536AB1E.6060507@gmail.com>
In-Reply-To: <5536AB1E.6060507@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac770993d24ae474ae7d1454dcb28fbb3e8350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 107.1.141.74
Archived-At: <http://mailarchive.ietf.org/arch/msg/dmm/4OVIoHf-F8n7IbWE-1ZT3pt49hU>
Cc: sofiane.imadali@gmail.com
Subject: Re: [DMM] Call for adoption: draft-perkins-dmm-4283mnids-01
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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: Tue, 21 Apr 2015 20:55:46 -0000

Hello folks,

The ...-00 document draft-dmm-4283mnids-00.txt has been submitted.

I'll make a new draft with VIN as a type of MNID as soon as Alex's 
questions have
proposed answers.

Regards,
Charlie P.


On 4/21/2015 12:55 PM, Alexandru Petrescu 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.
>
> 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
>