Re: [ipwave] FCC Moves Plan Forward to Chop Up Vehicle Safety Airwaves

Abdussalam Baryun <> Tue, 17 December 2019 13:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0DD6C12082B for <>; Tue, 17 Dec 2019 05:40:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Status: No, score=-1.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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id rgAXiWnqUC59 for <>; Tue, 17 Dec 2019 05:40:21 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9EA9A12082A for <>; Tue, 17 Dec 2019 05:40:20 -0800 (PST)
Received: by with SMTP id j22so5348736oij.9 for <>; Tue, 17 Dec 2019 05:40:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xlUgPi/eVdcHJwgz7/ge+m5iPa/4wUH6kbBG9raviCA=; b=a0tiAnab67u3NYmAu3zG9TYiWjaNgQCyCvLGIz1cKOGUcPVMbuykVN4vOt1CBtcpNP U6VHJS3wO175oE8+MbAYr06kLerrh1u1L9sbpxDKKGRvGd0HJDP6KkPgtVQ8OrP9AjyJ DMc7DPreF1vUyhXa8KOy9ZF71fTiiakONURvDGjCQyuTmleIBDlbQiTPIZZRmzL3VNXy /4gGSyS5PLQI5wNVFYA1XDCGhK+WEVT2rd7oXZMbB2SbvvEpAwxMvkraxZzxSdxEm42B jngCwvUOCzz+CTYDT6GzEQdVzF409DWNwh962cvVUtqWEQ6bIL75kfuA39qoi31iAOaJ IILw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xlUgPi/eVdcHJwgz7/ge+m5iPa/4wUH6kbBG9raviCA=; b=kOq3sIEIcphU8sQHKoyum8VOgESwW28OziliGXJsUldTANf+GxgWjnWpRmPY00o/M8 5OuHWKm8UWnR88X/IR/ydRvTspgvZPWV5Ns6DUEdbGFhGWLP2vnmueUEPyixAokrqavL ryClLUrJZ9JYcPK21LUpAQ67XlKAkY32kKgDi2jC2lTEp2WB3ZJKavzaBjLfDoba/Exz vQ3rujLw+Aafyfx694jXp2DrkNIRoG7zKprs/O8nyZF0VgYIzyW9lVr2LNA6sPSOl/NB BgM5xGneuisVO1NCPL7r7m+jFxCpgiWXH/o5MXw7dp8I4hChCRjrQYjbuB33h/NsrPLd 8BUg==
X-Gm-Message-State: APjAAAXztw2D1Ms09oSZ9fGGxEEFqlTVkXgLYjX6mJWJJCQ27uokPjkP as8yv6RjcxbJc2tn//Z/LgmvBmsG5U0YcKExnUni0lWn
X-Google-Smtp-Source: APXvYqxChyegDLXjK7gg+3VIycwwyA08AsXMZCNza/PL3slmCQTKvQ07DYgjYPE/FL/2ItI03Qis/xdBMYLfB6RJcTo=
X-Received: by 2002:aca:2210:: with SMTP id b16mr1448393oic.32.1576590019786; Tue, 17 Dec 2019 05:40:19 -0800 (PST)
MIME-Version: 1.0
References: <> <>
In-Reply-To: <>
From: Abdussalam Baryun <>
Date: Tue, 17 Dec 2019 15:40:05 +0200
Message-ID: <>
To: Alexandre Petrescu <>
Cc: its <>
Content-Type: multipart/alternative; boundary="0000000000001601b60599e678f0"
Archived-At: <>
Subject: Re: [ipwave] FCC Moves Plan Forward to Chop Up Vehicle Safety Airwaves
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 17 Dec 2019 13:40:25 -0000

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.

On Tue, Dec 17, 2019 at 12:58 PM Alexandre Petrescu <> wrote:

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

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.