Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 second guessing FCC

Jérôme Härri <jerome.haerri@eurecom.fr> Fri, 10 February 2017 12:07 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 96A871295D4 for <its@ietfa.amsl.com>; Fri, 10 Feb 2017 04:07:29 -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 xqFBpEPmqDWi for <its@ietfa.amsl.com>; Fri, 10 Feb 2017 04:07:28 -0800 (PST)
Received: from smtp2.eurecom.fr (smtp3.eurecom.fr [193.55.113.213]) by ietfa.amsl.com (Postfix) with ESMTP id 4C227129590 for <its@ietf.org>; Fri, 10 Feb 2017 04:07:28 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.35,141,1484002800"; d="scan'208";a="5756136"
Received: from monza.eurecom.fr ([192.168.106.15]) by drago2i.eurecom.fr with ESMTP; 10 Feb 2017 13:07:27 +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 0B3BE1AD8; Fri, 10 Feb 2017 13:07:27 +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> <166684fc-cc17-b281-4e00-7cc018a1d465@cea.fr>
In-Reply-To: <166684fc-cc17-b281-4e00-7cc018a1d465@cea.fr>
Date: Fri, 10 Feb 2017 13:07:26 +0100
Organization: EURECOM
Message-ID: <012701d28396$3ee2f500$bca8df00$@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: AQJOjypQjcVLCnmBW2ydKpCtKDvNtwI5yU7/oFg/CyA=
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/7BVkN9j05Bez0pZu8CQ-uXmEg1E>
Subject: Re: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 second guessing FCC
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:07:29 -0000

Hello Alex,

Agree..this is not the place to make such statement. However, I think if you
add my previously suggested statement, it would be enough to imply that some
'channels' might be restricted to some functions in some countries, but
without being specific...maybe we could add an normative reference to the
FCC and the ECC, leaving room for interpretation..

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

BR,

Jérôme

-----Original Message-----
From: its [mailto:its-bounces@ietf.org] On Behalf Of Alexandre Petrescu
Sent: Friday 10 February 2017 11:59
To: its@ietf.org
Subject: [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-00 second guessing
FCC

draft-ietf-ipwave-ipv6-over-80211ocb-00
second guessing FCC

Hello IPWAVErs,

There was a comment clarifying the interpretation of FCC-related text, and
advising against and undesirable but otherwise relatively common practice of
'second guessing' the Commision's oppinion by implementers.

As such, I will remove the following text:

old:
> o  The FCC created two more terms for particular channels 
> fcc-cc-172-184], among others.  The channel 172 (5855MHz to 5865MHz)) 
> is designated "exclusively for [V2V] safety communications for 
> accident avoidance and mitigation, and safety of life and property 
> applications", and the channel 184 (5915MHz to 5925MHz) is designated 
> "exclusively for high-power, longer- distance communications to be 
> used for public-safety applications involving safety of life and 
> property, including road-intersection collision mitigation".
> However, they are not named "control" channels, and the document does 
> not mention any particular restriction on the use of IP on either of 
> these channels.

Alex