Re: [icnrg] New Version Notification for draft-ravi-icnrg-5gc-icn-01.txt
Ravi Ravindran <ravi.ravindran@huawei.com> Wed, 21 March 2018 13:50 UTC
Return-Path: <ravi.ravindran@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 8F38F12702E for <icnrg@ietfa.amsl.com>; Wed, 21 Mar 2018 06:50:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level:
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 dIuMT6GfKGvG for <icnrg@ietfa.amsl.com>; Wed, 21 Mar 2018 06:50:28 -0700 (PDT)
Received: from huawei.com (dfwrgout.huawei.com [206.16.17.72]) (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 CE18B1243FE for <icnrg@irtf.org>; Wed, 21 Mar 2018 06:50:27 -0700 (PDT)
Received: from dfweml702-cah.china.huawei.com (unknown [172.18.9.221]) by Forcepoint Email with ESMTP id BB1B7FEB5A4A4; Wed, 21 Mar 2018 08:50:24 -0500 (CDT)
Received: from SJCEML702-CHM.china.huawei.com (10.208.112.38) by dfweml702-cah.china.huawei.com (10.193.5.176) with Microsoft SMTP Server (TLS) id 14.3.382.0; Wed, 21 Mar 2018 06:50:25 -0700
Received: from SJCEML521-MBS.china.huawei.com ([169.254.2.168]) by SJCEML702-CHM.china.huawei.com ([169.254.4.179]) with mapi id 14.03.0382.000; Wed, 21 Mar 2018 06:50:21 -0700
From: Ravi Ravindran <ravi.ravindran@huawei.com>
To: "Trossen, Dirk" <Dirk.Trossen@InterDigital.com>, Luca Muscariello <luca.muscariello@gmail.com>
CC: Marie-Jose Montpetit <marie@mjmontpetit.com>, "icnrg@irtf.org" <icnrg@irtf.org>
Thread-Topic: [icnrg] New Version Notification for draft-ravi-icnrg-5gc-icn-01.txt
Thread-Index: AQHTsAyNl/E9DBeJWkaqhy39ZQHEkqO4uQ+AgCFLMgCAAAGIgP//n8kigAAwpTCAAVIggIAAErAAgAABroCAAABrgP//lBBQ
Date: Wed, 21 Mar 2018 13:50:19 +0000
Message-ID: <D96E28F4A22C864DBC6C871B5B1C4CC33469DBD0@sjceml521-mbs.china.huawei.com>
References: <151976449876.28549.12419761863938225649.idtracker@ietfa.amsl.com> <D96E28F4A22C864DBC6C871B5B1C4CC33468DB31@sjceml521-mbs.china.huawei.com> <CAHx=1M5FZnYu77Vjyvp2k9LgGsFsw02H+uYa+3Y_XkX43U1s1A@mail.gmail.com> <CO2PR10MB000767292C4F2B18B28FC9E8F3AB0@CO2PR10MB0007.namprd10.prod.outlook.com> <5ab16075.1c69fb81.c2538.e6fbSMTPIN_ADDED_BROKEN@mx.google.com> <B92D4D30-5E64-4CA3-8448-3D786E1D1BC3@mjmontpetit.com> <D96E28F4A22C864DBC6C871B5B1C4CC33469C029@sjceml521-mbs.china.huawei.com> <CAHx=1M5L2usyoDnw6PQx+fF3Uom87iJ2AY026kW+s49H1h=6BQ@mail.gmail.com> <DM2PR10MB001041605C9A8D2E44F2915DF3AA0@DM2PR10MB0010.namprd10.prod.outlook.com> <CAHx=1M6zarftQDtiDAwEfz=N==BY_wEcfeGKXH4xHqW6tjQ=hQ@mail.gmail.com> <DM2PR10MB0010061B337ACC437690C651F3AA0@DM2PR10MB0010.namprd10.prod.outlook.com>
In-Reply-To: <DM2PR10MB0010061B337ACC437690C651F3AA0@DM2PR10MB0010.namprd10.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.80.174]
Content-Type: multipart/alternative; boundary="_000_D96E28F4A22C864DBC6C871B5B1C4CC33469DBD0sjceml521mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/nawCh3zVsZW3EsyEGrfc5snpNBI>
Subject: Re: [icnrg] New Version Notification for draft-ravi-icnrg-5gc-icn-01.txt
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.22
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: Wed, 21 Mar 2018 13:50:31 -0000
Just to add, the ICN-DN in the –00 version was implying CCN/NDN. But since the ICN-DN (referring to the terminology as used in the draft) itself could be based on any ICN architecture, and considering one has the traffic classification function in 5GC, the ICN PDUs could be handed over to different kind of ICN network, which lines in the spirit of network slicing. Having said that, in the future revisions, we can make the discussions more ICN architecture specific, whereever required. Regards, Ravi From: Trossen, Dirk [mailto:Dirk.Trossen@InterDigital.com] Sent: Wednesday, March 21, 2018 12:56 PM To: Luca Muscariello <luca.muscariello@gmail.com> Cc: Ravi Ravindran <ravi.ravindran@huawei.com>; Marie-Jose Montpetit <marie@mjmontpetit.com>; icnrg@irtf.org Subject: RE: [icnrg] New Version Notification for draft-ravi-icnrg-5gc-icn-01.txt Luca, Yes, it’s the wider definition. Our IPoICN does not utilize CCN/NDN but I’m not saying one couldn’t either. Dirk From: icnrg [mailto:icnrg-bounces@irtf.org] On Behalf Of Luca Muscariello Sent: 21 March 2018 12:54 To: Trossen, Dirk <Dirk.Trossen@InterDigital.com<mailto:Dirk.Trossen@InterDigital.com>> Cc: Ravi Ravindran <ravi.ravindran@huawei.com<mailto:ravi.ravindran@huawei.com>>; Marie-Jose Montpetit <marie@mjmontpetit.com<mailto:marie@mjmontpetit.com>>; icnrg@irtf.org<mailto:icnrg@irtf.org> Subject: Re: [icnrg] New Version Notification for draft-ravi-icnrg-5gc-icn-01.txt Dirk I was using the term definion to ask if I have to read ICN as CCN/NDN or also other systems. From your answer it seems the draft accommodates any kind of ICN system but I’m not sure you are saying that. Luca On Wed 21 Mar 2018 at 12:48, Trossen, Dirk <Dirk.Trossen@interdigital.com<mailto:Dirk.Trossen@interdigital.com>> wrote: Luca, (note that I got only late to this draft but still picking up on this) If we were to assume RFC7927 as a baseline when it comes to a ‘definition’ (not saying that this is the only one), would the points in the discussion become any clearer? I’m not sure if the references to CP/CP work in 3GPP are much clearer with that definition. I do think though that a categorization of IP/ICN operations via the suggested transport selector and convergence layer would be beneficial to understand how the CP/UP work might influence the workings, particularly considering that ICN is possible to be run via non-IP PDUs (native ICN) as well as IP PDUs (in overlay as well as concurrent mode, such as in hICN), while IP could run natively over IP PDU, via IPoICN over non-IP PDU and possibly (don’t shoot me) via IPoICN in concurrent hICN mode over IP PDU. Most certainly those operational categories and the efficiency as well as details will be influenced by said 3GPP work. Best, Dirk From: icnrg [mailto:icnrg-bounces@irtf.org<mailto:icnrg-bounces@irtf.org>] On Behalf Of Luca Muscariello Sent: 21 March 2018 11:41 To: Ravi Ravindran <ravi.ravindran@huawei.com<mailto:ravi.ravindran@huawei.com>> Cc: Marie-Jose Montpetit <marie@mjmontpetit.com<mailto:marie@mjmontpetit.com>>; icnrg@irtf.org<mailto:icnrg@irtf.org>; Trossen, Dirk <Dirk.Trossen@InterDigital.com<mailto:Dirk.Trossen@InterDigital.com>> Subject: Re: [icnrg] New Version Notification for draft-ravi-icnrg-5gc-icn-01.txt Ravi and Dirk, let me ask a propaedeutic question, what is the definition of ICN in this draft? It is never defined in the document and I think it is necessary at least to understand each other in this thread. Thanks Luca On Tue, Mar 20, 2018 at 11:44 PM, Ravi Ravindran <ravi.ravindran@huawei.com<mailto:ravi.ravindran@huawei.com>> wrote: Sure Marie, that’s a good feedback, the architecture presented in the draft covers both the scenarios, i..e. ICN over IP and ICN over non-IP PDUs, however it will be good to see if this architectural complexity can be reduced for the later scenario. We hope to have more details around this in the next revision. PS: In my response to Luca, I noted a typo :- “which is also trying to enable end-to-end ICN network”, also was a typo there. Regards, Ravi From: Marie-Jose Montpetit [mailto:marie@mjmontpetit...com<mailto:marie@mjmontpetit.com>] Sent: Tuesday, March 20, 2018 7:37 PM To: Ravi Ravindran <ravi.ravindran@huawei.com<mailto:ravi.ravindran@huawei.com>> Cc: Trossen, Dirk <Dirk.Trossen@InterDigital.com<mailto:Dirk.Trossen@InterDigital.com>>; Luca Muscariello <luca.muscariello@gmail.com<mailto:luca.muscariello@gmail.com>>; icnrg@irtf.org<mailto:icnrg@irtf.org> Subject: Re: [icnrg] New Version Notification for draft-ravi-icnrg-5gc-icn-01.txt While i know that you guys have nothing to do with the current complexities of 5G Networks which I gather are still optimized at the lower layer and with complex control planes I think that if ICN is to be successful it has to reduce complexity not making it worst. On Mar 20, 2018, at 7:26 PM, Ravi Ravindran <ravi.ravindran@huawei.com<mailto:ravi.ravindran@huawei.com>> wrote: hi Luca, I havent read this draft yet, but aware of this work study work item. The objective of this draft is to introduce flatter and richer IP network between the UPFs to get rid of the anchor points points approach that phase-1 inherits from lte, and use these new networks between these UPFs such as ILA or Lisp to handle mobilty, multihomig etc, but its primarily optimizations is to aid IP end points. But as Dirk pointed out, I'm not sure how this would apply to our draft, which is also trying to enable end-to-end ICN network in 5G. But I could talk to the authors, to see if we can take some ideas from our draft into this one, probably a way to take ICN into more active discussion. Regards Ravi -------------------------------------------------- Ravindran Ravishankar Ravindran Ravishankar M: 001-408-410-8240<tel:001-408-410-8240> E: ravi.ravindran@huawei.com<mailto:ravi.ravindran@huawei.com> 2012<tel:2012>实验室-硅谷网络技术实验室 2012<tel:2012> Laboratories-Silicon Valley Network Technology Lab From:Trossen, Dirk To:Luca Muscariello,Ravi Ravindran, Cc:icnrg@irtf.org<mailto:icnrg@irtf.org>, Date:2018-03-20 18:22:33 Subject:RE: [icnrg] New Version Notification for draft-ravi-icnrg-5gc-icn-01.txt Luca, I tend to agree with lots of relevant work in progress to exit but would also acknowledge that there are lots of moving targets in this space, including the CT4 work as well as the SA2 study item on service-based architecture (SBA) for CP and UP traffic. However, I would argue that the draft aligns reasonably well with those moving targets since it aligns with the removal of GTP for non-IP PDUs, where this matters most for ICN deployment. But I might miss some missing target, so apologies beforehand. As for the specific DMM reference, it would be good to understand where you find this fitting since my confusion comes with the relation to the ICN part (granted that DMM is relevant for the IP side). Best, Dirk From: icnrg [mailto:icnrg-bounces@irtf.org] On Behalf Of Luca Muscariello Sent: 20 March 2018 18:16 To: Ravi Ravindran <ravi.ravindran@huawei.com<mailto:ravi.ravindran@huawei.com>> Cc: icnrg@irtf.org<mailto:icnrg@irtf.org> Subject: Re: [icnrg] New Version Notification for draft-ravi-icnrg-5gc-icn-01.txt Ravi, considering that there is no time to ask questions in the room, I have to use the list. All this work of using ICN for 5G is missing relevant work in progress in other places such as DMM. 3GPP CT4 has approved a study item to consider different solutions to replace GTP to connect UPFs. https://datatracker.ietf.org/doc/draft-bogineni-dmm-optimized-mobile-user-plane/ Is there any plan to contribute in that space? Luca On Tue, Feb 27, 2018 at 9:56 PM, Ravi Ravindran <ravi.ravindran@huawei.com<mailto:ravi.ravindran@huawei.com>> wrote: The revised draft offers discussion on leveraging non-IP PDU provision in 5GC for ICN deployment and supporting IP-over-ICN solutions in 5GC. We have also included another user case discussion related to multiuser VR scenario. Regards, Ravi -----Original Message----- From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> [mailto:internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>] Sent: Tuesday, February 27, 2018 12:48 PM To: Ravi Ravindran <ravi.ravindran@huawei.com<mailto:ravi.ravindran@huawei.com>>; Prakash Suthar <psuthar@cisco.com<mailto:psuthar@cisco.com>>; Dirk Trossen <Dirk.Trossen@InterDigital.com<mailto:Dirk..Trossen@InterDigital.com>>; Prakash suthar <psuthar@cisco.com<mailto:psuthar@cisco.com>>; Guoqiang Wang <gq.wang@huawei.comSubject<mailto:gq.wang@huawei.comsubject>: New Version Notification for draft-ravi-icnrg-5gc-icn-01.txt A new version of I-D, draft-ravi-icnrg-5gc-icn-01.txt has been successfully submitted by Ravi Ravindran and posted to the IETF repository. Name: draft-ravi-icnrg-5gc-icn Revision: 01 Title: Enabling ICN in 3GPP's 5G NextGen Core Architecture Document date: 2018-02-27 Group: Individual Submission Pages: 25 URL: https://www.ietf.org/internet-drafts/draft-ravi-icnrg-5gc-icn-01.txt Status: https://datatracker.ietf.org/doc/draft-ravi-icnrg-5gc-icn/ Htmlized: https://tools.ietf.org/html/draft-ravi-icnrg-5gc-icn-01 Htmlized: https://datatracker.ietf.org/doc/html/draft-ravi-icnrg-5gc-icn-01 Diff: https://www.ietf.org/rfcdiff?url2=draft-ravi-icnrg-5gc-icn-01 Abstract: The proposed 3GPP's 5G core nextgen architecture (5GC) offers flexibility to introduce new user and control plane function, considering the support for network slicing functions, that allows greater flexibility to handle heterogeneous devices and applications. In this draft, we provide a short description of the proposed 5GC architecture, followed by extensions to 5GC's control and user plane to support packet data unit (PDU) sessions from information-centric networks. The value of enabling ICN in 5GC is discussed using multiple service scenarios in the context of mobile edge computing such as smart mobility and VR use case, and to enable network services such as seamless mobility for ICN sessions. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org<http://tools.ietf.org/>. The IETF Secretariat _______________________________________________ icnrg mailing list icnrg@irtf.org<mailto:icnrg@irtf.org> https://www.irtf.org/mailman/listinfo/icnrg _______________________________________________ icnrg mailing list icnrg@irtf.org<mailto:icnrg@irtf.org> https://www.irtf.org/mailman/listinfo/icnrg
- [icnrg] New Version Notification for draft-ravi-i… Ravi Ravindran
- Re: [icnrg] New Version Notification for draft-ra… Luca Muscariello
- Re: [icnrg] New Version Notification for draft-ra… Trossen, Dirk
- Re: [icnrg] New Version Notification for draft-ra… Ravi Ravindran
- Re: [icnrg] New Version Notification for draft-ra… Marie-Jose Montpetit
- Re: [icnrg] New Version Notification for draft-ra… Ravi Ravindran
- Re: [icnrg] New Version Notification for draft-ra… Luca Muscariello
- Re: [icnrg] New Version Notification for draft-ra… Trossen, Dirk
- Re: [icnrg] New Version Notification for draft-ra… Luca Muscariello
- Re: [icnrg] New Version Notification for draft-ra… Trossen, Dirk
- Re: [icnrg] New Version Notification for draft-ra… Ravi Ravindran