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

Jérôme Härri <jerome.haerri@eurecom.fr> Sat, 11 February 2017 14:09 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 8327E129454 for <its@ietfa.amsl.com>; Sat, 11 Feb 2017 06:09:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, 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 hSXrjDv9yyDT for <its@ietfa.amsl.com>; Sat, 11 Feb 2017 06:09:52 -0800 (PST)
Received: from smtp2.eurecom.fr (smtp3.eurecom.fr [193.55.113.213]) by ietfa.amsl.com (Postfix) with ESMTP id 452E51294E3 for <its@ietf.org>; Sat, 11 Feb 2017 06:09:52 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.35,146,1484002800"; d="scan'208";a="5760997"
Received: from waha.eurecom.fr (HELO smtps.eurecom.fr) ([10.3.2.236]) by drago2i.eurecom.fr with ESMTP; 11 Feb 2017 15:09:51 +0100
Received: from xerus29 (LFbn-1-6946-250.w90-116.abo.wanadoo.fr [90.116.128.250]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtps.eurecom.fr (Postfix) with ESMTPSA id 41949848; Sat, 11 Feb 2017 15:09:52 +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> <fc5883da-dd62-e846-b8ea-9f3cf8a867b1@cea.fr> <012501d28395$4e5429b0$eafc7d10$@eurecom.fr> <6da89922-9055-6499-aa9f-8a866ea9f4d5@gmail.com>
In-Reply-To: <6da89922-9055-6499-aa9f-8a866ea9f4d5@gmail.com>
Date: Sat, 11 Feb 2017 15:09:51 +0100
Organization: EURECOM
Message-ID: <00af01d28470$83558830$8a009890$@eurecom.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJOjypQjcVLCnmBW2ydKpCtKDvNtwIlfIuWAjDsvIwB7B2RLqA5rLaQ
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/ty_DCRg7lDE2W41O3UWmHk9mDXM>
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: Sat, 11 Feb 2017 14:09:54 -0000

Hello Alex,

I do not fully understand your argument about your country not imposing
restriction and why you prefer MAY NOT. 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.
 

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