Re: Vehicle's VIN in IPv6.

Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 31 March 2011 20:13 UTC

Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4E6C528C12B for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 13:13:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.818
X-Spam-Level:
X-Spam-Status: No, score=-3.818 tagged_above=-999 required=5 tests=[AWL=-0.219, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 76b54mupJ+FQ for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 13:13:31 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id CD38A28C12A for <ipv6@ietf.org>; Thu, 31 Mar 2011 13:13:30 -0700 (PDT)
Received: by bwz13 with SMTP id 13so2222788bwz.31 for <ipv6@ietf.org>; Thu, 31 Mar 2011 13:15:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=+4JeY0CRM0ve3VueJExknzi0jCuaLkRCoSTtgqDYJUY=; b=rDnaRPSWKnPzYxiccQKCEtdRqYwUYujEQqlHOFluGfMJmJuhAWjyowYkB/JIfi01bL /FUoAMTPgxuhH5Jiz1se3V+CMMp8Kr/roSNZok4s6U4fgPV/KPUF3YG6OWD6Ct6VSKe7 KmNDKQFWsINd3YR5oAJI1xOF1KoHhrp5h7xp4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=TN/ysR2pWvdSde0fcPJW+aqzba8hFp8+Uv7ArlJsu0FaX1HS+vR9s42qB0HumX6VKD xJi5kXPS2FrQvYhUG7ZXzLu+m1AOdciHDQMdI6kB6ykTM9ajPLSRxHdC2JpEdkWAgsNT qimMd6NBN1DyUXEbN/z4wyIREvF9LVxIzdLAs=
Received: by 10.204.74.7 with SMTP id s7mr409835bkj.57.1301602509800; Thu, 31 Mar 2011 13:15:09 -0700 (PDT)
Received: from [127.0.0.1] (dhcp-150a.meeting.ietf.org [130.129.21.10]) by mx.google.com with ESMTPS id l1sm969950bkl.13.2011.03.31.13.15.04 (version=SSLv3 cipher=OTHER); Thu, 31 Mar 2011 13:15:08 -0700 (PDT)
Message-ID: <4D94E0C3.9030400@gmail.com>
Date: Thu, 31 Mar 2011 22:14:59 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; fr; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Jong-Hyouk Lee <jonghyouk@gmail.com>
Subject: Re: Vehicle's VIN in IPv6.
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <4D944365.4020809@kit.edu> <4D944505.3060407@gmail.com> <E9DE74CB-03B0-4529-B6D1-BD875332C20F@gmail.com> <AANLkTimmqkddMrTAzn0yZYKJ1mnSGAoOTqiiir92beE2@mail.gmail.com> <6CEB6E26-AE20-450B-AD61-BE7B7029EFCF@gmail.com> <4D949559.3090509@gmail.com> <AANLkTinVqhU97_kvPJ4EUtNog-oKoehGdW9jqFHfCjdk@mail.gmail.com> <4D949FA2.5070901@gmail.com> <AANLkTikviCSzupW0L+fj6Zxh6gBVEiC6ZthJRShybfLX@mail.gmail.com>
In-Reply-To: <AANLkTikviCSzupW0L+fj6Zxh6gBVEiC6ZthJRShybfLX@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: ipv6@ietf.org, Bob Hinden <bob.hinden@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, =?ISO-8859-1?Q?Radek_Wr=F3bel?= <radoslaw.wrobel@pwr.wroc.pl>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 20:13:32 -0000

Le 31/03/2011 18:00, Jong-Hyouk Lee a écrit :
> Hi, Alex.
>
> Please, come back to a person who I know. See inline.
>
> On Thu, Mar 31, 2011 at 5:37 PM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com>;  wrote:
>>
>> Le 31/03/2011 17:02, Jong-Hyouk Lee a écrit :
>>>
>>> Hi, Alex.
>>>
>>> Plz, see inline. I fully failed to understand your words.
>>>
>>> On Thu, Mar 31, 2011 at 4:53 PM, Alexandru Petrescu
>>> <alexandru.petrescu@gmail.com>;    wrote:
>>>>
>>>> Le 31/03/2011 16:19, Bob Hinden a écrit :
>>>>>
>>>>> On Mar 31, 2011, at 1:15 PM, Scott Brim wrote:
>>>>>
>>>>>> On Thu, Mar 31, 2011 at 11:32, Bob
>>>>>> Hinden<bob.hinden@gmail.com>;  wrote:
>>>>>>>
>>>>>>> They could use a fixed car address and use mobile IPv6
>>>>>>> with a provider based address.
>>>>>>
>>>>>> That would help.  A rendezvous point (e.g. home agent)
>>>>>> always helps to protect confidentiality. Plus a firewall to
>>>>>> protect the always-out-of-date vehicle software.   They can
>>>>>> work out how to do path optimization later.
>>>>>
>>>>> I agree.  If you put the "home agent" in the middle of the
>>>>> internet (for some value of middle), then path optimization
>>>>> probably isn't that important.
>>>>
>>>> Makes some sense.  This "middle" depends on latency; and core
>>>> network has an order of magnitude (sometimes 2) less than even
>>>>  the first hop to vehicle.
>>>
>>> In the context of ITS communication, how do you expect the
>>> movement of vehicles?
>>
>> Right, mouvement of private vehicles is unpredictable.  Some
>> common sense may reduce the space to, say, mostly a continent.  And
>> even some vehicles like trains have very highly predictable
>> trajectories.
>>
>> Not only ITS should be considered, but also operators of public
>> transportation networks (if they're not already part of it).
>>
>>> Then, how do you decide the location of home agent for reducing
>>> the routing performance for user data packets destined to hosts
>>> attached to the router of a vehicle?
>>
>> The direct seller of vehicle (concessionnaire, garage) may decide
>> to host HA relativley close (geo terms) to where the vehicle is
>> owned, suffices HA to be on wire instead of wireless, which is
>> rather natural. The parts manufacturer too.  The transportation
>> operator, etc.
>
> Ummm...let me explain a little thing about the use of home agent
> (HA) in the context of ISO and ETSI. The HA is located at the central
> ITS station that must be maintained by authorized organization,
> i.e., belonging to the government.

Hmm... yes that can be done.  Some governments are even Cert Auth, but
that does not prevent other private organizations to be CA.

> Such private companies will not have permissions to install the HA;
> might be possible for only private company's client, but this is not
>  the case we're talking here.

Ah I see, I agree.

But I am still curious to understand the lines of VIN-v6 proposal
before discarding it. In the process maybe I (or someone else) get a
chance to suggest some alternative... to satisfy some requirement,
some problem statement.

Alex

>> The common wisdom of needing to host a webcache closer in order to
>> deliver data quicker to http clients assumes the http clients use
>> wire too (as the servers do).  The latency difference between pc's
>>  wire and server's wire is much smaller than between server's wire
>>  and wireless.
>
> Come on. I don't really know why you bring this text here.
>
>>
>>>> That means that it may suffice to put the HA on wired link,
>>>> anywhere in the Internet, and relatively close (in terms of
>>>> hopcount) to where the handover is about to take place.
>>>
>>> In the context of this thread, Bob mentioned about the routing
>>> performance, exactly saying user data packets' routing
>>> performance, not saying handover latency mainly consisted of 1)
>>> movement detection at IP level; 2) address configuration; and 3)
>>>  location update (BU/BA) to the home agent.
>>
>> Right, I didn't mean handover performance.
>>
>> Routing performance... hmm... I believe there is not much routing
>> performance gain when trying to bring HA as close as possible to
>> the handover place.
>>
>> Alex
>>>
>>> Cheers.
>>>
>>> And not necessarily put it where eg
>>>>
>>>> akamai stuff sits.
>>>>
>>>> Alex
>>>>
>>>>> Bob
>>>>>
>>>>> --------------------------------------------------------------------
>>>>>
>>>>>
>>>>>
>>>>>
>>
>>>>>
>>>>>
>>>>>
IETF IPv6 working group mailing list ipv6@ietf.org Administrative
>>>>>
>>>>> Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>>>> --------------------------------------------------------------------
>>>>
>>>>
>>>>>
>>>>>
>>>>>
>>
>>>>>
>>>>>
>>>>>
--------------------------------------------------------------------
>>>>
>>>> IETF IPv6 working group mailing list ipv6@ietf.org
>>>> Administrative Requests:
>>>> https://www.ietf.org/mailman/listinfo/ipv6
>>>> --------------------------------------------------------------------
>>>>
>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>>>>
>>>>
>>>>
>
>