Re: [icnrg] Next steps on the 4G/LTE Draft

"Trossen, Dirk" <Dirk.Trossen@InterDigital.com> Thu, 15 November 2018 15:48 UTC

Return-Path: <Dirk.Trossen@InterDigital.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 296F4130E08 for <icnrg@ietfa.amsl.com>; Thu, 15 Nov 2018 07:48:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=interdigital.onmicrosoft.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 oLygXh8n9c47 for <icnrg@ietfa.amsl.com>; Thu, 15 Nov 2018 07:48:50 -0800 (PST)
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (mail-eopbgr780105.outbound.protection.outlook.com [40.107.78.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7155E130E4A for <icnrg@irtf.org>; Thu, 15 Nov 2018 07:48:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=interdigital.onmicrosoft.com; s=selector1-interdigital-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=HRYJTDfVo3NdkcATEafC1FSDgT6jljxZlNx91eKQbBE=; b=qKvJWzwIx5vwuSHOVnE1dgOjsD0pp+Ht7YHzaTC753h6Iq3yrpl6PRJk7pktCJVECitUQuwNdZqy801TvPSP2buiW95bw2NPifcdGFV9Xc/7ocpJnh5p87gkGTvJJgMDc4CGPU6/SDew3fj4olvgHdLRcX7LPt0/aGkRVsrRUa0=
Received: from DM6PR10MB2777.namprd10.prod.outlook.com (20.177.216.82) by DM6PR10MB3435.namprd10.prod.outlook.com (20.177.220.88) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1294.28; Thu, 15 Nov 2018 15:48:47 +0000
Received: from DM6PR10MB2777.namprd10.prod.outlook.com ([fe80::d94f:ef2d:451c:4e62]) by DM6PR10MB2777.namprd10.prod.outlook.com ([fe80::d94f:ef2d:451c:4e62%4]) with mapi id 15.20.1294.045; Thu, 15 Nov 2018 15:48:47 +0000
From: "Trossen, Dirk" <Dirk.Trossen@InterDigital.com>
To: Luca Muscariello <luca.muscariello@gmail.com>, "Oran, Dave" <daveoran@orandom.net>
CC: icnrg <icnrg@irtf.org>
Thread-Topic: [icnrg] Next steps on the 4G/LTE Draft
Thread-Index: AQHUdmbLmnm3xNx96USiQLMe8dCJjKVEBjKAgAz9+QA=
Date: Thu, 15 Nov 2018 15:48:47 +0000
Message-ID: <DM6PR10MB277769EDF2B31A9B4E483683F3DC0@DM6PR10MB2777.namprd10.prod.outlook.com>
References: <840FA4F4-2A4F-4DC7-AEE8-8EB3C11396B9@orandom.net> <CAHx=1M74vBMb8jtD+xA6bqCgOXY32cqgNisW95n9850igf5XEA@mail.gmail.com>
In-Reply-To: <CAHx=1M74vBMb8jtD+xA6bqCgOXY32cqgNisW95n9850igf5XEA@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Dirk.Trossen@InterDigital.com;
x-originating-ip: [212.76.252.194]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM6PR10MB3435; 6:41AM5+FZVuuTr+h+ErxyqK6+NNFWC1mg1KZTnVrJHnR7e9/8SCrjG+xkLRDpSPeXBvcmLTypRLIWYb7GYgUDF42d306ZRXNEodfHOCiDiJBiF+zwPXKoeV//PXXKYHRxgsFeSH1VxFnyas/dpYzsBNYBNe4/sS7ykV4cVLwjy8MPs2VwI/QGBd8ScrLfiIMbN/H3XB64LO0H28LbS8/ctIsmew0frZl+p5LhphrydVLejyB2oz8jTkO7eFBajPDRaIMC+xCgIdg4liefCdJ1Mk8zGr/YwwXokfSvN66056yKx6dq8joEh7/fXWAelFd7tMi2qsdRXMHKnFefPd9Hkq1dwS4Bs3JkSdrH7QJVVUnYX0k/Di9LOkPRBUsWXubACtEs5LsHKzMWQnbiZ8BJ3lb1s4kOgU5q4ZAGFBw1eyxB9qy36/8SfCm/dCCjRD7gioZmHHnGmZ/dZZ/MpEr8Gw==; 5:kl5SFl7GWpThFNRP/cTFbjhcYa1uStMHeq3QIIz8xboWG+gLX6BMjFwDY0W4dRJbpQUzsecJ2H3mRQ2ppfb1kIcHkJC3fExZXK3xBUVCWgJoFDxlj2tWvDabe4HDdzmPOocS21kIoPG7bF6Sbg+zgE4yo3ENhlEjaPz05hRPtMA=; 7:IYVWWxJ53ccxZkIgBSSGj6FNRnYoc2oJ+sGIdMJ41ymEu3homZtdJuZiOASTo8KKVz6OmfjFkXuCGBw8qMuGiySbPIorIUuTnkmgMPPk9EM78wBUvz0QZYQCOTIpRaJh+uv0GipRUlmZjHzMRO8sFA==
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 79250417-478e-4a8c-f0af-08d64b11d49e
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390098)(7020095)(4652040)(8989299)(5600074)(711020)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(7193020); SRVR:DM6PR10MB3435;
x-ms-traffictypediagnostic: DM6PR10MB3435:
x-ld-processed: e351b779-f6d5-4e50-8568-80e922d180ae,ExtAddr
x-microsoft-antispam-prvs: <DM6PR10MB3435C7B658CEC1E2CAE7477EF3DC0@DM6PR10MB3435.namprd10.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(192374486261705)(21748063052155)(28532068793085)(190501279198761)(227612066756510)(120809045254105);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(10201501046)(3002001)(93006095)(93001095)(3231415)(944501410)(52105112)(148016)(149066)(150057)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123562045)(20161123564045)(20161123560045)(201708071742011)(7699051)(76991095); SRVR:DM6PR10MB3435; BCL:0; PCL:0; RULEID:; SRVR:DM6PR10MB3435;
x-forefront-prvs: 08572BD77F
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(39850400004)(396003)(346002)(136003)(366004)(199004)(189003)(81166006)(105586002)(66574009)(2900100001)(66066001)(11346002)(446003)(6246003)(106356001)(2906002)(81156014)(606006)(86362001)(97736004)(8676002)(790700001)(14454004)(71200400001)(71190400001)(3846002)(256004)(14444005)(6116002)(68736007)(6436002)(236005)(54896002)(6306002)(9686003)(26005)(186003)(72206003)(74316002)(8936002)(53546011)(7696005)(9326002)(102836004)(6506007)(316002)(39060400002)(478600001)(5660300001)(53936002)(99286004)(7736002)(4326008)(486006)(33656002)(476003)(25786009)(229853002)(966005)(55016002)(76176011)(110136005)(85282002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM6PR10MB3435; H:DM6PR10MB2777.namprd10.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: InterDigital.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: r/uhtzNTq0cr1us4VawB0lcYzkP4laSoRRRDuY2myxu+psHXaIQtxq7eE+iwuiohUKHM2HSlUy6xBkKsB6NpVuHASs2v8mgXzyZN6A8iEFURdbndn1tHJTtUmZXEEixXOvlrB8RKwh/MYt1QGxcUh2dVBV2rW6Fgp5Q/+MDw1IpjrG+CgudgMaFszYNukBgHqogO8bGZBn2hWXKWojqSYdWkt62USKLxq2gl0jH8AusokkhkWbpP+c4UNOIAoi6yXoqEPvFm04PMy80grm7P+JmkpQv+wAeg93wq2zQHW3qBHHcRIOjtBiEyv8MQOGzLzeZZ7fjNz82jlKJwQlAYZA+kkp7f/sCDNLBDRgBYq/w=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DM6PR10MB277769EDF2B31A9B4E483683F3DC0DM6PR10MB2777namp_"
MIME-Version: 1.0
X-OriginatorOrg: interdigital.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 79250417-478e-4a8c-f0af-08d64b11d49e
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Nov 2018 15:48:47.1866 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: e351b779-f6d5-4e50-8568-80e922d180ae
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR10MB3435
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/3D-joGj1-GEEz9Snj8Ag8lx1fkc>
Subject: Re: [icnrg] Next steps on the 4G/LTE Draft
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: Thu, 15 Nov 2018 15:49:01 -0000

Hi Luca,

The abstract provides a number of aspects for wanting to utilize ICN in 4G/LTE networks, such as “ICN has an inherent capability for multicast, anchorless mobility, security and it is optimized for data delivery using local caching at the edge.” – I agree that being brief, given that it’s in the abstract, but similar to what the paper discusses as opportunities. Furthermore, there’s a possible argument to be made that 4G/LTE will be around for some time to come, including being introduced in a number of markets as new deployments even – but should this be part of a technical draft?

I’m a bit confused by the ‘HAS to compare with those solutions’ comment. Do you expect a functional comparison, a reference to the (brief) discussion in Section V on possible deployments, …?

As for the HICN statement, I see your point on a possible misunderstanding (albeit it’s clear to me) – would you have a proposed improved formulation that avoids any such misunderstanding?

What is not clear to me though if your comment is meant as an opposition to the validity of the solution described in the draft and its adoption specifically?

Best,

Dirk

From: icnrg [mailto:icnrg-bounces@irtf.org] On Behalf Of Luca Muscariello
Sent: 07 November 2018 09:09
To: Oran, Dave <daveoran@orandom.net>
Cc: icnrg <icnrg@irtf.org>
Subject: Re: [icnrg] Next steps on the 4G/LTE Draft

Hi,

A few comments to the document:


The motivation of this document seems weak. E.g. Why should I do all these changes? Worth the pain?
Please find below a paper that may help to motivate that a little bit.

The following paper is also a good citation and the author of this draft should compare
at least with Sec V of it, where several deployment options where proposed including encapsulation in IP and GTP-U extension headers. This draft HAS to compare with those solutions. Beware that those solutions were Alcatel-Lucent IPR and should be Nokia IPR now.
There might be Orange SA IPR as well. If necessary I could check myself.

Until that comparison is not made, I feel this draft SHOULD NOT go through a final call.

G. Carofiglio, M. Gallo, L. Muscariello and D. Perino, "Scalable mobile backhauling via information-centric networking," The 21st IEEE International Workshop on Local and Metropolitan Area Networks, Beijing, 2015, pp. 1-6.


Minor:
This text is either wrong or inaccurate. Or maybe, it is so short that is prone to misguided interpretation.

       An alternative approach to implement ICN over IP is provided in

       Hybrid ICN [HICN], which implements ICN over IP by mapping of ICN

       names to the IPv4/IPv6 addresses.



HTH

Luca

On Wed, Nov 7, 2018 at 7:51 AM David R. Oran <daveoran@orandom.net<mailto:daveoran@orandom.net>> wrote:

At the ICNRG Interim meeting at IETF 103, we got an update status on https://datatracker.ietf..org/doc/draft-irtf-icnrg-icn-lte-4g/<https://datatracker.ietf.org/doc/draft-irtf-icnrg-icn-lte-4g/>

This document is reaching a mature state and the chairs would like to get a sense from the RG participants on two questions:

  1.  Do you think this is ready for an RG last call, and if not, what additions/changes you would like to see to move it forward.

  1.  Do you think the appropriate target for this particular set of work is the “Informational” or “Experimental RFC track. It seems to fall somewhat in a grey area between the two.

Please reply to the list. We would like to have feedback by the end of next week or so (November 17).

Dave, Dirk, & Börje.
_______________________________________________
icnrg mailing list
icnrg@irtf.org<mailto:icnrg@irtf.org>
https://www.irtf.org/mailman/listinfo/icnrg