Re: [ipwave] Mirja Kühlewind's Discuss on draft-ietf-ipwave-ipv6-over-80211ocb-49: (with DISCUSS and COMMENT)

John Kenney <jkenney@us.toyota-itc.com> Wed, 10 July 2019 23:40 UTC

Return-Path: <jkenney@us.toyota-itc.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 A3D78120019 for <its@ietfa.amsl.com>; Wed, 10 Jul 2019 16:40:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.603
X-Spam-Level:
X-Spam-Status: No, score=-0.603 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=us-toyota-itc-com.20150623.gappssmtp.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 SNPbpKr4CSRg for <its@ietfa.amsl.com>; Wed, 10 Jul 2019 16:40:28 -0700 (PDT)
Received: from mail-ot1-x32e.google.com (mail-ot1-x32e.google.com [IPv6:2607:f8b0:4864:20::32e]) (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 91139120247 for <its@ietf.org>; Wed, 10 Jul 2019 16:40:25 -0700 (PDT)
Received: by mail-ot1-x32e.google.com with SMTP id q20so3983378otl.0 for <its@ietf.org>; Wed, 10 Jul 2019 16:40:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=us-toyota-itc-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=f5Urh8L2GIfd6bSxLXPAPXzPsFztNao1brAl31XkR6w=; b=mlTJWOljq+ZX4F9qqrto5qeFqrr8UJuWjXSzUN9ZswkyTZ1hTXOXkOCP2G9EKGBLv5 SXV/ggpkY2m3KL4dckiFwqXui5sx9falCWfiHMlSzVRLlgmJ969S0fPzLUpn0bJKzN98 4G39+3N5hT3DEpl7yh8nJJW/CKydHTIY19b43XIhEokLXqLesOXyqxNYxU/9TfslpMXT nFPKcBHejNYFnTjhB8w40dY9VXHXIhRZN5deOUyeVNZ1QzTZWZsVyGGhXtUKMSujNi7+ eC1/RBw3zjv5HOUYYv/fW5aq24abSv/pMk0RE2ELcim7xhc5+yckdQDFqpK71y+P7s+d QW9Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=f5Urh8L2GIfd6bSxLXPAPXzPsFztNao1brAl31XkR6w=; b=K7OHlRoju3ImYVoGvzeT8eaDwIXEHP1G25kMSAM2pVi2RFwFhNHEV4/CTX0E8E2pxk VKBBeY8y04ixyk2xHMwn5qpN7RG5Sq4vELSQ8yvImRMFILjIqsKgf5IPDqqNqPG1o+NE dlgWAnTOdm/nlzfbSqgU0GOK1KkYHxdbQBILFH1fJ96WT3QE41KIHwa+Tsy54/y2jkIA fysCqKIuw6Dg88R8mdGogqpMSPaHFFGlitBUlsUzOm/mVeqgv6NVd6UNIJcyrbVqq4LA Kv9YxOjWGhn9EDhFWGbXXwXhzKr8HCCp5iF2og754QJaJLhsl4aGKa6RyEJM/D9k94qH WbcQ==
X-Gm-Message-State: APjAAAUDUBG0ERqephloN/vbSyGRtUbCqhGkCn2g3wRIPULIbZSAd8ic HlWIGFScWwhWHXOMELh/QhWTYsP2ksiccaNzha038A==
X-Google-Smtp-Source: APXvYqzj/aeQTUp1CRE5NZQBiHq+QLGQRdoLpSG1GucJsuVLvMhlCsza7dKTg+VMfdV2WSNKqAelsFv/LyJPOWKk4HA=
X-Received: by 2002:a9d:2969:: with SMTP id d96mr854058otb.85.1562802024477; Wed, 10 Jul 2019 16:40:24 -0700 (PDT)
MIME-Version: 1.0
References: <156269059867.15866.17764812378863873209.idtracker@ietfa.amsl.com> <CAD8vqFdPYvDOq2hELAyWiVw29214K7oBi7sH+TBzWTQmzQ33og@mail.gmail.com> <4FA280F6-FD9F-4DBA-991B-D0A3033FB124@kuehlewind.net> <CAD8vqFcMSQoGp3FavcR14a9B0k9s61+hy6urruXnGkdT-W0OYA@mail.gmail.com> <61138CEA-2D49-48C3-846E-D93DB17DDB27@kuehlewind.net>
In-Reply-To: <61138CEA-2D49-48C3-846E-D93DB17DDB27@kuehlewind.net>
From: John Kenney <jkenney@us.toyota-itc.com>
Date: Wed, 10 Jul 2019 16:40:13 -0700
Message-ID: <CAP6QOWRx_tKDOZ65kykNt6vb0Fdj63+Z+RusLBq_hoknAv94=Q@mail.gmail.com>
To: Mirja Kuehlewind <ietf@kuehlewind.net>
Cc: Nabil Benamar <n.benamar@est.umi.ac.ma>, draft-ietf-ipwave-ipv6-over-80211ocb@ietf.org, Carlos Bernardos <cjbc@it.uc3m.es>, The IESG <iesg@ietf.org>, its <its@ietf.org>, ipwave-chairs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000860860058d5c3357"
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/icg3vfJO0aaNEVmXOBeEYFsUJsw>
Subject: Re: [ipwave] Mirja Kühlewind's Discuss on draft-ietf-ipwave-ipv6-over-80211ocb-49: (with DISCUSS and COMMENT)
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 10 Jul 2019 23:40:30 -0000

Hi All:

I have no desire to re-litigate the QoS issue. However, it's important to
remember that IP-over-OCB will typically share public regulated spectrum
with non-IP safety-of-life communications. In the US, FCC regulations
require that such safety communications have access priority over other
communications [47 CFR § 90.377(d)] .  I would be cautious about removing
the current language unless you are convinced that doing so will not
adversely affect non-IP safety communications.

Best Regards,
John

On Wed, Jul 10, 2019 at 6:18 AM Mirja Kuehlewind <ietf@kuehlewind.net>
wrote:

> Thanks. Removing this text entirely is a good option.
>
> Mirja
>
>
> > On 10. Jul 2019, at 13:39, Nabil Benamar <n.benamar@est.umi.ac.ma>
> wrote:
> >
> > Hi Mirja,
> >
> > Actually, the text was written some time ago and different views were
> shared in the group. I think we need to remove this text to avoid confusion.
> >
> > On Wed, Jul 10, 2019 at 8:44 AM Mirja Kuehlewind <ietf@kuehlewind.net>
> wrote:
> > Hi Nabil,
> >
> > I think my point was slightly different. Dorothy mainly advised you
> _how_ to specify the priority. However my question is rather _if_ that is
> needed and if it is really appropriate to use a MUST here. Can you further
> explain why that is seen as a mandatory requirement?
> >
> > Mirja
> >
> >
> >
> > > On 9. Jul 2019, at 23:29, Nabil Benamar <n.benamar@est.umi.ac.ma>
> wrote:
> > >
> > > Hi Mirja,
> > >
> > > Thank you for your review and comments.
> > >
> > > You raised a very important point that was discussed extensively on
> the ML and then we asked the IEEE 802.11 members (thanks to Dorothy Stanly)
> to provide us with a review to help us clarify this point.
> > >
> > > Here is what we got from them:
> > >
> > > .  Suggest to simply state that the data is transmitted with “User
> Priority” of Background (numerically 1 or 2), and leave the internal
> details of how this is accomplished to the 802.11 specification.
> > >
> > > User Priority is typically described as a simple integer (not a binary
> value), and the mapping of this User Priority to TID header value is
> another 802.11 detail, best left to the 802.11 specification.  For example:
> in the 802.11 specification the TID field is specified to be 4 bits in the
> header.  The use of these 4 bits to carry the User Priority information is
> an internal specification of 802.11 and potentially subject to change..
> > >
> > > Suggest using terminology from the MAC SAP in IEEE Std 802.11-2016
> Clause 5.2.  This clause intentionally abstracts the exact details of
> 802..11’s internal operation, while describing specifically the behavior
> required by the user.  For example, the following text:
> > >
> > > “In the 802.11 header, the value of the Subtype sub-field in the Frame
> Control field MUST be set to 8 (i.e. 'QoS Data'); the value of the Traffic
> Identifier (TID) sub-field of the QoS Control field of the 802.11 header
> MUST be set to binary 001 (i.e.  User Priority 'Background', QoS Access
> Category 'AC_BK').”
> > >
> > > could be replaced by:
> > >
> > >
> > > “The mapping to the 802.11 data service MUST use a ‘priority’ value of
> 1, which specifies the use of QoS with a “Background” user priority.”
> > >
> > >
> > >
> > > Thanks again.
> > >
> > >
> > > On Tue, Jul 9, 2019 at 5:43 PM Mirja Kühlewind via Datatracker <
> noreply@ietf.org> wrote:
> > > Mirja Kühlewind has entered the following ballot position for
> > > draft-ietf-ipwave-ipv6-over-80211ocb-49: Discuss
> > >
> > > When responding, please keep the subject line intact and reply to all
> > > email addresses included in the To and CC lines. (Feel free to cut this
> > > introductory paragraph, however.)
> > >
> > >
> > > Please refer to
> https://www.ietf.org/iesg/statement/discuss-criteria.html
> > > for more information about IESG DISCUSS and COMMENT positions.
> > >
> > >
> > > The document, along with other ballot positions, can be found here:
> > > https://datatracker.ietf.org/doc/draft-ietf-ipwave-ipv6-over-80211ocb/
> > >
> > >
> > >
> > > ----------------------------------------------------------------------
> > > DISCUSS:
> > > ----------------------------------------------------------------------
> > >
> > > One point on this sentence, which I believe was also commented in the
> TSV-ART
> > > review (Thanks Jörg!):
> > >
> > > sec 4.2: "The mapping to the 802.11 data service MUST use a
> > >    'priority' value of 1, which specifies the use of QoS with a
> > >    'Background' user priority."
> > > I don't think this should be a MUST requirement. I assume the
> assumption here
> > > is that IP traffic is always some "random" data that is less important
> than
> > > other V2V communication. However, this is a generic mapping document
> and should
> > > therefore probably not make such an assumption (or at least it would
> need to be
> > > spelled out).
> > >
> > >
> > > ----------------------------------------------------------------------
> > > COMMENT:
> > > ----------------------------------------------------------------------
> > >
> > > One editorial high level comment: I seams like all text that was
> somehow deemed
> > > as out fo scope for the main body of this document got stuffed into the
> > > appendix. Please consider removing what is really not needed in this
> document
> > > as these pages also take review and RFC Editor time, especially as
> they seem to
> > > have received less review and therefore have more nits.
> > >
> > > nit: sec 4.5.2 s/in OCB mode.A  A future improvement/in OCB mode. A
> future
> > > improvement/
> > >
> > >
> > >
> > >
> > > --
> > >
> > > Best Regards
> > >
> > > Nabil Benamar
> > > Associate Professor
> > > Department of Computer Sciences
> > > School of Technology
> > > Moulay Ismail University
> > > Meknes. Morocco
> > >
> > >
> >
> >
> >
> > --
> >
> > Best Regards
> >
> > Nabil Benamar
> > Associate Professor
> > Department of Computer Sciences
> > School of Technology
> > Moulay Ismail University
> > Meknes. Morocco
> >
> >
>
> _______________________________________________
> its mailing list
> its@ietf.org
> https://www.ietf.org/mailman/listinfo/its
>


-- 
John Kenney
Director and Sr. Principal Researcher
Toyota InfoTech Labs
465 Bernardo Avenue
Mountain View, CA 94043
Tel: 650-694-4160. Mobile: 650-224-6644