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

François Simon <fygsimon@gmail.com> Wed, 01 February 2017 14:01 UTC

Return-Path: <fygsimon@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 4FF5A12944C for <its@ietfa.amsl.com>; Wed, 1 Feb 2017 06:01:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.688
X-Spam-Level:
X-Spam-Status: No, score=-2.688 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 F91g5Xd9m51C for <its@ietfa.amsl.com>; Wed, 1 Feb 2017 06:01:52 -0800 (PST)
Received: from mail-qt0-x232.google.com (mail-qt0-x232.google.com [IPv6:2607:f8b0:400d:c0d::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDF5D12945A for <its@ietf.org>; Wed, 1 Feb 2017 06:01:47 -0800 (PST)
Received: by mail-qt0-x232.google.com with SMTP id v23so265072850qtb.0 for <its@ietf.org>; Wed, 01 Feb 2017 06:01:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:thread-index:content-language; bh=Gi17f9sqym7dbnoaC3gsqqwIG4bLcC3LlkxpZjZ0P5c=; b=pkDAwkNwJT6wI76eQ2szDmEOUQtB6ndSna3oWII7/rXXY/wlqzW0/xJXH+yqoichKr 4dvWAVn/STlBhrKMZEJEyQgrLvS7/0WcLQXtov4yWJCsh3XHnjbi5CNZqGiQmxte7hH8 EvC5IhIfIYKhWiBuYv91+ghdyNXRsz46Sxee5SShj7hmNpET30bYF+MmMx6QLlpcPEs6 aKDr8YZmu7pubJ1SRbj+rdHjkQSpz93T1vnX5VpF7H9yE0vuWbi4CtEM1kX0tQNbmF4i excUyfzWgOTQksQpvk4hj2DEUA/GZBSA7HA0eBRsgFyjw5t4kOTSht6M7xnb044Q0rs+ FXCA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=Gi17f9sqym7dbnoaC3gsqqwIG4bLcC3LlkxpZjZ0P5c=; b=BZ8Szl2kDl4oUdpGN20NBtPCaeHsj7xEFe+OE9oDdUkUkQO6MotP51TOCgBo91pVK3 JD9IxMOgw51FXS7zCpsR/4fROqrYH2qiSIaPZX241NGCam9XDj5BMLEfuSGQIewZRyGX k2oxMEbf2ESorrc3YMcQ+zTWpbbEX5+uqyZXDp5Or5slwSsWrrbIOP/sRtPA3pm7G10S GMOpzGlGzWNbfXCqloi2Iy3q0S6dLrRZ7T8V8wy2I8szFpu/VYVsCnsfyluj9CLqySSi JTBfnFgxcpRkbya+nn+wqnx9QAOArWeoFJ81si8oGWOfwUvyEMo6EISMvgAQz8YMMT3g 3B1g==
X-Gm-Message-State: AIkVDXIUICNyIN3DasfmBQK2616f/EeqTu+czVj3TeosWQSEMmxceRkNSuex5O0CAUNFPQ==
X-Received: by 10.237.42.1 with SMTP id c1mr2725303qtd.10.1485957706710; Wed, 01 Feb 2017 06:01:46 -0800 (PST)
Received: from FrancoisPC (pool-173-66-69-120.washdc.fios.verizon.net. [173.66.69.120]) by smtp.gmail.com with ESMTPSA id 34sm18701034qtx.16.2017.02.01.06.01.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Feb 2017 06:01:46 -0800 (PST)
From: François Simon <fygsimon@gmail.com>
To: "'Dr. Hans-Joachim Fischer'" <HJFischer@fischer-tech.eu>, its@ietf.org
References: <148052970170.9607.12043916621198119260.idtracker@ietfa.amsl.com> <222853d1-235d-cd4e-844b-4ea6091bfb2b@cea.fr> <009901d27c83$3bd599e0$b380cda0$@eurecom.fr> <a1abcf92-8e4a-e2dd-fb34-b90ff7006f1c@fischer-tech.eu>
In-Reply-To: <a1abcf92-8e4a-e2dd-fb34-b90ff7006f1c@fischer-tech.eu>
Date: Wed, 01 Feb 2017 09:01:59 -0500
Message-ID: <009801d27c93$c1a04ab0$44e0e010$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0099_01D27C69.D8CD9E10"
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQJOjypQjcVLCnmBW2ydKpCtKDvNtwHybcogAYGf1c8B6gbavaAxF50w
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/FfKCGX_qKxbgYwnBe3rNzTHS3xE>
Cc: fygsimon@gmail.com
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 14:01:55 -0000

There is no need of beacons for IEEE 802.11 OCB, this has been debated in
the 802.11p WG years ago. 

 

Fygs

 

From: its [mailto:its-bounces@ietf.org] On Behalf Of Dr. Hans-Joachim
Fischer
Sent: Wednesday, February 01, 2017 8:19 AM
To: its@ietf.org
Subject: Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 .11-OCB does
use beacons

 

 

That is right, but it has to be presented completely. The simple drawing
suggests that Beacons are necessary for ordinary operation.

For sure MAC management frames are supported for specific purposes.

 

Hans-Joachim

 

Am 01.02.2017 um 13:03 schrieb Jérôme Härri:

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 <mailto: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

 






_______________________________________________
its mailing list
its@ietf.org <mailto:its@ietf.org> 
https://www.ietf.org/mailman/listinfo/its





-- 
Dr. Hans-Joachim Fischer
Managing Director
 
 
----------------------------------------------------------------------------
---- 
 
         Seminars on Cooperative Intelligent Transport Systems
             http://fischer-tech.eu/Feeds/CITSseminars.html
 
----------------------------------------------------------------------------
---- 
+ + + Instaurare omnia in Christo + + +
----------------------------------------------------------------------------
---- 
The information contained in this message is confidential and may be legally

privileged. This email is intended for the addressee(s). Addressees may be 
individual persons or members of mailing list. 
If you are not an addressee, you are hereby notified that any use, 
dissemination, or reproduction of this email and its optional attachements
is 
strictly prohibited and may be unlawful. If you are not an addressee, please

contact the sender by return e-mail and destroy all copies of the original 
message. 
----------------------------------------------------------------------------
---- 
ESF GmbH
Fichtenweg 9
89143 Blaubeuren
+49 (7344) 175340 (Direct line)
+49 (7344) 919188 (Central office)
+49 (7344) 919123 (Fax)
http://fischer-tech.eu : Main web of ESF GmbH
http://its-standards.eu : News on cooperative ITS standardization
http://its-testing.org : International consultancy for cooperative ITS
----------------------------------------------------------------------------
---- 
 
----------------------------------------------------------------------------
---- 
ESF online-news:    http://fischer-tech.eu/Feeds/esf.rss
C-ITS online news:  http://its-standards.info/Feeds/cits.rss
ESF Online Nachrichten: http://fischer-tech.de/Feeds/esfD.rss
----------------------------------------------------------------------------
---