Re: [ipwave] Risks for the future of OCB mode at 5.9GHz

Rex Buddenberg <buddenbergr@gmail.com> Mon, 15 February 2021 16:08 UTC

Return-Path: <buddenbergr@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 08CC73A0CE9 for <its@ietfa.amsl.com>; Mon, 15 Feb 2021 08:08:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level:
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_BLOCKED=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 Ngor5qvOozm8 for <its@ietfa.amsl.com>; Mon, 15 Feb 2021 08:08:01 -0800 (PST)
Received: from mail-pj1-x102f.google.com (mail-pj1-x102f.google.com [IPv6:2607:f8b0:4864:20::102f]) (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 71E383A0C03 for <its@ietf.org>; Mon, 15 Feb 2021 08:08:01 -0800 (PST)
Received: by mail-pj1-x102f.google.com with SMTP id d2so4176832pjs.4 for <its@ietf.org>; Mon, 15 Feb 2021 08:08:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:subject:from:to:date:in-reply-to:references:mime-version :content-transfer-encoding; bh=LfWsVGtBJfiAw/ANyiAQOzNL5z2DbZCjBaPWACPVTlo=; b=SiROlwfVuWJqSJoAonhtnSHc5oIxtrs5mikDNodFrDR5j92CTkfGM5V6PxH3uckabG xVUsNlDi7BnQSYmXuslSt1VubmzZTWjX2ZpBE5x5iHPG7qCohIlA0K15qCGj1WyxZUc7 LCscVXsbJhvPkLvdTKEkILW6/Cr5790rbmoYzU5zqMF9foy8CjZosHikT6TSRAgbq0Aa EuKK/d1feNSUm01uQUkF0iw5FZ6dgM6ubPqhyp+MWZZbhep3dcPHwRxqZhESUyaz4sTb szUcVWNJzahzPRMj4lsNzwztKqzSL8pIH8cpK2AHA8erNCdUAMJr8BYmOD22vaLAAnhT tEkA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:mime-version:content-transfer-encoding; bh=LfWsVGtBJfiAw/ANyiAQOzNL5z2DbZCjBaPWACPVTlo=; b=YhanGZDNYyyjI05IaMpVncT2adJSbhAN2xmBWqwCC8gb2oHgtLzHCa/pauhTJ/8O7g qYHAk6rCAtDrylO85LRxHYcMHyCLZTtDx9Dr64wB/xfJyuJ95taduxX57xPmET8KQCt2 xIj2en283glxwG/9GZuUF012/nY6tXBS6F0J/zMZdGoiDo1ERsQKF1WqVi8Fgp7STcsO BJ6UG/x4T+rPvBRStZzSZ/rBL0asE2M9di1ZyEp4mTPNTTK9ZsOjCkriOft6ir1Rw8H9 tsV3F7tc6unjRRP/F8Ckz9xBvy9MTKCktTbuqFXJNrr+EVlPljZkysA8yDWZrqO3sXd6 rpWA==
X-Gm-Message-State: AOAM530YWvHj8XmyfmOxDh+/YMSd3DIchscUm43lWA4vaqxqLC4yJ0Eg xdic3RBgQD6p5YnTkglCvX8w7HO6nzc=
X-Google-Smtp-Source: ABdhPJwXeBltweZxrUWPPAsnjI/znWOI6WKfMk6y573YowAiOOrtYjuzAbVQTa8QpLep6lMQiYoHyA==
X-Received: by 2002:a17:90a:b38b:: with SMTP id e11mr17235973pjr.214.1613405279765; Mon, 15 Feb 2021 08:07:59 -0800 (PST)
Received: from localhost.localdomain (c-73-241-197-249.hsd1.ca.comcast.net. [73.241.197.249]) by smtp.gmail.com with ESMTPSA id i67sm19556084pfe.19.2021.02.15.08.07.58 (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Mon, 15 Feb 2021 08:07:59 -0800 (PST)
Message-ID: <1613405277.18911.96.camel@gmail.com>
From: Rex Buddenberg <buddenbergr@gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, its@ietf.org
Date: Mon, 15 Feb 2021 08:07:57 -0800
In-Reply-To: <7799867a-7ce8-c38b-96f7-0ff03cb20bf0@gmail.com>
References: <e1d2a31f-5587-cf05-da86-e38fc47adab5@gmail.com> <7799867a-7ce8-c38b-96f7-0ff03cb20bf0@gmail.com>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.18.5.2 (3.18.5.2-1.fc23)
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/Spm-zSMiQuawRjj1brEUKeQUQEg>
Subject: Re: [ipwave] Risks for the future of OCB mode at 5.9GHz
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: Mon, 15 Feb 2021 16:08:03 -0000

The cellphone in my pocket (and probably yours) have both LTE and WiFi
interfaces. 


On Mon, 2021-02-15 at 12:37 +0100, Alexandre Petrescu wrote:
> A colleague pointed me to a video presentation of the problem of ITS-
> G5
> vs C-V2X of January 21, 2021.  The presentation is brief.  It
> describes
> this DSRC-vs-5G to be a problem because there are two standards, too
> complex for deployers, and there is uncertainty for vehicle
> users.  IMHO
> this uncertainty means : should I buy a Ford (C-V2X) or a VW (ITS-
> G5).
> The presenter gives his oppinion: probably C-V2X will win.
> 
> Starting at around 21:02 (21min, 2 seconds) and lasts for about 2
> minutes:
> 
> https://www.real-wireless.com/predicting-2021-trends-connectivity-ins
> ight-from-real-wireless/
> 
> It is interesting to note how he compares the problem to the VHS vs
> Betacam (presumably 5G is more of VHS, and ITS-G5/DSRC more of
> Betacam).
>   Certainly, in around 1995 one would no longer work on anything
> Betacam.
>   But they were both overcome by DVD and Bluray later, and now by 8K.
> 
> Also, the notion of direct communications in cellular systems (w/o
> base
> station) existed long before 5G's PC5: 3G tried it too but it did not
> work.  On another hand, in 3G there were no chips doing direct comm,
> no
> spectrum, but in 5G there are.
> 
> All in all, I am not sure how will this unfold.
> 
> Possibly one way forward is to consider IP:
> IP-over-PC5, and CAM-over-IP.
> 
> With IP tools at hand, the deployer would abstract from the DSRC-vs-
> PC5
> problem.
> 
> What do you think is a possible way forward in the DSRC-vs-PC5
> problem?
> 
> Alex
> 
> 
> Le 12/02/2021 à 11:51, Alexandre Petrescu a écrit :
> > 
> > I take advantage of a private message I received, in order to
> > explain
> > this in English, and to the public email list.
> > 
> > I have some doubts about the future of OCB mode of WiFi.
> > 
> > The recent re-allocation of spectrum by FCC in USA divides the
> > space
> >  typically used for OCB mode of 802.11 into a space for C-V2X (a 
> > different mode than 802.11) and a space for WiFi.
> > 
> > The C-V2X already ate the OCB mode at cca 5.8-5.9GHz, by
> > allocation.
> >  The WiFi is highly likely to eat the OCB mode at cca 5.4-5.8GHz.
> > The
> > reason of this is that WiFi is always and will always be looking at
> > increasing the bandwidth; that increase can be achieved by widening
> > the bands.  This is what WiFi 6E does when claiming to offer
> > 4Gbit/s
> > at 6GHz ('6' is a coincidence).
> > 
> > In the past, what FCC did in USA at 5.9GHz was simply replicated
> > in 
> > Europe and other parts of the world.  Even if today much RSU 
> > deployment exists in Europe (refs available) that runs OCB at
> > 5.9GHz, and VW Golf 8s send CAMs to each other, many indicators
> > point
> > that it might be that these will disappear.  Such indicators are,
> > for example, lack of OCB mode in smartphones, pushes from industry 
> > alliance 5GAA towards 5G-V2X, lack of FCC reply to IPv6-over-OCB 
> > comment, and other declarations.
> > 
> > It is for these reasons that I tend to think the future of OCB
> > mode 
> > of 802.11 at around 5.9GHz is probably at risk.
> > 
> > Alex
> > 
> > _______________________________________________ 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