Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 .11-OCB (non) use of beacons

Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 02 February 2017 15:21 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 4D77812965A for <its@ietfa.amsl.com>; Thu, 2 Feb 2017 07:21:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.353
X-Spam-Level:
X-Spam-Status: No, score=-5.353 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 cU90oSnC0DiF for <its@ietfa.amsl.com>; Thu, 2 Feb 2017 07:21:17 -0800 (PST)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 058AB129478 for <its@ietf.org>; Thu, 2 Feb 2017 07:21:16 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id v12FLCle021555; Thu, 2 Feb 2017 16:21:12 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 8AFA6209FD8; Thu, 2 Feb 2017 16:21:12 +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 7B137202B28; Thu, 2 Feb 2017 16:21:12 +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 v12FLCpN005710; Thu, 2 Feb 2017 16:21:12 +0100
To: dickroy@alum.mit.edu, 'Jérôme Härri' <jerome.haerri@eurecom.fr>, its@ietf.org
References: <148052970170.9607.12043916621198119260.idtracker@ietfa.amsl.com> <222853d1-235d-cd4e-844b-4ea6091bfb2b@cea.fr> <009901d27c83$3bd599e0$b380cda0$@eurecom.fr> <ABE9BD89094E4DCBA199B459F8176F2E@SRA6>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <687e75fd-7e89-211e-bce3-fea861d7baf0@gmail.com>
Date: Thu, 02 Feb 2017 16:20:52 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <ABE9BD89094E4DCBA199B459F8176F2E@SRA6>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/GpcWidJblDQ9F9dXSPZKdxS9pp8>
Subject: Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 .11-OCB (non) use of beacons
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: Thu, 02 Feb 2017 15:21:20 -0000

But some OCB implementations do send Beacons.

In that sense, I propose to say the following.

>> 4.  Aspects introduced by the OCB mode to 802.11
>>
>> In the IEEE 802.11 OCB mode, all nodes in the wireless range can
>> directly communicate with each other without authentication/
>> association procedures.  Briefly, the IEEE 802.11 OCB mode has the
>> following properties:
>>
>> o  Wildcard BSSID (i.e., all bits are set to 1) used by each node

old:
>> o  No beacons transmitted

new:
>> o  OCB implementations do not receive beacons and most OCB
>> implementations do not transmit Beacons.

Alex


Le 01/02/2017 à 20:20, Dick Roy a écrit :
> To reiterate, in OCB operation there are NO beacons and there are NO
> APs.
>
>
>
> RR
>
>
>
> ------------------------------------------------------------------------
>
>  *From:*Jérôme Härri [mailto:jerome.haerri@eurecom.fr] *Sent:*
> Wednesday, February 1, 2017 4:04 AM *To:* 'Alexandre Petrescu';
> its@ietf.org *Subject:* Re: [ipwave]
> draft-ietf-ipwave-ipv6-over-80211ocb-00 .11-OCB does use beacons
>
>
>
> Dear all,
>
>
>
> I do not agree and I would be happy to have the reference in the
> IEEE 802.11-2016 stating otherwise.
>
>
>
> In the 802.11 standard, it clearly state the following line:
>
>
>
> When dot11OCBActivated is true in a STA:
>
> " The STA _may send management frames of subtype Action_ and, if the
> STA maintains a TSF Timer, subtype Timing Advertisement "
>
> " The STA may send _control frames_, _except_ those of _subtype
> PS-Poll, CF-End, and CF-End + CFAck_ "
>
> " The STA may send _data frames of subtype Data, Null, QoS Data, and
> QoS Null_. "
>
>
>
> A beacon is a management frame, but not of a class Action, so it
> _cannot be transmitted when dot11OCBActivated_ is true in a STA. But
> I agree that it is ambiguous…nevertheless, I would then replace in
> the draft the mention of what OCB can do or can’t do (e.g. sending
> beacons) with the exact 802.11-2016 statements. This would avoid
> misunderstanding.
>
>
>
> But even if it could be possible, this does not make much sense. A
> beacon is transmitted on a channel you need to connect to get BSS
> information and also to get the right frequency. In case of OCB
> (outside context of a BSS), it is not required. But the real question
> is ‘why’ would we need beacon, assuming it could be transmitted?
>
>
>
> Best Regards,
>
>
>
> Jérôme
>
>
>
> -----Original Message----- From: its [mailto:its-bounces@ietf.org] On
> Behalf Of Alexandre Petrescu Sent: Wednesday 01 February 2017 11:51
> To: its@ietf.org Subject: [ipwave]
> draft-ietf-ipwave-ipv6-over-80211ocb-00 .11-OCB does use beacons
>
>
>
> draft-ietf-ipwave-ipv6-over-80211ocb-00 .11-OCB does use beacons
>
>
>
> Hello IPWAVErs,
>
>
>
> It was suggested in private that, contrary to what the draft says,
> the .11-OCB does use beacons.
>
>
>
> As such, the following line should disappear from the draft:
>
>
>
>> 4.  Aspects introduced by the OCB mode to 802.11
>
>>
>
>> In the IEEE 802.11 OCB mode, all nodes in the wireless range can
>
>> directly communicate with each other without authentication/
>
>> association procedures.  Briefly, the IEEE 802.11 OCB mode has the
>
>> following properties:
>
>>
>
>> o  Wildcard BSSID (i.e., all bits are set to 1) used by each node
>
>>
>
>> o  [strike through] No beacons transmitted
>
>
>
> Yours,
>
>
>
> Alex
>
>
>