IETF Logo Mail Archive

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> Fri, 10 February 2017 12:00 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 83554129572 for <its@ietfa.amsl.com>; Fri, 10 Feb 2017 04:00:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-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 bGvK1o6xEKXn for <its@ietfa.amsl.com>; Fri, 10 Feb 2017 04:00:44 -0800 (PST)
Received: from smtp2.eurecom.fr (smtp3.eurecom.fr [193.55.113.213]) by ietfa.amsl.com (Postfix) with ESMTP id 3ECA71289C4 for <its@ietf.org>; Fri, 10 Feb 2017 04:00:44 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.35,141,1484002800"; d="scan'208";a="5756112"
Received: from monza.eurecom.fr ([192.168.106.15]) by drago2i.eurecom.fr with ESMTP; 10 Feb 2017 13:00:43 +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 7306B1A9D; Fri, 10 Feb 2017 13:00:43 +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>
In-Reply-To: <fc5883da-dd62-e846-b8ea-9f3cf8a867b1@cea.fr>
Date: Fri, 10 Feb 2017 13:00:43 +0100
Organization: EURECOM
Message-ID: <012501d28395$4e5429b0$eafc7d10$@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: AQJOjypQjcVLCnmBW2ydKpCtKDvNtwIlfIuWoFjeuUA=
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/RMx9zSuuS5nypROCt1PRKZ7X0hU>
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: Fri, 10 Feb 2017 12:00:45 -0000

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

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

v2.23.0 | Report a Bug | By Email