Re: [ipwave] minor textual issues on channels
Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 29 May 2017 15:58 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 25942129AD0 for <its@ietfa.amsl.com>; Mon, 29 May 2017 08:58:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.367
X-Spam-Level: ***
X-Spam-Status: No, score=3.367 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=no 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 gAfyFvuPUiOU for <its@ietfa.amsl.com>; Mon, 29 May 2017 08:58:02 -0700 (PDT)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1671129AD3 for <its@ietf.org>; Mon, 29 May 2017 08:57:57 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id v4TFvt9l057718; Mon, 29 May 2017 17:57:55 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 7FACA205834; Mon, 29 May 2017 17:57:55 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 723D820581D; Mon, 29 May 2017 17:57:55 +0200 (CEST)
Received: from [132.166.84.45] ([132.166.84.45]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id v4TFvrG7013168; Mon, 29 May 2017 17:57:54 +0200
To: Michelle Wetterwald <mlwetterwald@gmail.com>
References: <CAF5de8tVv=zJD-DupHs+2sBkb4EjSuPbsKVEi04FD1=obLi6LA@mail.gmail.com>
Cc: "its@ietf.org" <its@ietf.org>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <ab73bc48-384e-b6ad-5daa-bf5417f4420c@gmail.com>
Date: Mon, 29 May 2017 18:57:53 +0300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CAF5de8tVv=zJD-DupHs+2sBkb4EjSuPbsKVEi04FD1=obLi6LA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/K-x79_dKlPyNKGOxgnkOQWwxyq0>
Subject: Re: [ipwave] minor textual issues on channels
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 29 May 2017 15:58:03 -0000
Le 22/05/2017 à 15:50, Michelle Wetterwald a écrit :
> Hi Alex,
>
> Regarding the new suggested text below, I would rather re-phrase it
> as: NEW2: Prohibition of IPv6 on some channels relevant for IEEE
> 802.11-OCB, as opposed to IPv6 not being prohibited on any channel
> on which 802.11a/b/g/n runs; this prohibition may be explicit at
> higher layer protocols providing services to the application; these
> higher layer protocols and prohibition are specified in related
> specifications, e.g., in IEEE 1609 documents. National or regional
> specifications and regulations need to be considered as well.
Ok, I added that "national or regional...".
I would like to let you know that the national and regional specs where
I live do not make statements with respect to IPv6 (neither prohibiting
nor allowing IPv6). However, the server where these specs are stored is
under maintenance since serveral months and it's hard to point to them.
("e-spectre"). Also these national/regional specs are often superseded
by supra-national specs which seem to be overseen by ETSI ITS, which
does make such statements with respect to IPv6.
Alex
-- This
> would not restrict to one set of specifications and allow a higher
> coverage of the issue. Moreover, it is future-proof and in line with
> what was discussed during the meeting in Chicago.
>
> Best, Michelle
>
>
> 2017-05-18 11:39 GMT+02:00 Alexandre Petrescu
> <alexandre.petrescu@gmail.com
> <mailto:alexandre.petrescu@gmail.com>>:
>
>
>
> OLD:
>
> Prohibition of IPv6 on some channels relevant for the PHY of IEEE
> 802.11-OCB, as opposed to IPv6 not being prohibited on any channel
> on which 802.11a/b/g/n runs; at the time of writing, this prohibition
> is explicit in IEEE 1609 documents.
>
>
> It was suggested that this is not a PHY prohibition, but rather a
> higher layer protocols providing services to the application.
>
> As such the new text is the following:
>
> NEW:
>
> Prohibition of IPv6 on some channels relevant for IEEE 802.11-OCB, as
> opposed to IPv6 not being prohibited on any channel on which
> 802.11a/b/g/n runs; at the time of writing, this prohibition is
> explicit at higher layer protocols providing services to the
> application; these higher layer protocols are specified in IEEE 1609
> documents.
>
>
> End issue.
>
>
>
>
>
> -- Michelle Wetterwald michelle.wetterwald@gmail.com
> <mailto:michelle.wetterwald@gmail.com>
- Re: [ipwave] minor textual issues on channels Michelle Wetterwald
- Re: [ipwave] minor textual issues on channels Alexandre Petrescu