Re: [6gip] 6G

Behcet Sarikaya <sarikaya2012@gmail.com> Thu, 14 January 2021 16:36 UTC

Return-Path: <sarikaya2012@gmail.com>
X-Original-To: 6gip@ietfa.amsl.com
Delivered-To: 6gip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 515263A15DC for <6gip@ietfa.amsl.com>; Thu, 14 Jan 2021 08:36:31 -0800 (PST)
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 ADrLinraVr0j for <6gip@ietfa.amsl.com>; Thu, 14 Jan 2021 08:36:28 -0800 (PST)
Received: from mail-yb1-xb32.google.com (mail-yb1-xb32.google.com [IPv6:2607:f8b0:4864:20::b32]) (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 92FE03A119E for <6gip@ietf.org>; Thu, 14 Jan 2021 08:36:28 -0800 (PST)
Received: by mail-yb1-xb32.google.com with SMTP id y4so2354651ybn.3 for <6gip@ietf.org>; Thu, 14 Jan 2021 08:36:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=sub7tgWT46yVS01GjtlvEO8lt5gL9bBPMxQXGRW21MM=; b=Etql93rt1jOB6PaE+TqForhu3L8W4lLYz9GO7ThPa3PvAH1EkdyOujeDGnYrA9wd6y gndobSFgzYqa70316vVlPyyI7GXWwixX8wY4r5oOCf9/2BcfSvsQLtRDHTxJmduvNwzF ERmZyBC+6ykoWvMQDauNqNOdP41p5XA9xBU48Z0JizVVz9k4W2yrBpyU7m5ii/tK/Ns7 wk/ku3TJHes07GTEDYqcUMP4E1saLFPgPMSbeT+byaO8rCH7mILY7KOlOnOT/lQKLdkb EJ9Hwu2LRrFCdqQR1hQT9EAAM8neSMllgLZvrIlwjj/JFY3xCdvfHcZ8Ut5c7ZHZEKkF olhw==
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:reply-to :from:date:message-id:subject:to:cc; bh=sub7tgWT46yVS01GjtlvEO8lt5gL9bBPMxQXGRW21MM=; b=P3wfgp/L8bgFsdEZXmKlDB6tDDumhhgvjyLJcDhqDAd3A9xrhvdkLROfPF+dVVmMtk ZG2CE2y0jf4izJomAKk/EkP0tTrGiCF78RtT2lSVZsjFLNU9VjeQfH1nkLkd9Z1alVb1 l6dLUax4BDQGxj+emmmbAoX/BxuYsdHcKey1D9isxjLeW1UIuGiIT0rfMRAGIsqgJT3I R8A7SNQR4SpmGMw3ZvEhqPtYalEi9XrjDBUFo8+t23CnZVa3R50lCBC0SKjiBwAz8G86 +cFGlOIy9hVr7iy11pdt1uxaB48yEEUFgfv/kcL6ofNPNmaGQSXUxxW7eW6ObHceDE4+ f1KQ==
X-Gm-Message-State: AOAM532J74Z5+nO3Mj4n8Dyk/be/JY89vT/tceQEsyEIvYoFYpnHJf7u KWfeG6Ld7t9oRvcyqYUVfyK+j/eT4GdzIQlS2zk=
X-Google-Smtp-Source: ABdhPJyk5hVdeiruNH6y7FwivqrKh4II1hICndOyOmaTlCbJ9rZYIwVPHa6lYtF4frqlTfBuiL7ivgJf21RUmYTD3IA=
X-Received: by 2002:a25:2554:: with SMTP id l81mr4088834ybl.243.1610642187627; Thu, 14 Jan 2021 08:36:27 -0800 (PST)
MIME-Version: 1.0
References: <HE1PR07MB3386A43B4B32BF2CE5DC48C79BAA0@HE1PR07MB3386.eurprd07.prod.outlook.com> <248399ab-7dc1-ee13-928c-751568ea58e5@gmail.com> <HE1PR07MB3386A19851BFFF1ED5DDECAE9BA90@HE1PR07MB3386.eurprd07.prod.outlook.com> <SA0PR13MB40801CE55D18D1EF814ED7CDE8A99@SA0PR13MB4080.namprd13.prod.outlook.com> <86fad3c0-a5b0-f6a5-4671-1802d724c5a5@gmail.com>
In-Reply-To: <86fad3c0-a5b0-f6a5-4671-1802d724c5a5@gmail.com>
Reply-To: sarikaya@ieee.org
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Thu, 14 Jan 2021 10:36:16 -0600
Message-ID: <CAC8QAccJ3tJnXY1vVz2nf1okHmmGyEBR7B2FOkzeDUbKOw-XZw@mail.gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: "6gip@ietf.org" <6gip@ietf.org>, "<Dirk.von-Hugo@telekom.de>" <Dirk.von-Hugo@telekom.de>
Content-Type: multipart/alternative; boundary="00000000000074333605b8dedb62"
Archived-At: <https://mailarchive.ietf.org/arch/msg/6gip/t_6M0AGEm5VJB_EUYyVCdOFn9fs>
Subject: Re: [6gip] 6G
X-BeenThere: 6gip@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IP Issues in 6th Generation Mobile Network System \(6gip\)" <6gip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6gip>, <mailto:6gip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6gip/>
List-Post: <mailto:6gip@ietf.org>
List-Help: <mailto:6gip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6gip>, <mailto:6gip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jan 2021 16:36:31 -0000

Hi Alex,

Thank you for this mail and all subsequent ones in the thread.

I think the content could make a good draft writing down these things in
one document helps us a lot.
So we encourage people to consider that seriously.

I read Lars comments. They rightly indicate that as we get more greedy on
these requirements, we are going to hit the physical limits like speed of
light that we can not change.

Dirk & Behcet

On Thu, Jan 14, 2021 at 2:38 AM Alexandre Petrescu <
alexandre.petrescu@gmail.com> wrote:

>
>
> Le 13/01/2021 à 17:24, Kaippallimalil John a écrit :
> > Hi, I share this view as well, and the QUIC example is a good one.
> >
> > Work on 5G still has a long way to go, and there is no clear view or
> > agreement on use cases /requirements for 6G. It may be hard to
> > define protocols or solutions for a problem that is not well
> > understood.
>
> In that sense, it might be appropriate to work on use-cases and
> requirements for 6G.
>
> It might be set that the bandwidth is 500Gbit/s and that RTT latency on
> the air 1 micro-second.
>
> What are the new use-cases that use that?  The tele-portation realistic
> 3D multi-party interacting holograms of humans using wand kinds of
> evolved smartphones, transparent high resolution glasses, gloves, masks
> and non-intrusive exo-squeletons with multi-sense instantaneous feedback
> over very long distance might be such a use-case.
>
> That is for the end user.
>
> For the core network, one should consider the future 6G networks to be
> access networks, mainly the wireless radio part.  The core network that
> plugs into 6G should be a same flat Ethernet-based network that is
> plugged into ADSL, fiber-to-the-home and space-terrestrial networks.  No
> tunnels, no 3GPP-specific protocols in the core.  As much as there wont
> be an all-optical networks that home network designs would like there
> wont be an an all-space network and no all-6G network either.
>
> What are the implications on IP protocols?  The addressing space of IPv6
> might be sufficient, but maybe more intelligent control taking more
> bandwidth could be useful.  Maybe better accommodating mobility of
> users, of groups of users, and of satelites.  Maybe better accomodating
> of QoS.
>
> What are the implications on other IETF protocols?
>
> What are the current tendencies in the 6MAN and V6OPS WGs of IETF about
> the evolution of IP protocols?  There are some activities about IP and
> 1hop protocols, some discussion around the 64bit boundary that I am
> aware of.  There are others.  Would they be good for the tele-portation
> use-case satisfying end users, and for the re-pluggable core network?
>
> Alex
>
> >
> > Best Regards, John
> >
> >
> > -----Original Message----- From: 6gip <6gip-bounces@ietf.org> On
> > Behalf Of Flinck, Hannu (Nokia - FI/Espoo) Sent: Wednesday, January
> > 13, 2021 9:58 AM To: Alexandre Petrescu
> > <alexandre.petrescu@gmail.com>; 6gip@ietf.org Subject: Re: [6gip] 6G
> > in 3GPP?
> >
> > Hello
> >
> > Neither I know any, nor my colleagues any 3GPP documents about 6G.
> >
> > 3GPP is currently at mid-way with 5G. There will still be a number
> > of releases left for 5G  to come. In fact, I assume that now when 5G
> > is pushing towards new verticals (mIoT, industry, vehicular, etc.)
> > there will be new requirements for protocol work needed for 5G. For
> > example, consider the discussion about multi-path support for QUIC
> > in QUIC wg. Similar requests are likely to come.
> >
> > Therefore, I am on the opinion that 6G work, even 6G related
> > protocol research work in the IRTF, should wait for use cases (and
> > radio extensions) that 5G is not able to respond.
> >
> >
> > Best regards Hannu
> >
> > -----Original Message----- From: Alexandre Petrescu
> > <alexandre.petrescu@gmail.com> Sent: Wednesday, January 13, 2021
> > 10:40 AM To: Flinck, Hannu (Nokia - FI/Espoo)
> > <hannu.flinck@nokia-bell-labs.com>; 6gip@ietf.org Subject: Re: 6G in
> > 3GPP?
> >
> > Me too I would like to ask I would like whether someone knows of a
> > document on the 3gpp.org site that has the term '6G' in it?
> >
> > Le 12/01/2021 à 17:55, Flinck, Hannu (Nokia - FI/Espoo) a écrit :
> >> Hello Alexandre
> >>
> >> In your slides you claim the 6G is discussed in Rel 17. Can you
> >> tell in which document or WG?
> >>
> >> I am involved quite a bit in 3GPP as well as in 6G research and I
> >> am not aware of any of such discussion.
> >>
> >> Without a reference I must consider that statement be
> >> misinformation.
> >>
> >> Best regards
> >>
> >> Hannu
> >
> > Thanks for having gone through the slides; the slides tried to
> > summarize the discussions on the email list at that time.
> >
> > It might be that a potential reationship between 3GPP and 6G to be a
> > stretch.
> >
> > I might bear responsibility of having misread the emails, or read
> > them too quickly, when drawing a conclusion that 3GPP might work on
> > 6G, and writing that down.  Sorry for misunderstanding.
> >
> > We had some mention on this list of an NGMN alliance (Next
> > Generation Mobile Networks) which initiated a task force on 6G;
> > elsewhere, NGMN is ack'ed as a contributor to 3GPP by a wikipedia
> > article.  That might make it that 3GPP might have some work on 6G.
> >
> > It might be that some discussions between usual contributors to 3GPP
> > might have mentioned 6G even though there might be no document on
> > 3gpp.org that reads '6G'.  For my part, I do not know what document
> > is Rel 17 more precisely, but I suspect I could find Rel 17 on
> > 3gpp.org.
> >
> > It might be that other industry alliances (e.g. 5GAA) could be
> > outright opposed to work on things deemed "6G".  It might be that
> > such opposition is supported by other funding bodies.  I do not know
> > why the opposition, but that is the way it is.
> >
> > If, for some reason, 3GPP considers the talk of 6G to be too early,
> > and why not potentially disruptive to the ongoing work of 5G, then
> > that is a 3GPP problem to solve.  That would not be the only problem
> > they should address.  I suspect a ling standing problem is even the
> > name "3G" in a 3GPP working on something else than 3G (e.g. 3GPP
> > working on 4G or 5G).
> >
> > I want to tell also that there might be other problems of 5G, on
> > which 3GPP works, and which deserve attention.
> >
> > Such problems could be solved by working on something new, like 6G.
> >
> > It is a speculation from my part.
> >
> > I would like to ask others whether someone knows of a document on
> > the 3gpp.org site that has the term '6G' in it?
> >
> > Alex
> >
> > -- 6gip mailing list 6gip@ietf.org
> >
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2F6gip&amp;data=04%7C01%7Cjohn.kaippallimalil%40futurewei.com%7C7fdd86f62b8a4531b7a308d8b7dc249f%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637461503443285528%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=fYapnHc1H75JcGA2Y6KRUXxD1%2B4VFcsyYmaBkf%2BkQOE%3D&amp;reserved=0
> >
>
> --
> 6gip mailing list
> 6gip@ietf.org
> https://www.ietf.org/mailman/listinfo/6gip
>