Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 handover considerations at 802.11-OCB and 1609

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 20 February 2017 15:05 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: its@ietfa.amsl.com
Delivered-To: its@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09961129410 for <its@ietfa.amsl.com>; Mon, 20 Feb 2017 07:05:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.333
X-Spam-Level:
X-Spam-Status: No, score=-5.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=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 fxJgbB5n2fx2 for <its@ietfa.amsl.com>; Mon, 20 Feb 2017 07:05:41 -0800 (PST)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41D041204D9 for <its@ietf.org>; Mon, 20 Feb 2017 07:05:41 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id v1KF5IkA012923; Mon, 20 Feb 2017 16:05:18 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 17A44202E85; Mon, 20 Feb 2017 16:05:18 +0100 (CET)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 0A7FB202E3C; Mon, 20 Feb 2017 16:05:18 +0100 (CET)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id v1KF5Hia007759; Mon, 20 Feb 2017 16:05:17 +0100
To: dickroy@alum.mit.edu, its@ietf.org
References: <148052970170.9607.12043916621198119260.idtracker@ietfa.amsl.com> <4dfb57e1-64fa-8798-2507-ae979cbfc8c9@cea.fr> <841D6C4B924C4AC0AC5129D9CE161B02@SRA6>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <c026bde8-0c64-8080-4a49-108f64bec0b4@gmail.com>
Date: Mon, 20 Feb 2017 16:05:12 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <841D6C4B924C4AC0AC5129D9CE161B02@SRA6>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/qYkzNo-2qpIjys_b5O57Q3En7R0>
Subject: Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 handover considerations at 802.11-OCB and 1609
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF <its.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/its>, <mailto:its-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/its/>
List-Post: <mailto:its@ietf.org>
List-Help: <mailto:its-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/its>, <mailto:its-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 15:05:43 -0000

Dick,

Le 04/02/2017 à 09:51, Dick Roy a écrit :
> Now you are getting to the real heart of the ITS WI in the IETF!
> 1609/802.11 OCB was and is simply a single link protocol set.  There
> are NO networks, no networking, no nothing.  IPv6 was recognized in
> the 1609 standards (and ISO standards) as the "preferred" networking
> technology should there be a need for such (which there obviously
> is!).  While 802.11 has developed and is developing functionality
> that makes seemless handover between APs a bit easier (.11ai and
> friends), the how it is accomplished in the "network" is out of scope
> for both 802 and 1609.  You will not get either group to develop
> mobility management protocols anytime soon (read: before we all pass
> away:^)  Furthermore, there is NO chance of deploying a wide area
> bridged network consisting solely of 5.9GHz RSUs.  Some networking
> functionality will be mandatory in any deployments.  Enter IPv6!
> IPv6 mobility management (handover, session continuity, etc.) for
> rapidly changing network topologies is EXACTLY what we (those of us
> doing all the other ITS comm stuff:^)) "hired you guys at the IETF"
> to do for us!

I can agree that IEEE would not do IP handover work.

Handovers are of two types: MAC handovers and IP handovers.  The IP
handovers are designed at IETF, e.g. the Mobile IP protocol.

The IP handovers would be specified in a separate document, because the
IP-over-foo RFCs dont describe handovers.

Alex

>
> Cheers,
>
> RR
>
> -----Original Message----- From: Alexandre Petrescu
> [mailto:alexandre.petrescu@gmail.com] Sent: Thursday, February 2,
> 2017 9:39 AM To: its@ietf.org Subject: [ipwave]
> draft-ietf-ipwave-ipv6-over-80211ocb-00 handover considerations at
> 802.11-OCB and 1609
>
> draft-ietf-ipwave-ipv6-over-80211ocb-00 handover considerations at
> 802.11-OCB and 1609
>
> Hello IPWAVErs,
>
> There has been a comment that handovers were never seriously
> addressed in 802.11p or IEEE 1609.
>
> As such, I suggest two things.
>
> One is I adapt the text like this:
>
> old:
>> However, there are several deployment considerations to optimize
>> the performances of running IPv6 over 802.11p (e.g. in the case of
>> handovers between 802.11p Access Points, or the consideration of
>> using the IP security layer).
>
> new:
>> However, there may be some deployment considerations helping
>> optimize the performances of running IPv6 over 802.11-OCB (e.g. in
>> the case of handovers between 802.11-OCB [term], or the
>> consideration of using the IP security layer).
>
> The other is that I suggest IEEE 802.11-OCB and IEEE P1609 to
> address seriously the handover considerations.  At IETF there are a
> few RFCs and running code that describe how IP handovers happen.
>
> Yours,
>
> Alex
>
>
>