IETF Logo Mail Archive

Re: [ipwave] 802.11 Data vs 802.11 QoS Data in IPv6-over-802.11-OCB

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 26 February 2018 13:16 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 471D7126DED for <its@ietfa.amsl.com>; Mon, 26 Feb 2018 05:16:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level:
X-Spam-Status: No, score=-2.633 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_MED=-2.3, 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 kxE6GqcFkXio for <its@ietfa.amsl.com>; Mon, 26 Feb 2018 05:16:26 -0800 (PST)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (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 91D9D126DC2 for <its@ietf.org>; Mon, 26 Feb 2018 05:16:26 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id w1QDGNSB149430; Mon, 26 Feb 2018 14:16:23 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 22766205214; Mon, 26 Feb 2018 14:16:23 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 0BD9420516D; Mon, 26 Feb 2018 14:16:23 +0100 (CET)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id w1QDGMhx006540; Mon, 26 Feb 2018 14:16:22 +0100
To: Jérôme Härri <jerome.haerri@eurecom.fr>, "'Bless, Roland (TM)'" <roland.bless@kit.edu>, 'Russ Housley' <housley@vigilsec.com>, 'Rex Buddenberg' <buddenbergr@gmail.com>, 'Tony Li' <tony1athome@gmail.com>
Cc: its@ietf.org
References: <CADnDZ8-CGKedTqZ8=uQAhK33LkVCx==tFwnt+Rk5hb_SDuLXzQ@mail.gmail.com> <7bf2fcd7-4328-28e5-baeb-4e0b34a89755@gmail.com> <9fa4ef44-7278-1423-5b39-5f951fce0740@gmail.com> <C2685D83-78A8-4673-BE2D-42E35BAAC33C@gmail.com> <006b01d3ace3$f0168e00$d043aa00$@eurecom.fr> <1519418411.2226.429.camel@gmail.com> <9231453B-5144-4FAE-8475-72B2708EE239@vigilsec.com> <80cd759d-c521-ce19-c7ee-06947c101142@kit.edu> <00ef01d3aefd$c728b8d0$557a2a70$@eurecom.fr>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <22a0f386-0fc4-3cad-73fd-5b23ff7c8359@gmail.com>
Date: Mon, 26 Feb 2018 14:16:22 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <00ef01d3aefd$c728b8d0$557a2a70$@eurecom.fr>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/x3wld2hW8rOKyGX6rhgTg_-be4k>
Subject: Re: [ipwave] 802.11 Data vs 802.11 QoS Data in IPv6-over-802.11-OCB
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.22
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, 26 Feb 2018 13:16:28 -0000


Le 26/02/2018 à 13:31, Jérôme Härri a écrit :
> Excellent...
> 
> Thanks Roland..
> 
> I think we should mention this in this IPv6-over-OCB draft...

Right now the draft mentions draft-ietf-tsvwg-ieee-802-11-11 which is a 
precursor of that RFC.  I could update it to the RFC number if necessary.

draft says:
>    The mapping between qos-related fields in the IPv6 header (e.g.
>    "Traffic Class", "Flow label") and fields in the "802.11 QoS Data
>    Header" (e.g.  "QoS Control") are not specified in this document.
>    Guidance for a potential mapping is provided in
>    [I-D.ietf-tsvwg-ieee-802-11], although it is not specific to OCB
>    mode.


The existence of that RFC8325 does not solve the interoperability problem.

If we continue to say that IPv6 could be sent either as QoSData, or 
alternatively as Data, any day someone will send it differently than the 
others can receive.

If, on the other hand, the linux kernel implemented QoSData in an open 
source code, and that it worked fine, then I could agree with you.  But 
up to now I feel like the QoSData is implemented _only_ by closed-source 
proprietary code to which I have no access.

If someone could show a packet dump of an IPv6 packet carried with 
802.11 QoSData header, then I would agree to document it in this draft.

Alex

v2.23.0 | Report a Bug | By Email