Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 no IPv6 prohibition on the control channel

Alexandre Petrescu <alexandre.petrescu@gmail.com> Sun, 12 February 2017 17:45 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 D9094129993 for <its@ietfa.amsl.com>; Sun, 12 Feb 2017 09:45:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.333
X-Spam-Level:
X-Spam-Status: No, score=-5.333 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, 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 ZiN0yyRMNxw1 for <its@ietfa.amsl.com>; Sun, 12 Feb 2017 09:45:06 -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 5D00E1293E0 for <its@ietf.org>; Sun, 12 Feb 2017 09:45:06 -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 v1CHj3pc019532; Sun, 12 Feb 2017 18:45:03 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 3D547205D14; Sun, 12 Feb 2017 18:45:03 +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 307DF2083B2; Sun, 12 Feb 2017 18:45:03 +0100 (CET)
Received: from [132.166.84.20] ([132.166.84.20]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id v1CHj2TP018079; Sun, 12 Feb 2017 18:45:02 +0100
To: Jérôme Härri <jerome.haerri@eurecom.fr>, its@ietf.org
References: <148052970170.9607.12043916621198119260.idtracker@ietfa.amsl.com> <fc5883da-dd62-e846-b8ea-9f3cf8a867b1@cea.fr> <012501d28395$4e5429b0$eafc7d10$@eurecom.fr> <6da89922-9055-6499-aa9f-8a866ea9f4d5@gmail.com> <00af01d28470$83558830$8a009890$@eurecom.fr>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <ab74f91d-89b2-8e2e-1fac-add82417c0cb@gmail.com>
Date: Sun, 12 Feb 2017 18:44:31 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <00af01d28470$83558830$8a009890$@eurecom.fr>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/qixAG8EZEu1nngwwBc5n3ezAb4U>
Subject: Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 no IPv6 prohibition on the control channel
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: Sun, 12 Feb 2017 17:45:08 -0000

Hello Jérôme,

Le 11/02/2017 à 15:09, Jérôme Härri a écrit :
> Hello Alex,
>
> I do not fully understand your argument about your country not
> imposing restriction

Because I have not seen such restriction forbidding IP, in the ARCEP
regulatory body controlling the use of 5.9GHz band.

> and why you prefer MAY NOT.

I agree.  When adding a NOT it looses your intention, and mine too.

> Your proposed new formulation gives the impression that in most
> countries, IPv6 is restricted...which is not the case actually. My
> formulation was the opposite, claiming that in general there is no
> restriction, but in some cases, maybe. I still think 'MAY' should
> remain, as it would not pose any problem in the country where you
> leave.

I think your formulation makes think there may be countries where the
regulator authority forbids IP on some 5.9GHz channel.

Do we know an example country where the frequency regulation authority
(e.g. that country's FCC) forbids the use of IP on some 5.9GHz channel?

Until now all we see is IEEE P1609 making such restriction.

Alex
>
>
> BR,
>
> Jérôme
>
> -----Original Message----- From: Alexandre Petrescu
> [mailto:alexandre.petrescu@gmail.com] Sent: Friday 10 February 2017
> 13:39 To: Jérôme Härri; its@ietf.org Subject: Re: [ipwave]
> draft-ietf-ipwave-ipv6-over-80211ocb-00 no IPv6 prohibition on the
> control channel
>
>
>
> Le 10/02/2017 à 13:00, Jérôme Härri a écrit :
>> Hello Alex,
>>
>> As discussed, there is a strick prohibition from ETSI and IEEE
>> WAVE. But, as this work will not use it, we do not need to comply
>> with it. We only need to comply with national spectrum
>> regulations...whatever is in there...
>>
>> I would however suggest to add the following statement:
>> "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."
>
> Jérôme,
>
> I agree with the first part, that I can add.
>
> The national spectrum regulation in the country where I live does
> not lead to restrictions on IP operations using 802.11 in OCB mode.
>
> So I could say:
>> "Transmissions of IPv6 packets on ITS spectrum SHALL comply with
>> the national spectrum regulations, which MAY NOT lead to
>> restrictions on IP operations using IEEE 802.11-2016 in OCB mode."
>
> Alex
>
>>
>> I think this leaves flexibility for this WG to propose solutions..
>>
>> BR,
>>
>> Jérôme
>>
>> -----Original Message----- From: its [mailto:its-bounces@ietf.org]
>> On Behalf Of Alexandre Petrescu Sent: Friday 10 February 2017
>> 12:05 To: its@ietf.org Subject: [ipwave]
>> draft-ietf-ipwave-ipv6-over-80211ocb-00 no IPv6 prohibition on the
>> control channel
>>
>> draft-ietf-ipwave-ipv6-over-80211ocb-00 no IPv6 prohibition on the
>> control channel
>>
>> Hello IPWAVErs,
>>
>> We received a comment stating that LCC/OBE does not prohibit the
>> use of IPv6 on the control channel.  (I do not understand what the
>> commenter meant meant by "LCC" - typo for FCC, LLC? or Lower
>> Control Channel? but that's another issue).
>>
>> As such I will remove the following text:
>>> On another hand, at IEEE, IPv6 is explicitely prohibited on
>>> channel number 178 decimal - the FCC's 'Control Channel'.  The
>>> document [ieeep1609.4-D9-2010] prohibits upfront the use of IPv6
>>> traffic on the Control Channel: 'data frames containing IP
>>> datagrams are only allowed on service channels'.  Other 'Service
>>> Channels' are allowed to use IP, but the Control Channel is not.
>>
>> There are many other reasons for removing that text that we
>> discussed here extensively.
>>
>> Alex
>>
>>
>>
>
>