[icnrg] comment on draft-kutscher-icnrg-challenges-02

<karagian@cs.utwente.nl> Mon, 03 March 2014 06:47 UTC

Return-Path: <karagian@cs.utwente.nl>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2F371A0CA3 for <icnrg@ietfa.amsl.com>; Sun, 2 Mar 2014 22:47:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 FutF4Znl7Wt6 for <icnrg@ietfa.amsl.com>; Sun, 2 Mar 2014 22:46:59 -0800 (PST)
Received: from out48-ams.mf.surf.net (out48-ams.mf.surf.net [145.0.1.48]) by ietfa.amsl.com (Postfix) with ESMTP id 5E93C1A0C7D for <icnrg@irtf.org>; Sun, 2 Mar 2014 22:46:58 -0800 (PST)
Received: from EXEDGE02.ad.utwente.nl (exedge02.ad.utwente.nl [130.89.5.49]) by outgoing2-ams.mf.surf.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id s236fn8m008451; Mon, 3 Mar 2014 07:46:54 +0100
Received: from EXHUB02.ad.utwente.nl (130.89.4.229) by EXEDGE02.ad.utwente.nl (130.89.5.49) with Microsoft SMTP Server (TLS) id 14.2.328.9; Mon, 3 Mar 2014 07:44:33 +0100
Received: from EXMBX23.ad.utwente.nl ([169.254.3.208]) by EXHUB02.ad.utwente.nl ([130.89.4.229]) with mapi id 14.02.0328.009; Mon, 3 Mar 2014 07:44:33 +0100
From: karagian@cs.utwente.nl
To: Dirk.Kutscher@neclab.eu
Thread-Topic: comment on draft-kutscher-icnrg-challenges-02
Thread-Index: Ac82rAjhE7eB8Z1pSKOLl+RGhWrwTA==
Date: Mon, 03 Mar 2014 06:44:33 +0000
Message-ID: <FF1A9612A94D5C4A81ED7DE1039AB80F4F432F76@EXMBX23.ad.utwente.nl>
References: <20140303005144.8006.9759.idtracker@ietfa.amsl.com>
In-Reply-To: <20140303005144.8006.9759.idtracker@ietfa.amsl.com>
Accept-Language: nl-NL, en-US
Content-Language: nl-NL
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mimectl: Produced By Microsoft Exchange V14.2.247.1
x-originating-ip: [80.229.76.233]
Content-Type: multipart/alternative; boundary="_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F432F76EXMBX23adutwent_"
MIME-Version: 1.0
X-Bayes-Prob: 0.005 (Score 0, tokens from: utwente-out:default, base:default, @@RPTN)
X-CanIt-Geo: ip=130.89.5.49; country=NL; region=15; city=Enschede; latitude=52.2195; longitude=6.8912; http://maps.google.com/maps?q=52.2195,6.8912&z=6
X-CanItPRO-Stream: utwente-out:default (inherits from utwente:default, base:default)
X-Canit-Stats-ID: 0vLwSKSau - 2b7dd665c5c7 - 20140303 (trained as not-spam)
X-Scanned-By: CanIt (www . roaringpenguin . com)
Archived-At: http://mailarchive.ietf.org/arch/msg/icnrg/Ylzqk29gx3wKEV7GQMjM78vGak0
Cc: icnrg@irtf.org
Subject: [icnrg] comment on draft-kutscher-icnrg-challenges-02
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.15
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: <http://www.irtf.org/mail-archive/web/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, 03 Mar 2014 06:47:03 -0000

Hi Dirk, Hi all,



I have reviewed draft-kutscher-icnrg-challenges-02. I think that he draft has a good quality and it is usefull. However, I have a comment!

The draft is not discussing any QoS related issues. This might be needed, since NDOs can represent content used in different types of applications. Such applications can be mainly of two types, (1) streaming applications, like VoD, or (2) best effort type of applications, like file distribution and sharing. Each of these two application types impose different QoS requirements on the in-network caching features, i.e., cache placement, content placement, request-to cache routing, provided by ICN.



You might include a paragraph in the Transport Services section. Something like:


The NDOs can represent content used in different types of applications. Such applications can be mainly of two types, (1) streaming applications, like VoD, or (2) best effort type of applications, like file distribution and sharing. Each of these two application types  impose different QoS requirements on the in-network caching features, i.e., cache placement, content placement, request-to cache routing, provided by ICN. Further research is needed on identifying how the above mentioned ICN features can support NDOs used by applications that are demanding QoS support.

Best regards,
Georgios


________________________________
Van: icnrg [icnrg-bounces@irtf.org] namens internet-drafts@ietf.org [internet-drafts@ietf.org]
Verzonden: maandag 3 maart 2014 1:51
To: i-d-announce@ietf.org
Cc: icnrg@irtf.org
Onderwerp: [icnrg] I-D Action: draft-irtf-icnrg-scenarios-02.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Information-Centric Networking Working Group of the IETF.

        Title           : Information-centric Networking: Baseline Scenarios
        Authors         : Kostas Pentikousis
                          Borje Ohlman
                          Daniel Corujo
                          Gennaro Boggia
                          Gareth Tyson
                          Elwyn Davies
                          Antonella Molinaro
                          Suyong Eum
        Filename        : draft-irtf-icnrg-scenarios-02.txt
        Pages           : 45
        Date            : 2014-03-02

Abstract:
   This document aims at establishing a common understanding about a set
   of scenarios that can be used as a base for the evaluation of
   different information-centric networking (ICN) approaches so that
   they can be tested and compared against each other while showcasing
   their own advantages.  Towards this end, we review the ICN literature
   and document scenarios which have been considered in previous
   performance evaluation studies.  We discuss a variety of aspects that
   an ICN solution can address.  This includes general aspects, such as,
   network efficiency, reduced complexity, increased scalability and
   reliability, mobility support, multicast and caching performance,
   real-time communication efficiency, energy consumption frugality, and
   disruption and delay tolerance.  We detail ICN-specific aspects as
   well, such as information security and trust, persistence,
   availability, provenance, and location independence.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-irtf-icnrg-scenarios/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-irtf-icnrg-scenarios-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-irtf-icnrg-scenarios-02


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
icnrg mailing list
icnrg@irtf.org
https://www.irtf.org/mailman/listinfo/icnrg