Re: [ipwave] minor textual issues on channels

Michelle Wetterwald <mlwetterwald@gmail.com> Mon, 22 May 2017 13:50 UTC

Return-Path: <mlwetterwald@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 E35A6127876 for <its@ietfa.amsl.com>; Mon, 22 May 2017 06:50:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.9
X-Spam-Level:
X-Spam-Status: No, score=0.9 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 SbOcCQhQ81zW for <its@ietfa.amsl.com>; Mon, 22 May 2017 06:50:58 -0700 (PDT)
Received: from mail-yb0-x22f.google.com (mail-yb0-x22f.google.com [IPv6:2607:f8b0:4002:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A603F1292D3 for <its@ietf.org>; Mon, 22 May 2017 06:50:58 -0700 (PDT)
Received: by mail-yb0-x22f.google.com with SMTP id 130so12315924ybl.3 for <its@ietf.org>; Mon, 22 May 2017 06:50:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=lyy9t5/6OkSQWZXbKk0l83nPPFr9rLqBKA8LAhuMs1s=; b=lLjdAiO9pz2ZUYp4HxSPpR6GRuEDORdA2aMjTBZj55v4+g3/gyrMhhGee1Q6Y3Rboy xAP1DlD6oOlwZ3BHMBG6IaZgVQxP5rMPCLz3gFjuLiQTbV+HmY/Sz1vHWNDpKR92UwU7 W2IOr3dd36ShQ3q8UKiBSDZhR+tXb3YIKWW3+C5itGfMWv2SbK2Uo5FfQi006KLuX1Of Hx0GYXU5p6E25GVKjAFxyJcRy4ue52x8aUCM+2Zkx+oi2ylWQfxsRoRF4P1hQKlTJeIa ggxqTvic3WJMJSfD+3E9EY+Ni9G/0jwiWlKtooGuFtnWyRd23HVzceAFRD1NFDZ7i3z5 ++6w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=lyy9t5/6OkSQWZXbKk0l83nPPFr9rLqBKA8LAhuMs1s=; b=DJPa1hOC7FSzpKXvh/4ssk1eDj62yn9VVrcDkEA0V+zschwKjBx0AEdxdKc+BkRJ+Z Hcxv1LM7nu+Mejc7D/Uos4PQEeVs31xbybeGrPoMGeD1E33o0hpp64069ycxpw+szq4L O4YVdUrBHmCjUhISaOf9uvr3iCbvtY/lR+n1BRKVslvHI+SfxEiAbnBPEiq7DxPPD9ia uOq+TKX/p9hKtaHoiipyeLSJRYQc2B8WklDWlX0Hq5x9w2sqw03yF16wB442Rs/W0RGt 53i2WiKjd/kZX2X/hyd110kcsh7OzyXLvBtmAXmbwbGA1ViVNdYIN09Z4sWCEVzkFcc2 Dxkw==
X-Gm-Message-State: AODbwcCSn8ZIKY5rkhcGkvttLM+v2LPq7v7Rovz3OScirEC3u40V+vsv 4+Ls1M63R4LCaZRgGY+q1A3uJ6aU+Avw
X-Received: by 10.37.43.199 with SMTP id r190mr5470431ybr.118.1495461057940; Mon, 22 May 2017 06:50:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.65.69 with HTTP; Mon, 22 May 2017 06:50:57 -0700 (PDT)
From: Michelle Wetterwald <mlwetterwald@gmail.com>
Date: Mon, 22 May 2017 15:50:57 +0200
Message-ID: <CAF5de8tVv=zJD-DupHs+2sBkb4EjSuPbsKVEi04FD1=obLi6LA@mail.gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: "its@ietf.org" <its@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c1358f4226a2905501d29c0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/eKFxaTxq2mZfoFsNS8xZLa-vG_o>
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, 22 May 2017 13:51:00 -0000

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

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