Re: [icnrg] I-D Action: draft-irtf-icnrg-icn-lte-4g-04.txt

"Anil Jangam (anjangam)" <anjangam@cisco.com> Wed, 02 October 2019 18:18 UTC

Return-Path: <anjangam@cisco.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 26A601200B7 for <icnrg@ietfa.amsl.com>; Wed, 2 Oct 2019 11:18:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=GH+7jiNu; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=hNiBLDBm
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 g4aiEvxrmRk2 for <icnrg@ietfa.amsl.com>; Wed, 2 Oct 2019 11:18:27 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C43312018B for <icnrg@irtf.org>; Wed, 2 Oct 2019 11:18:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=77135; q=dns/txt; s=iport; t=1570040307; x=1571249907; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=sFmdI+3lHsFntAwkt7aUaiCop4M6yKEWzB+Rt+iqfgw=; b=GH+7jiNurB1sxwjbwTfN7qXgTwPuhCmVTm63j447rFCD/+YdR3dB6PCN xAmg5dKY+9n9w07+66JnVJ1jaqTuHGPUhP0RacOcIr5tHMIcoCq7qYVfJ hlfoj6/gZ/rpABdqOGqN1rERWmmi4RTJpDX8sn26xamyYdgpn0RCi/W28 Q=;
IronPort-PHdr: 9a23:dMRcpxR6IrIag3PzY2Y35BCIbdpsv++ubAcI9poqja5Pea2//pPkeVbS/uhpkESXBNfA8/wRje3QvuigQmEG7Zub+FE6OJ1XH15g640NmhA4RsuMCEn1NvnvOiU8Hs1EW1Zg13q6KkNSXs35Yg6arw==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CyBQDQ6JRd/4oNJK1MGg4OAQEBBAEBDAQBAYFngRwvUANtViAECyqEIoNHA4o9gjcll3eBQoEQA1AECQEBAQwBARgBDAgCAQGEQAIXgiYjOBMCAwkBAQQBAQECAQUEbYUtDIVLAQEBBAEBEAgDBgQGEwEBDBoGBgUBDwIBCBEBAgECDRQBBgMCAgIlCgEUAwYIAgQBDQUUCQQBgwABgR1NAx0BAgw5pHsCgTiIYXV/M4J9AQEFgTQBAwIOQYMAGIIXCYE0hXiGFhiBQD+BEScME4FgbD6CVgsBAQEBAQEWgQ8FAQsHAQMGEgsHCQkMAQkCBoJPMoImjGQNQYI2hTAkiQeObAqCIocIi1WCORuCOHKGXI1UgV+OJoE9hmGCFIJpjBECBAIEBQIOAQEFgT8qIio9cXAVGiEqAYJBCQo9EBRWeYNzhRSCZoIeOgF0AQGBJ41HDxeCLgEB
X-IronPort-AV: E=Sophos;i="5.67,249,1566864000"; d="scan'208,217";a="343329573"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 02 Oct 2019 18:18:19 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by alln-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id x92IIJuF003513 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 2 Oct 2019 18:18:19 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 2 Oct 2019 13:18:18 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 2 Oct 2019 14:18:17 -0400
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 2 Oct 2019 14:18:17 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Dvkskvxu48pEd0ayGJUFsGGD72y2AjNKcG0ZCK8aiFIl7YP1aN+H+N4oT9yEXDJjlCGm67FmjkjFSI0+/FGaQ+8LriTFlalroQAs3tAV6TFbnVdGVv3s4T5vMHifzkQSaZ45z5f1WslCuqALMtjQTT2WomhB0F0CJO149W8JAKVW7uOrsLdbG6ulj6BJswVNPSU1VzCKljl8u8kNpr5R2P7svv941tMU+kKcFps69ePmIzmalwB4mzzKLzgn8g6oOWXTosoig+F6s6I1S1Fc6/WcyNBo1uPAkYIYvEdhZ1IaCxDFtdKbH9Qvst01zmC6lh8950LO7QP+bFB5qDV6dA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=sFmdI+3lHsFntAwkt7aUaiCop4M6yKEWzB+Rt+iqfgw=; b=UiFbdybEXYNoT9SHWIFJCXcPkUUh8fIW38hpaCYUfGnvUV0uCpybLwxvDOYizv9Hg8OUXD1jnpR4naPo/6/UDHofOvWLkK6fSW2Fq5lqu8xr7vOr0EHG2RcBBlKPl3HOlGLqBWIQze+VUxExLBjooelF7EazraHGGll7t3w2n6exGkBIbCb+Lo2p0bHrBBvRX2BKq8TeYzRNLbJquO74bPYcTQtFIVa1Us8JJkY4DiBFQsNFxSitbyWzGytmCJu7zdGIfPQ/n3qiW6tD4bveP90TRCvYtAE3DK+5b8oSs2y8SGu62/BZNhnryXVO9GS6Im8aF6/HG4k88+M0BE2UIQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=sFmdI+3lHsFntAwkt7aUaiCop4M6yKEWzB+Rt+iqfgw=; b=hNiBLDBmDDEJKFS81m1KI6wiaNDKY9jia7oWa2/WjkBSvKJ9rSfvjExD1TfvbQ7jlSBG9kReQp0DjRdntAp7xYiYIj/N5qvqqadkStidZ8GAq033CUXbko208T0fmdkuerwKL6LWM7Wmfw1O5eoOCO0nramJCMYlISobTcPeMWE=
Received: from BYAPR11MB3687.namprd11.prod.outlook.com (20.178.237.160) by BYAPR11MB3464.namprd11.prod.outlook.com (20.177.187.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2305.20; Wed, 2 Oct 2019 18:18:15 +0000
Received: from BYAPR11MB3687.namprd11.prod.outlook.com ([fe80::5dd4:f4a6:2c33:4102]) by BYAPR11MB3687.namprd11.prod.outlook.com ([fe80::5dd4:f4a6:2c33:4102%3]) with mapi id 15.20.2305.023; Wed, 2 Oct 2019 18:18:15 +0000
From: "Anil Jangam (anjangam)" <anjangam@cisco.com>
To: "Reed, Martin J" <mjreed@essex.ac.uk>, "icnrg@irtf.org" <icnrg@irtf.org>
CC: "Prakash Suthar (psuthar)" <psuthar@cisco.com>, "Milan Stolic (mistolic)" <mistolic@cisco.com>, Ravi Ravindran <ravi.ravindran@huawei.com>, Dirk Trossen <Dirk.Trossen@InterDigital.com>
Thread-Topic: [icnrg] I-D Action: draft-irtf-icnrg-icn-lte-4g-04.txt
Thread-Index: AQHVeRy7kOzI3StFyEqgKG9sqRubkqdHM/IA
Date: Wed, 02 Oct 2019 18:18:14 +0000
Message-ID: <DA93C416-BA69-4306-BE09-01ADB500F1D9@cisco.com>
References: <mailman.278.1568115487.9675.icnrg@irtf.org> <6F72F397-8805-4236-9F7D-A4C7963E0C4F@essex.ac.uk>
In-Reply-To: <6F72F397-8805-4236-9F7D-A4C7963E0C4F@essex.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=anjangam@cisco.com;
x-originating-ip: [2001:420:292:1260:1998:bd2c:b0b2:a070]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 1ad2c809-fb34-4387-061a-08d74764e47d
x-ms-traffictypediagnostic: BYAPR11MB3464:
x-ms-exchange-purlcount: 7
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <BYAPR11MB346415E933C5236CE41507C7C19C0@BYAPR11MB3464.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0178184651
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(396003)(39860400002)(136003)(376002)(366004)(27574002)(189003)(199004)(171004002)(14454004)(236005)(316002)(54906003)(66946007)(6306002)(6512007)(110136005)(76116006)(5660300002)(6246003)(64756008)(66476007)(66446008)(30864003)(66556008)(33656002)(71200400001)(71190400001)(54896002)(36756003)(256004)(14444005)(5024004)(6486002)(66574012)(7736002)(86362001)(19273905006)(6436002)(2906002)(4326008)(16799955002)(229853002)(102836004)(8936002)(186003)(446003)(966005)(25786009)(76176011)(99286004)(53546011)(478600001)(6506007)(486006)(8676002)(476003)(2616005)(11346002)(606006)(81156014)(81166006)(2501003)(46003)(6116002)(13710500001)(563064011); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3464; H:BYAPR11MB3687.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: h/I+H2T8JTV/MXOujA//H23VM0HiNSPzcu1xwpAFquHVf11c00MXgV+YAytJPu7fVxUXv5z/GAd7N+3IDHCapZKwAhMLZ5Ux/XllvZhEL0AT8F3OzzxT93LFBjjhMNWwv0PRBqvi+pERXv0YLQeRXatTUL2iJGLwrhdqtWoOmTMOMpMPmgaUcXdh19zUOhmNLjHtI9JI2LLhA4p3865x7x60LwOcb+CUluDwLoIL6qCm+DgS90mAMhRo6eUo5Aq9pq091soE4uEDuCM/mj0/Zk8avlZ3Avv/ffcrlPYgFYW8Zv10aGDr2pykqxykINeUOWxp+JwQkwifhWW0Sux9EB8HRfYcnUHicgdnZeGrlu1UA1SjBlgD98rw6+54Sk9K0O8GGZZGKp9Rv+5Gea47sgE+f9JS54FZbY9CLCy+rRYUissw3GY0sWMc5Ud3n/IV8/rcHDxQpNwSEyyRf5TZxg==
Content-Type: multipart/alternative; boundary="_000_DA93C416BA694306BE0901ADB500F1D9ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 1ad2c809-fb34-4387-061a-08d74764e47d
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Oct 2019 18:18:14.9226 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: D+hYB7AOYBXjVtPzE9b4ChEE6Pk+s1lyiiKN5nVX8xYxhoKbmKp/lu/yh19x7IW9wqQhfaPLjEsWKD2NGCkJCw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3464
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.14, xch-aln-004.cisco.com
X-Outbound-Node: alln-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/xCg_lMk8rCiWo2ButuC1H17tqTU>
Subject: Re: [icnrg] I-D Action: draft-irtf-icnrg-icn-lte-4g-04.txt
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: Wed, 02 Oct 2019 18:18:32 -0000

Thank you Martin for your feedback. We will wait for some more and put a consolidated update.

Thank you,
/anil.


icnrg on behalf of Reed, Martin J icnrg-bounces@irtf.org<mailto:icnrg-bounces@irtf.org> on behalf of mjreed@essex.ac.uk<mailto:mjreed@essex.ac.uk> 10/2/19, 5:28 AM

Hi.

I support draft-irtf-icnrg-icn-lte-4g-04.txt

Minor suggested changes:

 Expand CUPS on first use in section 4.1

 With this major architecture change, User Plane Function -> With this major architecture change, a User Plane Function

 TCL can use a number of mechanisms for the selection of transport. -> The TCL can use a number of mechanisms for the selection of transport.

 On other hand, PGW shall -> On other hand, the PGW shall

 At the end of point 3 in Section 4.2  it says

 "Detailed user plane deployment use cases are described in
 Section 4.4.  Application conveys the preference to the TCL,
 which in turn sends the ICN data packets using the IP transport. “

 I would suggest removing the last sentence as it is explained fully in 4.4.1 and the context
 is not clear at the end of Section 4.2, else this last sentence needs a little more context.


Regards,

Martin

Dr. M.J. Reed                                         Room:       1NW.4.18
School of Computer Science and Electronic Engineering
Tel:+44 (0)1206 872479            FAX:+44 (0)1206 872900
University of Essex, Colchester CO4 3SQ, UK
Email mjreed@essex.ac.uk<mailto:mjreed@essex.ac.uk>
Web: http://csee.essex.ac.uk/staff/mjreed
Doodle meetme: http://doodle.com/martinjreed


On 10 Sep 2019, at 12:38, icnrg-request@irtf.org<mailto:icnrg-request@irtf.org> wrote:

Send icnrg mailing list submissions to
icnrg@irtf.org<mailto:icnrg@irtf.org>

To subscribe or unsubscribe via the World Wide Web, visit
https://www.irtf.org/mailman/listinfo/icnrg
or, via email, send a message with subject or body 'help' to
icnrg-request@irtf.org

You can reach the person managing the list at
icnrg-owner@irtf.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of icnrg digest..."
Today's Topics:

  1. ACM ICN: Early bird registration extended (Matthias Waehlisch)
  2. I-D Action: draft-irtf-icnrg-icn-lte-4g-04.txt
     (internet-drafts@ietf.org)
  3. Re: I-D Action: draft-irtf-icnrg-icn-lte-4g-04.txt
     (Anil Jangam (anjangam))
  4. Re: New Version Notification for
     draft-irtf-icnrg-terminology-05.txt (B?rje Ohlman)
From: Matthias Waehlisch <m.waehlisch@fu-berlin.de>
Subject: [icnrg] ACM ICN: Early bird registration extended
Date: 10 September 2019 at 00:10:43 BST
To: ICNRG <icnrg@irtf.org>
Message-Id: <alpine.WNT.2.00.1909091600200.16312@mw-x1>



**
Due to multiple requests the deadline of early registration has been
extended to September 13, 2019. Check
https://conferences.sigcomm.org/acm-icn/2019/registration.php
**

Futher updates include details about the keynote, panels, and sessions.


              CALL FOR PARTICIPATION

ACM Conference on Information-Centric Networking 2019
 Macau, SAR China, September 24-26, 2019
 https://conferences.sigcomm.org/acm-icn/2019/


The organizing committee is delighted to invite you to the 6th ACM
conference on Information-Centric Networking (ICN), to be held in Macao,
SAR China from September 24-26, 2019.  ACM ICN 2019 is focusing on
significant research contributions to ICN as broadly defined, and
featuring paper presentations, posters, and demonstrations.

**Change of Venue**

In contrast to previous announcements, ICN '19 is moved to Macau
University in Macau due to the continuing concerns regarding events in
Hong Kong.

**Keynote**

The keynote will be given by Dave Clark: "ICNs, Internets, and the
future of Networking".

**Program**

15 papers presented in single-track sessions:

Session: Applications

* Secure Scuttlebutt: An Information-Centric Protocol for Subjective and Decentralised Community Applications
* InterServer Game State Synchronisation using Named Data Networking
* Decentralised and Secure Multimedia Sharing Application over Named Data Networking

Session: Architectures and Infrastructure (1h 30m)

* Enabling ICN in the Internet Protocol: Analysis and Evaluation of the Hybrid-ICN Architecture
* Compute First Networking: Distributed Computing meets ICN
* Towards Peer-to-Peer Content Retrieval Markets: Enhancing IPFS with ICN

Session: Name Spaces

* NDN-CNL: A Hierarchical Namespace API for Named Data Networking
* The Missing Piece: On Namespace Management in NDN and How DNSSEC Might Help
* Space Analysis: Verification of Named Data Network Data Planes

Session: Caching

* On the power of in-network caching in the Hadoop Distributed File System
* Easy as ABC: A Lightweight Centrality-Based Caching Strategy for Information-Centric IoT

Session: Protocol enhancements

* Learned Building a Secure, Network Measurement Framework using Basic NDN
* NDN-ABS: Attribute-Based Signature Scheme for Named Data Networking
* Mesh under the Microscope: How much ICN is Inside?
* More for Less: The Surprising Benefits of QoS Management in Constrained NDN Networks


2 panels: "Industry Applications of ICN" Panel about "The Values of
Decentralization".

12 posters and demos about emerging topics.

4 half-day tutorials on
 * Service-based Routing at the Edge
 * TouchNDN: Visual Programming of Data-centric Video
 * Building IoT Systems over Named Data Networking
 * The InterPlanetary File System (IPFS)

Note that participating in the tutorials is covered by the conference
fees.

More details: https://conferences.sigcomm.org/acm-icn/2019/program.php

** Registration**

https://conferences.sigcomm.org/acm-icn/2019/registration.php

**Side Events*

Travel once and enjoy multiple events in addition to ACM ICN:

 * September 23: Hands-on workshop that explores how Future Internet
 will impact dynamic media artworks and multimedia systems. Creating
 Distributed Media Experiences with TouchDesigner and NDN.

 * September 27: Interim meeting of the IRTF ICN Research Group.




From: internet-drafts@ietf.org
Subject: [icnrg] I-D Action: draft-irtf-icnrg-icn-lte-4g-04.txt
Date: 10 September 2019 at 06:38:47 BST
To: <i-d-announce@ietf.org>
Cc: icnrg@irtf.org
Reply-To: icnrg@irtf.org
Message-Id: <156809392721.9121.5183022179218242281@ietfa.amsl.com>



A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Information-Centric Networking RG of the IRTF.

       Title           : Native Deployment of ICN in LTE, 4G Mobile Networks
       Authors         : Prakash Suthar
                         Milan Stolic
                         Anil Jangam
                         Dirk Trossen
                         Ravishankar Ravindran
Filename        : draft-irtf-icnrg-icn-lte-4g-04.txt
Pages           : 37
Date            : 2019-09-09

Abstract:
  LTE, 4G mobile networks use IP based transport for control plane to
  establish the data session and user plane for actual data delivery.
  In existing architecture, IP transport used in user plane is not
  optimized for data transport, which leads to an inefficient data
  delivery.  IP unicast routing from server to clients is used for
  delivery of multimedia content to User Equipment (UE), where each
  user gets a separate stream.  From bandwidth and routing perspective
  this approach is inefficient.  Multicast and broadcast technologies
  have emerged recently for mobile networks, but their deployments are
  very limited or at an experimental stage due to complex architecture
  and radio spectrum issues.  ICN is a rapidly emerging technology with
  built-in features for efficient multimedia data delivery, however
  majority of the work is focused on fixed networks.  The main focus of
  this draft is on native deployment of ICN in cellular mobile networks
  by using ICN in 3GPP protocol stack.  ICN has an inherent capability
  for multicast, anchorless mobility, security and it is optimized for
  data delivery using local caching at the edge.  The proposed
  approaches in this draft allow ICN to be enabled natively over the
  current LTE stack comprising of PDCP/RLC/MAC/PHY or in a dual stack
  mode (along with IP) help optimize the mobile networks by leveraging
  the inherent benefits of ICN.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-irtf-icnrg-icn-lte-4g/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-irtf-icnrg-icn-lte-4g-04
https://datatracker.ietf.org/doc/html/draft-irtf-icnrg-icn-lte-4g-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-irtf-icnrg-icn-lte-4g-04


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/




From: "Anil Jangam (anjangam)" <anjangam@cisco.com>
Subject: Re: [icnrg] I-D Action: draft-irtf-icnrg-icn-lte-4g-04.txt
Date: 10 September 2019 at 07:00:26 BST
To: "icnrg@irtf.org" <icnrg@irtf.org>
Cc: Akbar Rahman <Akbar.Rahman@InterDigital.com>, Luca Muscariello <muscariello@ieee.org>
Message-Id: <51EB19AE-F455-4AF6-AA1B-7598A2444609@cisco.com>


Dear Friends,

We have uploaded an update to our draft incorporating all the feedback we received so far.
Specifically, we worked offline with reviewers (CC'ed), discussed their feedback and incorporated it.

We are looking forward to further comments, if any.
We also request chairs to guide us further on progression of this draft.

Thank you,
/anil.



   A New Internet-Draft is available from the on-line Internet-Drafts directories.
   This draft is a work item of the Information-Centric Networking RG of the IRTF.

           Title           : Native Deployment of ICN in LTE, 4G Mobile Networks
           Authors         : Prakash Suthar
                             Milan Stolic
                             Anil Jangam
                             Dirk Trossen
                             Ravishankar Ravindran
    Filename        : draft-irtf-icnrg-icn-lte-4g-04.txt
    Pages           : 37
    Date            : 2019-09-09

   Abstract:
      LTE, 4G mobile networks use IP based transport for control plane to
      establish the data session and user plane for actual data delivery.
      In existing architecture, IP transport used in user plane is not
      optimized for data transport, which leads to an inefficient data
      delivery.  IP unicast routing from server to clients is used for
      delivery of multimedia content to User Equipment (UE), where each
      user gets a separate stream.  From bandwidth and routing perspective
      this approach is inefficient.  Multicast and broadcast technologies
      have emerged recently for mobile networks, but their deployments are
      very limited or at an experimental stage due to complex architecture
      and radio spectrum issues.  ICN is a rapidly emerging technology with
      built-in features for efficient multimedia data delivery, however
      majority of the work is focused on fixed networks.  The main focus of
      this draft is on native deployment of ICN in cellular mobile networks
      by using ICN in 3GPP protocol stack.  ICN has an inherent capability
      for multicast, anchorless mobility, security and it is optimized for
      data delivery using local caching at the edge.  The proposed
      approaches in this draft allow ICN to be enabled natively over the
      current LTE stack comprising of PDCP/RLC/MAC/PHY or in a dual stack
      mode (along with IP) help optimize the mobile networks by leveraging
      the inherent benefits of ICN.


   The IETF datatracker status page for this draft is:
   https://datatracker.ietf.org/doc/draft-irtf-icnrg-icn-lte-4g/

   There are also htmlized versions available at:
   https://tools.ietf.org/html/draft-irtf-icnrg-icn-lte-4g-04
   https://datatracker.ietf.org/doc/html/draft-irtf-icnrg-icn-lte-4g-04

   A diff from the previous version is available at:
   https://www.ietf.org/rfcdiff?url2=draft-irtf-icnrg-icn-lte-4g-04


   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.

   Internet-Drafts are also available by anonymous FTP at:
   ftp://ftp.ietf.org/internet-drafts/

   _______________________________________________
   icnrg mailing list
   icnrg@irtf.org
   https://www.irtf.org/mailman/listinfo/icnrg




From: Börje Ohlman <Borje.Ohlman@abc.se>
Subject: Re: [icnrg] New Version Notification for draft-irtf-icnrg-terminology-05.txt
Date: 10 September 2019 at 12:37:55 BST
To: icnrg <icnrg@irtf.org>
Cc: Colin Perkins <csp@csperkins.org>, draft-irtf-icnrg-terminology@ietf.org, David R Oran <daveoran@orandom.net>
Message-Id: <B6AC6E68-DD20-459C-A816-3ECC54F959A6@abc.se>

If you have any comments or objections to this please send them to the list by the end of this week.
If there are non I will ask Colin to put this to a final IRTF poll in the beginning of next week.

Börje


On 7 Sep 2019, at 14:25, David R. Oran <daveoran@orandom.net<mailto:daveoran@orandom.net>> wrote:

This posting is a revision of the ICN Terminology draft with changes resulting from the IRSG review. Attached please find the comments by Marie-Jose Montpetit (the IRSG Reviewer) and responses noting the associated changes.
In addition to the specific comment responses, a bit of text was added to improve the document in preparation for final IRTF poll. These are:
·         expanded text to fill our two use cases that had eclipses rather than actual fleshed out information.
·         an acknowledgements section was added
Please check this over to ensure the support indicated ion the RG last call still stands. Börje is acting as Shepherd so this is now in his hands to assess readiness for final IRTF Poll.
Thanks again to the IRSG, particularly Marie-Jose, for the review, and to the ICNRG for its support of this work.
DaveO.
On 7 Sep 2019, at 8:17, internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> wrote:
A new version of I-D, draft-irtf-icnrg-terminology-05.txt
has been successfully submitted by David Oran and posted to the
IETF repository.
Name: draft-irtf-icnrg-terminology
Revision: 05
Title: Information-Centric Networking (ICN): CCNx and NDN Terminology
Document date: 2019-09-07
Group: icnrg
Pages: 18
URL:  https://www.ietf.org/internet-drafts/draft-irtf-icnrg-terminology-05.txt
Status:  https://datatracker.ietf.org/doc/draft-irtf-icnrg-terminology/
Htmlized:  https://tools.ietf.org/html/draft-irtf-icnrg-terminology-05
Htmlized:  https://datatracker.ietf.org/doc/html/draft-irtf-icnrg-terminology
Diff:  https://www.ietf.org/rfcdiff?url2=draft-irtf-icnrg-terminology-05
Abstract:
Information Centric Networking (ICN) is a novel paradigm where
network communications are accomplished by requesting named content,
instead of sending packets to destination addresses. Named Data
Networking (NDN) and Content-Centric Networking (CCNx) are two
prominent ICN architectures. This document provides an overview of
the terminology and definitions that have been used in describing
concepts in these two implementations of ICN. While there are other
ICN architectures, they are not part of the NDN and CCNx concepts and
as such are out of scope for this document. This document is a
product of the Information-Centric Networking Research Group (ICNRG).
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
DaveO
<Marie-Jose Monpetit review with responses.txt>_______________________________________________
icnrg mailing list
icnrg@irtf.org<mailto:icnrg@irtf.org>
https://www.irtf.org/mailman/listinfo/icnrg



_______________________________________________
icnrg mailing list
icnrg@irtf.org
https://www.irtf.org/mailman/listinfo/icnrg