[icnrg] Draft on ICNRG Deployment Configurations
"Rahman, Akbar" <Akbar.Rahman@InterDigital.com> Sun, 12 March 2017 02:57 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 BD6B01294CC for <icnrg@ietfa.amsl.com>; Sat, 11 Mar 2017 18:57:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.107
X-Spam-Level:
X-Spam-Status: No, score=-1.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793] 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 uFdr1o71JUNZ for <icnrg@ietfa.amsl.com>; Sat, 11 Mar 2017 18:57:41 -0800 (PST)
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 43CFE129443 for <icnrg@irtf.org>; Sat, 11 Mar 2017 18:57:41 -0800 (PST)
X-ASG-Debug-ID: 1489287459-06daaa37b9000b0001-Tk25uo
Received: from NALENITE.InterDigital.com (nalenite.interdigital.com [10.2.64.253]) by smtp-in1.interdigital.com with ESMTP id uYwCW7UAaH3Rss8s (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO) for <icnrg@irtf.org>; Sat, 11 Mar 2017 21:57:39 -0500 (EST)
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.0319.002; Sat, 11 Mar 2017 21:57:38 -0500
From: "Rahman, Akbar" <Akbar.Rahman@InterDigital.com>
To: "icnrg@irtf.org" <icnrg@irtf.org>
Thread-Topic: Draft on ICNRG Deployment Configurations
X-ASG-Orig-Subj: Draft on ICNRG Deployment Configurations
Thread-Index: AdKa2/aGL5aTrSGLQP6C+gol0ZObBg==
Date: Sun, 12 Mar 2017 02:57:37 +0000
Message-ID: <36F5869FE31AB24485E5E3222C288E1F6DCE2E36@NABESITE.InterDigital.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.3.247.39]
x-exclaimer-md-config: bb79a19d-f711-475c-a0f9-4d93b71c94dd
Content-Type: multipart/related; boundary="_003_36F5869FE31AB24485E5E3222C288E1F6DCE2E36NABESITEInterDi_"; type="text/plain"
MIME-Version: 1.0
X-Barracuda-Connect: nalenite.interdigital.com[10.2.64.253]
X-Barracuda-Start-Time: 1489287459
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: 3021
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.37157 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/SPs6viSPZ6MR5sl1mtUcaTOqk8w>
Subject: [icnrg] Draft on ICNRG Deployment Configurations
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: Sun, 12 Mar 2017 02:57:43 -0000
Hi All, Here is our draft on ICNRG Deployment Configurations. We look forward to any comments that you may have on the Email list or in Chicago at the F2F meeting. Also we are specifically soliciting input for any relevant ICN trial experience summary for Section 5 of this document. Best Regards, Akbar [cid:image52b0f5.PNG@82efb6c4.43ac565a] [cid:image3c14d1.PNG@b7f2fe6c.439be5f8]<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: Saturday, March 11, 2017 9:40 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-00.txt A new version of I-D, draft-rahman-icnrg-deployment-guidelines-00.txt has been successfully submitted by Akbar Rahman and posted to the IETF repository. Name: draft-rahman-icnrg-deployment-guidelines Revision: 00 Title: Deployment Configurations for Information-Centric Networks (ICN) Document date: 2017-03-11 Group: Individual Submission Pages: 17 URL: https://www.ietf.org/internet-drafts/draft-rahman-icnrg-deployment-guidelines-00.txt Status: https://datatracker.ietf.org/doc/draft-rahman-icnrg-deployment-guidelines/ Htmlized: https://tools.ietf.org/html/draft-rahman-icnrg-deployment-guidelines-00 Abstract: This document provides technical deployment guidelines for the ICN community. First, the possible deployment configurations for ICN are described including overlay and underlay approaches. Then proposed deployment migration paths for these configurations are outlined to address the major issues facing ICN such as application migration, and core and edge network migration. Next, selected ICN trial experiences are summarized. Finally, recommendations are given for protocol areas that require further standardization to facilitate future ICN interoperable 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
- [icnrg] Draft on ICNRG Deployment Configurations Rahman, Akbar