Re: [ipwave] FCC Moves Plan Forward to Chop Up Vehicle Safety Airwaves
Abdussalam Baryun <abdussalambaryun@gmail.com> Tue, 17 December 2019 14:29 UTC
Return-Path: <abdussalambaryun@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 A1B71120848 for <its@ietfa.amsl.com>; Tue, 17 Dec 2019 06:29:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.997
X-Spam-Level:
X-Spam-Status: No, score=-0.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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_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=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 Gd14Hmq17rYO for <its@ietfa.amsl.com>; Tue, 17 Dec 2019 06:29:17 -0800 (PST)
Received: from mail-ot1-x330.google.com (mail-ot1-x330.google.com [IPv6:2607:f8b0:4864:20::330]) (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 A93F11200C3 for <its@ietf.org>; Tue, 17 Dec 2019 06:29:17 -0800 (PST)
Received: by mail-ot1-x330.google.com with SMTP id h20so13972121otn.5 for <its@ietf.org>; Tue, 17 Dec 2019 06:29:17 -0800 (PST)
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=l8+k9YSqOOnT58e4yUtCs1SB/EOSB+KzPr7xTj1okNc=; b=Y6gMYeCCRYA7BEAa6dZ3JS7msScw/cNNy1IbvDx+aBuQo3BsriVc1Bz1jfZRGHOf8F i4S0I5nktf/uZ0qB7QiHndXESAqSENlskKBmsFctmIHV5V7vlXHtByrXO+RottlFUTJp NkpxNrEmPzYKLq+75lB+2ngXGYC+k6HqBP4omWGp4hI+U/fXqcmev8fPQXR//rSY4t1O bGu5JDwUpp3oZLOfQBFPkNtAEBA+YWn88DPTlkBgaFVaBH6G0i/2NQPB93o2panXfvWF yTLfzUok9QU/tiTWpjQn5IZ5ckwJxdoBbUHoX1vJRKVmnCNMcNHw4B7Gda8vgnO0dN7U /MtQ==
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=l8+k9YSqOOnT58e4yUtCs1SB/EOSB+KzPr7xTj1okNc=; b=qSYyxKSPXZaWDFRotQQ1ZOw8PJkADualWp3RSnSBGY3YHHXHXP3XGQLNVtoHm9Y/8f +HmJi2RdNBgZPqHGWcwgzc/Gsp7uM+wbF6PJ6EEZf/Q7KKZBBvLeldCZtNNjH0cEKENB TP+7fT6i27zpCy2PqxjYoZZmWj0x9WdSiVPPLCtMiC97JzyLYw56tdB/H84VFNn01c9Z 2YFpQYA6k4J3nHw0aKuRRLWU0EGES00XGTVhBoastwuHp24Ncw4sckRlH5eSEgxMfRZe tTFoTO/gWKREGZ/VfrWadPRXR4eg9VKoN+u0PsjTgOnlkkFnMSVnKKWJRbMx7HJJfpbn RcEQ==
X-Gm-Message-State: APjAAAXQ5XDwwbiKuZpWyUExlDZMdtpvce4BHalGVSLgO9J7U2bivpuC kL1pOPpsJnskDExnHLgAEhORFFCDlpdG//8oeyY=
X-Google-Smtp-Source: APXvYqyBx+7f0Gpuj3pb5ar1AJYVm3oGohckmw+ZnME0cVXDBu8IpIUOpLR81vvu2yuvbNa0RDpHj9cfBw5taOCELFo=
X-Received: by 2002:a9d:7ad9:: with SMTP id m25mr35962275otn.13.1576592956965; Tue, 17 Dec 2019 06:29:16 -0800 (PST)
MIME-Version: 1.0
References: <EED81985-1D4C-41B2-8CCA-A46B96390A18@vigilsec.com> <1c70cda6-050b-e018-6786-abd99281b6bb@gmail.com> <CADnDZ8-opM3O5U7-C8v+KYTX6-ruQzajRZgDWzzZtXRnJt575Q@mail.gmail.com> <ad3ccd6c-cd99-c47a-d0df-bfb94b5ab40f@gmail.com>
In-Reply-To: <ad3ccd6c-cd99-c47a-d0df-bfb94b5ab40f@gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
Date: Tue, 17 Dec 2019 16:29:01 +0200
Message-ID: <CADnDZ8_wwa91-5UWeqxhJy=nMBp8kwu4ZvfxsAojZCY9DG8jSA@mail.gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: its <its@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000027c8800599e72787"
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/_euXP9yEiOePA2OHp7-bwj3hwm0>
Subject: Re: [ipwave] FCC Moves Plan Forward to Chop Up Vehicle Safety Airwaves
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: Tue, 17 Dec 2019 14:29:20 -0000
I think IEEE defines WLAN as IEEE802.11. so any IEEE802.11xx standard can be called a WLAN standard. http://www.ieee802.org/11/ also IEEE defines WMAN as IEEE802.16 technology, which was replaced by LTE cellular technology. AB On Tue, Dec 17, 2019 at 3:54 PM Alexandre Petrescu < alexandre.petrescu@gmail.com> wrote: > > > Le 17/12/2019 à 14:40, Abdussalam Baryun a écrit : > > V2X and V2V communications had two design proposals: > > > > 1- using WLAN technology > > 2- using Cellular network technology > > > > So we worked on the first in this WG. > > OCB is not the typical WLAN - it is 802.11 in mode OCB. One cant link > OCB channels to non-OCB channels (typical WiFi) such as to make very > large channel widhts they seem to need. > in frequency yes > > I think FCC wants much parts of the 5.9GHz for WLAN (not OCB) and other > parts for C-V2X. > FCC is pushing for 5G services/qualities to be achieved. I think it may depend on locations/regions, because some locations may not have good cellular communication signals. > > I think the FCC question is whether or not to keep the 5895-5905MHz for > DSRC or to give that too to C-V2X; that is the only question they > formulate. > I agree, they are pushing for that, > > That channel is a place where FCC hardly allowed for IPv6 in the first > place. Even in this WG it was often said that IPv6 is not for that > channel. > > I think there is no place for OCB mode anywhere and even less for IPv6. > we never know what will happen tomorrow. AB > > Alex > > > > On Tue, Dec 17, 2019 at 12:58 PM Alexandre Petrescu > > <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>> > wrote: > > > > > https://docs.fcc.gov/public/attachments/DOC-361339A1.pdf > > > > > For Immediate Release FCC SEEKS TO PROMOTE INNOVATION IN THE 5.9 > GHZ > > > BAND WASHINGTON, December 12, 2019—The Federal Communications > > > Commission today voted[...] > > > > What does C in C-V2X mean? Is it Cellular V2X like in 3GPP? I > assume > > this is what is meant by C-V2X: point-to-point links from 3GPP. > > > > Yes, there are 4G and 5G > > > > Or is C-V2X something more like BSM messages put on 802.11 kind of > link > > (be it OCB or more traditional WiFi)? > > > > > > no it is cellular network communication technologies/protocols > > > > > > What does C-V2X mean entirely? Is it sending BSM messages or is it > also > > sending CAM messages (in 3GPP there are only CAM messages > AFAIremember). > > > > What are the implementations of C-V2X and on which hardware from > which > > manufacturer? > > > > > > see our draft mentions c-v2x: > > > > > https://tools.ietf.org/html/draft-ietf-ipwave-vehicular-networking-03#page-19 > > > > I think it is important that we do more work for the C-V2X section in > > the draft as well. > > > > > > Detailing this term is key to understand the plan and to be able to > > answer the consultation. It might be very worrisome as well as it > might > > be nothing new but a change in terms. > > > > > > The C-V2X is challenging with WiFi V2X, it depends on what is mostly > > used by countries, but the WiFi is probably will win. > > > > AB > > > > >
- [ipwave] FCC Moves Plan Forward to Chop Up Vehicl… Russ Housley
- Re: [ipwave] FCC Moves Plan Forward to Chop Up Ve… Alexandre Petrescu
- Re: [ipwave] FCC Moves Plan Forward to Chop Up Ve… Abdussalam Baryun
- Re: [ipwave] FCC Moves Plan Forward to Chop Up Ve… Alexandre Petrescu
- Re: [ipwave] FCC Moves Plan Forward to Chop Up Ve… Alexandre Petrescu
- Re: [ipwave] FCC Moves Plan Forward to Chop Up Ve… Abdussalam Baryun
- Re: [ipwave] FCC Moves Plan Forward to Chop Up Ve… Abdussalam Baryun
- Re: [ipwave] FCC Moves Plan Forward to Chop Up Ve… Alexandre Petrescu
- Re: [ipwave] FCC Moves Plan Forward to Chop Up Ve… Alexandre Petrescu
- Re: [ipwave] FCC Moves Plan Forward to Chop Up Ve… Alexandre Petrescu
- Re: [ipwave] FCC Moves Plan Forward to Chop Up Ve… Abdussalam Baryun
- Re: [ipwave] FCC Moves Plan Forward to Chop Up Ve… Alexandre Petrescu
- Re: [ipwave] FCC Moves Plan Forward to Chop Up Ve… Alexandre Petrescu
- Re: [ipwave] FCC Moves Plan Forward to Chop Up Ve… Abdussalam Baryun
- Re: [ipwave] FCC Moves Plan Forward to Chop Up Ve… Alexandre Petrescu
- Re: [ipwave] FCC Moves Plan Forward to Chop Up Ve… Jérôme Härri
- Re: [ipwave] FCC Moves Plan Forward to Chop Up Ve… Jérôme Härri
- Re: [ipwave] FCC Moves Plan Forward to Chop Up Ve… Alexandre Petrescu
- [ipwave] Commenting on the FCC plan (was: Re: FCC… Alexandre Petrescu
- Re: [ipwave] Commenting on the FCC plan (was: Re:… Abdussalam Baryun
- Re: [ipwave] Commenting on the FCC plan Alexandre Petrescu
- Re: [ipwave] Commenting on the FCC plan Alexandre Petrescu
- Re: [ipwave] Commenting on the FCC plan Abdussalam Baryun
- Re: [ipwave] Commenting on the FCC plan Alexandre Petrescu
- Re: [ipwave] Commenting on the FCC plan Alexandre Petrescu
- Re: [ipwave] Commenting on the FCC plan Alexandre Petrescu
- Re: [ipwave] Commenting on the FCC plan Alexandre Petrescu
- Re: [ipwave] Commenting on the FCC plan Abdussalam Baryun
- Re: [ipwave] Commenting on the FCC plan fygsimon@gmail.com
- Re: [ipwave] Commenting on the FCC plan Alexandre Petrescu
- Re: [ipwave] Commenting on the FCC plan Alexandre Petrescu
- Re: [ipwave] Commenting on the FCC plan Alexandre Petrescu
- Re: [ipwave] Commenting on the FCC plan Alexandre Petrescu
- Re: [ipwave] Commenting on the FCC plan Alexandre Petrescu
- Re: [ipwave] Commenting on the FCC plan Chris Shen
- Re: [ipwave] Commenting on the FCC plan, and a no… Alexandre Petrescu
- Re: [ipwave] Commenting on the FCC plan, and a no… Alexandre Petrescu
- Re: [ipwave] Commenting on the FCC plan - related… Alexandre Petrescu
- Re: [ipwave] Commenting on the FCC plan - related… Alexandre Petrescu