Re: [ipwave] 802.11bd D1.0 preliminary spec available somewhere?

Dorothy Stanley <dstanley1389@gmail.com> Thu, 10 September 2020 16:26 UTC

Return-Path: <dstanley1389@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 9A9A13A0D9D for <its@ietfa.amsl.com>; Thu, 10 Sep 2020 09:26:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level:
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 j2xbCzUk8PTa for <its@ietfa.amsl.com>; Thu, 10 Sep 2020 09:26:32 -0700 (PDT)
Received: from mail-il1-x135.google.com (mail-il1-x135.google.com [IPv6:2607:f8b0:4864:20::135]) (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 2A6643A0D83 for <its@ietf.org>; Thu, 10 Sep 2020 09:26:32 -0700 (PDT)
Received: by mail-il1-x135.google.com with SMTP id t13so6217582ile.9 for <its@ietf.org>; Thu, 10 Sep 2020 09:26:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=aLgAAzGtGVlk4ywtE/LuNPuaOwRjzBTQFpa/c7bE3kE=; b=dL/fIBXkYpZONh+miPTChRrgqP2YyTYG0f4oB0XirvC2OVsBs3anWUjQ1qBWmWQY3v 3iGPXwNVIBvoY/h0a3tPGcDwd4N0yYaKivni0g3bU5fyKEkPrfcEjYQ6LVqTlQnxYVTU 11o2w86mLAsCh+2LeKHOpxhh3GAw5vpfGQSDBeCC44N5ASMD/7l8nFCB8YRri9nSf3qL R58XbqlhrV3LrNWgfF2Il0fZuyNgo416n1C1w2AAJATKsJDx9ffGtIfVhDgcBiDCkHKx CYOFCQfW2maWQXOmBtufA/g0NJv0Flyq780aUKNXYTqqwdYBTnEzwPHa7670I8L/nrah VqQA==
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=aLgAAzGtGVlk4ywtE/LuNPuaOwRjzBTQFpa/c7bE3kE=; b=HSFhMZ1LN2IyrXzvHimbsWVB6zvwPtaAZ/HpI9fFs6g6s1UQbKNdNnvTYCD7k1nCWL N/YQCgE4Y3i5pQvfv0FQswZZqedXYovCEdk/pj40q946UlSB9KXawW8kPQHxr+3pLyyy fozB2Ug2cIRDrmHHUKS8WYXmzOzygMoDDJXhuHuOiPBOVf15yXUMUTy8W/jmtiSrXgOq TXNH5Pyhq36oMx8i7d7jVfWE+oHaYLm2ZntG+8wA+p8sUHXTq/i9G/KSWemsaiH6vkGC joNrqxBfYNNquZDeaJawKx/2VdlCp48faS62YK0g+pL98KAse++tYDbmzfxCnVGUiLWm kMvg==
X-Gm-Message-State: AOAM53349MX8ktukLUrKkdfjisOpmT0b9qOBaY2huaupHG4P9jdDHcHz T0KinwtcXlKxDp8DyF/AOTynbmA7K5PKMe/j7uE=
X-Google-Smtp-Source: ABdhPJx7cyTlKG/9eZv94TS3ap2RhXerzTCLRAr4vFP5i21GZ944lSzZ9LJeuq1KCuV1GyphevS4SeswJcTVUo71olI=
X-Received: by 2002:a05:6e02:e07:: with SMTP id a7mr8183798ilk.277.1599755191241; Thu, 10 Sep 2020 09:26:31 -0700 (PDT)
MIME-Version: 1.0
References: <fa3ec50d-1338-f12a-cf37-3f5502f13c94@gmail.com> <CAP6QOWQ8gGnyYUeof5ajzajk1xdW3Gqkmx--+ZkSoaZYN4ShMQ@mail.gmail.com> <9b780ad5-3892-36ef-762d-58f1d186a94d@gmail.com> <04857EE4CB264A50B80347971C0A4030@SRA6> <35a5909e-50b3-49c6-7998-69c809f14b57@gmail.com> <B3C884FEB2BF448691F36217D1B16945@SRA6> <95690a67-566e-9fa8-e73d-12bdeae89593@gmail.com>
In-Reply-To: <95690a67-566e-9fa8-e73d-12bdeae89593@gmail.com>
From: Dorothy Stanley <dstanley1389@gmail.com>
Date: Thu, 10 Sep 2020 09:26:19 -0700
Message-ID: <CAGRfTMkXHW0+4mgYJ5m-uGDxa0Ud3LwzkOoSYYwe-6X4517bug@mail.gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: Richard Roy <dickroy@alum.mit.edu>, John Kenney <jkenney@us.toyota-itc.com>, IPWAVE WG <its@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e6cfc205aef8071f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/jPM-HpQ9mNYBvnCY2YsMK6sJxqY>
Subject: Re: [ipwave] 802.11bd D1.0 preliminary spec available somewhere?
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: Thu, 10 Sep 2020 16:26:35 -0000

As John mentioned, P802.11bd D1.0 is still in preparation, and expected to
be available soon.

See https://tools.ietf.org/html/rfc7241 section 3.3, and in particular

*IEEE 802 WG Chairs have the authority to grant membership in their WGs and can
   use this authority to grant membership to an IETF WG chair upon
   request.  The IETF WG chair will be provided with access to the
   username/password for the IEEE 802 WG archives and is permitted to
   share that information with participants in the IETF WG.  Since it is
   possible to participate in IETF without attending meetings, or even
   joining a mailing list, IETF WG chairs will provide the information
   to anyone who requests it.  However, since IEEE 802 work in progress
   is copyrighted, copyright restrictions prohibit incorporating
   material into IETF documents or postings.*

If access to P802.11bd D1.0 and related drafts is needed to support IPWAVE
WG work, the
IPWAVE WG Chair should send me the corresponding request.

Thanks,

Dorothy

----------------------
Dorothy Stanley
IEEE 802.11 WG Chair, dstanley@ieee.org
Hewlett Packard Enterprise
dorothy.stanley@hpe.com <dstanley@arubanetworks.com>
dstanley1389@gmail.com
+1 630-363-1389 <630-363-1389>


On Thu, Sep 10, 2020 at 3:33 AM Alexandre Petrescu <
alexandre.petrescu@gmail.com> wrote:

>
>
> Le 10/09/2020 à 11:41, Dick Roy a écrit :
> > Standards relevant to layer 3 can and often do mention IP and the
> > relevant RFCs.  Standards relevant to other layers should not have
> > any need to reference protocols at other layers in ay normative way
> > ... that's the whole point of the layered model and layer separation.
> > Any attempts to violate the layer separation principle do so at their
> > own peril.
>
> YEs layer separation, but there are interfaces between layers, right?
>
> I mean, if RFC8691 specifies that the MTU must a be of a minimum
> 1280bytes, then the MAC should satisfy that by fragmenting and
> reassembling where necessary, if necessary.
>
> If RFC8691 says that the frame format below IP must use QoS Data headers
> then 802.11bd wouldnt say otherwise.
>
> If RFC8691 says that the priority value must be '1' in the QoS data
> header (at the MAC layer) then 802.11bd wouldnt say otherwise, right?
>
> Alex
>
> >
> > RR
> >
> > -----Original Message----- From: its [mailto:its-bounces@ietf.org] On
> > Behalf Of Alexandre Petrescu Sent: Thursday, September 10, 2020 2:07
> > AM To: dickroy@alum.mit.edu; 'John Kenney' Cc: 'IPWAVE WG' Subject:
> > Re: [ipwave] 802.11bd D1.0 preliminary spec available somewhere?
> >
> >
> >
> > Le 10/09/2020 à 09:18, Dick Roy a écrit :
> >> Hi Alex,
> >>
> >> FYI ... there is very little if anything in any IEEE 802 LAN
> >> specification that in any way specifies or constrains what happens
> >> in any network layer protocol.  (W)LANs operate at layer 2 and
> >> below. IPvx is functionality at layer 3.
> >
> > True enough.
> >
> > However, when looking at details of the specs, it might that 802.11
> > documents do use the words 'IP' and 'IPv6' in particular.  Last time
> > I looked at an 802.11 spec I was successful in searching and finding
> > the word IPv6.  That was some years ago.
> >
> > Now the situation is different.  The word should be there, but it
> > should cite [RFC 8691] in the case of OCB operation of 802.11.
> >
> > I mean, if the word 'IPv6' is there in the 802.11bd document, then
> > it makes no sense to not cite RFC 8691.
> >
> > If the word 'IPv6' is not there in the 802.11bd document, then indeed
> > it makes sense to not cite RFC 8691.
> >
> > (I would be tempted to suggest the same to ISO TC204 documents but I
> > know you will not agree because I know in your thought this RFC8691
> > does not fully address one's expectations of fully variable wireless
> > environments of automobile networks; so I dont suggest it for ISO TC
> > 204).
> >
> > Yours,
> >
> > Alex
> >
> >>
> >> Hope this helps...
> >>
> >> RR
> >>
> >> -----Original Message----- From: its [mailto:its-bounces@ietf.org]
> >> On Behalf Of Alexandre Petrescu Sent: Thursday, September 10, 2020
> >> 12:08 AM To: John Kenney Cc: IPWAVE WG Subject: Re: [ipwave]
> >> 802.11bd D1.0 preliminary spec available somewhere?
> >>
> >> Hi, John,
> >>
> >> Thank you for the reply.
> >>
> >> Does the document mention the word 'IPv6'? (RFC8691?)
> >>
> >> Alex
> >>
> >> Le 09/09/2020 à 23:41, John Kenney a écrit :
> >>> Hi Alex,
> >>>
> >>> No, this is a work in progress, scheduled to be completed later
> >>> this month. It will be a draft standard. Unless a decision is
> >>> made to make it available for sale, it will only be available to
> >>> IEEE 802.11 WG voting members.
> >>>
> >>> Best Regards, John
> >>>
> >>>
> >>> On Wed, Sep 9, 2020 at 5:49 AM Alexandre Petrescu
> >>> <alexandre.petrescu@gmail.com
> >>> <mailto:alexandre.petrescu@gmail.com>>
> >> wrote:
> >>>
> >>> Hi,
> >>>
> >>> I am looking for the IEEE 802.11bd D1.0 preliminary spec.  Is it
> >>> available somewhere I could look at it?
> >>>
> >>> It is to see whether, hopefully, it cites RFC8691 for IPv6 use.
> >>>
> >>> Alex
> >>>
> >>> _______________________________________________ its mailing list
> >>> its@ietf.org <mailto: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
> >>
> >> _______________________________________________ its mailing list
> >> its@ietf.org https://www.ietf.org/mailman/listinfo/its
> >>
> >
> > _______________________________________________ its mailing list
> > its@ietf.org https://www.ietf.org/mailman/listinfo/its
> >
>
> _______________________________________________
> its mailing list
> its@ietf.org
> https://www.ietf.org/mailman/listinfo/its
>