Re: [Metaverse] New Version Notification for draft-fmbk-icnrg-metaverse-01.txt

Giuseppe Fioccola <giuseppe.fioccola@huawei.com> Wed, 12 July 2023 08:49 UTC

Return-Path: <giuseppe.fioccola@huawei.com>
X-Original-To: metaverse@ietfa.amsl.com
Delivered-To: metaverse@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 058F5C151B0C for <metaverse@ietfa.amsl.com>; Wed, 12 Jul 2023 01:49:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ONgtYbJV614z for <metaverse@ietfa.amsl.com>; Wed, 12 Jul 2023 01:49:38 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FD67C151B04 for <metaverse@ietf.org>; Wed, 12 Jul 2023 01:49:38 -0700 (PDT)
Received: from frapeml500006.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4R1BFT45p4z6J6rk; Wed, 12 Jul 2023 16:47:25 +0800 (CST)
Received: from frapeml500006.china.huawei.com (7.182.85.219) by frapeml500006.china.huawei.com (7.182.85.219) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.27; Wed, 12 Jul 2023 10:49:36 +0200
Received: from frapeml500006.china.huawei.com ([7.182.85.219]) by frapeml500006.china.huawei.com ([7.182.85.219]) with mapi id 15.01.2507.027; Wed, 12 Jul 2023 10:49:36 +0200
From: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
To: Bob Hinden <bob.hinden@gmail.com>
CC: ICNRG <icnrg@irtf.org>, "metaverse@ietf.org" <metaverse@ietf.org>, Paulo Jorge Milheiro Mendes <paulo.mendes@airbus.com>, "Burke, Jeff" <jburke@remap.ucla.edu>, Dirk Kutscher <ietf@dkutscher.net>
Thread-Topic: [Metaverse] New Version Notification for draft-fmbk-icnrg-metaverse-01.txt
Thread-Index: AQHZs2doWLWiCW0N70qoBxiuL4oGG6+0RBoQgABMHwCAATlVIA==
Date: Wed, 12 Jul 2023 08:49:36 +0000
Message-ID: <7d47c180481545bab52d88b8719950f3@huawei.com>
References: <168901845148.56574.9118910195410052393@ietfa.amsl.com> <8677a700295f4b9cbf923c7450b79ab4@huawei.com> <6F49272E-A084-4014-9323-4FA22695BE24@gmail.com>
In-Reply-To: <6F49272E-A084-4014-9323-4FA22695BE24@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.203.246.60]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/metaverse/0wc0mQ-SlvlIbkNdh75MNzdlfX8>
Subject: Re: [Metaverse] New Version Notification for draft-fmbk-icnrg-metaverse-01.txt
X-BeenThere: metaverse@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Metaverse Discussion <metaverse.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/metaverse>, <mailto:metaverse-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/metaverse/>
List-Post: <mailto:metaverse@ietf.org>
List-Help: <mailto:metaverse-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/metaverse>, <mailto:metaverse-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2023 08:49:43 -0000

Hi Bob,
Thank you for the feedback.
What we meant with that sentence is that there are different definitions of the Metaverse, even involving the concept of Web3.0. While we considered the notion of a persistent eXtended Reality. I think we can surely clarify better this point in a next revision of the draft.
In this initial version of the document, we already referred to some measurements presented in the following paper: https://dl.acm.org/doi/abs/10.1145/3517745.3561417.
This is a study of five popular social VR platforms and the experimental results reveal that all the tested platforms face fundamental technical challenges to realize the vision of Metaverse. In particular it is showed that throughput, end-to-end latency and on-device computation resource utilization increase almost linearly with the number of users, leading to scalability issues.
There are different proposals currently discussed in IETF (e.g. Media over QUIC and QuicR, APN, CATS,...) but it is not clear whether these solutions can solve all the issues. For this reason, we published this draft in IRTF (and not IETF) to recap the research challenges related to the concept of Information-Centric Networking, which can be seen as a common denominator for the Metaverse in the longer term.

Regards,

Giuseppe


-----Original Message-----
From: Bob Hinden <bob.hinden@gmail.com> 
Sent: Tuesday, July 11, 2023 5:28 PM
To: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
Cc: Bob Hinden <bob.hinden@gmail.com>; ICNRG <icnrg@irtf.org>; metaverse@ietf.org; Paulo Jorge Milheiro Mendes <paulo.mendes@airbus.com>; Burke, Jeff <jburke@remap.ucla.edu>; Dirk Kutscher <ietf@dkutscher.net>
Subject: Re: [Metaverse] New Version Notification for draft-fmbk-icnrg-metaverse-01.txt

Giuseppe,

> On Jul 11, 2023, at 2:05 AM, Giuseppe Fioccola <giuseppe.fioccola=40huawei.com@dmarc.ietf.org> wrote:
> 
> Hi All,
> Please note that we just submitted a new draft in ICNRG about Metaverse as an Information-Centric Network.
> The document aims to explore the new research challenges for the transport network brought by the Metaverse.
> 
> Your inputs and reviews are really welcome.

I note in the introduction is says:

    "Metaverse" is a place-holder for a range of new technologies and
     experiences that is not particularly well-defined…"

based on that, I find the requirements listed in the next section to just be speculation.       Perhaps instead of speculating on the requirements and their solutions, it would be better to propose some work to do real measurements in some existing “metaverse” prototypes to better understand if there are any issues.

Bob


> 
> Best Regards,
> 
> Giuseppe
> (on behalf of the coauthors)
> 
> -----Original Message-----
> From: internet-drafts@ietf.org <internet-drafts@ietf.org>
> Sent: Monday, July 10, 2023 9:48 PM
> To: Dirk Kutscher <ietf@dkutscher.net>; Giuseppe Fioccola <giuseppe.fioccola@huawei.com>; Jeff Burke <jburke@remap.ucla.edu>; Paulo Mendes <paulo.mendes@airbus.com>
> Subject: New Version Notification for draft-fmbk-icnrg-metaverse-01.txt
> 
> 
> A new version of I-D, draft-fmbk-icnrg-metaverse-01.txt has been successfully submitted by Giuseppe Fioccola and posted to the IETF repository.
> 
> Name:		draft-fmbk-icnrg-metaverse
> Revision:	01
> Title:		Information-Centric Metaverse
> Document date:	2023-07-10
> Group:		Individual Submission
> Pages:		14
> URL:            https://www.ietf.org/archive/id/draft-fmbk-icnrg-metaverse-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-fmbk-icnrg-metaverse/
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-fmbk-icnrg-metaverse
> Diff:           https://author-tools.ietf.org/iddiff?url2=draft-fmbk-icnrg-metaverse-01
> 
> Abstract:
>   This document aims to explore the new challenges for the transport
>   network brought by the development of Metaverse.  It discusses the
>   Metaverse as an Information-Centric Network (ICN).
> 
> 
> 
> 
> The IETF Secretariat
> 
> 
> 
> --
> Metaverse mailing list
> Metaverse@ietf.org
> https://www.ietf.org/mailman/listinfo/metaverse