Re: [6gip] 6G in 3GPP?

"Sri Gundavelli (sgundave)" <sgundave@cisco.com> Wed, 13 January 2021 16:00 UTC

Return-Path: <sgundave@cisco.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 578003A1182 for <6gip@ietfa.amsl.com>; Wed, 13 Jan 2021 08:00:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.601
X-Spam-Level:
X-Spam-Status: No, score=-9.601 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=RYATPXz+; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=oK5Y+iiN
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 nnVUZZahpfcc for <6gip@ietfa.amsl.com>; Wed, 13 Jan 2021 08:00:22 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FA6A3A11AE for <6gip@ietf.org>; Wed, 13 Jan 2021 08:00:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5424; q=dns/txt; s=iport; t=1610553621; x=1611763221; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=i5ghiUNdhMYNbpUkvMFJ71tAnbO/Df6BNLQn2SZ3W7s=; b=RYATPXz+R2zHowEDZaYtpLOvUh3d4AZ6dkI8Jj2AuKuFfXwg+sJLC2/e yHSFq7wJu/o7GpdkRToAzcRXk+E6lE7XvPQZnUMsfMGcFL/9h3T1FrjsR ADJzqJcSs55faPvDxASyR2L3tjIenyaq1r3lIn6CSlTvCZ4q/PaDe6sug Q=;
X-IPAS-Result: A0D2BACgFf9fkI0NJK1iHgEBCxIMg2IpKH1bLy4KhDWDSAONdQOKHI52gUKBEQNUCwEBAQ0BARgLCgIEAQGESgIXgVMCJTgTAgMBAQEDAgMBAQEBBQEBAQIBBgQUAQEBAQEBhjgMhXMBAQUBASERDAEBLAwLBgEIEQEDAQEDAiYCBB8GCxUCBgoEARKDJgGCVQMuAQ6jPgKKJXaBMoMEAQEGgTMBg2MNC4IQCYEOKoJ1gmxORIJMg3ImG4FBP4ERJxyCVj6CG0IBAYEpAQESATiDATSCLIFZdlkBVlsqEisZK2qKaogEh1qcNjlYCoJ3iCGBCowlcoUdAx+DKYEwjl6PKZQSjg6OXYRVAgQCBAUCDgEBBoFtIWlwcBU7KgGCPglHFwINjiEMDgmBAgEJgkKFFIVEdDkGAQqBCYtOATBgAQE
IronPort-PHdr: 9a23:p3TVoBLxKrFq6PYsndmcpTVXNCE6p7X5OBIU4ZM7irVIN76u5InmIFeGvqs/iljKXIye4f9Aj6/Suqr7H2cH5MXJvHMDdclKUBkIwYUTkhc7CcGIQUv8MLbxbiM8EcgDMT0t/3yyPUVPXsqrYVrUry606j0TE1D1OA5xY+D8EJWUhMOyhKi+/pTJaFBOgzywKbp5MBSxq1DXsc8b5OkqKqs4xhbT5HVSfOEDzmJzLlXVlBH5tco=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.79,344,1602547200"; d="scan'208";a="666907803"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 13 Jan 2021 16:00:19 +0000
Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by alln-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id 10DG01x7010370 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 13 Jan 2021 16:00:17 GMT
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 13 Jan 2021 10:00:09 -0600
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 13 Jan 2021 10:00:07 -0600
Received: from NAM10-MW2-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Wed, 13 Jan 2021 11:00:07 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=VQ3NeYM2nLMYIHOSpqsi4PLnGPYClzpT/ZsKn3YBIe1JqGV3FfG5+jF9IS3lNK7+aUSTVS4f0cgf+K18fUTwPtBakqvvYWisbHJ5d8I6f2K+/YlzTisHiCaQBenMDV38r7EMeag13+alWqJt7cnQKAlsnU9HhqbSx+sxAVa2Jt4oncFfMQ5cx2HYFbeLSYZjV5nAtopKbgrSgijbG3UPe1X3q/W9poIUqaVbvxCESWfFKZHyjoSKugX29pC6pGdj9X8GDdpPL7dL/PARGHZjzaBS1lcLCaa4RyJjEKbFmmWT1xNJhnvVlyZ7P/XJsg1KlZpQpNhIDCMex0cWoqLUFQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=i5ghiUNdhMYNbpUkvMFJ71tAnbO/Df6BNLQn2SZ3W7s=; b=eUm/yT2osKqumgEHBvD953FSEuJKugzrjSSACECITeRqDD5CUkPcXUb4YCUzapIdpXp5RVOFqoYtldoESgiDCFAZwJPUY+Ge0s7+SWPnhmkABv4mcmQ7Z00jjpvtR96sblOkowKOUm5Bm3gZVY4vpJXM4duxdaLGabStiAl1MFj0qCs4ITfP1+JOXW5C/gmXpCPimBWOxy5akQOhj7Wck5qsR3f9JNKcZUVPrvHkF/RZhpP2duUPGUNPg9YhmlCtxifp3oLFpQqANf89KhNz8DOIQCYjeJ4zwFCwXe2LqLva7cxqsq+eHKC86DdLSIan0VXNQPL+PAfBJdEXBfrA7A==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=i5ghiUNdhMYNbpUkvMFJ71tAnbO/Df6BNLQn2SZ3W7s=; b=oK5Y+iiNyfpvMs1xvK1h7FmWgGesO9Xizch8QeW+jgu8ebMus7PtuDI8CKSVL4boPXuA2SEIAZeam9VM2WEtTWQdrtoyzFzMrMXLcHbViwEnhu/+aHUpA3402ayrVCCTzpHDvImEIShdwOevuZ/w8++JbRfv5JTQGH+huhruCw0=
Received: from BYAPR11MB3558.namprd11.prod.outlook.com (2603:10b6:a03:b3::11) by BYAPR11MB3480.namprd11.prod.outlook.com (2603:10b6:a03:79::27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.9; Wed, 13 Jan 2021 16:00:05 +0000
Received: from BYAPR11MB3558.namprd11.prod.outlook.com ([fe80::ddf8:d2b5:c453:4ad8]) by BYAPR11MB3558.namprd11.prod.outlook.com ([fe80::ddf8:d2b5:c453:4ad8%7]) with mapi id 15.20.3763.010; Wed, 13 Jan 2021 16:00:05 +0000
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: "Flinck, Hannu (Nokia - FI/Espoo)" <hannu.flinck@nokia-bell-labs.com>, Alexandre Petrescu <alexandre.petrescu@gmail.com>, "6gip@ietf.org" <6gip@ietf.org>
Thread-Topic: [6gip] 6G in 3GPP?
Thread-Index: AQHW6cUouAVr8p9+3E68l9b3/XT0Qw==
Date: Wed, 13 Jan 2021 16:00:05 +0000
Message-ID: <23FA62E7-D3B7-45BE-A8DF-0F41EF7D20C8@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.43.20110804
authentication-results: nokia-bell-labs.com; dkim=none (message not signed) header.d=none;nokia-bell-labs.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [128.107.241.178]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b0ebb642-cdc2-4882-b811-08d8b7dc4b3b
x-ms-traffictypediagnostic: BYAPR11MB3480:
x-microsoft-antispam-prvs: <BYAPR11MB34802199A74ABFDF5778FE07D9A90@BYAPR11MB3480.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: qNKvA0BFvBmdwRTr0RN+dd1tOcgOWjVgoTadTCKizp0bcnWgwyxJhZSMzuipbcTCopXEzZoDfYrzNVhOPv1qACNUik389RgCD9a5YG6v6yLgXqqg1BoVoBJ24gQx10VsPX8j3uGcgVPUKQnWMp5Num7EoWMfffKVM5/tsuwbR27zrnXvScj/ZUwObmMgyIX43y8rhPQmg7oi8pbQGyoQ8vz0SUkDKAYwL7+rslrfZfmklqAHNrWXTSJzhWGZXCC+voCeUY21p6cPBHk5V105ay/QL4GM2BOD4wzRK45ymPEyigjhfI0NgZa9Ag+ali4vEBWE5j4XOO+EqbYhVWe9dPXJzSq/Zu9fDbybEebOVDvjjROmGmFl9f0OMRIKb2lgg9UO0c0/MyLpORcz9sZ6vzoX51ZliK5d17p5DK0jKPiKEsB3okNq9Kd9WTLdey6HRNgWGEDhsPLRcHZLchB4FVdbcDqSXCcTc0plbsQ8kPxdaamJRjVOO2T3WESV9xO5oqZhUmNuXObnc8cDv3JMbg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BYAPR11MB3558.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(396003)(39860400002)(376002)(366004)(346002)(136003)(8676002)(36756003)(83380400001)(6486002)(53546011)(8936002)(33656002)(64756008)(110136005)(478600001)(66476007)(6506007)(26005)(2616005)(6512007)(66556008)(2906002)(966005)(316002)(5660300002)(71200400001)(86362001)(76116006)(66446008)(66946007)(186003)(45980500001); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: tU9Bm1vkgwTAiQV7ojYYkn58y6S94P0DsXE5wyF5MJtvpNUbXyiUhgg+myDarLyOuVcCkDYOMTYv5UP0g8/IPTQVEjw/KKvU9wBCvvSuh9/bPRHdN2b7yQG1amSJEKZs/qRZSbRtG0/1y9SDaOHrndPsQUWZ/c6Y/FAdMIbiyrz1Jn0z6ahR95eDYfLnoSy6/fmej1GbQEjNUpT2joDpKja5LcnmpuXDJ51PuVBxQG+HsoXXoDMpamVCrb5L5rqK0Za5Nqm18kDduhWM5V2Zu9lIIYz5sOtsAD9rhRXFckcrdqHplmjzbjuq/kB6limL4iwJQQO9HvOaZTC/3DgOmLjrH6+7b5VcggjHmh8j9vjPwkVXcVGZD433yG/c2K3J6437oGjacSwE1j16iJz6ll68/yyhrUhxRiNZAeX4RzbQHFwiGVKjARKwZ1uEHduuC9+lvvivog7Tlna9bt4kDdnLE2cajx9uh1IhnaYSAh5vA9ii5n0J8PFW8uAF8coYQ2QqFYMxSgo3+zvu6akxBck7yGhvREPGsMGbPH+C/r3niBf1uGM3+rbkWTGGlUv3Gl9aVuyHgUpHzsPOoMWiI0XjPaz6b7uB7zo0olQtNhKaQ84zlkWmYcQv2cVbJGWDx0i0EKtMlvd21fgZDla2WD9IxA+5XvPxohWg+lA1GmTrQvKqE2XvoUPatUBto0lyU1bwZiE7V+PZ9z1z1h2EvEito1uAiFmJqIN1FDP+dyQLiKysBmRTxqlDFHnEaxtDpH0sJr6d4B3SODwGaItQw0TJMzy3xLZktssRQXBGNOXqu5wRHv0cW/IMGowZNCDnrlSi6YeVtYnG24Ih3N22n4LaEaoXq3h5VRnqfA5tAzhvnbnDwW5oAiVKVTPo+8utR1hZLMdEsMCjvbEc/zHuIJtgzbYxSNGMuOIQiinSZ0KEXbj1bKXSxPWMH+ML5U9ui+58fPUxv706Ykplza/Q0hnJrEXFojPlN42j/V1Jb34p3+eWR3QiCMaERx8+OVyd
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <C5EF0022B3F83D4EB2321171C6CE8379@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BYAPR11MB3558.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: b0ebb642-cdc2-4882-b811-08d8b7dc4b3b
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Jan 2021 16:00:05.4778 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: xUKsPNCwa1G0LV80JJgpTiLdok7hxo6dF1t/tkEVA2mVNPi9nOn5OTXuIjMY2snmY8/halGsQfc6gzj7aEm6pg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3480
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.13, xch-rcd-003.cisco.com
X-Outbound-Node: alln-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/6gip/dl7T-hQwuX8AiFrsfdA9UTDuAPo>
Subject: Re: [6gip] 6G in 3GPP?
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: Wed, 13 Jan 2021 16:00:25 -0000

I have the same question. What is 6G? I am looking for the definition. Minimally, is 6G more about radio, or about a certain type of mobility architecture?


Sri




On 1/13/21, 7:58 AM, "6gip on behalf of Flinck, Hannu (Nokia - FI/Espoo)" <6gip-bounces@ietf.org on behalf of hannu.flinck@nokia-bell-labs.com> wrote:

    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://www.ietf.org/mailman/listinfo/6gip