Return-Path: 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 84E081289B0 for ; Tue, 20 Mar 2018 12:36:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mjmontpetit-com.20150623.gappssmtp.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 Bhl6AIXsJJ2H for ; Tue, 20 Mar 2018 12:36:55 -0700 (PDT) Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (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 1A7711241F5 for ; Tue, 20 Mar 2018 12:36:55 -0700 (PDT) Received: by mail-wm0-x231.google.com with SMTP id h21so5647496wmd.1 for ; Tue, 20 Mar 2018 12:36:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mjmontpetit-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=i/kSfE4RVD5tdCIHAhJHI4VQTg0Nkt/x5Cqxm40CC6k=; b=l/UsuFWMC4LziDjasRtxOJHWikSBdsDmmAGVljiq+RMiw8Ceu1I9o1GUf9aON0af6x zutqSsEJsSMKFppUm3EPmPmmZFxcfA6xmyPLu8GPIj2WsV08dvb1IpsSVkRDMGjU7TSd Rx7xrELfS5IG6dOhi3H6iTqNDizfPWbTswFfj3PgJLLt9q4qn6oPhoqIVBTzqXnpVgP/ dn6dsSGwrKHHWrnbv7i8O82STIOFbEpfK5gaAWaH5OugpB2d6zBhDSyLJC6Ee9lW/b7h cZc1XuC6Inv26Hl9rWdqteIBYjB6YPimjuDxvjjf8BMWYa4l07BYIZaE8hYWN2bWTaul oT6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=i/kSfE4RVD5tdCIHAhJHI4VQTg0Nkt/x5Cqxm40CC6k=; b=jJRctOoK2hQ0Ur76NeaXINCoSF8RGTy8bZmTQeFQK7TXbnR0uHrGezr2qgxYFbaxnM /zDZYoA7vAFHd6JuuJKNbISsPaRBF1mPyFxvOn3joQA6njTvS5E2FDmsF+dNnr4yXXtH rc9qJKPx1qZipy8XbqluQoSAxD69S6Fc/T7czd0MXwf4cw8t1KLoq4JwfrMsilQ8DsIo 17vnTt2+yKhem0GRz25mWhRKZKJC6DML9FpgL0oMwMGQRxp5LCjJd50kmvoWdkjBO7tL BoFsxKha269L2wek3U/Og89Ibp1Zkj9o5HklCAf1Nai9WQnBsj6Mws8uYrfp5rgPuJAh 3t4Q== X-Gm-Message-State: AElRT7Hcl1lWQR6v5KLOzFxmWnbWAlrQoB6rPYGfahDxMtekGMEvDg+q rYx5G1ygSnFoJLlbF05bARS5vg== X-Google-Smtp-Source: AG47ELuiix/Ur+xpRia36lH+KxbN181MnWnEyy0YY+A/hMuJuW0KgSwpQpkC3U0Wk877ZTZFd+OCsg== X-Received: by 10.28.5.145 with SMTP id 139mr615555wmf.31.1521574613527; Tue, 20 Mar 2018 12:36:53 -0700 (PDT) Received: from winterfell.home ([2a00:23c0:fcf6:2901:50a2:c0cb:e32:ed9c]) by smtp.gmail.com with ESMTPSA id q13sm2469346wrg.56.2018.03.20.12.36.51 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 20 Mar 2018 12:36:52 -0700 (PDT) Content-Type: multipart/alternative; boundary="Apple-Mail=_381171C5-5D0C-48B1-B8FB-5C650401B439" Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Marie-Jose Montpetit In-Reply-To: <5ab16075.1c69fb81.c2538.e6fbSMTPIN_ADDED_BROKEN@mx.google.com> Date: Tue, 20 Mar 2018 19:36:51 +0000 Cc: "Trossen, Dirk" , Luca Muscariello , "icnrg@irtf.org" Message-Id: References: <151976449876.28549.12419761863938225649.idtracker@ietfa.amsl.com> <5ab16075.1c69fb81.c2538.e6fbSMTPIN_ADDED_BROKEN@mx.google.com> To: Ravi Ravindran X-Mailer: Apple Mail (2.3124) Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2018 19:37:00 -0000 --Apple-Mail=_381171C5-5D0C-48B1-B8FB-5C650401B439 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 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.=20 > On Mar 20, 2018, at 7:26 PM, Ravi Ravindran = wrote: >=20 > hi Luca, >=20 > 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. >=20 > But as Dirk pointed out, I'm not sure how this would apply to=20 > 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. >=20 > Regards > Ravi >=20 > -------------------------------------------------- > Ravindran Ravishankar Ravindran Ravishankar > M: 001-408-410-8240 > E: ravi.ravindran@huawei.com > 2012 =E5=AE=9E=E9=AA=8C=E5=AE=A4-=E7=A1=85=E8=B0=B7=E7=BD=91=E7= =BB=9C=E6=8A=80=E6=9C=AF=E5=AE=9E=E9=AA=8C=E5=AE=A4 > 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 >=20 > Luca, > =20 > 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. > =20 > 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. > =20 > 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). > =20 > Best, > =20 > Dirk > =C2=A0 <> > From: icnrg [mailto:icnrg-bounces@irtf.org = ] On Behalf Of Luca Muscariello > Sent: 20 March 2018 18:16 > To: Ravi Ravindran > > Cc: icnrg@irtf.org > Subject: Re: [icnrg] New Version Notification for = draft-ravi-icnrg-5gc-icn-01.txt > =20 > Ravi, > =20 > considering that there is no time to ask questions in the room, I have = to use the list. > =20 > All this work of using ICN for 5G is missing relevant work in progress = in other places > such as DMM. > =20 > =20 > 3GPP CT4 has approved a study item to consider different solutions to = replace GTP to connect > UPFs.=20 > =20 > = https://datatracker.ietf.org/doc/draft-bogineni-dmm-optimized-mobile-user-= plane/ = > =20 > Is there any plan to contribute in that space? > =20 > Luca > =20 > =20 > =20 > On Tue, Feb 27, 2018 at 9:56 PM, Ravi Ravindran = > 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. >=20 > Regards, > Ravi >=20 >=20 >=20 > -----Original Message----- > From: internet-drafts@ietf.org = [mailto:internet-drafts@ietf.org ] > Sent: Tuesday, February 27, 2018 12:48 PM > To: Ravi Ravindran >; Prakash Suthar >; Dirk Trossen >; Prakash suthar = >; Guoqiang Wang = : New = Version Notification for draft-ravi-icnrg-5gc-icn-01.txt >=20 >=20 > 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. >=20 > 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=3Ddraft-ravi-icnrg-5gc-icn-01 = >=20 > 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. >=20 >=20 >=20 >=20 > 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 . >=20 > The IETF Secretariat >=20 > _______________________________________________ > icnrg mailing list > icnrg@irtf.org > https://www.irtf.org/mailman/listinfo/icnrg = > =20 > _______________________________________________ > icnrg mailing list > icnrg@irtf.org > https://www.irtf.org/mailman/listinfo/icnrg = --Apple-Mail=_381171C5-5D0C-48B1-B8FB-5C650401B439 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 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=E5=AE=9E=E9=AA=8C=E5=AE=A4-=E7=A1=85=E8=B0= =B7=E7=BD=91=E7=BB=9C=E6=8A=80=E6=9C=AF=E5=AE=9E=E9=AA=8C=E5=AE=A4
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] 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-m= obile-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>; Prakash suthar <psuthar@cisco.com>; = Guoqiang Wang <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-0= 1.txt
Status:         https://datatracker.ietf.org/doc/draft-ravi-icnrg-5gc-icn/<= br class=3D"">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=3Ddraft-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

= --Apple-Mail=_381171C5-5D0C-48B1-B8FB-5C650401B439--