[lisp] 5G deployment status (was: Re: [ipwave] I-D Action: draft-barkai-lisp-nexagon-10.txt)
Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 25 September 2019 14:14 UTC
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EC0012006E; Wed, 25 Sep 2019 07:14:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.893
X-Spam-Level:
X-Spam-Status: No, score=-0.893 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, SPOOFED_FREEMAIL=1.739] autolearn=no autolearn_force=no
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 oS4ZQjN4FUHp; Wed, 25 Sep 2019 07:14:15 -0700 (PDT)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB819120048; Wed, 25 Sep 2019 07:14:14 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x8PEDnek036287; Wed, 25 Sep 2019 16:13:49 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 335CB202D20; Wed, 25 Sep 2019 16:13:49 +0200 (CEST)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 1B21D205CC8; Wed, 25 Sep 2019 16:13:49 +0200 (CEST)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x8PEDmQO019421; Wed, 25 Sep 2019 16:13:49 +0200
To: Sharon Barkai <sharon.barkai@getnexar.com>, dickroy@alum.mit.edu
Cc: "Victor Moreno (vimoreno)" <vimoreno@cisco.com>, "Ratliff, Stanley" <sratliff@idirect.net>, lisp@ietf.org, its@ietf.org, William Whyte <wwhyte@qti.qualcomm.com>
References: <156862357770.28196.6343819812576579929@ietfa.amsl.com> <d6358cfd-9c8f-3c27-28a5-d7ae20280ec8@joelhalpern.com> <EE82B5CD-B2AC-4590-9F6C-8543E30A68FF@gmail.com> <B452A31E-150E-4AE4-A693-A18AA630AB87@cisco.com> <109358A7-6F14-44DF-9113-3F36DE2194B5@getnexar.com> <BN6PR22MB00364FB9221E42BB7862C424DE890@BN6PR22MB0036.namprd22.prod.outlook.com> <d41c82441d50469ba13955af54fe6577@NALASEXR01H.na.qualcomm.com> <A175A6F452C44636ACCAEEC48CF8B1A7@SRA6> <3EAFD2B8-5FA0-475C-B436-A6ACFB32EED5@getnexar.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <f1976b08-9fbb-6237-c7a4-fb0b84f636df@gmail.com>
Date: Wed, 25 Sep 2019 16:13:48 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0
MIME-Version: 1.0
In-Reply-To: <3EAFD2B8-5FA0-475C-B436-A6ACFB32EED5@getnexar.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/3cXNTODx3nkHABhRqIgX5OLVtRk>
Subject: [lisp] 5G deployment status (was: Re: [ipwave] I-D Action: draft-barkai-lisp-nexagon-10.txt)
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Sep 2019 14:14:18 -0000
Hi Le 20/09/2019 à 04:23, Sharon Barkai and Dick Roy ([RR]) wrote: [...] >> */[RR] This is a really long story, however, C-V2X is being specified >> as an alternative to US DSRC, not as a cellular access technology >> since that’s already available and deployed. The reason LTE Release >> 14 and successors is being specified has nothing to do with its >> lineage as a child of cellular; in fact, it is provably a square peg >> being forced into a round hole and we all know how that generally ends >> up, and that’s a story for another day/* >> >> The 5G evolution is supposed to match the latency of peer to peer WiFi. When that matches, WiFi will have leaped forward to below 100micro-second latency. This was so (cellular catching up with a leaping forward WiFi latency) since the invention of WiFi 20 years ago, and it wont change. It's a constant of evolution. >> */[RR] 5G is nothing but hype at the moment Here is a more precise status, according to my personal understanding. This obviously differs from many people's understandings, who may be more knowledgeable. In France, frequencies for use in 5G radio would start to be discussed now in September, with allocation towards December. The allocation is similar, but not quite like, the process that was used for 3G: auction sales. The differences from 3G are: (1) it is not expected to generate huge revenues for gov't and (2) some sales, like of the 3.5GHz band, would actually be a re-allocation from what was previously allocated to wimax operators (e.g. SDH in France) and to City Authority (like Mayor) in places where there was no operator). Obviously, until these frequencies are allocated one cant really talk about 5G deployment on public roads, even if... If one wants to talk about 5G like when talking a higher bandwidth and lower latency than 4G, then one assumes 4G to be 50ms latency and 2Mbit/s bandwidth. One can talk then about 25ms latency and 10Mbit/s, and claim that to be 5G. But it is not 5G. It is just another Class or Category of 4G. In theory, one can still be 4G and run at 1Gbps (e.g. Category 16). Also, one can talk about a higher bandwidth outdoors network by running 802.11 WiFi on 5.4 GHz and, why not, at 5.9GHz. Colleagues call these 'acrobatics 5G'. This is when one wonders: what is 5G anyways? with its associated question: why was the predecessor of 5G called 'LTE' (Long Term Evolution), or where is the long term? Is 5G LTE? With respect to other countries, I heard two recent announcements, about Spain and Germany. They both claim 5G is deployed in the respective areas. This claims 15 cities in Spain on June 15th, by Vodafone: https://www.xataka.com/empresas-y-economia/red-5g-comercial-vodafone-espana-tiene-fecha-lanzamiento-15-ciudades-15-junio This claims 5 cities in Germany, but it does not say when, by Deutsche Telekom: https://www.telekom.de/start/netzausbau?wt_mc=alias_1070_netzausbau As hardware for end users, this is the situation now: - there is no 5G smartphone for sale in France. I guess it is the same in more countries. If it were different, it would be an isolation easily spot by many. - iphone 11 just launched features 'Gigabit-class LTE' and 'LTE Advanced' but no '5G'. They run on 'LTE Bands' which are your typical frequencies below 5GHz for cellular communications, but nowhere like a 26GHz of 5G. No such band is called a '5G band'. - one can buy off the shelf modules, like miniPCIe (I have a list) that go very high in terms of bandwidth, well beyond what normal 4G would do, but couldnt really use them at that high parameters. Alex >> and simply matching the >> latency would be no reason to switch from DSRC to another access >> technology for V2V safety, though nothing prevents the addition of 5G >> NR access technologies in ITS stations (aka OBUs) for other uses. /* I agree. [...] Alex
- Re: [lisp] I-D Action: draft-barkai-lisp-nexagon-… Joel Halpern
- Re: [lisp] I-D Action: draft-barkai-lisp-nexagon-… Dino Farinacci
- Re: [lisp] I-D Action: draft-barkai-lisp-nexagon-… Victor Moreno (vimoreno)
- Re: [lisp] I-D Action: draft-barkai-lisp-nexagon-… Sharon Barkai
- Re: [lisp] I-D Action: draft-barkai-lisp-nexagon-… Victor Moreno (vimoreno)
- Re: [lisp] I-D Action: draft-barkai-lisp-nexagon-… Ratliff, Stanley
- Re: [lisp] I-D Action: draft-barkai-lisp-nexagon-… Dino Farinacci
- Re: [lisp] I-D Action: draft-barkai-lisp-nexagon-… Sharon Barkai
- Re: [lisp] I-D Action: draft-barkai-lisp-nexagon-… Dino Farinacci
- Re: [lisp] I-D Action: draft-barkai-lisp-nexagon-… Dino Farinacci
- Re: [lisp] [ipwave] I-D Action: draft-barkai-lisp… William Whyte
- Re: [lisp] [ipwave] I-D Action: draft-barkai-lisp… Dino Farinacci
- Re: [lisp] [ipwave] I-D Action: draft-barkai-lisp… Sharon Barkai
- Re: [lisp] [ipwave] I-D Action: draft-barkai-lisp… William Whyte
- Re: [lisp] [ipwave] I-D Action: draft-barkai-lisp… Sharon Barkai
- Re: [lisp] [ipwave] I-D Action: draft-barkai-lisp… Sharon Barkai
- Re: [lisp] [ipwave] I-D Action: draft-barkai-lisp… Sharon Barkai
- [lisp] 5G deployment status (was: Re: [ipwave] I-… Alexandre Petrescu
- Re: [lisp] 5G deployment status Alexandre Petrescu
- Re: [lisp] 5G deployment status Alexandre Petrescu
- Re: [lisp] 5G deployment status (was: Re: [ipwave… Sharon Barkai
- Re: [lisp] [ipwave] I-D Action: draft-barkai-lisp… Abdussalam Baryun