[icnrg] FW: New Version Notification for draft-rahman-icnrg-deployment-guidelines-03.txt

"Rahman, Akbar" <Akbar.Rahman@InterDigital.com> Mon, 14 August 2017 19:03 UTC

Return-Path: <Akbar.Rahman@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 323D2132399 for <icnrg@ietfa.amsl.com>; Mon, 14 Aug 2017 12:03:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.108
X-Spam-Level:
X-Spam-Status: No, score=-1.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=no 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 i0_TbNU0gwZV for <icnrg@ietfa.amsl.com>; Mon, 14 Aug 2017 12:03:39 -0700 (PDT)
Received: from smtp-in1.interdigital.com (unknown [68.168.94.174]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81C44132409 for <icnrg@irtf.org>; Mon, 14 Aug 2017 12:03:38 -0700 (PDT)
X-ASG-Debug-ID: 1502737416-06daaa462d23d8f0001-Tk25uo
Received: from NALENITE.InterDigital.com (nalenite.interdigital.com [10.2.64.253]) by smtp-in1.interdigital.com with ESMTP id szbbEI0AHZckJpw4 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 Aug 2017 15:03:36 -0400 (EDT)
X-Barracuda-Envelope-From: Akbar.Rahman@InterDigital.com
Received: from NABESITE.InterDigital.com ([fe80::4d8a:a889:67c2:f009]) by NALENITE.InterDigital.com ([::1]) with mapi id 14.03.0361.001; Mon, 14 Aug 2017 15:03:35 -0400
From: "Rahman, Akbar" <Akbar.Rahman@InterDigital.com>
To: David Oran <daveoran@orandom.net>, Börje Ohlman <borje.ohlman@ericsson.com>, "Prakash Suthar (psuthar)" <psuthar@cisco.com>
CC: icnrg <icnrg@irtf.org>
Thread-Topic: New Version Notification for draft-rahman-icnrg-deployment-guidelines-03.txt
X-ASG-Orig-Subj: FW: New Version Notification for draft-rahman-icnrg-deployment-guidelines-03.txt
Thread-Index: AQHTFS5D45FPz5/QUEmiXk/xAO6klaKEMxUA
Date: Mon, 14 Aug 2017 19:03:35 +0000
Message-ID: <36F5869FE31AB24485E5E3222C288E1F973ED42F@NABESITE.InterDigital.com>
References: <150273665232.457.2535162097636301486.idtracker@ietfa.amsl.com>
In-Reply-To: <150273665232.457.2535162097636301486.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.3.2.144]
x-exclaimer-md-config: bb79a19d-f711-475c-a0f9-4d93b71c94dd
Content-Type: multipart/related; boundary="_003_36F5869FE31AB24485E5E3222C288E1F973ED42FNABESITEInterDi_"; type="text/plain"
MIME-Version: 1.0
X-Barracuda-Connect: nalenite.interdigital.com[10.2.64.253]
X-Barracuda-Start-Time: 1502737416
X-Barracuda-Encrypted: ECDHE-RSA-AES256-SHA
X-Barracuda-URL: https://10.1.245.3:443/cgi-mod/mark.cgi
X-Barracuda-Scan-Msg-Size: 4765
X-Virus-Scanned: by bsmtpd at interdigital.com
X-Barracuda-BRTS-Status: 1
X-Barracuda-Spam-Score: 0.50
X-Barracuda-Spam-Status: No, SCORE=0.50 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests=BSF_RULE7568M, EXTRA_MPART_TYPE
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.41943 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.00 EXTRA_MPART_TYPE Header has extraneous Content-type:...type= entry 0.50 BSF_RULE7568M Custom Rule 7568M
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/OuGIO8uEK53BSKfKqotgYW1iw6g>
Subject: [icnrg] FW: New Version Notification for draft-rahman-icnrg-deployment-guidelines-03.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, 14 Aug 2017 19:03:41 -0000

Hi Chairs,

https://tools.ietf.org/html/draft-rahman-icnrg-deployment-guidelines-03

We decided to do a quick update of our draft to address the meeting comments from Prague.

Prakahsh and Haru (?) - Please use this version for your review comments.


Below is a short summary of the updates:
-------------------------------------------------------
1.      Added reference to dual mode devices in section 4.1 (Application and Service Migration) and referenced Prakash’s “Native ICN for LTE” as an example.
2.      Added a summary section of deployment trial experiences in new section 5.3 to draw conclusions from our analysis of the various deployments.
       •       This addresses Eve Schooler’s question of “whether ICN technology is ready for prime time deployment?”
3.      Scrubbed section 6 “further standardization” and added some more items (i.e. OAM, SFC impacts) to summary of protocol gaps Table 1 and corresponding text.
4.      Added references to ICN over Low Power WLAN experiments from Thomas Schmidt, and added new section 5.2.4. (NDN IoT Trials)
5.      Various editorial updates including:
       •       Adding reference to ICNRG Charter in Intro
       •       Clarified the differences in the island approach between “ICN-as-an-Overlay” and “ICN-as-an-Underlay” (i.e. former connected by ICN/IP tunnels, and later going through gateways)
6.      Note: We think points 1 and 4 above together address Lixia’s comment on explicitly addressing “native ICN directly on top of wireless”.

-------------------------------------------------------


Best Regards,

Akbar





[cid:image319c60.PNG@20914401.4db2dff6]
[cid:image685d0f.PNG@0ca6e63c.4cac4f2e]<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: Monday, August 14, 2017 2:51 PM
To: Ravi Ravindran <ravi.ravindran@huawei.com>; Trossen, Dirk <Dirk.Trossen@InterDigital.com>; Dirk Kutscher <ietf@dkutscher.net>; Ravi Ravindrna <ravi.ravindran@huawei.com>; Rahman, Akbar <Akbar.Rahman@InterDigital.com>; Trossen, Dirk <Dirk.Trossen@InterDigital.com>
Subject: New Version Notification for draft-rahman-icnrg-deployment-guidelines-03.txt


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

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

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.  First, the major
  deployment configurations for ICN are 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