[icnrg] Review, draft-trossen-icnrg-ip-icn-5glan

Rute Sofia <sofia@fortiss.org> Tue, 12 May 2020 14:13 UTC

Return-Path: <sofia@fortiss.org>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id A69213A0A1E for <icnrg@ietfa.amsl.com>; Tue, 12 May 2020 07:13:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 5NSOWYqyvvkL for <icnrg@ietfa.amsl.com>; Tue, 12 May 2020 07:13:02 -0700 (PDT)
Received: from mail.fortiss.org (mail.fortiss.org []) (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 96E773A09E4 for <icnrg@irtf.org>; Tue, 12 May 2020 07:13:02 -0700 (PDT)
Received: from [] (port=63934 helo=ms01.fortiss.fortiss.org) by mail.fortiss.org with esmtps (TLSv1.2:AES256-GCM-SHA384:256) (Exim 4.82_1-5b7a7c0-XX) (envelope-from <sofia@fortiss.org>) id 1jYVeP-0003MP-2K; Tue, 12 May 2020 16:12:53 +0200
Received: from ms01.fortiss.fortiss.org ( by ms01.fortiss.fortiss.org ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Tue, 12 May 2020 16:12:53 +0200
Received: from ms01.fortiss.fortiss.org ([fe80::3928:e952:611b:9286]) by ms01.fortiss.fortiss.org ([fe80::3928:e952:611b:9286%12]) with mapi id 15.01.1913.010; Tue, 12 May 2020 16:12:53 +0200
X-CTCH-RefID: str=0001.0A782F1C.5EBAAEB1.0058, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
From: Rute Sofia <sofia@fortiss.org>
To: "dirk.trossen@huawei.com" <dirk.trossen@huawei.com>, "icnrg@irtf.org" <icnrg@irtf.org>
Thread-Topic: Review, draft-trossen-icnrg-ip-icn-5glan
Thread-Index: AdYoYR+ALWZF06mWSOKGsEIjlxlJ8w==
Date: Tue, 12 May 2020 14:12:53 +0000
Message-ID: <a1ab08826e1d4c56aeeb62e8b4207678@fortiss.org>
Accept-Language: en-US, de-DE
x-originating-ip: []
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="sha-256"; boundary="----C2731EC99A11AA1E3C417DAD3B6D914F"
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/xbzQ-lLqXpc45_Omj4Aapw4P5w8>
Subject: [icnrg] Review, draft-trossen-icnrg-ip-icn-5glan
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/icnrg/>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 May 2020 14:13:05 -0000

Dear Dirk, Chan, all,

here is a review for the draft (Internet Services over ICN in 5G LAN Environments


The draft is well written, so not much to add. Just a few additional comments and some minor typos detected. As described, the current proposal is targeted to  anycast or multicast transmission. What about N to M, which is supported in ICN and relevant to environments such as IoT?


"Through such replacement of IP routing with ICN routing, we

   capitalize on several ICN capabilities:
" - IMO it would be best to write down something as through ICN integration...

-          5GC is used but not yet defined, so replace with  5G-NextGen Core (5GC)

-          MEC is an architecture, so the definition should be more clear about it (currently, it starts with MEC is located at the edge of the network; the edge today is more than an eNodeB, so the definition needs to be made more objective).

-          One aspect that is missing IMO is the possibility to assist T2T communication. The integration of IoT and 5G benefits from a Pub/Sub approach such as the one in ICN.

-          Terminology: client/consumer/receiver; server/producer/sender should be added
3. again an IoT example would be relevant here.

"To realize the flat device nature," - to support the flat network nature?

Best Regards,

Rute Sofia

fortiss · Landesforschungsinstitut des Freistaats Bayern
An-Institut Technische Universität München
Guerickestraße 25
80805 München
Tel.: +49 (89) 3603522 170
Fax: +49 (89) 3603522 50
E-Mail: sofia@fortiss.org<mailto:sofia@fortiss.org>

Amtsgericht München: HRB: 176633
USt-IdNr.: DE263907002, Steuer-Nr.: 143/237/25900
Rechtsform: gemeinnützige GmbH
Sitz der Gesellschaft: München
Geschäftsführer: Dr. Harald Rueß, Thomas Vallon
Vorsitzender des Aufsichtsrats: Dr. Manfred Wolter