[icnrg] New Version Notification for draft-zhang-icnrg-icniot-requirements-01.txt
Ravi Ravindran <ravi.ravindran@huawei.com> Sat, 23 April 2016 00:05 UTC
Return-Path: <ravi.ravindran@huawei.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 E30D812DA2F for <icnrg@ietfa.amsl.com>; Fri, 22 Apr 2016 17:05:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.217
X-Spam-Level:
X-Spam-Status: No, score=-5.217 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 4EXUKLlKwByD for <icnrg@ietfa.amsl.com>; Fri, 22 Apr 2016 17:05:12 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61B4912DBDE for <icnrg@irtf.org>; Fri, 22 Apr 2016 17:05:12 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml702-cah.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BPK26653; Fri, 22 Apr 2016 19:05:11 -0500 (CDT)
Received: from SJCEML703-CHM.china.huawei.com (10.218.25.36) by dfweml702-cah.china.huawei.com (10.193.5.176) with Microsoft SMTP Server (TLS) id 14.3.235.1; Fri, 22 Apr 2016 17:05:10 -0700
Received: from SJCEML701-CHM.china.huawei.com ([169.254.3.126]) by SJCEML703-CHM.china.huawei.com ([169.254.5.228]) with mapi id 14.03.0235.001; Fri, 22 Apr 2016 17:05:08 -0700
From: Ravi Ravindran <ravi.ravindran@huawei.com>
To: "icnrg@irtf.org" <icnrg@irtf.org>
Thread-Topic: New Version Notification for draft-zhang-icnrg-icniot-requirements-01.txt
Thread-Index: AQHRnPPKY9LJg/3Xpk+/dF+5+2U79g==
Date: Sat, 23 Apr 2016 00:05:05 +0000
Message-ID: <D96E28F4A22C864DBC6C871B5B1C4CC320BF72F9@SJCEML701-CHM.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.212.246.115]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/icnrg/t7ymu2Y96voA-6qS2kXzhoXw1Fk>
Subject: [icnrg] New Version Notification for draft-zhang-icnrg-icniot-requirements-01.txt
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.17
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: Sat, 23 Apr 2016 00:05:15 -0000
Dear All, Based on the comments from the mailing list we have updated the ICN-IoT requirements draft. Following are the updates to the draft: 1. Sections 2.10&5.6 have been updated based on Yuansong's contributions and references. 2. Sections 3.2&2.9 have been updated to address Akbar's comments. 3. A new Section 2.13 on IoT platform management challenge has been added, and Sections 2.3,5.7&6.3 have been updated to address Thomas's comments. 4. Sections 2.5&6.4 have been updated to address Bastiaan's comments. More comments are welcome for improving this contribution. Regards, Ravi -----Original Message----- From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] Sent: Friday, April 22, 2016 4:59 PM To: Dipankar Raychadhuri; Yanyong Zhang; Emmanuel Baccelli; Jeff Burke; Ravi Ravindran; GQ Wang; Olov Schelen; Bengt Ahlgren; Luigi Alfredo Grieco Subject: New Version Notification for draft-zhang-icnrg-icniot-requirements-01.txt A new version of I-D, draft-zhang-icnrg-icniot-requirements-01.txt has been successfully submitted by Ravishankar Ravindran and posted to the IETF repository. Name: draft-zhang-icnrg-icniot-requirements Revision: 01 Title: Requirements and Challenges for IoT over ICN Document date: 2016-04-22 Group: Individual Submission Pages: 39 URL: https://www.ietf.org/internet-drafts/draft-zhang-icnrg-icniot-requirements-01.txt Status: https://datatracker.ietf.org/doc/draft-zhang-icnrg-icniot-requirements/ Htmlized: https://tools.ietf.org/html/draft-zhang-icnrg-icniot-requirements-01 Diff: https://www.ietf.org/rfcdiff?url2=draft-zhang-icnrg-icniot-requirements-01 Abstract: The Internet of Things (IoT) promises to connect billions of objects to the Internet. After deploying many stand-alone IoT systems in different domains, the current trend is to develop a common, "thin waist" of protocols forming a horizontal unified, defragmented IoT platform. Such a platform will make objects accessible to applications across organizations and domains. Towards this goal, quite a few proposals have been made to build a unified host-centric IoT platform as an overlay on top of today's host-centric Internet. However, there is a fundamental mismatch between the host-centric nature of todays Internet and the information-centric nature of the IoT system. To address this mismatch, we propose to build a common set of protocols and services, which form an IoT platform, based on the Information Centric Network (ICN) architecture, which we call ICN-IoT. ICN-IoT leverages the salient features of ICN, and thus provides seamless mobility support, security, scalability, and efficient content and service delivery. This draft describes representative IoT requirements and ICN challenges to realize a unified ICN-IoT framework. Towards this, we first identify a list of important requirements which a unified IoT architecture should have to support tens of billions of objects, then we discuss how the current IP-IoT overlay fails to meet these requirements, followed by discussion on suitability of ICN for IoT. Though we see most of the IoT requirements can be met by ICN, we discuss specific challenges ICN has to address to satisfy them. Then we provide discussion of popular IoT scenarios including the "smart" home, campus, grid, transportation infrastructure, healthcare, Education, and Entertainment for completeness, as specific scenarios requires appropriate design choices and architectural considerations towards developing an ICN-IoT solution. 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] New Version Notification for draft-zhang-… Ravi Ravindran
- Re: [icnrg] New Version Notification for draft-zh… Dirk Kutscher
- Re: [icnrg] New Version Notification for draft-zh… Rahman, Akbar
- Re: [icnrg] New Version Notification for draft-zh… Dirk Kutscher
- Re: [icnrg] New Version Notification for draft-zh… Jagodits, Thomas
- Re: [icnrg] New Version Notification for draft-zh… Ravi Ravindran