Re: [icnrg] New Version Notification for draft-rahman-icnrg-deployment-guidelines-01.txt

Ravi Ravindran <ravi.ravindran@huawei.com> Mon, 22 May 2017 20:07 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 82449127A91 for <icnrg@ietfa.amsl.com>; Mon, 22 May 2017 13:07:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 mwT9_ZUdun5Q for <icnrg@ietfa.amsl.com>; Mon, 22 May 2017 13:06:59 -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 8EC36126C26 for <icnrg@irtf.org>; Mon, 22 May 2017 13:06:59 -0700 (PDT)
Received: from 172.18.9.243 (EHLO DFWEML703-CAH.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DNK45718; Mon, 22 May 2017 15:06:58 -0500 (CDT)
Received: from SJCEML701-CHM.china.huawei.com (10.208.112.40) by DFWEML703-CAH.china.huawei.com (10.193.5.177) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 22 May 2017 13:06:58 -0700
Received: from SJCEML702-CHM.china.huawei.com ([169.254.4.117]) by SJCEML701-CHM.china.huawei.com ([169.254.3.56]) with mapi id 14.03.0235.001; Mon, 22 May 2017 13:06:55 -0700
From: Ravi Ravindran <ravi.ravindran@huawei.com>
To: "Rahman, Akbar" <Akbar.Rahman@InterDigital.com>, icnrg <icnrg@irtf.org>
Thread-Topic: New Version Notification for draft-rahman-icnrg-deployment-guidelines-01.txt
Thread-Index: AQHSz/WAle0TIFONREmVUK1KVM55kKH6SzqwgAaCCjA=
Date: Mon, 22 May 2017 20:06:54 +0000
Message-ID: <D96E28F4A22C864DBC6C871B5B1C4CC3229A6FE5@SJCEML702-CHM.china.huawei.com>
References: <149512564563.6647.10726567434975285132.idtracker@ietfa.amsl.com> <36F5869FE31AB24485E5E3222C288E1F6DD0D186@NABESITE.InterDigital.com>
In-Reply-To: <36F5869FE31AB24485E5E3222C288E1F6DD0D186@NABESITE.InterDigital.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.213.49.38]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/WU1rtvG5mtlTqI2m2Dd9GpFnaN0>
Subject: Re: [icnrg] New Version Notification for draft-rahman-icnrg-deployment-guidelines-01.txt
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.22
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: Mon, 22 May 2017 20:07:02 -0000

This is the paper Akbar's email is referring to:

" 5G-ICN: Delivering ICN Services over 5G Using Network Slicing", that appeared in this month's IEEE Communication Magazine. The paper takes a service-centric view of ICN. We also discuss deployment models over a LTE framework, but the discussion is also applicable to 5G architecture discussion currently underway in 3GPP SA2 WG, where network function definitions are more generalized.

Regards,
Ravi

-----Original Message-----
From: icnrg [mailto:icnrg-bounces@irtf.org] On Behalf Of Rahman, Akbar
Sent: Thursday, May 18, 2017 9:44 AM
To: icnrg <icnrg@irtf.org>
Subject: [icnrg] FW: New Version Notification for draft-rahman-icnrg-deployment-guidelines-01.txt

Dear Chairs (and RG members),


We have made a major update of the draft to address most of the comments received at the Chicago F2F meeting.  Among the updates are:

1)      Changed the title from "Deployment Configurations ..." to "Deployment Considerations ...", and expanded the Abstract

2)      Updated the Deployment Trial Experiences (section 5)
       * Grouping them clearly as Overlay or Underlay
       * Adding new ICN2020 effort
       * Streamlining the text and making it more consistent

3)      Added reference to 5G-ICN paper that Ravi had suggested (section 3.4), and clarifying that ICN is not creating the 5G slice but simply running inside it

4)      Added reference to the TCP/IP to TCP/ICN paper that Dave Oran had suggested (section 4.1)

5)      Updated the Further Standardization effort (section 6) to clarify that the references to multiple BoFs, did not necessarily imply separate BoFs but that it could also be one consolidated BoF.  Also, clarified that the details of the protocol specification efforts will have to be done in the future by the appropriate WGs and/or BoFs (section 6&7)

6)      Added the Security Considerations (section 9)

7)      Expanded the Conclusions (section 7) to summarize the key considerations (i.e. configurations, migration paths) in addition to identifying the required new IETF standardization effort


Any feedback (from either the Chairs or RG members) would be much appreciated and we will try to address those comments in another update before Prague if required.


Best Regards,


Akbar



[cid:image581399.PNG@4dfc35a4.4bb4c094]
[cid:image0a03d4.PNG@7fe86a75.46aec3b9]<http://ir.interdigital.com/File/Index?KeyFile=37447876>


This e-mail is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and/or otherwise protected from disclosure to anyone other than its intended recipient. Unintended transmission shall not constitute waiver of any privilege or confidentiality obligation. If you received this communication in error, please do not review, copy or distribute it, notify me immediately by email, and delete the original message and any attachments. Unless expressly stated in this e-mail, nothing in this message or any attachment should be construed as a digital or electronic signature.


-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
Sent: Thursday, May 18, 2017 12:41 PM
To: Dirk Kutscher <ietf@dkutscher.net>; Trossen, Dirk <Dirk.Trossen@InterDigital.com>; Rahman, Akbar <Akbar.Rahman@InterDigital.com>; Trossen, Dirk <Dirk.Trossen@InterDigital.com>
Subject: New Version Notification for draft-rahman-icnrg-deployment-guidelines-01.txt


A new version of I-D, draft-rahman-icnrg-deployment-guidelines-01.txt
has been successfully submitted by Akbar Rahman and posted to the IETF repository.

Name:           draft-rahman-icnrg-deployment-guidelines
Revision:       01
Title:          Deployment Considerations for Information-Centric Networking (ICN)
Document date:  2017-05-18
Group:          Individual Submission
Pages:          19
URL:            https://www.ietf.org/internet-drafts/draft-rahman-icnrg-deployment-guidelines-01.txt
Status:         https://datatracker.ietf.org/doc/draft-rahman-icnrg-deployment-guidelines/
Htmlized:       https://tools.ietf.org/html/draft-rahman-icnrg-deployment-guidelines-01
Htmlized:       https://datatracker.ietf.org/doc/html/draft-rahman-icnrg-deployment-guidelines-01
Diff:           https://www.ietf.org/rfcdiff?url2=draft-rahman-icnrg-deployment-guidelines-01

Abstract:
  Information-Centric Networking (ICN) is now reaching technological
  maturity after many years of fundamental research and
  experimentation.  This document provides a number of deployment
  considerations in the interest of helping the ICN community move
  forward to the next step of live deployments.  The major deployment
  configurations for ICN are first described including the main overlay
  and underlay approaches.  Then proposed deployment migration paths
  are outlined to address major practical issues such as network and
  application migration.  Next, selected ICN trial experiences are
  summarized.  Finally, protocol areas that require further
  standardization are identified to facilitate future interoperable ICN
  deployments.




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