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 D7B00127867 for ; Tue, 20 Mar 2018 11:16:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, SPF_PASS=-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 s6X52qFJwOUO for ; Tue, 20 Mar 2018 11:16:04 -0700 (PDT) Received: from mail-qt0-x22f.google.com (mail-qt0-x22f.google.com [IPv6:2607:f8b0:400d:c0d::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 0B6F41275AB for ; Tue, 20 Mar 2018 11:16:04 -0700 (PDT) Received: by mail-qt0-x22f.google.com with SMTP id l25so2625733qtj.1 for ; Tue, 20 Mar 2018 11:16:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=3l3cZIK84mfRGN7AR+0yS/utxwHkhPLNUd4aXK13ONA=; b=tfpROXaUfWhu40xGw+iw+ws24TiJDRpMT3q9Tt/il+O13WnuLl9DgjZPVLj5zprLDu Ie+FZJ3Bek4RRy9GsxjIgHx6BY/ldeetCLtglWfXl4P+yChEfLYloXDeEFTN3nIUKNFO kLRj08+YBX5Fi0o7yLGY7grMAuJgKLSYbxTBYQ6aNu+j6ZFrgAsKn4B/k6dzT0Jqt6mO As12U1G0tzayN6vUOVymXcjcrPWfwe3MIjlI6XFq9ZvmbL15wkYGJHamoyQJgi66iU/p TrPosqqsW+LxYetkoxo1RdGQPKKv+YzqxLfmyExnf8w6ryAJ3SdWl/7sxI6Ku3Yr+TWW jrXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=3l3cZIK84mfRGN7AR+0yS/utxwHkhPLNUd4aXK13ONA=; b=nUJ0gNa4m14kYwilhLJbnxGQVEXMvpcirkzA7ienfg/DoewtyWqNj+qDOZjFFIjhmI oSeshXAvJV474d7K56fJ93dVuUY/RsA8C5J26yOiUYPwLZ9tWY5m7nODDuU1gKZDpiSD LQuqK7C/nSGzA7qilwzS8uVb1wZJwVWheaQXUMeVuNhX0bQItzyHAizqdPZbYx4TLWq5 m6KAxATdmp40V4djZNTqDI/1rwuhL1Oy8vWYlSYJyxn60HEPoYVCS/XlD+O9qI7U7UAA IF9fLYZUbLoyFZeeyWdYyZPJLusvlVRtHhz/YfmDeOvk5mZJwd2wqYQsjltPNerIEhFj HxCA== X-Gm-Message-State: AElRT7GBvPJdMu1cTx+4uJi0486XjX2PBVPvIADKdE1On1vZXhGGdA6g eHklm2Wd1FF92mBMpSRK0PMnKTVvDgoM3tq4p5k= X-Google-Smtp-Source: AG47ELt5674jfs91v9+LF2wGp7gk6uTztFmMTwdmbZZcNN81g0ZXc2GdZsr1Z0doMLRGZD2Yjv7CXWWvL9aGc7nvcfQ= X-Received: by 10.200.68.15 with SMTP id j15mr25804385qtn.323.1521569763084; Tue, 20 Mar 2018 11:16:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.209.134 with HTTP; Tue, 20 Mar 2018 11:16:02 -0700 (PDT) In-Reply-To: References: <151976449876.28549.12419761863938225649.idtracker@ietfa.amsl.com> From: Luca Muscariello Date: Tue, 20 Mar 2018 19:16:02 +0100 Message-ID: To: Ravi Ravindran Cc: "icnrg@irtf.org" Content-Type: multipart/alternative; boundary="f4f5e80953043ad1040567dc11d7" 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 18:16:07 -0000 --f4f5e80953043ad1040567dc11d7 Content-Type: text/plain; charset="UTF-8" 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 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 ; Prakash Suthar < > psuthar@cisco.com>; Dirk Trossen ; Prakash > suthar ; Guoqiang Wang 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 > --f4f5e80953043ad1040567dc11d7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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.=C2=A0


Is there any plan to co= ntribute in that space?

Luca

<= div>

On Tue, Feb 27, 2018 at 9:56 PM, Ravi Ravindran <ravi.ravindran= @huawei.com> wrote:
The rev= ised 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 in= cluded another user case discussion related to multiuser VR scenario.

Regards,
Ravi



-----Original Message-----
From: internet-drafts@ietf.org<= /a> [mailto:internet-drafts@iet= f.org]
Sent: Tuesday, February 27, 2018 12:48 PM
To: Ravi Ravindran <ravi.ra= vindran@huawei.com>; Prakash Suthar <psuthar@cisco.com>; Dirk Trossen <Dirk.Trossen@InterDigi= tal.com>; Prakash suthar <p= suthar@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 success= fully submitted by Ravi Ravindran and posted to the IETF repository.

Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-ravi-icnrg-5gc-icn
Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A001
Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Enabling ICN in 3GPP's 5G Next= Gen Core Architecture
Document date:=C2=A0 2018-02-27
Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Individual Submission
Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 25
URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 https://www.ietf.org/internet-drafts/draft-ravi-icnrg-5g= c-icn-01.txt
Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0h= ttps://datatracker.ietf.org/doc/draft-ravi-icnrg-5gc-icn/
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0https://t= ools.ietf.org/html/draft-ravi-icnrg-5gc-icn-01
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0https://datatracker.ietf.org/doc/html/draft-ravi-icnrg-5gc-icn-0= 1
Diff:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0https://www.ietf.org/rfcdiff?url2=3Ddraft-ravi-icnrg-5gc-icn-= 01

Abstract:
=C2=A0 =C2=A0The proposed 3GPP's 5G core nextgen architecture (5GC) off= ers
=C2=A0 =C2=A0flexibility to introduce new user and control plane function,<= br> =C2=A0 =C2=A0considering the support for network slicing functions, that al= lows
=C2=A0 =C2=A0greater flexibility to handle heterogeneous devices and applic= ations.
=C2=A0 =C2=A0In this draft, we provide a short description of the proposed = 5GC
=C2=A0 =C2=A0architecture, followed by extensions to 5GC's control and = user plane
=C2=A0 =C2=A0to support packet data unit (PDU) sessions from information-ce= ntric
=C2=A0 =C2=A0networks.=C2=A0 The value of enabling ICN in 5GC is discussed = using
=C2=A0 =C2=A0multiple service scenarios in the context of mobile edge compu= ting
=C2=A0 =C2=A0such as smart mobility and VR use case, and to enable network<= br> =C2=A0 =C2=A0services such as seamless mobility for ICN sessions.




Please note that it may take a couple of minutes from the time of submissio= n 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

--f4f5e80953043ad1040567dc11d7--