On 02/19/2013 12:40 PM, Alexandru Petrescu wrote:
Le 19/02/2013 18:39, Doug Barton a écrit :
On 02/19/2013 07:40 AM, Alexandru Petrescu wrote:
Such a concern would be all the more valid if there were a
specification which said 'each vehicle MUST form its IIDs based on
their VINs'. But this is
>>
>>=> Someone, somewhere (perhaps the IAB) needs to write an
>> architectural document to tell various industries to _stop_ doing
>> that. The IID is a set of bits that have no meaning, please stop
>> trying to create it in an industry/link layer technology-specific
>> manner. It does do anything
> -Original Message-
> From: ipv6-boun...@ietf.org [mailto:ipv6-boun...@ietf.org] On Behalf Of
> Alexandru
> Petrescu
> Sent: Tuesday, February 19, 2013 9:40 PM
> To: ipv6@ietf.org
> Subject: Re: I-D Action: draft-imadali-its-vinipv6-viid-00.txt
> Outside the VIN discussion, it is alread
On 2/19/13 12:40 PM, Alexandru Petrescu wrote:
I think I may need to actually better expose the problem: how to form
IPv6 addresses for vehicles. (yes we know these already exist: DHPCv6,
PRefix Delegation on cellular, stateless autoconf, NAT, NPT, 64share).
One of the questions I have in that
On 02/19/13 15:40, Alexandru Petrescu allegedly wrote:
> Le 19/02/2013 18:39, Doug Barton a écrit :
>> On 02/19/2013 07:40 AM, Alexandru Petrescu wrote:
>>> Such a concern would be all the more valid if there were a
>>> specification which said 'each vehicle MUST form its IIDs based on
>>> their V
Le 19/02/2013 18:39, Doug Barton a écrit :
On 02/19/2013 07:40 AM, Alexandru Petrescu wrote:
Such a concern would be all the more valid if there were a
specification which said 'each vehicle MUST form its IIDs based on
their VINs'. But this is not the case. We are not trying for
such a defini
On Feb 19, 2013, at 9:31 AM, Alexandru Petrescu
wrote:
> Le 18/02/2013 22:07, Roger Jørgensen a écrit :
>> On Mon, Feb 18, 2013 at 9:36 PM, Scott Brim
>> wrote:
>>> I have the usual concerns about privacy. I have no problem with
>>> someone knowing the endpoint that is communicating is associ
On 02/19/2013 07:40 AM, Alexandru Petrescu wrote:
Such a concern would be all the more valid if there were a specification
which said 'each vehicle MUST form its IIDs based on their VINs'. But
this is not the case. We are not trying for such a definitive document.
We are certain that some vehi
Le 19/02/2013 16:59, Roger Jørgensen a écrit :
On Tue, Feb 19, 2013 at 4:56 PM, Alexandru Petrescu
wrote:
Yes, and if I am not wrong, ULAs are globally unique.
There is no guaranty that it will ever be unique, just that the
chance of a collision are quite low.
I agree. The same with VINs
On Tue, Feb 19, 2013 at 4:56 PM, Alexandru Petrescu
wrote:
> Yes, and if I am not wrong, ULAs are globally unique.
There is no guaranty that it will ever be unique, just that the chance
of a collision are quite low.
--
Roger Jorgensen | ROJO9-RIPE
rog...@gmail.com | - IPv
Le 19/02/2013 15:56, Brian E Carpenter a écrit :
3.3. Examples of use
The Mobile Router (MR) that executes the previous algorithm, is
capable of announcing the generated prefix on one or several internal
interfaces and configure one or several external interfaces,
depending on t
Le 19/02/2013 15:49, Scott Brim a écrit :
On 02/19/13 09:23, Alexandru Petrescu allegedly wrote:
Well I agree with you in a sense. Connecting a vehicle to the
Internet in that way makes it easier than before to find its VIN.
However, may I add that the VIN of a vehicle is very easy to get.
It
Le 19/02/2013 15:40, Brian E Carpenter a écrit :
I do not understand the following:
Bits 55 and 56 that correspond to U/L bits are set accordingly to
the recommendations.
I suppose the reference is to the U and G bits (in positions 6 and 7
in the IID, or 70 and 71 in the IPv6 address, in IETF
On 2/19/13 6:31 AM, Alexandru Petrescu wrote:
Le 18/02/2013 22:07, Roger Jørgensen a écrit :
On Mon, Feb 18, 2013 at 9:36 PM, Scott Brim
wrote:
I have the usual concerns about privacy. I have no problem with
someone knowing the endpoint that is communicating is associated
with a vehicle (or t
> 3.3. Examples of use
>
>The Mobile Router (MR) that executes the previous algorithm, is
>capable of announcing the generated prefix on one or several internal
>interfaces and configure one or several external interfaces,
>depending on the scenario. For instance, under some cond
On 02/19/13 09:36, Alexandru Petrescu allegedly wrote:
> I agree to the privacy concerns.
Great. Thanks.
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
---
On 02/19/13 09:40, Brian E Carpenter allegedly wrote:
> Also, I do not wish to broadcast my VIN number to the world.
> While VIN numbers are not a big secret, associating my on line
> transactions with my car's identity is definitely a big no-no.
Right.
---
On 02/19/13 09:23, Alexandru Petrescu allegedly wrote:
> Well I agree with you in a sense. Connecting a vehicle to the Internet
> in that way makes it easier than before to find its VIN.
>
> However, may I add that the VIN of a vehicle is very easy to get. It is
> displayed under the shield and
I do not understand the following:
>Bits 55 and 56 that correspond to U/L bits are set accordingly to the
>recommendations.
I suppose the reference is to the U and G bits (in positions 6 and 7
in the IID, or 70 and 71 in the IPv6 address, in IETF notation).
But what "recommendations" app
Le 19/02/2013 00:06, Thierry Ernst a écrit :
I also think a VIN-based IPv6 addressing is a bad idea.
People involved in ITS (Intelligent Transportation System) in other
SDOs (ISO, ETSI, CEN) are using pseudonyms at L2 (see the SeVeCom
project, or the PRESERVE project) and NEMO at L3 (see GeoNet
Le 18/02/2013 22:07, Roger Jørgensen a écrit :
On Mon, Feb 18, 2013 at 9:36 PM, Scott Brim
wrote:
I have the usual concerns about privacy. I have no problem with
someone knowing the endpoint that is communicating is associated
with a vehicle (or that I, a human, am communicating from a
vehicle
Le 18/02/2013 22:07, Roger Jørgensen a écrit :
On Mon, Feb 18, 2013 at 9:36 PM, Scott Brim
wrote:
I have the usual concerns about privacy. I have no problem with
someone knowing the endpoint that is communicating is associated
with a vehicle (or that I, a human, am communicating from a
vehicle
Le 19/02/2013 08:46, Hesham Soliman a écrit :
On Mon, Feb 18, 2013 at 9:36 PM, Scott Brim
wrote:
I have the usual concerns about privacy. I have no problem with
someone knowing the endpoint that is communicating is associated
with a vehicle (or that I, a human, am communicating from a
vehicl
6MAN has a two hour slot allocated for Orlando:
6man Session (2:00)
2013-03-15
Friday Afternoon Session I 1120 - 1220
Friday Afternoon Session II 1230 - 1330
Room Name: Caribbean 4
If you have a draft you would like to discuss, please send your request for
agenda time to the 6man chair
24 matches
Mail list logo
