Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 .11-OCB does use beacons

Jérôme Härri <jerome.haerri@eurecom.fr> Wed, 01 February 2017 12:03 UTC

Return-Path: <jerome.haerri@eurecom.fr>
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 7ED8F129400 for <its@ietfa.amsl.com>; Wed, 1 Feb 2017 04:03:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.097
X-Spam-Level:
X-Spam-Status: No, score=-5.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-3.199, URIBL_BLOCKED=0.001] 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 eXuLN-ZrW3CT for <its@ietfa.amsl.com>; Wed, 1 Feb 2017 04:03:45 -0800 (PST)
Received: from smtp2.eurecom.fr (smtp3.eurecom.fr [193.55.113.213]) by ietfa.amsl.com (Postfix) with ESMTP id 6A2B01293EC for <its@ietf.org>; Wed, 1 Feb 2017 04:03:44 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.33,320,1477954800"; d="scan'208,217";a="5707262"
Received: from monza.eurecom.fr ([192.168.106.15]) by drago2i.eurecom.fr with ESMTP; 01 Feb 2017 13:03:43 +0100
Received: from xerus29 (xerus29.eurecom.fr [172.17.31.38]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by monza.eurecom.fr (Postfix) with ESMTPSA id 5866910E5; Wed, 1 Feb 2017 13:03:43 +0100 (CET)
From: Jérôme Härri <jerome.haerri@eurecom.fr>
To: 'Alexandre Petrescu' <alexandre.petrescu@gmail.com>, its@ietf.org
References: <148052970170.9607.12043916621198119260.idtracker@ietfa.amsl.com> <222853d1-235d-cd4e-844b-4ea6091bfb2b@cea.fr>
In-Reply-To: <222853d1-235d-cd4e-844b-4ea6091bfb2b@cea.fr>
Date: Wed, 01 Feb 2017 13:03:43 +0100
Organization: EURECOM
Message-ID: <009901d27c83$3bd599e0$b380cda0$@eurecom.fr>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_009A_01D27C8B.9D9C72E0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJOjypQjcVLCnmBW2ydKpCtKDvNtwHybcogoExKXMA=
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/z44AaBa5X502nqeOtxuMshEzTLc>
Subject: Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 .11-OCB does use 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: Wed, 01 Feb 2017 12:03:46 -0000

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