Re: [icnrg] ICNRG Research Group Last Call on "Deployment Considerations for Information-Centric Networking"

"David R. Oran" <daveoran@orandom.net> Fri, 24 August 2018 16:10 UTC

Return-Path: <daveoran@orandom.net>
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 C52CD130E0E for <icnrg@ietfa.amsl.com>; Fri, 24 Aug 2018 09:10:59 -0700 (PDT)
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, 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 c6V5nX1xHxyt for <icnrg@ietfa.amsl.com>; Fri, 24 Aug 2018 09:10:57 -0700 (PDT)
Received: from spark.crystalorb.net (spark.crystalorb.net [IPv6:2607:fca8:1530::c]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5AF5127333 for <icnrg@irtf.org>; Fri, 24 Aug 2018 09:10:57 -0700 (PDT)
Received: from [10.1.10.52] ([IPv6:2001:470:818c:1:55d3:fba0:45a1:73b8]) (authenticated bits=0) by spark.crystalorb.net (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id w7OG8o82016458 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NO); Fri, 24 Aug 2018 09:08:52 -0700
From: "David R. Oran" <daveoran@orandom.net>
To: "Rahman, Akbar" <Akbar.Rahman@InterDigital.com>
Cc: Adisorn Lertsinsrubtavee <adisorn.lert@gmail.com>, icnrg <icnrg@irtf.org>
Date: Fri, 24 Aug 2018 09:08:50 -0700
X-Mailer: MailMate (1.11.3r5513)
Message-ID: <23C9B371-7264-4B10-BC0D-C488A482A2BF@orandom.net>
In-Reply-To: <BN6PR10MB13291E065889355DECCCFF86E7360@BN6PR10MB1329.namprd10.prod.outlook.com>
References: <681245A1-D173-4D01-BD4F-31EB21E102C9@orandom.net> <EAEA4A49-06E1-4DAB-BC63-4B9A4AE1D2B8@gmail.com> <BN6PR10MB13291E065889355DECCCFF86E7360@BN6PR10MB1329.namprd10.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/7knE6Ew69zfZC_0aWChq8usS1P0>
Subject: Re: [icnrg] ICNRG Research Group Last Call on "Deployment Considerations for Information-Centric Networking"
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.27
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: Fri, 24 Aug 2018 16:11:00 -0000

On 23 Aug 2018, at 22:05, Rahman, Akbar wrote:

> Hi Adisorn,
>
>
> Thanks for the feedback and suggestion.  While it is clear in the 
> draft that the list of deployments in section 5 is not exhaustive, I 
> believe that adding your suggested UMOBILE project activities would be 
> easy to do and beneficial (because of the interesting edge computation 
> and disaster recovery focus).  So I will work with you off line to 
> quickly develop some text to add UMOBILE as another example of an 
> overlay deployment.
>
> Dave – Would it be acceptable to have an update of the draft ready 
> in approximately one week to capture Adisorn’s comments?  Also we 
> got some useful editorial improvement suggestions from Anil Jangam 
> that we could incorporate at the same time.
>
Sure, I’ll just leave the last call open until we have some feedback 
from Adisorn on how you have handled his comments.

Take as long as you need (within reason :-) )

> Best Regards,
>
>
> Akbar
>
> From: icnrg [mailto:icnrg-bounces@irtf.org] On Behalf Of Adisorn 
> Lertsinsrubtavee
> Sent: Thursday, August 23, 2018 7:04 AM
> To: Oran, Dave <daveoran@orandom.net>
> Cc: icnrg <icnrg@irtf.org>
> Subject: Re: [icnrg] ICNRG Research Group Last Call on "Deployment 
> Considerations for Information-Centric Networking"
>
> Dear Chairs of ICNRG and all
>
> I have gone through this document and found that there are some 
> deployments are missing in the draft. Those deployments were related 
> to UMOBILE project’ s activities[1]. The UMOBILE project was funded 
> under the H2020 framework program. The UMOBILE architecture[2] was 
> developed on top of NDN to support edge computation and mobile 
> opportunistic wireless environments. The deployment trail was based on 
> overlay approach. The project has done some couple of ICN deployment 
> trails. One of that was related to the post disaster scenario. In this 
> trail [3], a special DTN face was created to provide reachability to 
> remote area where there is no typical Internet connection. Another 
> trail was the ICN deployment over the Guifi.net<http://Guifi.net> 
> community network. This trial focused on the evaluation of ICN edge 
> computing platform, called PiCasso [4] which is a part of UMOBILE 
> project.  Several single board computers (e.g., raspberry Pi) running 
> PiCasso have been deployed across the urban area of Barcelona to 
> create an ICN overlay network on top of the existing qMp’s routing 
> protocol.
>
> I hope this clarification would help to improve the quality of the 
> document.
>
> Best regards,
> Adisorn Lertsinsrubtavee
> intERLab, Asian Institute of Technology
>
> References
> [1] Universal, mobile-centric and opportunistic communications 
> architecture (UMOBILE), http://www.umobile-project.eu
> [2] C. Sarros et al., "Connecting the Edges: A Universal, 
> Mobile-Centric, and Opportunistic Communications Architecture," in 
> IEEE Communications Magazine, vol. 56, no. 2, pp. 136-143, Feb. 2018. 
> doi: 10.1109/MCOM.2018.1700325
> [3] C. Sarros et al., “ ICN-based edge service deployment in 
> challenged networks”. In Proceedings of the 4th ACM Conference on 
> Information-Centric Networking (ICN '17). ACM, New York, NY, USA, 
> 210-211. DOI: https://doi.org/10.1145/3125719.3132096
> [4] Adisorn Lertsinsrubtavee, Mennan Selimi, Arjuna Sathiaseelan, 
> Llorenç Cerdà-Alabern, Leandro Navarro, and Jon Crowcroft. 2018. 
> Information-Centric Multi-Access Edge Computing Platform for Community 
> Mesh Networks. In Proceedings of the 1st ACM SIGCAS Conference on 
> Computing and Sustainable Societies (COMPASS '18). ACM, New York, NY, 
> USA, Article 19, 12 pages. DOI: 
> https://doi.org/10.1145/3209811.3209867
>
>
>
> On 28 Jul BE 2561, at 02:25, David R. Oran 
> <daveoran@orandom.net<mailto:daveoran@orandom.net>> wrote:
>
> Dear ICNRG,
>
> The Chairs are starting an ICNRG last call on 
> https://datatracker.ietf.org/doc/draft-irtf-icnrg-deployment-guidelines/
>
> This work has gone through three revisions and after discussion at the 
> IETF 102 Montreal ICNRG meeting the participants and authors felt that 
> the work is ready for last call.
>
> Given we are in the summer holiday period, this last call will extend 
> to four weeks rather than the usual two, to give time for people to 
> review and comment. Last Call will close Monday August 28. Please send 
> your comments to the icnrg list as usual.
>
> We hope everyone got home safe and sound from Montreal.
>
> Börje, Dave & Dirk
>
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org<mailto:icnrg@irtf.org>
> https://www.irtf.org/mailman/listinfo/icnrg
>
> [Banner]
> 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.



DaveO