Re: [icnrg] Review, draft-trossen-icnrg-ip-icn-5glan
Dirk Trossen <dirk.trossen@huawei.com> Tue, 12 May 2020 14:15 UTC
Return-Path: <dirk.trossen@huawei.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 900A23A0A6C for <icnrg@ietfa.amsl.com>; Tue, 12 May 2020 07:15:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 NZIEptKxMtFk for <icnrg@ietfa.amsl.com>; Tue, 12 May 2020 07:15:38 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 A640B3A0A69 for <icnrg@irtf.org>; Tue, 12 May 2020 07:15:38 -0700 (PDT)
Received: from lhreml704-chm.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id A99DB517FDB71341D54F; Tue, 12 May 2020 15:15:33 +0100 (IST)
Received: from lhreml701-chm.china.huawei.com (10.201.108.50) by lhreml704-chm.china.huawei.com (10.201.108.53) 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 15:15:33 +0100
Received: from lhreml701-chm.china.huawei.com ([10.201.68.196]) by lhreml701-chm.china.huawei.com ([10.201.68.196]) with mapi id 15.01.1913.007; Tue, 12 May 2020 15:15:32 +0100
From: Dirk Trossen <dirk.trossen@huawei.com>
To: Rute Sofia <sofia@fortiss.org>, "icnrg@irtf.org" <icnrg@irtf.org>
Thread-Topic: Review, draft-trossen-icnrg-ip-icn-5glan
Thread-Index: AdYoYR+ALWZF06mWSOKGsEIjlxlJ8wABpIzQ
Date: Tue, 12 May 2020 14:15:32 +0000
Message-ID: <051b3c726e5e467d946d9e5d4fbe8a77@huawei.com>
References: <a1ab08826e1d4c56aeeb62e8b4207678@fortiss.org>
In-Reply-To: <a1ab08826e1d4c56aeeb62e8b4207678@fortiss.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.3.14]
Content-Type: multipart/alternative; boundary="_000_051b3c726e5e467d946d9e5d4fbe8a77huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/WfE502pR_ikuyALTT-02QgTx2II>
Subject: Re: [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:15:41 -0000
Dear Rute, Many thanks for the review, which is very useful. I'll discuss the progress of the draft with the author team and hope we can progress further. Best, Dirk From: Rute Sofia [mailto:sofia@fortiss.org] Sent: 12 May 2020 16:13 To: Dirk Trossen <dirk.trossen@huawei.com>; icnrg@irtf.org Subject: Review, draft-trossen-icnrg-ip-icn-5glan Dear Dirk, Chan, all, here is a review for the draft (Internet Services over ICN in 5G LAN Environments ) https://datatracker.ietf.org/doc/draft-trossen-icnrg-internet-icn-5glan/?include_text=1 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? Specifically, Introduction: "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. 5.1 "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 Germany Tel.: +49 (89) 3603522 170 Fax: +49 (89) 3603522 50 E-Mail: sofia@fortiss.org<mailto:sofia@fortiss.org> https://www.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
- [icnrg] Review, draft-trossen-icnrg-ip-icn-5glan Rute Sofia
- Re: [icnrg] Review, draft-trossen-icnrg-ip-icn-5g… Dirk Trossen