Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 IP channel prohibition by 1609 (and not by .11)

Jérôme Härri <jerome.haerri@eurecom.fr> Fri, 03 February 2017 14:25 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 1E085129417 for <its@ietfa.amsl.com>; Fri, 3 Feb 2017 06:25:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.098
X-Spam-Level:
X-Spam-Status: No, score=-5.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-3.199, URIBL_BLOCKED=0.001] autolearn=unavailable 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 pAgQ44dEa7KD for <its@ietfa.amsl.com>; Fri, 3 Feb 2017 06:25:15 -0800 (PST)
Received: from smtp2.eurecom.fr (smtp3.eurecom.fr [193.55.113.213]) by ietfa.amsl.com (Postfix) with ESMTP id 11066129D5C for <its@ietf.org>; Fri, 3 Feb 2017 06:19:55 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.33,329,1477954800"; d="scan'208";a="5720863"
Received: from monza.eurecom.fr ([192.168.106.15]) by drago2i.eurecom.fr with ESMTP; 03 Feb 2017 15:19:55 +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 108661C72; Fri, 3 Feb 2017 15:19:55 +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> <0ba01e6b-5e61-a9ae-35c5-4be300d147fd@cea.fr>
In-Reply-To: <0ba01e6b-5e61-a9ae-35c5-4be300d147fd@cea.fr>
Date: Fri, 03 Feb 2017 15:19:54 +0100
Organization: EURECOM
Message-ID: <02a001d27e28$9763d6e0$c62b84a0$@eurecom.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJOjypQjcVLCnmBW2ydKpCtKDvNtwDfKgqfoFgxpaA=
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/Kxe6sm8RaNAu9gg3O9HKkQ_HQiQ>
Subject: Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 IP channel prohibition by 1609 (and not by .11)
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: Fri, 03 Feb 2017 14:25:16 -0000

Hi Alex,

Correct, and same for ETSI. So, in theory, we are not bound by these 'restrictions'. But as Michelle just said, it is not that simple, as accessing a particular ITS channel (US or EU) has usually some specific restrictions, irrespectively if you use WAVE/ISO/ETSI ITS stack or no stack at all. 

A typical example for ETSI is that if we use ITS-G5 (IEEE 802.11-OCB in EU) in Europe, then it needs to implement a DCC mechanism according to the ETSI Harmonized Standard 'EN 302 571'. So, even if we are not bound to have a DCC when we use IPv6-over-OCB, but if we want to access the ITS-G5 bands, we will need to have one, and this, irrespectively if we use the ETSI ITS stack or not. 

Another aspect I just saw by reading through the harmonized standard, is that EN 302 571 restricts the frame size of any ITS-G5 device to 1500 bytes (even if a MAC frame cam be bigger). So, again, even if we can get bigger frames, if we want to use the ITS-G5 spectrum, we need to comply to this. 

I yet did not find any restrictions to IPv6 on this harmonized standard..I will further dig into this to see where precisely this restriction if made at ETSI and if it applies to the spectrum/channel or to the Stack......

You are yet bringing a very good point to the discussions: we need to have a list of the requirements for any ITS-G5/DSRC device to access the ITS bands (UE/EU) and see how we can cope with  them...I can take care of this, if you want.

As for now, I would suggest to replace the current text (too complicated and only restricted to WAVE) with a short sentence such as:

"Transmissions of IPv6 packets on ITS spectrum SHALL comply with the national spectrum regulations, which MAY lead to restrictions on IP operations using IEEE 802.11-2016 in OCB mode."

Best Regards,

Jérôme

-----Original Message-----
From: its [mailto:its-bounces@ietf.org] On Behalf Of Alexandre Petrescu
Sent: Friday 03 February 2017 14:42
To: its@ietf.org
Subject: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 IP channel prohibition by 1609 (and not by .11)

draft-ietf-ipwave-ipv6-over-80211ocb-00
IP channel prohibition by 1609 (and not by .11)

Hello IPWAVErs,

A comment was made suggesting that the 802.11-OCB standard does not prohibit IP on any channel and, if there is such prohibition, it is certainly mandated by 1609 documents instead.  It was also commented that this prohibition is out of the scope of this Internet Draft.

As such, I suggest to remove the following old text:
> o	Explicit prohibition of IPv6 on some channels relevant for the PHY
> of IEEE 802.11p, as opposed to IPv6 not being prohibited on any 
> channel on which 802.11a/b/g/n runs; for example, IPv6 is prohibited 
> on the 'Control Channel' (number 178 at FCC/IEEE, and
> 180 at ETSI); for a detailed analysis of IEEE and ETSI prohibition of 
> IP in particular channels see Appendix B.

Alex