Re: [icnrg] New Version Notification for draft-ravi-icnrg-5gc-icn-01.txt

Luca Muscariello <luca.muscariello@gmail.com> Wed, 21 March 2018 12:54 UTC

Return-Path: <luca.muscariello@gmail.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 9AE6812DA2B for <icnrg@ietfa.amsl.com>; Wed, 21 Mar 2018 05:54:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 eArfJ2KKjmpt for <icnrg@ietfa.amsl.com>; Wed, 21 Mar 2018 05:54:33 -0700 (PDT)
Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AC9612DA23 for <icnrg@irtf.org>; Wed, 21 Mar 2018 05:54:33 -0700 (PDT)
Received: by mail-qk0-x22f.google.com with SMTP id b198so5245636qkg.9 for <icnrg@irtf.org>; Wed, 21 Mar 2018 05:54:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=c+SDBjontjtcvPq+/I/nw1uzJoYkssOllbQ0Zf9rh/U=; b=VKvlSnfANycr+JteeSF3CnDRQJ8hDxJZwVEgY3YtQuWxBHtcbkQZgvAhnjgig8unIP 2HP7va7ndtmsKod4MPryy+Wnq0iA3kmMw7UTN1RtyMXavxVgSf7GlzpssBbVFaaKtst/ aFLcM6pO+RFFsDQk3WX4VDJOgbslDiYfjgp6nNiZXY0HUNAkdPv4CQfa5CPD13c7lEEe lcb9mqZ5wJMGCoQKH1ZYrcI8kVzjTJSaq0hD0fsz6o7k1HtDTtGXgYCNToTb8yNi6xJJ e0hTZBS6xxrMm0rOeuqogfKI/k0gPp4T0XJVniQAldgK8VPuo2IY+YfDABCnzv7jRBh3 Y4GQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=c+SDBjontjtcvPq+/I/nw1uzJoYkssOllbQ0Zf9rh/U=; b=uSN3MHIPdMfFuRfCKiO69QSO5717JxPnYY4IKZQqoblQbPlWqy9361FWH4QORocrqa 9EANu80/Bp1AmWG4QgQIXx29Zez+RrSQZ0/aws2NAsFmSuwY4/A8kfO3ISP5xFgFZE0d OKeGPLhzQmvP+DTlLhVZTAC/BQBUi7dRYkvxGLwTn/zlw9K4U9gi7SxweyYR56mBdwEb FfuC77dB6q3zIcVZyonPgiVnMUmLhjh6qGKs0Hv/vydK6CQYG1zwpi+iq5I0k7clK3Ph HcI9U16m3ntd/RMlwVjVFFPkX8iiCUEKy5cQ+K5O2MA73I4OYUH6IWiPtumw6YFsqm/G lSBg==
X-Gm-Message-State: AElRT7HSKryTX92QckSUhWnmrMgIS7YFflzqpYoASVI4f/0VRiGFh9KR qkDXbjQxscoNTvJuv2ISGe8fGgSQ5pN26d0u9SY=
X-Google-Smtp-Source: AG47ELtsa5P4ZOnXJBEi2+UUfcGmulVvpdYxoa/If1yVUSF6dAwGMec3/ePDenUH29cOiYk5DW/BP1N0kTs6/kPYEW4=
X-Received: by 10.55.133.131 with SMTP id h125mr29644241qkd.79.1521636872336; Wed, 21 Mar 2018 05:54:32 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <DM2PR10MB001041605C9A8D2E44F2915DF3AA0@DM2PR10MB0010.namprd10.prod.outlook.com>
From: Luca Muscariello <luca.muscariello@gmail.com>
Date: Wed, 21 Mar 2018 12:54:21 +0000
Message-ID: <CAHx=1M6zarftQDtiDAwEfz=N==BY_wEcfeGKXH4xHqW6tjQ=hQ@mail.gmail.com>
To: "Trossen, Dirk" <Dirk.Trossen@interdigital.com>
Cc: Marie-Jose Montpetit <marie@mjmontpetit.com>, Ravi Ravindran <ravi.ravindran@huawei.com>, "icnrg@irtf.org" <icnrg@irtf.org>
Content-Type: multipart/alternative; boundary="94eb2c07c66640c0800567ebb13e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/avcYjCoXICSQ0JYVvqR7-rfTkJQ>
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 12:54:38 -0000

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>
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] *On Behalf Of *Luca
> Muscariello
> *Sent:* 21 March 2018 11:41
> *To:* Ravi Ravindran <ravi.ravindran@huawei.com>
> *Cc:* Marie-Jose Montpetit <marie@mjmontpetit.com>; icnrg@irtf.org;
> Trossen, Dirk <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> 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
> <marie@mjmontpetit.com>]
>
> *Sent:* Tuesday, March 20, 2018 7:37 PM
> *To:* Ravi Ravindran <ravi.ravindran@huawei.com>
> *Cc:* Trossen, Dirk <Dirk.Trossen@InterDigital.com>; Luca Muscariello <
> luca.muscariello@gmail.com>; 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>
> 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
> E: ravi.ravindran@huawei.com
> 2012实验室-硅谷网络技术实验室
> 2012 Laboratories-Silicon Valley Network Technology Lab
>
> *From:*Trossen, Dirk
>
> *To:*Luca Muscariello,Ravi Ravindran,
>
> *Cc:*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 <icnrg-bounces@irtf.org>] *On
> Behalf Of *Luca Muscariello
> *Sent:* 20 March 2018 18:16
> *To:* Ravi Ravindran <ravi.ravindran@huawei.com>
> *Cc:* 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>
> 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]
> Sent: Tuesday, February 27, 2018 12:48 PM
> To: Ravi Ravindran <ravi.ravindran@huawei.com>; Prakash Suthar <
> psuthar@cisco.com>; Dirk Trossen <Dirk.Trossen@InterDigital.com
> <Dirk..Trossen@InterDigital.com>>; Prakash suthar <psuthar@cisco.com>;
> Guoqiang Wang <gq.wang@huawei.comSubject <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.
>
> The IETF Secretariat
>
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg
>
>
>
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg
>
>
>
>