Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 802.21 for IP handovers

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 20 February 2017 15:08 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 C1CD51295A6 for <its@ietfa.amsl.com>; Mon, 20 Feb 2017 07:08:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.333
X-Spam-Level:
X-Spam-Status: No, score=-0.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, SPF_SOFTFAIL=0.665] autolearn=no 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 0Bfh8F4NVs5P for <its@ietfa.amsl.com>; Mon, 20 Feb 2017 07:08:09 -0800 (PST)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5CD712956D for <its@ietf.org>; Mon, 20 Feb 2017 07:08:02 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id v1KF81Cr042797; Mon, 20 Feb 2017 16:08:01 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id EFE2520A6D9; Mon, 20 Feb 2017 16:08:00 +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 E217B2065AE; Mon, 20 Feb 2017 16:08:00 +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 v1KF80eA009693; Mon, 20 Feb 2017 16:08:00 +0100
To: Jérôme Härri <jerome.haerri@eurecom.fr>, its@ietf.org
References: <148052970170.9607.12043916621198119260.idtracker@ietfa.amsl.com> <e14a985e-ae65-cc59-c431-47fed128c3a8@cea.fr> <007401d285e2$18183b30$4848b190$@eurecom.fr>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <3e22c987-163c-dcd3-f775-e9b49617c6d1@gmail.com>
Date: Mon, 20 Feb 2017 16:07:55 +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: <007401d285e2$18183b30$4848b190$@eurecom.fr>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/tV420DStwej8pYTp7wkEJQH0O7Y>
Subject: Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 802.21 for IP handovers
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:08:11 -0000

Jérôme,

Le 13/02/2017 à 11:15, Jérôme Härri a écrit :
> Hello Alex,
>
> I am not sure to fully understand the objective of this piece of text
> anymore.

It is an IP-over-foo document.  There are many IP-over-foo RFCs, e.g.
RFC2464.  They describe very simple parameters like MTU, address
mapping, and others.

> I follow some other comments raising concerns on mentioning any IEEE
> 1609-related message, as it would imply that our stack would be able
> to decode them..which is far from being clear at this time. It is
> indeed also an IEEE standard, but it is not the same 'community' and
> not the same stack level.
>
> I think we are being too specific in a field of large unknown. We
> should remain more pragmatic and adopt one of the following two
> strategy: 1) a full specification of our claim: if we claim that
> something can be done with one specific message and if it is in the
> scope of the document, then explicitly mention it. This would
> typically be the case if we want to explain how to get RSSI from
> IPv6 RA or any other related IPv6 message.

This should be described in an 'IP handover on 802.11 OCB' Internet Draft.

> 2) just mention generalities, without any specifics: e.g. this text
> could be simplified as follows: "(...) in case of absence of L3
> signaling, L2 signaling MAY be used to estimate the channel or link
> quality. " (whatever L2 means).

Even that may look too detail for some.

Alex

>
> Best regards,
>
> Jérôme
>
>
> -----Original Message----- From: its [mailto:its-bounces@ietf.org]
> On Behalf Of Alexandre Petrescu Sent: Sunday 12 February 2017 19:06
> To: its@ietf.org Subject: [ipwave]
> draft-ietf-ipwave-ipv6-over-80211ocb-00 802.21 for IP handovers
>
> draft-ietf-ipwave-ipv6-over-80211ocb-00 802.21 for IP handovers
>
> Hello IPWAVErs,
>
> José Santa Lozano commented that their implementation can rely on
> 802.21 (instead of WSA-with-WRA-field or RA) to realize IP handovers
> in 802.11-OCB.
>
> The old text is this:
>> One such message may be the 802.11p's Time Advertisement, or
>> higher layer messages such as the "Basic Safety Message" (in the
>> US) or the "Cooperative Awareness Message " (in the EU), that are
>> usually sent several times per second. Another alternative
>> replacement for the IPv6 Router Advertisement may be the message
>> 'WAVE Routing Advertisement' (WRA), which is part of the WAVE
>> Service Advertisement and which may contain optionally the
>> transmitter location; this message is described in section 8.2.5
>> of [ieeep1609.3-D9-2010].
>
> New, if at all:
>> One such message may be the 802.11p's Time Advertisement, or
>> higher layer messages such as the "Basic Safety Message" (in the
>> US) or the "Cooperative Awareness Message " (in the EU), that are
>> usually sent several times per second. Another alternative
>> replacement for the IPv6 Router Advertisement may be the message
>> 'WAVE Routing Advertisement' (WRA), which is part of the WAVE
>> Service Advertisement and which may contain optionally the
>> transmitter location; this message is described in section 8.2.5
>> of [ieeep1609.3-D9-2010].  Yet another alternative replacement for
>> IPv6 RA is the involvement of 802.21 signal levels, or additional
>> 802.21 entities,
>
> Alex
>
>
>