| 1 |
<pre>Internet Research Task Force (IRTF) K. Pentikousis, Ed. |
| 2 |
Request for Comments: 7476 EICT |
| 3 |
Category: Informational B. Ohlman |
| 4 |
ISSN: 2070-1721 Ericsson |
| 5 |
D. Corujo |
| 6 |
Universidade de Aveiro |
| 7 |
G. Boggia |
| 8 |
Politecnico di Bari |
| 9 |
G. Tyson |
| 10 |
Queen Mary, University of London |
| 11 |
E. Davies |
| 12 |
Trinity College Dublin |
| 13 |
A. Molinaro |
| 14 |
UNIRC |
| 15 |
S. Eum |
| 16 |
NICT |
| 17 |
March 2015 |
| 18 |
|
| 19 |
|
| 20 |
<span class="h1">Information-Centric Networking: Baseline Scenarios</span> |
| 21 |
|
| 22 |
Abstract |
| 23 |
|
| 24 |
This document aims at establishing a common understanding about a set |
| 25 |
of scenarios that can be used as a base for the evaluation of |
| 26 |
different information-centric networking (ICN) approaches so that |
| 27 |
they can be tested and compared against each other while showcasing |
| 28 |
their own advantages. Towards this end, we review the ICN literature |
| 29 |
and document scenarios which have been considered in previous |
| 30 |
performance evaluation studies. We discuss a variety of aspects that |
| 31 |
an ICN solution can address. This includes general aspects, such as, |
| 32 |
network efficiency, reduced complexity, increased scalability and |
| 33 |
reliability, mobility support, multicast and caching performance, |
| 34 |
real-time communication efficiency, energy consumption frugality, and |
| 35 |
disruption and delay tolerance. We detail ICN-specific aspects as |
| 36 |
well, such as information security and trust, persistence, |
| 37 |
availability, provenance, and location independence. |
| 38 |
|
| 39 |
This document is a product of the IRTF Information-Centric Networking |
| 40 |
Research Group (ICNRG). |
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Pentikousis, et al. Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 55 |
|
| 56 |
|
| 57 |
Status of This Memo |
| 58 |
|
| 59 |
This document is not an Internet Standards Track specification; it is |
| 60 |
published for informational purposes. |
| 61 |
|
| 62 |
This document is a product of the Internet Research Task Force |
| 63 |
(IRTF). The IRTF publishes the results of Internet-related research |
| 64 |
and development activities. These results might not be suitable for |
| 65 |
deployment. This RFC represents the consensus of the Information- |
| 66 |
Centric Networking Research Group of the Internet Research Task Force |
| 67 |
(IRTF). Documents approved for publication by the IRSG are not a |
| 68 |
candidate for any level of Internet Standard; see Section 2 of <a href="./rfc5741">RFC</a> |
| 69 |
<a href="./rfc5741">5741</a>. |
| 70 |
|
| 71 |
Information about the current status of this document, any errata, |
| 72 |
and how to provide feedback on it may be obtained at |
| 73 |
<a href="http://www.rfc-editor.org/info/rfc7476">http://www.rfc-editor.org/info/rfc7476</a>. |
| 74 |
|
| 75 |
Copyright Notice |
| 76 |
|
| 77 |
Copyright (c) 2015 IETF Trust and the persons identified as the |
| 78 |
document authors. All rights reserved. |
| 79 |
|
| 80 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 81 |
Provisions Relating to IETF Documents |
| 82 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 83 |
publication of this document. Please review these documents |
| 84 |
carefully, as they describe your rights and restrictions with respect |
| 85 |
to this document. |
| 86 |
|
| 87 |
|
| 88 |
|
| 89 |
|
| 90 |
|
| 91 |
|
| 92 |
|
| 93 |
|
| 94 |
|
| 95 |
|
| 96 |
|
| 97 |
|
| 98 |
|
| 99 |
|
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Pentikousis, et al. Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 111 |
|
| 112 |
|
| 113 |
Table of Contents |
| 114 |
|
| 115 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a> |
| 116 |
<a href="#section-1.1">1.1</a>. Baseline Scenario Selection ................................<a href="#page-4">4</a> |
| 117 |
<a href="#section-1.2">1.2</a>. Document Goals and Outline .................................<a href="#page-5">5</a> |
| 118 |
<a href="#section-2">2</a>. Scenarios .......................................................<a href="#page-6">6</a> |
| 119 |
<a href="#section-2.1">2.1</a>. Social Networking ..........................................<a href="#page-6">6</a> |
| 120 |
<a href="#section-2.2">2.2</a>. Real-Time Communication ....................................<a href="#page-7">7</a> |
| 121 |
<a href="#section-2.3">2.3</a>. Mobile Networking ..........................................<a href="#page-9">9</a> |
| 122 |
<a href="#section-2.4">2.4</a>. Infrastructure Sharing ....................................<a href="#page-11">11</a> |
| 123 |
<a href="#section-2.5">2.5</a>. Content Dissemination .....................................<a href="#page-13">13</a> |
| 124 |
<a href="#section-2.6">2.6</a>. Vehicular Networking ......................................<a href="#page-14">14</a> |
| 125 |
<a href="#section-2.7">2.7</a>. Delay- and Disruption-Tolerance ...........................<a href="#page-17">17</a> |
| 126 |
<a href="#section-2.7.1">2.7.1</a>. Opportunistic Content Sharing ......................<a href="#page-20">20</a> |
| 127 |
<a href="#section-2.7.2">2.7.2</a>. Emergency Support and Disaster Recovery ............<a href="#page-21">21</a> |
| 128 |
<a href="#section-2.8">2.8</a>. Internet of Things ........................................<a href="#page-22">22</a> |
| 129 |
<a href="#section-2.9">2.9</a>. Smart City ................................................<a href="#page-25">25</a> |
| 130 |
<a href="#section-3">3</a>. Cross-Scenario Considerations ..................................<a href="#page-27">27</a> |
| 131 |
<a href="#section-3.1">3.1</a>. Multiply Connected Nodes and Economics ....................<a href="#page-27">27</a> |
| 132 |
<a href="#section-3.2">3.2</a>. Energy Efficiency .........................................<a href="#page-31">31</a> |
| 133 |
<a href="#section-3.3">3.3</a>. Operation across Multiple Network Paradigms ...............<a href="#page-33">33</a> |
| 134 |
<a href="#section-4">4</a>. Summary ........................................................<a href="#page-34">34</a> |
| 135 |
<a href="#section-5">5</a>. Security Considerations ........................................<a href="#page-35">35</a> |
| 136 |
<a href="#section-6">6</a>. Informative References .........................................<a href="#page-36">36</a> |
| 137 |
Acknowledgments ...................................................<a href="#page-44">44</a> |
| 138 |
Authors' Addresses ................................................<a href="#page-44">44</a> |
| 139 |
|
| 140 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 141 |
|
| 142 |
Information-centric networking (ICN) marks a fundamental shift in |
| 143 |
communications and networking. In contrast with the omnipresent and |
| 144 |
very successful host-centric paradigm, which is based on perpetual |
| 145 |
connectivity and the end-to-end principle, ICN changes the focal |
| 146 |
point of the network architecture from the end host to "named |
| 147 |
information" (or content, or data). In this paradigm, connectivity |
| 148 |
may well be intermittent. End-host and in-network storage can be |
| 149 |
capitalized upon transparently, as bits in the network and on storage |
| 150 |
devices have exactly the same value. Mobility and multiaccess are |
| 151 |
the norm, and anycast, multicast, and broadcast are natively |
| 152 |
supported. |
| 153 |
|
| 154 |
It is also worth noting that with the transition from a host-centric |
| 155 |
to an information-centric communication model the security paradigm |
| 156 |
changes as well. In a host-centric network, the basic idea is to |
| 157 |
create secure (remote-access) tunnels to trusted providers of data. |
| 158 |
In an information-centric network, on the other hand, any source |
| 159 |
(cache) should be equally usable. This requires some mechanism for |
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Pentikousis, et al. Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 167 |
|
| 168 |
|
| 169 |
making each information item trustworthy by itself; this can be |
| 170 |
achieved, for example, by name-data integrity or by signing data |
| 171 |
objects. |
| 172 |
|
| 173 |
Although interest in ICN is growing rapidly, ongoing work on |
| 174 |
different architectures, such as NetInf [<a href="#ref-NetInf" title=""Design considerations for a network of information"">NetInf</a>], the original |
| 175 |
Content-Centric Networking [<a href="#ref-CCN" title=""Networking Named Content"">CCN</a>], and its successors, Project CCNx |
| 176 |
[<a href="#ref-CCNx" title=""CCN 1.0 Protocol Architecture"">CCNx</a>] and Named Data Networking (NDN) [<a href="#ref-NDNP" title=""Named Data Networking (NDN) Project"">NDNP</a>], the Publish-Subscribe |
| 177 |
Internet (PSI) architecture [<a href="#ref-PSI" title=""Designing and realizing an information-centric internet"">PSI</a>], and the Data-Oriented Network |
| 178 |
Architecture [<a href="#ref-DONA" title=""A Data-Oriented (and Beyond) Network Architecture"">DONA</a>] is far from being completed. One could think of |
| 179 |
ICN today as being at a stage of development similar to that of |
| 180 |
packet-switched networking in the late 1970s when different |
| 181 |
technologies, e.g., DECnet, Internetwork Packet Exchange (IPX), and |
| 182 |
IP, just to name a few, were being actively developed and put to the |
| 183 |
test. As such, ICN's current development phase and the plethora of |
| 184 |
approaches to tackle the hardest problems make this a very active and |
| 185 |
growing research area, but, on the downside, it also makes it more |
| 186 |
difficult to compare different proposals on an equal footing. This |
| 187 |
document aims to partially address this by establishing a common |
| 188 |
understanding about potential experimental setups where different ICN |
| 189 |
approaches can be tested and compared against each other while |
| 190 |
showcasing their advantages. |
| 191 |
|
| 192 |
The first draft version of this document appeared in November 2012. |
| 193 |
It was adopted by ICNRG at IETF 87 (July 2013) as the document to |
| 194 |
address the work item on the definition of "reference baseline |
| 195 |
scenarios to enable performance comparisons between different |
| 196 |
approaches". Earlier draft versions of this document have been |
| 197 |
presented during the ICNRG meetings at IETF 85, IETF 86, IETF 87, |
| 198 |
IETF 88, IETF 89, and the ICNRG interim meeting in Stockholm in |
| 199 |
February 2013. This document has been reviewed, commented, and |
| 200 |
discussed extensively for a period of nearly two years by the vast |
| 201 |
majority of ICNRG members, which certainly exceeds 100 individuals. |
| 202 |
It is the consensus of ICNRG that the baseline scenarios described in |
| 203 |
this document should be published in the IRTF Stream of the RFC |
| 204 |
series. This document does not constitute a standard. |
| 205 |
|
| 206 |
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Baseline Scenario Selection</span> |
| 207 |
|
| 208 |
Earlier surveys [<a href="#ref-SoA1" title=""A survey of information-centric networking"">SoA1</a>] [<a href="#ref-SoA2" title=""A survey of information-centric networking research"">SoA2</a>] note that describing ICN architectures |
| 209 |
is akin to shooting a moving target. We find that comparing these |
| 210 |
different approaches is often even more tricky. It is not uncommon |
| 211 |
that researchers devise different performance evaluation scenarios, |
| 212 |
typically with good reason, in order to highlight the advantages of |
| 213 |
their approach. This should be expected to some degree at this early |
| 214 |
stage of ICN development. Nevertheless, this document shows that |
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Pentikousis, et al. Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 223 |
|
| 224 |
|
| 225 |
certain baseline scenarios seem to emerge in which ICN architectures |
| 226 |
could showcase their comparative advantages over current systems, in |
| 227 |
general, and against each other, in particular. |
| 228 |
|
| 229 |
This document surveys the peer-reviewed ICN literature and presents |
| 230 |
prominent evaluation study cases as a foundation for the baseline |
| 231 |
scenarios to be considered by the IRTF Information-Centric Networking |
| 232 |
Research Group (ICNRG) in its future work. There are two goals for |
| 233 |
this document: first, to provide a set of use cases and applications |
| 234 |
that highlight opportunities for testing different ICN proposals; |
| 235 |
second, to identify key attributes of a common set of techniques that |
| 236 |
can be instrumental in evaluating ICN. Further, these scenarios are |
| 237 |
intended to equip researchers with sufficient configuration data to |
| 238 |
effectively evaluate their ICN proposals in a variety of settings, |
| 239 |
particularly extending beyond scenarios focusing simply on |
| 240 |
traditional content delivery. The overall aim is that each scenario |
| 241 |
is described at a sufficient level of detail, and with adequate |
| 242 |
references to already published work, so that it can serve as the |
| 243 |
base for comparative evaluations of different approaches. Example |
| 244 |
code that implements some of the scenarios and topologies included in |
| 245 |
this document is available from |
| 246 |
<<a href="http://telematics.poliba.it/icn-baseline-scenarios">http://telematics.poliba.it/icn-baseline-scenarios</a>>. |
| 247 |
|
| 248 |
<span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Document Goals and Outline</span> |
| 249 |
|
| 250 |
This document incorporates input from ICNRG participants and their |
| 251 |
corresponding text contributions, has been reviewed by several ICNRG |
| 252 |
active participants (see <a href="#section-7">Section 7</a>), and represents the consensus of |
| 253 |
the research group. However, this document does not constitute an |
| 254 |
IETF standard, but is an Informational document; see also [<a href="./rfc5743" title=""Definition of an Internet Research Task Force (IRTF) Document Stream"">RFC5743</a>]. |
| 255 |
As mentioned above, these scenarios are intended to provide a |
| 256 |
framework for evaluating different ICN approaches. The methodology |
| 257 |
for how to do these evaluations as well as definitions of metrics |
| 258 |
that should be used are described in a separate document |
| 259 |
[<a href="#ref-EVAL-METHOD">EVAL-METHOD</a>]. In addition, interested readers should consider |
| 260 |
reviewing [<a href="#ref-CHALLENGES">CHALLENGES</a>]. |
| 261 |
|
| 262 |
The remainder of this document presents a number of scenarios grouped |
| 263 |
into several categories in <a href="#section-2">Section 2</a>, followed by a number of cross- |
| 264 |
scenario considerations in <a href="#section-3">Section 3</a>. Overall, note that certain |
| 265 |
evaluation scenarios span across these categories, so the boundaries |
| 266 |
between them should not be considered rigid and inflexible. |
| 267 |
<a href="#section-4">Section 4</a> summarizes the main evaluation aspects across the range of |
| 268 |
scenarios discussed in this document. |
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Pentikousis, et al. Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Scenarios</span> |
| 282 |
|
| 283 |
This section presents nine scenario categories based on use cases and |
| 284 |
evaluations that have appeared in the peer-reviewed literature. |
| 285 |
|
| 286 |
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Social Networking</span> |
| 287 |
|
| 288 |
Social-networking applications have proliferated over the past decade |
| 289 |
based on overlay content dissemination systems that require large |
| 290 |
infrastructure investments to roll out and maintain. Content |
| 291 |
dissemination is at the heart of the ICN paradigm. Therefore, we |
| 292 |
would expect that social-networking scenarios are a "natural fit" for |
| 293 |
comparing ICN performance with traditional client-server TCP/IP-based |
| 294 |
systems. Mathieu et al. [<a href="#ref-ICN-SN" title=""Information-centric networking: a natural design for social network applications"">ICN-SN</a>], for instance, illustrate how an |
| 295 |
Internet Service Provider (ISP) can capitalize on CCN to deploy a |
| 296 |
short-message service akin to Twitter at a fraction of the complexity |
| 297 |
of today's systems. Their key observation is that such a service can |
| 298 |
be seen as a combination of multicast delivery and caching. That is, |
| 299 |
a single user addresses a large number of recipients, some of which |
| 300 |
receive the new message immediately as they are online at that |
| 301 |
instant, while others receive the message whenever they connect to |
| 302 |
the network. |
| 303 |
|
| 304 |
Along similar lines, Kim et al. [<a href="#ref-VPC" title=""Content Centric Network-based Virtual Private Community"">VPC</a>] present an ICN-based social- |
| 305 |
networking platform in which a user shares content with her/his |
| 306 |
family and friends without the need for centralized content servers; |
| 307 |
see also <a href="#section-2.4">Section 2.4</a>, below, and [<a href="#ref-CBIS" title=""Custodian-Based Information Sharing"">CBIS</a>]. Based on the CCN naming |
| 308 |
scheme, [<a href="#ref-VPC" title=""Content Centric Network-based Virtual Private Community"">VPC</a>] takes a user name to represent a set of devices that |
| 309 |
belong to the person. Other users in this in-network, serverless |
| 310 |
social sharing scenario can access the user's content not via a |
| 311 |
device name/address but with the user's name. In [<a href="#ref-VPC" title=""Content Centric Network-based Virtual Private Community"">VPC</a>], signature |
| 312 |
verification does not require any centralized authentication server. |
| 313 |
Kim and Lee [<a href="#ref-VPC2" title=""CCN-based virtual private community for extended home media service"">VPC2</a>] present a proof-of-concept evaluation in which |
| 314 |
users with ordinary smartphones can browse a list of members or |
| 315 |
content using a name, and download the content selected from the |
| 316 |
list. |
| 317 |
|
| 318 |
In other words, the above-mentioned evaluation studies indicate that |
| 319 |
with ICN there may be no need for an end-to-end system design that |
| 320 |
intermediates between content providers and consumers in a hub-and- |
| 321 |
spoke fashion at all times. |
| 322 |
|
| 323 |
Earlier work by Arianfar et al. [<a href="#ref-CCR" title=""On content-centric router design and implications"">CCR</a>] considers a similar pull-based |
| 324 |
content retrieval scenario using a different architecture, pointing |
| 325 |
to significant performance advantages. Although the authors consider |
| 326 |
a network topology (redrawn in Figure 1 for convenience) that has |
| 327 |
certain interesting characteristics, they do not explicitly address |
| 328 |
social networking in their evaluation scenario. Nonetheless, |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Pentikousis, et al. Informational [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 335 |
|
| 336 |
|
| 337 |
similarities are easy to spot: "followers" (such as C0, C1, ..., and |
| 338 |
Cz in Figure 1) obtain content put "on the network" (I1, ..., Im, and |
| 339 |
B1, B2) by a single user (e.g., Px) relying solely on network |
| 340 |
primitives. |
| 341 |
|
| 342 |
\--/ |
| 343 |
|C0| |
| 344 |
/--\ +--+ +--+ +--+ +--+ |
| 345 |
*=== |I0| === |I1| ... |In| |P0| |
| 346 |
\--/ +--+ +--+ +--+ +--+ |
| 347 |
|C1| \ / o |
| 348 |
/--\ +--+ +--+ o |
| 349 |
o |B1| === |B2| o |
| 350 |
o o o o o +--+ +--+ o |
| 351 |
o / \ o |
| 352 |
o +--+ +--+ +--+ +--+ |
| 353 |
o *=== |Ik| === |Il| ... |Im| |Px| |
| 354 |
\--/ +--+ +--+ +--+ +--+ |
| 355 |
|Cz| |
| 356 |
/--\ |
| 357 |
|
| 358 |
Figure 1. Dumbbell with Linear Daisy Chains |
| 359 |
|
| 360 |
In summary, the social-networking scenario aims to exercise each ICN |
| 361 |
architecture in terms of network efficiency, multicast support, |
| 362 |
caching performance and its reliance on centralized mechanisms (or |
| 363 |
lack thereof). |
| 364 |
|
| 365 |
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Real-Time Communication</span> |
| 366 |
|
| 367 |
Real-time audio and video (A/V) communications include an array of |
| 368 |
services ranging from one-to-one voice calls to multiparty multimedia |
| 369 |
conferences with support ranging from whiteboards to augmented |
| 370 |
reality. Real-time communications have been studied and deployed in |
| 371 |
the context of packet- and circuit-switched networks for decades. |
| 372 |
The stringent Quality of Service (QoS) requirements that this type of |
| 373 |
communication imposes on network infrastructure are well known. |
| 374 |
Since one could argue that network primitives that are excellent for |
| 375 |
information dissemination are not well-suited for conversational |
| 376 |
services, ICN evaluation studies should consider real-time |
| 377 |
communication scenarios in detail. |
| 378 |
|
| 379 |
Notably, Jacobson et al. [<a href="#ref-VoCCN" title=""VoCCN: Voice-over Content-Centric Networks"">VoCCN</a>] presented an early evaluation where |
| 380 |
the performance of a VoIP (Voice over IP) call using an information- |
| 381 |
centric approach was compared with that of an off-the-shelf VoIP |
| 382 |
implementation using RTP/UDP. The results indicated that despite the |
| 383 |
extra cost of adding security support in the ICN approach, |
| 384 |
performance was virtually identical in the two cases evaluated in |
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Pentikousis, et al. Informational [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 391 |
|
| 392 |
|
| 393 |
their testbed. However, the experimental setup presented is quite |
| 394 |
rudimentary, while the evaluation considered a single voice call |
| 395 |
only. Xuan and Yan [<a href="#ref-NDNpb" title=""Enhancing Routing Efficiency in Named Data Network with Piggybacked Interest"">NDNpb</a>] revisit the same scenario but are |
| 396 |
primarily interested in reducing the overhead that may arise in one- |
| 397 |
to-one communication employing an ICN architecture. Both studies |
| 398 |
illustrate that quality telephony services are feasible with at least |
| 399 |
one ICN approach. That said, future ICN evaluations should employ |
| 400 |
standardized call arrival patterns, for example, following well- |
| 401 |
established methodologies from the QoS and QoE (Quality of |
| 402 |
Experience) evaluation toolbox and would need to consider more |
| 403 |
comprehensive metrics. |
| 404 |
|
| 405 |
Given the widespread deployment of real-time A/V communications, an |
| 406 |
evaluation of an ICN system should demonstrate capabilities beyond |
| 407 |
feasibility. For example, with respect to multimedia conferencing, |
| 408 |
Zhu et al. [<a href="#ref-ACT" title=""ACT: Audio Conference Tool Over Named Data Networking"">ACT</a>] describe the design of a distributed audio |
| 409 |
conference tool based on NDN. Their system includes ICN-based |
| 410 |
conference discovery, speaker discovery, and voice data distribution. |
| 411 |
The reported evaluation results point to gains in scalability and |
| 412 |
security. Moreover, Chen et al. [<a href="#ref-G-COPSS" title=""G-COPSS: A Content Centric Communication Infrastructure for Gaming Applications"">G-COPSS</a>] explore the feasibility of |
| 413 |
implementing a Massively Multiplayer Online Role-Playing Game |
| 414 |
(MMORPG) based on CCNx code and show that stringent temporal |
| 415 |
requirements can be met, while scalability is significantly improved |
| 416 |
when compared to a host-centric (IP-based) client-server system. |
| 417 |
This type of work points to benefits for both the data and control |
| 418 |
path of a modern network infrastructure. |
| 419 |
|
| 420 |
Real-time communication also brings up the issue of named data |
| 421 |
granularity for dynamically generated content. In many cases, A/V |
| 422 |
data is generated in real-time and is distributed immediately. One |
| 423 |
possibility is to apply a single name to the entire content, but this |
| 424 |
could result in significant distribution delays. Alternatively, |
| 425 |
distributing A/V content in smaller "chunks" that are named |
| 426 |
individually may be a better option with respect to real-time |
| 427 |
distribution but raises naming scalability concerns. |
| 428 |
|
| 429 |
We observe that, all in all, the ICN research community has hitherto |
| 430 |
only scratched the surface of illustrating the benefits of adopting |
| 431 |
an information-centric approach as opposed to a host-centric one, and |
| 432 |
thus more work is recommended in this direction. Scenarios in this |
| 433 |
category should illustrate not only feasibility but reduced |
| 434 |
complexity, increased scalability, reliability, and capacity to meet |
| 435 |
stringent QoS/QoE requirements when compared to established host- |
| 436 |
centric solutions. Accordingly, the primary aim of this scenario is |
| 437 |
to exercise each ICN architecture in terms of its ability to satisfy |
| 438 |
real-time QoS requirements and provide improved user experience. |
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Pentikousis, et al. Informational [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 447 |
|
| 448 |
|
| 449 |
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Mobile Networking</span> |
| 450 |
|
| 451 |
IP mobility management relies on anchors to provide ubiquitous |
| 452 |
connectivity to end-hosts as well as moving networks [<a href="#ref-MMIN" title=""Mobility Management in Infrastructure Networks"">MMIN</a>]. This is |
| 453 |
a natural choice for a host-centric paradigm that requires end-to-end |
| 454 |
connectivity and a continuous network presence for hosts [<a href="#ref-SCES" title=""Enabling an Energy-Efficient Future Internet through Selectively Connected End Systems"">SCES</a>]. An |
| 455 |
implicit assumption in host-centric mobility management is therefore |
| 456 |
that the mobile node aims to connect to a particular peer, as well as |
| 457 |
to maintain global reachability and service continuity [<a href="#ref-EEMN" title=""In Search of Energy-Efficient Mobile Networking"">EEMN</a>]. |
| 458 |
However, with ICN, new ideas about mobility management should come to |
| 459 |
the fore, capitalizing on the different nature of the paradigm, such |
| 460 |
as native support for multihoming, abstraction of network addresses |
| 461 |
from applications, less dependence on connection-oriented sessions, |
| 462 |
and so on [<a href="#ref-MOBSURV" title=""A Survey of Mobility in Information- Centric Networks: Challenges and Research Directions"">MOBSURV</a>]. |
| 463 |
|
| 464 |
Dannewitz et al. [<a href="#ref-N-Scen" title=""Scenarios and research issues for a Network of Information"">N-Scen</a>] illustrate a scenario where a multiaccess |
| 465 |
end-host can retrieve email securely using a combination of cellular |
| 466 |
and Wireless Local Area Network (WLAN) connectivity. This scenario |
| 467 |
borrows elements from previous work, e.g., [<a href="#ref-DTI" title=""Drive-thru Internet: IEEE 802.11b for 'automobile' users"">DTI</a>], and develops them |
| 468 |
further with respect to multiaccess. Unfortunately, Dannewitz et al. |
| 469 |
[<a href="#ref-N-Scen" title=""Scenarios and research issues for a Network of Information"">N-Scen</a>] do not present any results demonstrating that an ICN |
| 470 |
approach is, indeed, better. That said, the scenario is interesting |
| 471 |
as it considers content specific to a single user (i.e., her mailbox) |
| 472 |
and does point to reduced complexity. It is also compatible with |
| 473 |
recent work in the Distributed Mobility Management (DMM) Working |
| 474 |
Group within the IETF. Finally, Xylomenos et al. [<a href="#ref-PSIMob" title=""Caching and Mobility Support in a Publish-Subscribe Internet Architecture"">PSIMob</a>] as well as |
| 475 |
Pentikousis [<a href="#ref-EEMN" title=""In Search of Energy-Efficient Mobile Networking"">EEMN</a>] argue that an information-centric architecture can |
| 476 |
avoid the complexity of having to manage tunnels to maintain end-to- |
| 477 |
end connectivity as is the case with mobile anchor-based protocols |
| 478 |
such as Mobile IP (and its variants). Similar considerations hold |
| 479 |
for a vehicular (networking) environment, as we discuss in <a href="#section-2.6">Section</a> |
| 480 |
<a href="#section-2.6">2.6</a>. |
| 481 |
|
| 482 |
Overall, mobile networking scenarios have not been developed in |
| 483 |
detail, let alone evaluated at a large scale. Further, the majority |
| 484 |
of scenarios discussed so far have related to the mobility of the |
| 485 |
information consumer, rather than the source. We expect that in the |
| 486 |
coming period more papers will address this topic. Earlier work |
| 487 |
[<a href="#ref-mNetInf" title=""A Multiaccess Network of Information"">mNetInf</a>] argues that for mobile and multiaccess networking scenarios |
| 488 |
we need to go beyond the current mobility management mechanisms in |
| 489 |
order to capitalize on the core ICN features. They present a testbed |
| 490 |
setup (redrawn in Figure 2) that can serve as the basis for other ICN |
| 491 |
evaluations. In this scenario, node "C0" has multiple network |
| 492 |
interfaces that can access local domains N0 and N1 simultaneously, |
| 493 |
allowing C0 to retrieve objects from whichever server (I2 or I3) can |
| 494 |
supply them without necessarily needing to access the servers in the |
| 495 |
core network "C" (P1 and P2). Lindgren [<a href="#ref-HybICN" title=""Efficient content distribution in an information-centric hybrid mobile networks"">HybICN</a>] explores this |
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Pentikousis, et al. Informational [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 503 |
|
| 504 |
|
| 505 |
scenario further for an urban setting. He uses simulation and |
| 506 |
reports sizable gains in terms of reduction of object retrieval times |
| 507 |
and core network capacity use. |
| 508 |
|
| 509 |
+------------+ +-----------+ |
| 510 |
| Network N0 | | Network C | |
| 511 |
| | | | |
| 512 |
| +--+ | ==== | +--+ | |
| 513 |
| |I2| | | |P1| | |
| 514 |
| +--+ | | +--+ | |
| 515 |
| \--/ | | | |
| 516 |
+-----|C0|---+ | | |
| 517 |
| /--\ | | | |
| 518 |
| +--+ | | | |
| 519 |
| |I3| | | +--+ | |
| 520 |
| +--+ | ==== | |P2| | |
| 521 |
| | | +--+ | |
| 522 |
| Network N1 | | | |
| 523 |
+------------+ +-----------+ |
| 524 |
|
| 525 |
Figure 2. Overlapping Wireless Multiaccess |
| 526 |
|
| 527 |
The benefits from capitalizing on the broadcast nature of wireless |
| 528 |
access technologies has yet to be explored to its full potential in |
| 529 |
the ICN literature, including quantifying possible gains in terms of |
| 530 |
energy efficiency [<a href="#ref-E-CHANET" title=""E-CHANET: Routing, Forwarding and Transport in Information-Centric Multihop Wireless Networks"">E-CHANET</a>]. Obviously, ICN architectures must |
| 531 |
avoid broadcast storms. Early work in this area considers |
| 532 |
distributed packet suppression techniques that exploit delayed |
| 533 |
transmissions and overhearing; examples can be found in [<a href="#ref-MobiA" title=""Ad Hoc Networking via Named Data"">MobiA</a>] and |
| 534 |
[<a href="#ref-CCNMANET" title=""Content Centric Networking in Tactical and Emergency MANETs"">CCNMANET</a>] for ICN-based mobile ad-hoc networks (MANETs), and in |
| 535 |
[<a href="#ref-RTIND" title=""Rapid Traffic Information Dissemination Using Named Data"">RTIND</a>] and [<a href="#ref-CCNVANET" title=""Content-Centric Networking: is that a Solution for Upcoming Vehicular Networks?"">CCNVANET</a>] for vehicular scenarios. |
| 536 |
|
| 537 |
One would expect that mobile networking scenarios will be naturally |
| 538 |
coupled with those discussed in the previous sections, as more users |
| 539 |
access social-networking and multimedia applications through mobile |
| 540 |
devices. Further, the constraints of real-time A/V applications |
| 541 |
create interesting challenges in handling mobility, particularly in |
| 542 |
terms of maintaining service continuity. This scenario therefore |
| 543 |
spans across most of the others considered in this document with the |
| 544 |
likely need for some level of integration, particularly considering |
| 545 |
the well-documented increases in mobile traffic. Mobility is further |
| 546 |
considered in <a href="#section-2.7">Section 2.7</a> and the economic consequences of nodes |
| 547 |
having multiple network interfaces is explored in <a href="#section-3.1">Section 3.1</a>. |
| 548 |
|
| 549 |
Host-centric mobility management has traditionally used a range of |
| 550 |
metrics for evaluating performance on a per-node and network-wide |
| 551 |
level. The first metric that comes to mind is handover latency, |
| 552 |
defined in [<a href="./rfc5568" title=""Mobile IPv6 Fast Handovers"">RFC5568</a>] as the "period during which the mobile node is |
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Pentikousis, et al. Informational [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 559 |
|
| 560 |
|
| 561 |
unable to send or receive packets". This metric should be considered |
| 562 |
in ICN performance evaluation studies dealing with mobility. Note |
| 563 |
that, in IP-based networks, handover latency has been addressed by |
| 564 |
the introduction of mobility management protocols that aim to hide |
| 565 |
node mobility from the correspondent node, and often follow a make- |
| 566 |
before-break approach in order to ensure seamless connectivity and |
| 567 |
minimize (or eliminate altogether) handover latency. The "always-on" |
| 568 |
and "always best connected" [<a href="#ref-ABC" title=""Always best connected"">ABC</a>] paradigms have guided mobility |
| 569 |
management research and standardization for a good decade or so. One |
| 570 |
can argue that such mechanisms are not particularly suited for ICN. |
| 571 |
That said, there has been a lot of interest recently in distributed |
| 572 |
mobility management schemes (see [<a href="#ref-MMIN" title=""Mobility Management in Infrastructure Networks"">MMIN</a>] for a summary), where |
| 573 |
mobility management support is not "always on" by default. Such |
| 574 |
schemes may be more suitable for ICN. As a general recommendation, |
| 575 |
ICN designs should aim to minimize handover latency so that the end- |
| 576 |
user and service QoE is not affected adversely. |
| 577 |
|
| 578 |
Network overhead, such as the amount of signaling necessary to |
| 579 |
minimize handover latency, is also a metric that should be considered |
| 580 |
when studying ICN mobility management. In the past, network overhead |
| 581 |
has been seen as one of the main factors hindering the deployment of |
| 582 |
various mobility solutions. In IP-based networks, network overhead |
| 583 |
includes, but is not limited to, tunneling overhead, in-band control |
| 584 |
protocol overhead, mobile terminal and network equipment state |
| 585 |
maintenance and update. ICN designs and evaluation studies should |
| 586 |
clearly identify the network overhead associated with handling |
| 587 |
mobility. Alongside network overhead, deployment complexity should |
| 588 |
also be studied. |
| 589 |
|
| 590 |
To summarize, mobile networking scenarios should aim to provide |
| 591 |
service continuity for those applications that require it, decrease |
| 592 |
complexity and control signaling for the network infrastructure, as |
| 593 |
well as increase wireless capacity utilization by taking advantage of |
| 594 |
the broadcast nature of the medium. Beyond this, mobile networking |
| 595 |
scenarios should form a cross-scenario platform that can highlight |
| 596 |
how other scenarios can still maintain their respective performance |
| 597 |
metrics during periods of high mobility. |
| 598 |
|
| 599 |
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Infrastructure Sharing</span> |
| 600 |
|
| 601 |
A key idea in ICN is that the network should secure information |
| 602 |
objects per se, not the communications channel that they are |
| 603 |
delivered over. This means that hosts attached to an information- |
| 604 |
centric network can share resources on an unprecedented scale, |
| 605 |
especially when compared to what is possible in an IP network. All |
| 606 |
devices with network access and storage capacity can contribute their |
| 607 |
resources thereby increasing the value of an information-centric |
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Pentikousis, et al. Informational [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 615 |
|
| 616 |
|
| 617 |
network, although compensation schemes motivating users to contribute |
| 618 |
resources remain a research challenge primarily from a business |
| 619 |
perspective. |
| 620 |
|
| 621 |
For example, Jacobson et al. [<a href="#ref-CBIS" title=""Custodian-Based Information Sharing"">CBIS</a>] argue that in ICN the "where and |
| 622 |
how" of obtaining information are new degrees of freedom. They |
| 623 |
illustrate this with a scenario involving a photo-sharing application |
| 624 |
that takes advantage of whichever access network connectivity is |
| 625 |
available at the moment (WLAN, Bluetooth, and even SMS) without |
| 626 |
requiring a centralized infrastructure to synchronize between |
| 627 |
numerous devices. It is important to highlight that since the focus |
| 628 |
of communication changes, keep-alives in this scenario are simply |
| 629 |
unnecessary, as devices participating in the testbed network |
| 630 |
contribute resources in order to maintain user content consistency, |
| 631 |
not link state information as is the case in the host-centric |
| 632 |
paradigm. This means that the notion of "infrastructure" may be |
| 633 |
completely different in the future. |
| 634 |
|
| 635 |
Muscariello et al. [<a href="#ref-SHARE" title=""Bandwidth and storage sharing performance in information centric networking"">SHARE</a>], for instance, presented early work on an |
| 636 |
analytical framework that attempts to capture the storage/bandwidth |
| 637 |
tradeoffs that ICN enables and can be used as the foundation for a |
| 638 |
network planning tool. In addition, Chai et al. [<a href="#ref-CL4M" title=""Cache 'Less for More' in Information-centric Networks"">CL4M</a>] explore the |
| 639 |
benefits of ubiquitous caching throughout an information-centric |
| 640 |
network and argue that "caching less can actually achieve more." |
| 641 |
These papers also sit alongside a variety of other studies that look |
| 642 |
at various scenarios such as caching HTTP-like traffic [<a href="#ref-CCNCT" title=""Modelling and Evaluation of CCN- Caching Trees"">CCNCT</a>] and |
| 643 |
BitTorrent-like traffic [<a href="#ref-BTCACHE" title=""A Trace-Driven Analysis of Caching in Content-Centric Networks"">BTCACHE</a>]. We observe that much more work is |
| 644 |
needed in order to understand how to make optimal use of all |
| 645 |
resources available in an information-centric network. In real-world |
| 646 |
deployments, policy and commercial considerations are also likely to |
| 647 |
affect the use of particular resources, and more work is expected in |
| 648 |
this direction as well. |
| 649 |
|
| 650 |
In conclusion, scenarios in this category would cover the |
| 651 |
communication-computation-storage tradeoffs that an ICN deployment |
| 652 |
must consider. This would exercise features relating to network |
| 653 |
planning, perhaps capitalizing on user-provided resources, as well as |
| 654 |
operational and economical aspects of ICN, and contrast them with |
| 655 |
other approaches. An obvious baseline to compare against in this |
| 656 |
regard is existing federations of IP-based Content Distribution |
| 657 |
Networks (CDNs), such as the ones discussed in the IETF Content |
| 658 |
Delivery Networks Interconnection Working Group. |
| 659 |
|
| 660 |
|
| 661 |
|
| 662 |
|
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Pentikousis, et al. Informational [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 671 |
|
| 672 |
|
| 673 |
<span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. Content Dissemination</span> |
| 674 |
|
| 675 |
Content dissemination has attracted more attention than other aspects |
| 676 |
of ICN. Scenarios in this category abound in the literature, |
| 677 |
including stored and streaming A/V distribution, file distribution, |
| 678 |
mirroring and bulk transfers, versioned content services (cf. |
| 679 |
Subversion-type revision control), as well as traffic aggregation. |
| 680 |
|
| 681 |
Decentralized content dissemination with on-the-fly aggregation of |
| 682 |
information sources was envisaged in [<a href="#ref-N-Scen" title=""Scenarios and research issues for a Network of Information"">N-Scen</a>], where information |
| 683 |
objects can be dynamically assembled based on hierarchically |
| 684 |
structured subcomponents. For example, a video stream could be |
| 685 |
associated with different audio streams and subtitle sets, which can |
| 686 |
all be obtained from different sources. Using the topology depicted |
| 687 |
in Figure 1 as an example, an application at C1 may end up obtaining, |
| 688 |
say, the video content from I1, but the user-selected subtitles from |
| 689 |
Px. Semantics and content negotiation, on behalf of the user, were |
| 690 |
also considered, e.g., for the case of popular tunes that may be |
| 691 |
available in different encoding formats. Effectively, this scenario |
| 692 |
has the information consumer issuing independent requests for content |
| 693 |
based on information identifiers, and stitching the pieces together |
| 694 |
irrespective of "where" or "how" they were obtained. |
| 695 |
|
| 696 |
A case in point for content dissemination are vehicular ad hoc |
| 697 |
networks (VANETs), as an ICN approach may address their needs for |
| 698 |
information dissemination between vehicles better than today's |
| 699 |
solutions, as discussed in the following section. The critical part |
| 700 |
of information dissemination in a VANET scenario revolves around |
| 701 |
"where" and "when". For instance, one may be interested in traffic |
| 702 |
conditions 2 km ahead while having no interest in similar information |
| 703 |
about the area around the path origin. VANET scenarios may provide |
| 704 |
fertile ground for showcasing the ICN advantage with respect to |
| 705 |
content dissemination especially when compared with current host- |
| 706 |
centric approaches. That said, information integrity and filtering |
| 707 |
are challenges that must be addressed. As mentioned above, content |
| 708 |
dissemination scenarios in VANETs have a particular affinity to the |
| 709 |
mobility scenarios discussed in <a href="#section-2.3">Section 2.3</a>. |
| 710 |
|
| 711 |
Content dissemination scenarios, in general, have a large overlap |
| 712 |
with those described in the previous sections and are explored in |
| 713 |
several papers, such as [<a href="#ref-DONA" title=""A Data-Oriented (and Beyond) Network Architecture"">DONA</a>], [<a href="#ref-PSI" title=""Designing and realizing an information-centric internet"">PSI</a>], [<a href="#ref-PSIMob" title=""Caching and Mobility Support in a Publish-Subscribe Internet Architecture"">PSIMob</a>], [<a href="#ref-NetInf" title=""Design considerations for a network of information"">NetInf</a>], [<a href="#ref-CCN" title=""Networking Named Content"">CCN</a>], |
| 714 |
[<a href="#ref-CBIS" title=""Custodian-Based Information Sharing"">CBIS</a>], and [<a href="#ref-CCR" title=""On content-centric router design and implications"">CCR</a>], just to name a few. In addition, Chai et al. |
| 715 |
[<a href="#ref-CURLING" title=""CURLING: Content-Ubiquitous Resolution and Delivery Infrastructure for Next-Generation Services"">CURLING</a>] present a hop-by-hop hierarchical content resolution |
| 716 |
approach that employs receiver-driven multicast over multiple |
| 717 |
domains, advocating another content dissemination approach. Yet, |
| 718 |
largely, work in this area did not address the issue of access |
| 719 |
authorization in detail. Often, the distributed content is mostly |
| 720 |
assumed to be freely accessible by any consumer. Distribution of |
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Pentikousis, et al. Informational [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 727 |
|
| 728 |
|
| 729 |
paid-for or otherwise restricted content on a public ICN network |
| 730 |
requires more attention in the future. Fotiou et al. [<a href="#ref-ACDICN" title=""Access control enforcement delegation for information-centric networking architectures"">ACDICN</a>] |
| 731 |
consider a scheme to this effect, but it still requires access to an |
| 732 |
authorization server to verify the user's status after the |
| 733 |
(encrypted) content has been obtained. This may effectively negate |
| 734 |
the advantage of obtaining the content from any node, especially in a |
| 735 |
disruption-prone or mobile network. |
| 736 |
|
| 737 |
In summary, scenarios in this category aim to exercise primarily |
| 738 |
scalability and the cost and performance attributes of content |
| 739 |
dissemination. Particularly, they should highlight the ability of an |
| 740 |
ICN to scale to billions of objects, while not exceeding the cost of |
| 741 |
existing content dissemination solutions (i.e., CDNs) and, ideally, |
| 742 |
increasing performance. These should be shown in a holistic manner, |
| 743 |
improving content dissemination for both information consumers and |
| 744 |
publishers of all sizes. We expect that in particular for content |
| 745 |
dissemination, in both extreme as well as typical scenarios, can be |
| 746 |
specified by drawing data from current CDN deployments. |
| 747 |
|
| 748 |
<span class="h3"><a class="selflink" id="section-2.6" href="#section-2.6">2.6</a>. Vehicular Networking</span> |
| 749 |
|
| 750 |
Users "on wheels" are interested in road safety, traffic efficiency, |
| 751 |
and infotainment applications that can be supported through vehicle- |
| 752 |
to-vehicle (V2V) and vehicle-to-infrastructure (V2I) wireless |
| 753 |
communications. These applications exhibit unique features in terms |
| 754 |
of traffic generation patterns, delivery requirements, and spatial |
| 755 |
and temporal scope, which pose great challenges to traditional |
| 756 |
networking solutions. VANETs, by their nature, are characterized by |
| 757 |
challenges such as fast-changing topology, intermittent connectivity, |
| 758 |
and high node mobility, but also by the opportunity to combine |
| 759 |
information from different sources as each vehicle does not care |
| 760 |
about "who" delivers the named data objects. |
| 761 |
|
| 762 |
ICN is an attractive candidate solution for vehicular networking, as |
| 763 |
it has several advantages. First, ICN fits well to the nature of |
| 764 |
typical vehicular applications that are geography- and time-dependent |
| 765 |
(e.g., road traveler information, accident warning, point-of-interest |
| 766 |
advertisements) and usually target vehicles in a given area, |
| 767 |
regardless of their identity or IP address. These applications are |
| 768 |
likely to benefit from in-network and decentralized data caching and |
| 769 |
replication mechanisms. Second, content caching is particularly |
| 770 |
beneficial for intermittent on-the-road connectivity and can speed up |
| 771 |
data retrieval through content replication in several nodes. Caching |
| 772 |
can usually be implemented at relatively low cost in vehicles, as the |
| 773 |
energy demands of the ICN device are likely to be a negligible |
| 774 |
fraction of the total vehicle energy consumption, thus allowing for |
| 775 |
sophisticated processing, continuous communication, and adequate |
| 776 |
storage in the vehicle. Finally, ICN natively supports asynchronous |
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Pentikousis, et al. Informational [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 783 |
|
| 784 |
|
| 785 |
data exchange between end-nodes. By using (and redistributing) |
| 786 |
cached named information objects, a mobile node can serve as a link |
| 787 |
between disconnected areas. In short, ICN can enable communication |
| 788 |
even under intermittent network connectivity, which is typical of |
| 789 |
vehicular environments with sparse roadside infrastructure and fast- |
| 790 |
moving nodes. |
| 791 |
|
| 792 |
The advantages of ICN in vehicular networks were preliminarily |
| 793 |
discussed in [<a href="#ref-EWC" title=""Exploiting the wisdom of the crowd: localized, distributed information-centric VANETs"">EWC</a>] and [<a href="#ref-DMND" title=""DMND: Collecting data from mobiles using Named Data"">DMND</a>], and additionally investigated in |
| 794 |
[<a href="#ref-DNV2V" title=""Data Naming in Vehicle-to-Vehicle Communications"">DNV2V</a>], [<a href="#ref-RTIND" title=""Rapid Traffic Information Dissemination Using Named Data"">RTIND</a>], [<a href="#ref-CCNHV" title=""A Self-Organizing Content Centric Network Model for Hybrid Vehicular Ad-Hoc Networks"">CCNHV</a>], [<a href="#ref-CCDIVN" title=""A Content Centric Approach to Dissemination of Information in Vehicular Networks"">CCDIVN</a>], [<a href="#ref-CCNVANET" title=""Content-Centric Networking: is that a Solution for Upcoming Vehicular Networks?"">CCNVANET</a>], and [<a href="#ref-CRoWN" title=""CRoWN: Content-Centric Networking in Vehicular Ad Hoc Networks"">CRoWN</a>]. For |
| 795 |
example, Bai and Krishnamachari [<a href="#ref-EWC" title=""Exploiting the wisdom of the crowd: localized, distributed information-centric VANETs"">EWC</a>] take advantage of the localized |
| 796 |
and dynamic nature of a VANET to explore how a road congestion |
| 797 |
notification application can be implemented. Wang et al. [<a href="#ref-DMND" title=""DMND: Collecting data from mobiles using Named Data"">DMND</a>] |
| 798 |
consider data collection where Road-Side Units (RSUs) collect |
| 799 |
information from vehicles by broadcasting NDN-like Interest packets. |
| 800 |
The proposed architecture is evaluated using simulation in a grid |
| 801 |
topology and is compared against a host-centric alternative based on |
| 802 |
Mobile IP. See Figure 3 for an indicative example of an urban VANET |
| 803 |
topology. Their results indicate high efficiency for ICN even at |
| 804 |
high speeds. That said, this work is a preliminary exploration of |
| 805 |
ICN in vehicular environments, so various issues remain for |
| 806 |
evaluation. They include system scalability to large numbers of |
| 807 |
vehicles and the impact of vehicles that forward Interest packets or |
| 808 |
relay data to other vehicles. |
| 809 |
|
| 810 |
+ - - _- - -_- - - -_- - _- - - + |
| 811 |
| /_\ /_\ /_\ /_\ | |
| 812 |
| o o o o o o o o | |
| 813 |
| +-------+ +-------+ _ | |
| 814 |
| | | | |/_\ | |
| 815 |
| _ | | | |o o | |
| 816 |
| /_\| | | | | |
| 817 |
| o o+--_----+\===/+--_----+ | |
| 818 |
| /_\ |RSU| /_\ | |
| 819 |
| o o /===\ o o | |
| 820 |
| +-------+ +-------+ _ | |
| 821 |
| | | | |/_\ | |
| 822 |
| _ | | | |o o | |
| 823 |
|/_\ | | | | | |
| 824 |
|o o +_-----_+ +_-----_+ | |
| 825 |
| /_\ /_\ /_\ /_\ | |
| 826 |
+_ _ o_o_ _o_o_ _ _o_o_ _o_o_ _ + |
| 827 |
|
| 828 |
Figure 3. Urban Grid VANET Topology |
| 829 |
|
| 830 |
As mentioned in the previous section, due to the short communication |
| 831 |
duration between a vehicle and the RSU, and the typically short time |
| 832 |
of sustained connectivity between vehicles, VANETs may be a good |
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Pentikousis, et al. Informational [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 839 |
|
| 840 |
|
| 841 |
showcase for the ICN advantages with respect to content |
| 842 |
dissemination. Wang et al. [<a href="#ref-DNV2V" title=""Data Naming in Vehicle-to-Vehicle Communications"">DNV2V</a>], for instance, analyze the |
| 843 |
advantages of hierarchical naming for vehicular traffic information |
| 844 |
dissemination. Arnould et al. [<a href="#ref-CCNHV" title=""A Self-Organizing Content Centric Network Model for Hybrid Vehicular Ad-Hoc Networks"">CCNHV</a>] apply ICN principles to safety |
| 845 |
information dissemination between vehicles with multiple radio |
| 846 |
interfaces. In [<a href="#ref-CCDIVN" title=""A Content Centric Approach to Dissemination of Information in Vehicular Networks"">CCDIVN</a>], TalebiFard and Leung use network coding |
| 847 |
techniques to improve content dissemination over multiple ICN paths. |
| 848 |
Amadeo et al. [<a href="#ref-CCNVANET" title=""Content-Centric Networking: is that a Solution for Upcoming Vehicular Networks?"">CCNVANET</a>] [<a href="#ref-CRoWN" title=""CRoWN: Content-Centric Networking in Vehicular Ad Hoc Networks"">CRoWN</a>] propose an application-independent |
| 849 |
ICN framework for content retrieval and distribution where the role |
| 850 |
of provider can be played equivalently by both vehicles and RSUs. |
| 851 |
ICN forwarding is extended through path-state information carried in |
| 852 |
Interest and Data packets, stored in a new data structure kept by |
| 853 |
vehicular nodes, and exploited also to cope with node mobility. |
| 854 |
|
| 855 |
Typical scenarios for testing content distribution in VANETs may be |
| 856 |
highways with vehicles moving in straight lines, with or without RSUs |
| 857 |
along the road, as shown in Figure 4. With an NDN approach in mind, |
| 858 |
for example, RSUs may send Interest packets to collect data from |
| 859 |
vehicles [<a href="#ref-DMND" title=""DMND: Collecting data from mobiles using Named Data"">DMND</a>], or vehicles may send Interest packets to collect |
| 860 |
data from other peers [<a href="#ref-RTIND" title=""Rapid Traffic Information Dissemination Using Named Data"">RTIND</a>] or from RSUs [<a href="#ref-CCNVANET" title=""Content-Centric Networking: is that a Solution for Upcoming Vehicular Networks?"">CCNVANET</a>]. Figure 2 |
| 861 |
applies to content dissemination in VANET scenarios as well, where C0 |
| 862 |
represents a vehicle that can obtain named information objects via |
| 863 |
multiple wireless peers and/or RSUs (I2 and I3 in the figure). Grid |
| 864 |
topologies such as the one illustrated in Figure 3 should be |
| 865 |
considered in urban scenarios with RSUs at the crossroads or |
| 866 |
co-located with traffic lights as in [<a href="#ref-CRoWN" title=""CRoWN: Content-Centric Networking in Vehicular Ad Hoc Networks"">CRoWN</a>]. |
| 867 |
|
| 868 |
\___/ \___/ |
| 869 |
|RSU| |RSU| |
| 870 |
================================ |
| 871 |
_ _ _ _ |
| 872 |
/_\ /_\ /_\ /_\ |
| 873 |
_ _ o_o_ _o_o_ _o_o_ _o_o_ _ _ _ |
| 874 |
_ _ _ _ |
| 875 |
/_\ /_\ /_\ /_\ |
| 876 |
o o o o o o o o |
| 877 |
================================ |
| 878 |
|
| 879 |
Figure 4. Highway VANET Topology |
| 880 |
|
| 881 |
To summarize, VANET scenarios aim to exercise ICN deployment from |
| 882 |
various perspectives, including scalability, caching, transport, and |
| 883 |
mobility issues. There is a need for further investigation in (i) |
| 884 |
challenging scenarios (e.g., disconnected segments); (ii) scenarios |
| 885 |
involving both consumer and provider mobility; (iii) smart caching |
| 886 |
techniques that take into consideration node mobility patterns, |
| 887 |
spatial and temporal relevance, content popularity, and social |
| 888 |
relationships between users/vehicles; (iv) identification of new |
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Pentikousis, et al. Informational [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 895 |
|
| 896 |
|
| 897 |
applications (beyond data dissemination and traffic monitoring) that |
| 898 |
could benefit from the adoption of an ICN paradigm in vehicular |
| 899 |
networks (e.g., mobile cloud, social networking). |
| 900 |
|
| 901 |
<span class="h3"><a class="selflink" id="section-2.7" href="#section-2.7">2.7</a>. Delay- and Disruption-Tolerance</span> |
| 902 |
|
| 903 |
Delay- and Disruption-Tolerant Networking (DTN) originated as a means |
| 904 |
to extend the Internet to interplanetary communications [<a href="#ref-DTN" title=""A delay-tolerant network architecture for challenged internets"">DTN</a>]. |
| 905 |
However, it was subsequently found to be an appropriate architecture |
| 906 |
for many terrestrial situations as well. Typically, this was where |
| 907 |
delays were greater than protocols such as TCP could handle, and |
| 908 |
where disruptions to communications were the norm rather than |
| 909 |
occasional annoyances, e.g., where an end-to-end path does not |
| 910 |
necessarily exist when communication is initiated. DTN has now been |
| 911 |
applied to many situations, including opportunistic content sharing, |
| 912 |
handling infrastructural issues during emergency situations (e.g., |
| 913 |
earthquakes) and providing connectivity to remote rural areas without |
| 914 |
existing Internet provision and little or no communications or power |
| 915 |
infrastructure. |
| 916 |
|
| 917 |
The DTN architecture [<a href="./rfc4838" title=""Delay-Tolerant Networking Architecture"">RFC4838</a>] is based on a "store, carry, and |
| 918 |
forward" paradigm that has been applied extensively to situations |
| 919 |
where data is carried between network nodes by a "data mule", which |
| 920 |
carries bundles of data stored in some convenient storage medium |
| 921 |
(e.g., a USB memory stick). With the advent of sensor and peer-to- |
| 922 |
peer (P2P) networks between mobile nodes, DTN is becoming a more |
| 923 |
commonplace type of networking than originally envisioned. Since ICN |
| 924 |
also does not rely on the familiar end-to-end communications |
| 925 |
paradigm, there are clear synergies [<a href="#ref-DTNICN" title=""Towards an Information-Centric Delay-Tolerant Network"">DTNICN</a>]. It could therefore be |
| 926 |
argued that many of the key principles embodied within DTN also exist |
| 927 |
in ICN, as we explain next. |
| 928 |
|
| 929 |
First, both approaches rely on in-network storage. In the case of |
| 930 |
DTN, bundles are stored temporarily on devices on a hop-by-hop basis. |
| 931 |
In the case of ICN, information objects are also cached on devices in |
| 932 |
a similar fashion. As such, both paradigms must provision storage |
| 933 |
within the network. |
| 934 |
|
| 935 |
Second, both approaches espouse late binding of names to locations |
| 936 |
due to the potentially large interval between request and response |
| 937 |
generation. In the case of DTN, it is often impossible to predict |
| 938 |
the exact location (in a disconnected topology) where a node will be |
| 939 |
found. Similarly, in the case of ICN, it is also often impossible to |
| 940 |
predict where an information object might be found. As such, the |
| 941 |
binding of a request/bundle to a destination (or routing locator) |
| 942 |
must be performed as late as possible. |
| 943 |
|
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Pentikousis, et al. Informational [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 951 |
|
| 952 |
|
| 953 |
Finally, both approaches treat data as a long-lived component that |
| 954 |
can exist in the network for extended periods of time. In the case |
| 955 |
of DTN, bundles are carried by nodes until appropriate next hops are |
| 956 |
discovered. In the case of ICN, information objects are typically |
| 957 |
cached until storage is exhausted. As such, both paradigms require a |
| 958 |
direct shift in the way applications interact with the network. |
| 959 |
|
| 960 |
Through these similarities, it becomes possible to identify many DTN |
| 961 |
principles that are already in existence within ICN architectures. |
| 962 |
For example, ICN nodes will often retain information objects locally, |
| 963 |
making them accessible later on, much as DTN bundles are handled. |
| 964 |
Consequently, these synergies suggest strong potential for marrying |
| 965 |
the two technologies. This could include, for instance, building new |
| 966 |
integrated Information-Centric Delay Tolerant Network (ICDTN) |
| 967 |
protocols or, alternatively, building ICN schemes over existing DTN |
| 968 |
protocols (and vice versa). |
| 969 |
|
| 970 |
The above similarities suggest that integration of the two principles |
| 971 |
would be feasible. Beyond this, there are also a number of |
| 972 |
identifiable direct benefits. Through caching and replication, ICN |
| 973 |
offers strong information resilience, whilst, through store-and- |
| 974 |
forward, DTN offers strong connectivity resilience. As such, both |
| 975 |
architectures could benefit greatly from each other. Initial steps |
| 976 |
have already been taken in the DTN community to integrate ICN |
| 977 |
principles, e.g., the Bundle Protocol Query Block [<a href="#ref-BPQ" title=""Bundle Protocol Query Extension Block"">BPQ</a>] has been |
| 978 |
proposed for the DTN Bundle Protocol [<a href="./rfc5050" title=""Bundle Protocol Specification"">RFC5050</a>]. Similarly, initial |
| 979 |
steps have also been taken in the ICN community, such as [<a href="#ref-SLINKY" title=""Slinky: An adaptive protocol for content access in disruption- tolerant ad hoc networks"">SLINKY</a>]. |
| 980 |
In fact, the Scalable and Adaptive Internet Solutions (SAIL) project |
| 981 |
has developed a prototype implementation of NetInf running over the |
| 982 |
DTN Bundle Protocol. |
| 983 |
|
| 984 |
Of course, in many circumstances, information-centricity is not |
| 985 |
appropriate for use in delay- and disruption-tolerant environments. |
| 986 |
This is particularly the case when information is not the key |
| 987 |
communications atom transmitted. Further, situations where a single |
| 988 |
sink is always used for receiving information may not warrant the |
| 989 |
identification and routing of independent information objects. |
| 990 |
However, there are a number of key scenarios where clear benefits |
| 991 |
could be gained by introducing information-centric principles into |
| 992 |
DTNs, two of which we describe later in this section. |
| 993 |
|
| 994 |
For the purpose of evaluating the use of ICNs in a DTN setting, two |
| 995 |
key scenarios are identified in this document. (Note the rest of |
| 996 |
this section uses the term "ICDTN".) These are both prominent use |
| 997 |
cases that are currently active in both the ICN and DTN communities. |
| 998 |
The first is opportunistic content sharing, whilst the second is the |
| 999 |
use of ad hoc networks during disaster recovery (e.g., earthquakes). |
| 1000 |
We discuss both types of scenarios in the context of a simulation- |
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Pentikousis, et al. Informational [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
based evaluation: due to the scale and mobility of DTN-like setups, |
| 1010 |
this is the primary method of evaluation used. Within the DTN |
| 1011 |
community, the majority of simulations are performed using the |
| 1012 |
Opportunistic Network Environment (ONE) simulator [<a href="#ref-ONE" title=""The Opportunistic Network Environment simulator"">ONE</a>], which is |
| 1013 |
referred to in this document. Before exploring the two scenarios, |
| 1014 |
the key shared components of their simulation are discussed. This is |
| 1015 |
separated into the two primary inputs that are required: the |
| 1016 |
environment and the workload. |
| 1017 |
|
| 1018 |
In both types of scenarios the environment can be abstractly modeled |
| 1019 |
by a time series of active connections between device pairs. Unlike |
| 1020 |
other scenarios in this document, an ICDTN scenario therefore does |
| 1021 |
not depend on (relatively) static topologies but, rather, a set of |
| 1022 |
time-varying disconnected topologies. In opportunistic networks, |
| 1023 |
these topologies are actually products of the mobility of users. For |
| 1024 |
example, if two users walk past each other, an opportunistic link can |
| 1025 |
be created. There are two methods used to generate these mobility |
| 1026 |
patterns and, in turn, the time series of topologies. The first is |
| 1027 |
synthetic, whereby a (mathematical) model of user behavior is created |
| 1028 |
in an agent-based fashion, e.g., random waypoint, Gauss-Markov. The |
| 1029 |
second is trace-driven, whereby the mobility of real users is |
| 1030 |
recorded and used. In both cases, the output is a sequence of time- |
| 1031 |
stamped "contacts", i.e., periods of time in which two devices can |
| 1032 |
communicate. An important factor missing from typical mobility |
| 1033 |
traces, however, is the capacity of these contacts: how much data can |
| 1034 |
be transferred? In both approaches to modeling mobility, links are |
| 1035 |
usually configured as Bluetooth or Wi-Fi (ONE easily allows this, |
| 1036 |
although lower-layer considerations are ignored, e.g., interference). |
| 1037 |
This is motivated by the predominance of these technologies on mobile |
| 1038 |
phones. |
| 1039 |
|
| 1040 |
The workload in an ICDTN is modeled much like the workload within the |
| 1041 |
other scenarios. It involves object creation/placement and object |
| 1042 |
retrieval. Object creation/placement can either be done statically |
| 1043 |
at the beginning of the simulations or, alternatively, dynamically |
| 1044 |
based on a model of user behavior. In both cases, the latter is |
| 1045 |
focused on, as it models far better the characteristics of the |
| 1046 |
scenarios. |
| 1047 |
|
| 1048 |
Once the environment and workload have been configured, the next step |
| 1049 |
is to decide the key metrics for the study. Unlike traditional |
| 1050 |
networking, the QoS expectation is typically far lower in an ICDTN, |
| 1051 |
thereby moving away from metrics such as throughput. At a high |
| 1052 |
level, it is of clear interest to evaluate different ICN approaches |
| 1053 |
with respect to both their delay- and disruption-tolerance (i.e., how |
| 1054 |
effective is the approach when used in an environment subject to |
| 1055 |
significant delay and/or disruption) and to their active support for |
| 1056 |
operations in a DTN environment. |
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Pentikousis, et al. Informational [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
The two most prominent metrics considered in a host-centric DTN are |
| 1066 |
delivery probability and delivery delay. The former relates to the |
| 1067 |
probability by which a sent message will be received within a certain |
| 1068 |
delay bound, whilst the latter captures the average length of time it |
| 1069 |
takes for nodes to receive the message. These metrics are similarly |
| 1070 |
important in an ICDTN, although they are slightly different due to |
| 1071 |
the request-response nature of ICN. Therefore, the two most |
| 1072 |
prominent evaluative metrics are satisfaction probability and |
| 1073 |
satisfaction delay. The former refers to the probability by which an |
| 1074 |
information request (e.g., Interest) will be satisfied (i.e., how |
| 1075 |
often a Data response will be received). Satisfaction delay refers |
| 1076 |
to the length of time it takes an information request to be |
| 1077 |
satisfied. |
| 1078 |
|
| 1079 |
Note that the key difference between the host-centric and |
| 1080 |
information-centric metrics is the need for a round-trip rather than |
| 1081 |
a one-way communication. Beyond this, depending on the focus of the |
| 1082 |
work, other elements that may be investigated include name |
| 1083 |
resolution, routing, and forwarding in disconnected parts of the |
| 1084 |
network; support for unidirectional links; number of round trips |
| 1085 |
needed to complete a data transfer; long-term content availability |
| 1086 |
(or resilience); efficiency in the face of disruption; and so on. It |
| 1087 |
is also important to weigh these performance metrics against the |
| 1088 |
necessary overheads. In the case of an ICDTN, this is generally |
| 1089 |
measured by the number of message replicas required to access |
| 1090 |
content. Note that routing in a DTN is often replication based, |
| 1091 |
which leads to many copies of the same message. |
| 1092 |
|
| 1093 |
<span class="h4"><a class="selflink" id="section-2.7.1" href="#section-2.7.1">2.7.1</a>. Opportunistic Content Sharing</span> |
| 1094 |
|
| 1095 |
The first key baseline scenario in this context is opportunistic |
| 1096 |
content sharing. This occurs when mobile nodes create opportunistic |
| 1097 |
links between each other to share content of interest. For example, |
| 1098 |
people riding on an underground train can pass news items between |
| 1099 |
their mobile phones. Equally, content generated on the phones (e.g., |
| 1100 |
tweets [<a href="#ref-TWIMIGHT" title=""Twitter in disaster mode: smart probing for opportunistic peers"">TWIMIGHT</a>]) could be stored for later forwarding (or even |
| 1101 |
forwarded amongst interested passengers on the train). Such |
| 1102 |
scenarios, clearly, must be based around either the altruistic or |
| 1103 |
incentivized interaction amongst users. The latter is a particularly |
| 1104 |
active area of research. These networks are often termed "pocket- |
| 1105 |
switched networks", as they are independently formed between the user |
| 1106 |
devices. Here, the evaluative scenario of ICDTN microblogging is |
| 1107 |
proposed. As previously discussed, the construction of such an |
| 1108 |
evaluative scenario requires a formalization of its environment and |
| 1109 |
workload. Fortunately, there exist a number of datasets that offer |
| 1110 |
exactly this information required for microblogging. |
| 1111 |
|
| 1112 |
|
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">Pentikousis, et al. Informational [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
In terms of the environment (i.e., mobility patterns), the Haggle |
| 1122 |
project produced contact traces based on conference attendees using |
| 1123 |
Bluetooth. These traces are best targeted at application scenarios |
| 1124 |
in which a small group of (50-100) people are in a relatively |
| 1125 |
confined space. In contrast, larger-scale traces are also available, |
| 1126 |
most notably MIT's Reality Mining project. These are better suited |
| 1127 |
for cases where longer-term movement patterns are of interest. |
| 1128 |
|
| 1129 |
The second input, workload, relates to the creation and consumption |
| 1130 |
of microblogs (e.g., tweets). This can be effectively captured |
| 1131 |
because subscriptions conveniently formalize who consumes what. For |
| 1132 |
bespoke purposes, specific data can be directly collected from |
| 1133 |
Twitter for trace-driven simulations. Several Twitter datasets are |
| 1134 |
already available to the community containing a variety of data, |
| 1135 |
ranging from Tweets to follower graphs. See |
| 1136 |
<<a href="http://www.tweetarchivist.com">http://www.tweetarchivist.com</a>> and |
| 1137 |
<<a href="http://socialcomputing.asu.edu/datasets/Twitter">http://socialcomputing.asu.edu/datasets/Twitter</a>>. These datasets |
| 1138 |
can therefore be used to extract information production, placement, |
| 1139 |
and consumption. |
| 1140 |
|
| 1141 |
<span class="h4"><a class="selflink" id="section-2.7.2" href="#section-2.7.2">2.7.2</a>. Emergency Support and Disaster Recovery</span> |
| 1142 |
|
| 1143 |
The second key baseline scenario in this context relates to the use |
| 1144 |
of ICDTNs in emergency scenarios. In these situations, it is typical |
| 1145 |
for infrastructure to be damaged or destroyed, leading to the |
| 1146 |
collapse of traditional forms of communications (e.g., cellular |
| 1147 |
telephone networks). This has been seen in the recent North Indian |
| 1148 |
flooding, as well as the 2011 Tohoku earthquake and tsunami. Power |
| 1149 |
problems often exacerbate the issue, with communication failures |
| 1150 |
lasting for days. Therefore, in order to address this, DTNs have |
| 1151 |
been used due to their high levels of resilience and independence |
| 1152 |
from fixed infrastructure. The most prominent use of DTNs in |
| 1153 |
disaster areas would be the dissemination of information, e.g., |
| 1154 |
warnings and evacuation maps. Unlike the previous scenario, it can |
| 1155 |
be assumed that certain users (e.g., emergency responders) are highly |
| 1156 |
altruistic. However, it is likely many other users (e.g., endangered |
| 1157 |
civilians) might become far more conservative in how they use their |
| 1158 |
devices for battery-conserving purposes. Here, we focus on the |
| 1159 |
dissemination of standard broadcast information that should be |
| 1160 |
received by all parties; generally, this is something led by |
| 1161 |
emergency responders. |
| 1162 |
|
| 1163 |
For the environmental setup, there are no commonly used mobility |
| 1164 |
traces for disaster zones, unlike in the previous scenario. This is |
| 1165 |
clearly due to the difficultly (near impossibility) of acquiring them |
| 1166 |
in a real setting. That said, various synthetic models are |
| 1167 |
available. The Post-Disaster Mobility Model [<a href="#ref-MODEL1" title=""A post-disaster mobility model for Delay Tolerant Networking"">MODEL1</a>] models |
| 1168 |
civilians and emergency responders after a disaster has occurred, |
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">Pentikousis, et al. Informational [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
with people attempting to reach evacuation points (this has also been |
| 1178 |
implemented in the ONE simulator). Aschenbruck et al. [<a href="#ref-MODEL2" title=""Modeling mobility in disaster area scenarios"">MODEL2</a>] focus |
| 1179 |
on emergency responders, featuring the removal of nodes from the |
| 1180 |
disaster zone, as well as things like obstacles (e.g., collapsed |
| 1181 |
buildings). Cabrero et al. [<a href="#ref-MODEL3" title=""An Overlay Routing Protocol for Video over sparse MANETs in Emergencies"">MODEL3</a>] also look at emergency |
| 1182 |
responders but focus on patterns associated with common procedures. |
| 1183 |
For example, command and control centers are typically set up with |
| 1184 |
emergency responders periodically returning. Clearly, the mobility |
| 1185 |
of emergency responders is particularly important in this setting |
| 1186 |
because they usually are the ones who will "carry" information into |
| 1187 |
the disaster zone. It is recommended that one of these emergency- |
| 1188 |
specific models be used during any evaluations, due to the inaccuracy |
| 1189 |
of alternate models used for "normal" behavior. |
| 1190 |
|
| 1191 |
The workload input in this evaluative scenario is far simpler than |
| 1192 |
for the previous scenario. In emergency cases, the dissemination of |
| 1193 |
individual pieces of information to all parties is the norm. This is |
| 1194 |
often embodied using things like the Common Alert Protocol (CAP), |
| 1195 |
which is an XML standard for describing warning message. It is |
| 1196 |
currently used by various systems, including the Integrated Public |
| 1197 |
Alert & Warning System and Google Crisis Response. As such, small |
| 1198 |
objects (e.g., 512 KB to 2 MB) are usually generated containing text |
| 1199 |
and images; note that the ONE simulator offers utilities to easily |
| 1200 |
generate these. These messages are also always generated by central |
| 1201 |
authorities, therefore making the placement problem easier (they |
| 1202 |
would be centrally generated and given to emergency responders to |
| 1203 |
disseminate as they pass through the disaster zone). The key |
| 1204 |
variable is therefore the generation rate, which is synonymous with |
| 1205 |
the rate that microblogs are written in the previous scenario. This |
| 1206 |
will largely be based on the type of disaster occurring; however, |
| 1207 |
hourly updates would be an appropriate configuration. Higher rates |
| 1208 |
can also be tested, based on the rate at which situations change |
| 1209 |
(landslides, for example, can exhibit highly dynamic properties). |
| 1210 |
|
| 1211 |
To summarize, this section has highlighted the applicability of ICN |
| 1212 |
principles to existing DTN scenarios. Two evaluative setups have |
| 1213 |
been described in detail, namely, mobile opportunistic content |
| 1214 |
sharing (microblogging) and emergency information dissemination. |
| 1215 |
|
| 1216 |
<span class="h3"><a class="selflink" id="section-2.8" href="#section-2.8">2.8</a>. Internet of Things</span> |
| 1217 |
|
| 1218 |
Advances in electronics miniaturization combined with low-power |
| 1219 |
wireless access technologies (e.g., ZigBee, Near Field Communication |
| 1220 |
(NFC), Bluetooth, and others) have enabled the coupling of |
| 1221 |
interconnected digital services with everyday objects. As devices |
| 1222 |
with sensors and actuators connect into the network, they become |
| 1223 |
"smart objects" and form the foundation for the so-called Internet of |
| 1224 |
|
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">Pentikousis, et al. Informational [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
Things (IoT). IoT is expected to increase significantly the amount |
| 1234 |
of content carried by the network due to machine-to-machine (M2M) |
| 1235 |
communication as well as novel user-interaction possibilities. |
| 1236 |
|
| 1237 |
Yet, the full potential of IoT does not lie in simple remote access |
| 1238 |
to smart object data. Instead, it is the intersection of Internet |
| 1239 |
services with the physical world that will bring about the most |
| 1240 |
dramatic changes. Burke [<a href="#ref-IoTEx" title=""Authoring Place-based Experiences with an Internet of Things: Tussles of Expressive, Operational, and Participatory Goals"">IoTEx</a>], for instance, makes a very good |
| 1241 |
case for creating everyday experiences using interconnected things |
| 1242 |
through participatory sensing applications. In this case, inherent |
| 1243 |
ICN capabilities for data discovery, caching, and trusted |
| 1244 |
communication are leveraged to obtain sensor information and enable |
| 1245 |
content exchange between mobile users, repositories, and |
| 1246 |
applications. |
| 1247 |
|
| 1248 |
Kutscher and Farrell [<a href="#ref-IWMT" title=""Towards an Information- Centric Internet with more Things"">IWMT</a>] discuss the benefits that ICN can provide |
| 1249 |
in these environments in terms of naming, caching, and optimized |
| 1250 |
transport. The Named Information URI scheme (ni) [<a href="./rfc6920" title=""Naming Things with Hashes"">RFC6920</a>], for |
| 1251 |
instance, could be used for globally unique smart object |
| 1252 |
identification, although an actual implementation report is not |
| 1253 |
currently available. Access to information generated by smart |
| 1254 |
objects can be of varied nature and often vital for the correct |
| 1255 |
operation of large systems. As such, supporting timestamping, |
| 1256 |
security, scalability, and flexibility need to be taken into account. |
| 1257 |
|
| 1258 |
Ghodsi et al. [<a href="#ref-NCOA" title=""Naming in Content-oriented Architectures"">NCOA</a>] examine hierarchical and self-certifying naming |
| 1259 |
schemes and point out that ensuring reliable and secure content |
| 1260 |
naming and retrieval may pose stringent requirements (e.g., the |
| 1261 |
necessity for employing PKI), which can be too demanding for low- |
| 1262 |
powered nodes, such as sensors. That said, earlier work by Heidemann |
| 1263 |
et al. [<a href="#ref-nWSN" title=""Building efficient wireless sensor networks with low-level naming"">nWSN</a>] shows that, for dense sensor network deployments, |
| 1264 |
disassociating sensor naming from network topology and using named |
| 1265 |
content at the lowest level of communication in combination with in- |
| 1266 |
network processing of sensor data is feasible in practice and can be |
| 1267 |
more efficient than employing a host-centric binding between node |
| 1268 |
locator and the content existing therein. |
| 1269 |
|
| 1270 |
Burke et al. [<a href="#ref-NDNl" title=""Authenticated Lighting Control Using Named Data Networking"">NDNl</a>] describe the implementation of a building |
| 1271 |
automation system for lighting control where the security, naming, |
| 1272 |
and device discovery NDN mechanisms are leveraged to provide |
| 1273 |
configuration, installation, and management of residential and |
| 1274 |
industrial lighting control systems. The goal is an inherently |
| 1275 |
resilient system, where even smartphones can be used for control. |
| 1276 |
Naming reflects fixtures with evolved identification and node- |
| 1277 |
reaching capabilities, thus simplifying bootstrapping, discovery, and |
| 1278 |
user interaction with nodes. The authors report that this ICN-based |
| 1279 |
system requires less maintenance and troubleshooting than typical |
| 1280 |
IP-based alternatives. |
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
<span class="grey">Pentikousis, et al. Informational [Page 23]</span></pre> |
| 1285 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1286 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
Biswas et al. [<a href="#ref-CIBUS" title=""Contextualized Information-Centric Home Network"">CIBUS</a>] visualize ICN as a contextualized information- |
| 1290 |
centric bus (CIBUS) over which diverse sets of service producers and |
| 1291 |
consumers coexist with different requirements. ICN is leveraged to |
| 1292 |
unify different platforms to serve consumer-producer interaction in |
| 1293 |
both infrastructure and ad hoc settings. Ravindran et al. [<a href="#ref-Homenet" title=""Information-centric Networking based Homenet"">Homenet</a>] |
| 1294 |
show the application of this idea in the context of a home network, |
| 1295 |
where consumers (residents) require policy-driven interactions with |
| 1296 |
diverse services such as climate control, surveillance systems, and |
| 1297 |
entertainment systems. Name-based protocols are developed to enable |
| 1298 |
zero-configuration node and service discovery, contextual service |
| 1299 |
publishing and subscription, policy-based routing and forwarding with |
| 1300 |
name-based firewall, and hoc device-to-device communication. |
| 1301 |
|
| 1302 |
IoT exposes ICN concepts to a stringent set of requirements that are |
| 1303 |
exacerbated by the quantity of nodes, as well as by the type and |
| 1304 |
volume of information that must be handled. A way to address this is |
| 1305 |
proposed in [<a href="#ref-IoTScope" title=""Efficient information lookup for the Internet of Things"">IoTScope</a>], which tackles the problem of mapping named |
| 1306 |
information to an object, diverting from the currently typical |
| 1307 |
centralized discovery of services and leveraging the intrinsic ICN |
| 1308 |
scalability capabilities for naming. It extends the base [<a href="#ref-PURSUIT" title=""Developing Information Networking Further: From PSIRP to PURSUIT"">PURSUIT</a>] |
| 1309 |
design with hierarchically based scopes, facilitating lookup, access, |
| 1310 |
and modifications of only the part of the object information that the |
| 1311 |
user is interested in. Another important aspect is how to |
| 1312 |
efficiently address resolution and location of the information |
| 1313 |
objects, particularly when large numbers of nodes are connected, as |
| 1314 |
in IoT deployments. In [<a href="#ref-ICN-DHT" title=""On inter-domain name resolution for information-centric networks"">ICN-DHT</a>], Katsaros et al. propose a |
| 1315 |
Distributed Hash Table (DHT) that is compared with the Data-Oriented |
| 1316 |
Network Architecture described in [<a href="#ref-DONA" title=""A Data-Oriented (and Beyond) Network Architecture"">DONA</a>]. Their results show how |
| 1317 |
topological routing information has a positive impact on resolution, |
| 1318 |
at the expense of memory and processing overhead. |
| 1319 |
|
| 1320 |
The use of ICN mechanisms in IoT scenarios faces the most dynamic and |
| 1321 |
heterogeneous type of challenges, when taking into consideration the |
| 1322 |
requirements and objectives of such integration. The disparity in |
| 1323 |
technologies (not only in access technologies, but also in terms of |
| 1324 |
end-node diversity such as sensors, actuators, and their |
| 1325 |
characteristics) as well as in the information that is generated and |
| 1326 |
consumed in such scenarios, will undoubtedly bring about many of the |
| 1327 |
considerations presented in the previous sections. For instance, IoT |
| 1328 |
shares similarities with the constraints and requirements applicable |
| 1329 |
to vehicular networking. Here, a central problem is the deployment |
| 1330 |
of mechanisms that can use opportunistic connectivity in unreliable |
| 1331 |
networking environments (similar to the vehicular networking and DTN |
| 1332 |
scenarios). |
| 1333 |
|
| 1334 |
However, one important concern in IoT scenarios, also motivated by |
| 1335 |
this strongly heterogeneous environment, is how content dissemination |
| 1336 |
will be affected by the different semantics of the disparate |
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
<span class="grey">Pentikousis, et al. Informational [Page 24]</span></pre> |
| 1341 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span> |
| 1342 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 1343 |
|
| 1344 |
|
| 1345 |
information and content being shared. In fact, this is already a |
| 1346 |
difficult problem that goes beyond the scope of ICN [<a href="#ref-SEMANT" title=""Semantic Sensor Web,"">SEMANT</a>]. With |
| 1347 |
the ability of the network nodes to cache forwarded information to |
| 1348 |
improve future requests, a challenge arises regarding whether the ICN |
| 1349 |
fabric should be involved in any kind of procedure (e.g., tagging) |
| 1350 |
that facilitates the relationship or the interpretation of the |
| 1351 |
different sources of information. |
| 1352 |
|
| 1353 |
Another issue lies with the need for having energy-efficiency |
| 1354 |
mechanisms related to the networking capabilities of IoT |
| 1355 |
infrastructures. Often, the devices in IoT deployments have limited |
| 1356 |
battery capabilities, and thus need low power consumption schemes |
| 1357 |
working at multiple levels. In principle, energy efficiency gains |
| 1358 |
should be observed from the inherent in-network caching capability. |
| 1359 |
However, this might not be the most usual case in IoT scenarios, |
| 1360 |
where the information (particularly from sensors or controlling |
| 1361 |
actuators) is more akin to real-time traffic, thus reducing the scale |
| 1362 |
of potential savings due to ubiquitous in-network caching. |
| 1363 |
|
| 1364 |
ICN approaches, therefore, should be evaluated with respect to their |
| 1365 |
capacity to handle the content produced and consumed by extremely |
| 1366 |
large numbers of diverse devices. IoT scenarios aim to exercise ICN |
| 1367 |
deployment from different aspects, including ICN node design |
| 1368 |
requirements, efficient naming, transport, and caching of time- |
| 1369 |
restricted data. Scalability is particularly important in this |
| 1370 |
regard as the successful deployment of IoT principles could increase |
| 1371 |
both device and content numbers dramatically beyond all current |
| 1372 |
expectations. |
| 1373 |
|
| 1374 |
<span class="h3"><a class="selflink" id="section-2.9" href="#section-2.9">2.9</a>. Smart City</span> |
| 1375 |
|
| 1376 |
The rapid increase in urbanization sets the stage for the most |
| 1377 |
compelling and challenging environments for networking. By 2050 the |
| 1378 |
global population will reach nine billion people, 75% of which will |
| 1379 |
dwell in urban areas. In order to cope with this influx, many cities |
| 1380 |
around the world have started their transformation toward the "smart |
| 1381 |
city" vision. Smart cities will be based on the following innovation |
| 1382 |
axes: smart mobility, smart environment, smart people, smart living, |
| 1383 |
and smart governance. In development terms, the core goal of a smart |
| 1384 |
city is to become a business-competitive and attractive environment, |
| 1385 |
while serving citizen well-being [<a href="#ref-CPG" title=""Content Centric Services in Smart Cities"">CPG</a>]. |
| 1386 |
|
| 1387 |
In a smart city, ICT plays a leading role and acts as the glue |
| 1388 |
bringing together all actors, services, resources (and their |
| 1389 |
interrelationships) that the urban environment is willing to host and |
| 1390 |
provide [<a href="#ref-MVM" title=""Smart cities at the forefront of the future Internet"">MVM</a>]. ICN appears particularly suitable for these |
| 1391 |
scenarios. Domains of interest include intelligent transportation |
| 1392 |
systems, energy networks, health care, A/V communications, peer-to- |
| 1393 |
|
| 1394 |
|
| 1395 |
|
| 1396 |
<span class="grey">Pentikousis, et al. Informational [Page 25]</span></pre> |
| 1397 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span> |
| 1398 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 1399 |
|
| 1400 |
|
| 1401 |
peer and collaborative platforms for citizens, social inclusion, |
| 1402 |
active participation in public life, e-government, safety and |
| 1403 |
security, and sensor networks. Clearly, this scenario has close ties |
| 1404 |
to the vision of IoT, discussed in the previous section, as well as |
| 1405 |
to vehicular networking. |
| 1406 |
|
| 1407 |
Nevertheless, the road to build a real information-centric digital |
| 1408 |
ecosystem will be long, and more coordinated effort is required to |
| 1409 |
drive innovation in this domain. We argue that smart-city needs and |
| 1410 |
ICN technologies can trigger a virtuous innovation cycle toward |
| 1411 |
future ICT platforms. Recent concrete ICN-based contributions have |
| 1412 |
been formulated for home energy management [<a href="#ref-iHEMS" title=""iHEMS: An Information-Centric Approach to Secure Home Energy Management"">iHEMS</a>], geo-localized |
| 1413 |
services [<a href="#ref-ACC" title=""A scalable architecture for geo- localized service access in smart cities"">ACC</a>], smart-city services [<a href="#ref-IB" title=""A Development Framework for Smart City Services, Integrating Smart City Service Components"">IB</a>], and traffic information |
| 1414 |
dissemination in vehicular scenarios [<a href="#ref-RTIND" title=""Rapid Traffic Information Dissemination Using Named Data"">RTIND</a>]. Some of the proposed |
| 1415 |
ICN-based solutions are implemented in real testbeds, while others |
| 1416 |
are evaluated through simulation. |
| 1417 |
|
| 1418 |
Zhang et al. [<a href="#ref-iHEMS" title=""iHEMS: An Information-Centric Approach to Secure Home Energy Management"">iHEMS</a>] propose a secure publish-subscribe architecture |
| 1419 |
for handling the communication requirements of Home Energy Management |
| 1420 |
Systems (HEMS). The objective is to safely and effectively collect |
| 1421 |
measurement and status information from household elements, aggregate |
| 1422 |
and analyze the data, and ultimately enable intelligent control |
| 1423 |
decisions for actuation. They consider a simple experimental testbed |
| 1424 |
for their proof-of-concept evaluation, exploiting open source code |
| 1425 |
for the ICN implementation, and emulating some node functionality in |
| 1426 |
order to facilitate system operation. |
| 1427 |
|
| 1428 |
A different scenario is considered in [<a href="#ref-ACC" title=""A scalable architecture for geo- localized service access in smart cities"">ACC</a>], where DHTs are employed |
| 1429 |
for distributed, scalable, and geographically aware service lookup in |
| 1430 |
a smart city. Also in this case, the ICN application is validated by |
| 1431 |
considering a small-scale testbed: a small number of nodes are |
| 1432 |
emulated with simple embedded PCs or specific hardware boards (e.g., |
| 1433 |
for some sensor nodes); other nodes (which connect the principal |
| 1434 |
actors of the tests) are emulated with workstations. The proposal in |
| 1435 |
[<a href="#ref-IB" title=""A Development Framework for Smart City Services, Integrating Smart City Service Components"">IB</a>] draws from a smart-city scenario (mainly oriented towards waste |
| 1436 |
collection management) comprising sensors and moving vehicles, as |
| 1437 |
well as a cloud-computing system that supports data retrieval and |
| 1438 |
storage operations. The main aspects of this proposal are analyzed |
| 1439 |
via simulation using open source code that is publicly available. |
| 1440 |
Some software applications are designed on real systems (e.g., PCs |
| 1441 |
and smartphones). |
| 1442 |
|
| 1443 |
With respect to evaluating ICN approaches in smart-city scenarios, it |
| 1444 |
is necessary to consider generic metrics useful to track and monitor |
| 1445 |
progress on services results and also for comparing localities |
| 1446 |
between themselves and learn from the best [<a href="#ref-ISODIS" title=""Sustainable development and resilience of communities --Indicators for city services and quality of life"">ISODIS</a>]. In particular, |
| 1447 |
it is possible to select a specific set of Key Performance Indicators |
| 1448 |
(KPIs) for a given project in order to evaluate its success. These |
| 1449 |
|
| 1450 |
|
| 1451 |
|
| 1452 |
<span class="grey">Pentikousis, et al. Informational [Page 26]</span></pre> |
| 1453 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span> |
| 1454 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 1455 |
|
| 1456 |
|
| 1457 |
KPIs may reflect the city's environmental and social goals, as well |
| 1458 |
as its economic objectives, and they can be calculated at the global, |
| 1459 |
regional, national, and local levels. Therefore, it is not possible |
| 1460 |
to define a unique set of interesting metrics, but in the context of |
| 1461 |
smart cities, the KPIs should be characterized with respect to the |
| 1462 |
developed set of services offered by using the ICN paradigm. |
| 1463 |
|
| 1464 |
To sum up, smart-city scenarios aim to exercise several ICN aspects |
| 1465 |
in an urban environment. In particular, they can be useful to (i) |
| 1466 |
analyze the capacity of using ICN for managing extremely large data |
| 1467 |
sets; (ii) study ICN performance in terms of scalability in |
| 1468 |
distributed services; (iii) verify the feasibility of ICN in a very |
| 1469 |
complex application like vehicular communication systems; and (iv) |
| 1470 |
examine the possible drawbacks related to privacy and security issues |
| 1471 |
in complex networked environments. |
| 1472 |
|
| 1473 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Cross-Scenario Considerations</span> |
| 1474 |
|
| 1475 |
This section discusses considerations that span multiple scenarios. |
| 1476 |
|
| 1477 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Multiply Connected Nodes and Economics</span> |
| 1478 |
|
| 1479 |
The evolution of, in particular, wireless networking technologies has |
| 1480 |
resulted in a convergence of the bandwidth and capabilities of |
| 1481 |
various different types of network. Today, a leading-edge mobile |
| 1482 |
telephone or tablet computer will typically be able to access a Wi-Fi |
| 1483 |
access point, a 4G cellular network, and the latest generation of |
| 1484 |
Bluetooth local networking. Until recently, a node would usually |
| 1485 |
have a clear favorite network technology appropriate to any given |
| 1486 |
environment. The choice would, for example, be primarily determined |
| 1487 |
by the available bandwidth with cost as a secondary determinant. |
| 1488 |
Furthermore, it is normally the case that a device only uses one of |
| 1489 |
the technologies at a time for any particular application. |
| 1490 |
|
| 1491 |
It seems likely that this situation will change so that nodes are |
| 1492 |
able to use all of the available technologies in parallel. This will |
| 1493 |
be further encouraged by the development of new capabilities in |
| 1494 |
cellular networks including Small Cell Networks [<a href="#ref-SCN" title=""Green small-cell networks"">SCN</a>] and |
| 1495 |
Heterogeneous Networks [<a href="#ref-HetNet" title=""Efficient HetNet implementation using broadband wireless access with fiber-connected massively distributed antennas architecture"">HetNet</a>]. Consequently, mobile devices will |
| 1496 |
have similar choices to wired nodes attached to multiple service |
| 1497 |
providers allowing "multihoming" via the various different |
| 1498 |
infrastructure networks as well as potential direct access to other |
| 1499 |
mobile nodes via Bluetooth or a more capable form of ad hoc Wi-Fi. |
| 1500 |
|
| 1501 |
Infrastructure networks are generally under the control of separate |
| 1502 |
economic entities that may have different policies about the |
| 1503 |
information of an ICN deployed within their network caches. As ICN |
| 1504 |
shifts the focus from nodes to information objects, the interaction |
| 1505 |
|
| 1506 |
|
| 1507 |
|
| 1508 |
<span class="grey">Pentikousis, et al. Informational [Page 27]</span></pre> |
| 1509 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span> |
| 1510 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 1511 |
|
| 1512 |
|
| 1513 |
between networks will likely evolve to capitalize on data location |
| 1514 |
independence, efficient and scalable in-network named object |
| 1515 |
availability, and access via multiple paths. These interactions |
| 1516 |
become critical in evaluating the technical and economic impact of |
| 1517 |
ICN architectural choices, as noted in [<a href="#ref-ArgICN" title=""Arguments for an information centric internetworking architecture"">ArgICN</a>]. Beyond simply |
| 1518 |
adding diversity in deployment options, these networks have the |
| 1519 |
potential to alter the incentives among existing (and future, we may |
| 1520 |
add) network players, as noted in [<a href="#ref-EconICN" title=""Economic Incentives in Information Centric Networking: Implications for Protocol Design and Public Policy"">EconICN</a>]. |
| 1521 |
|
| 1522 |
Moreover, such networks enable more numerous internetwork |
| 1523 |
relationships where exchange of information may be conditioned on a |
| 1524 |
set of multilateral policies. For example, shared SCNs are emerging |
| 1525 |
as a cost-effective way to address coverage of complex environments |
| 1526 |
such as sports stadiums, large office buildings, malls, etc. Such |
| 1527 |
networks are likely to be a complex mix of different cellular and |
| 1528 |
WLAN access technologies (such as HSPA, LTE, and Wi-Fi) as well as |
| 1529 |
ownership models. It is reasonable to assume that access to content |
| 1530 |
generated in such networks may depend on contextual information such |
| 1531 |
as the subscription type, timing, and location of both the owner and |
| 1532 |
requester of the content. The availability of such contextual |
| 1533 |
information across diverse networks can lead to network |
| 1534 |
inefficiencies unless data management can benefit from an |
| 1535 |
information-centric approach. The "Event with Large Crowds" |
| 1536 |
demonstrator created by the SAIL project investigated this kind of |
| 1537 |
scenario; more details are available in [<a href="#ref-SAIL-B3" title=""Final NetInf Architecture"">SAIL-B3</a>]. |
| 1538 |
|
| 1539 |
Jacobson et al. [<a href="#ref-CCN" title=""Networking Named Content"">CCN</a>] include interactions between networks in their |
| 1540 |
overall system design and mention both "an edge-driven, bottom-up |
| 1541 |
incentive structure" and techniques based on evolutions of existing |
| 1542 |
mechanisms both for ICN router discovery by the end-user and for |
| 1543 |
interconnecting between Autonomous Systems (ASes). For example, a |
| 1544 |
BGP extension for domain-level content prefix advertisement can be |
| 1545 |
used to enable efficient interconnection between ASes. Liu et al. |
| 1546 |
[<a href="#ref-MLDHT" title=""A multi-level DHT routing framework with aggregation"">MLDHT</a>] proposed to address the "suffix-hole" issue found in prefix- |
| 1547 |
based name aggregation through the use of a combination of Bloom- |
| 1548 |
filter-based aggregation and multi-level DHT. |
| 1549 |
|
| 1550 |
Name aggregation has been discussed for a flat naming design, for |
| 1551 |
example, in [<a href="#ref-NCOA" title=""Naming in Content-oriented Architectures"">NCOA</a>], in which the authors note that based on |
| 1552 |
estimations in [<a href="#ref-DONA" title=""A Data-Oriented (and Beyond) Network Architecture"">DONA</a>] flat naming may not require aggregation. This |
| 1553 |
is a point that calls for further study. Scenarios evaluating name |
| 1554 |
aggregation, or lack thereof, should take into account the amount of |
| 1555 |
state (e.g., size of routing tables) maintained in edge routers as |
| 1556 |
well as network efficiency (e.g., amount of traffic generated). |
| 1557 |
|
| 1558 |
|
| 1559 |
|
| 1560 |
|
| 1561 |
|
| 1562 |
|
| 1563 |
|
| 1564 |
<span class="grey">Pentikousis, et al. Informational [Page 28]</span></pre> |
| 1565 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span> |
| 1566 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 1567 |
|
| 1568 |
|
| 1569 |
+---------------+ |
| 1570 |
+---------->| Popular Video | |
| 1571 |
| +---------------+ |
| 1572 |
| ^ ^ |
| 1573 |
| | | |
| 1574 |
| +-+-+ $0/MB +-+-+ |
| 1575 |
| | A +-------+ B | |
| 1576 |
| ++--+ +-+-+ |
| 1577 |
| | ^ ^ | |
| 1578 |
| $8/MB | | | | $10/MB |
| 1579 |
| v | | v |
| 1580 |
+-+-+ $0/MB +--+---------+--+ |
| 1581 |
| D +---------+ C | |
| 1582 |
+---+ +---------------+ |
| 1583 |
|
| 1584 |
Figure 5. Relationships and Transit Costs between Networks A to D |
| 1585 |
|
| 1586 |
DiBenedetto et al. [<a href="#ref-RP-NDN" title=""Routing policies in named data networking"">RP-NDN</a>] study policy knobs made available by NDN |
| 1587 |
to network operators. New policies that are not feasible in the |
| 1588 |
current Internet are described, including a "cache sharing peers" |
| 1589 |
policy, where two peers have an incentive to share content cached in, |
| 1590 |
but not originating from, their respective network. The simple |
| 1591 |
example used in the investigation considers several networks and |
| 1592 |
associated transit costs, as shown in Figure 5 (based on Figure 1 of |
| 1593 |
[<a href="#ref-RP-NDN" title=""Routing policies in named data networking"">RP-NDN</a>]). Agyapong and Sirbu [<a href="#ref-EconICN" title=""Economic Incentives in Information Centric Networking: Implications for Protocol Design and Public Policy"">EconICN</a>] further establish that ICN |
| 1594 |
approaches should incorporate features that foster (new) business |
| 1595 |
relationships. For example, publishers should be able to indicate |
| 1596 |
their willingness to partake in the caching market, proper reporting |
| 1597 |
should be enabled to avoid fraud, and content should be made |
| 1598 |
cacheable as much as possible to increase cache hit ratios. |
| 1599 |
|
| 1600 |
Kutscher et al. [<a href="#ref-SAIL-B3" title=""Final NetInf Architecture"">SAIL-B3</a>] enable network interactions in the NetInf |
| 1601 |
architecture using a name resolution service at domain edge routers |
| 1602 |
and a BGP-like routing system in the NetInf Default-Free Zone. |
| 1603 |
Business models and incentives are studied in [<a href="#ref-SAIL-A7" title=""New business models and business dynamics of the future networks"">SAIL-A7</a>] and |
| 1604 |
[<a href="#ref-SAIL-A8" title=""Evaluation of business models"">SAIL-A8</a>], including scenarios where the access network provider (or |
| 1605 |
a virtual CDN) guarantees QoS to end users using ICN. Figure 6 |
| 1606 |
illustrates a typical scenario topology from this work that involves |
| 1607 |
an interconnectivity provider. |
| 1608 |
|
| 1609 |
|
| 1610 |
|
| 1611 |
|
| 1612 |
|
| 1613 |
|
| 1614 |
|
| 1615 |
|
| 1616 |
|
| 1617 |
|
| 1618 |
|
| 1619 |
|
| 1620 |
<span class="grey">Pentikousis, et al. Informational [Page 29]</span></pre> |
| 1621 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span> |
| 1622 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 1623 |
|
| 1624 |
|
| 1625 |
+----------+ +-----------------+ +------+ |
| 1626 |
| Content | | Access Network/ | | End | |
| 1627 |
| Provider +---->| ICN Provider +---->| User | |
| 1628 |
+----------+ +-+-------------+-+ +------+ |
| 1629 |
| | |
| 1630 |
| | |
| 1631 |
v v |
| 1632 |
+-------------------+ +----------------+ +------+ |
| 1633 |
| Interconnectivity | | Access Network | | End | |
| 1634 |
| Provider +---->| Provider +------>| User | |
| 1635 |
+-------------------+ +----------------+ +------+ |
| 1636 |
|
| 1637 |
Figure 6. Setup and Operating Costs of Network Entities |
| 1638 |
|
| 1639 |
Jokela et al. [<a href="#ref-LIPSIN" title=""LIPSIN: line speed publish/subscribe inter-networking"">LIPSIN</a>] propose a two-layer approach where additional |
| 1640 |
rendezvous systems and topology formation functions are placed |
| 1641 |
logically above multiple networks and enable advertising and routing |
| 1642 |
content between them. Visala et al. [<a href="#ref-LANES" title=""LANES: An Inter-Domain Data-Oriented Routing Architecture"">LANES</a>] further describe an ICN |
| 1643 |
architecture based on similar principles, which, notably, relies on a |
| 1644 |
hierarchical DHT-based rendezvous interconnect. Rajahalme et al. |
| 1645 |
[<a href="#ref-PSIRP1" title=""Inter-Domain Rendezvous Service Architecture"">PSIRP1</a>] describe a rendezvous system using both a BGP-like routing |
| 1646 |
protocol at the edge and a DHT-based overlay at the core. Their |
| 1647 |
evaluation model is centered around policy-compliant path stretch, |
| 1648 |
latency introduced by overlay routing, caching efficacy, and load |
| 1649 |
distribution. |
| 1650 |
|
| 1651 |
Rajahalme et al. [<a href="#ref-ICCP" title=""Incentive-Compatible Caching and Peering in Data-Oriented Networks"">ICCP</a>] point out that ICN architectural changes may |
| 1652 |
conflict with the current tier-based peering model. For example, |
| 1653 |
changes leading to shorter paths between ISPs are likely to meet |
| 1654 |
resistance from Tier-1 ISPs. Rajahalme [<a href="#ref-IDMcast" title=""Incentive-informed Inter-domain Multicast"">IDMcast</a>] shows how |
| 1655 |
incentives can help shape the design of specific ICN aspects, and in |
| 1656 |
[<a href="#ref-IDArch" title=""Inter-domain incentives and Internet architecture"">IDArch</a>] he presents a modeling approach to exploit these incentives. |
| 1657 |
This includes a network model that describes the relationship between |
| 1658 |
Autonomous Systems based on data inferred from the current Internet, |
| 1659 |
a traffic model taking into account business factors for each AS, and |
| 1660 |
a routing model integrating the valley-free model and policy |
| 1661 |
compliance. A typical scenario topology is illustrated in Figure 7, |
| 1662 |
which is redrawn here based on Figure 1 of [<a href="#ref-ICCP" title=""Incentive-Compatible Caching and Peering in Data-Oriented Networks"">ICCP</a>]. Note that it |
| 1663 |
relates well with the topology illustrated in Figure 1 of this |
| 1664 |
document. |
| 1665 |
|
| 1666 |
|
| 1667 |
|
| 1668 |
|
| 1669 |
|
| 1670 |
|
| 1671 |
|
| 1672 |
|
| 1673 |
|
| 1674 |
|
| 1675 |
|
| 1676 |
<span class="grey">Pentikousis, et al. Informational [Page 30]</span></pre> |
| 1677 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span> |
| 1678 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 1679 |
|
| 1680 |
|
| 1681 |
o-----o |
| 1682 |
+-----+ J +-----+ |
| 1683 |
| o--*--o | |
| 1684 |
| * | |
| 1685 |
o--+--o * o--+--o |
| 1686 |
| H +-----------+ I | |
| 1687 |
o-*-*-o * o-*-*-o |
| 1688 |
* * * * * |
| 1689 |
****** ******* * ******* ******* |
| 1690 |
* * * * * |
| 1691 |
o--*--o o*-*-*o o--*--o |
| 1692 |
| E +--------+ F +---------+ G + |
| 1693 |
o-*-*-o o-----o o-*-*-o |
| 1694 |
* * * * |
| 1695 |
****** ******* ****** ****** |
| 1696 |
* * * * |
| 1697 |
o--*--o o--*--o o--*--o o--*--o |
| 1698 |
| A | | B +-----------+ C | | D | |
| 1699 |
o-----o o--+--o o--+--o o----+o |
| 1700 |
| | ^^ | route |
| 1701 |
data | data | data || | to |
| 1702 |
| | || | data |
| 1703 |
o---v--o o---v--o o++--v-o |
| 1704 |
| User | | User | | Data | |
| 1705 |
o------o o------o o------o |
| 1706 |
|
| 1707 |
Legend: |
| 1708 |
***** Transit link |
| 1709 |
+---+ Peering link |
| 1710 |
+---> Data delivery or route to data |
| 1711 |
|
| 1712 |
Figure 7. Tier-Based Set of Interconnections between AS A to J |
| 1713 |
|
| 1714 |
To sum up, the evaluation of ICN architectures across multiple |
| 1715 |
network types should include a combination of technical and economic |
| 1716 |
aspects, capturing their various interactions. These scenarios aim |
| 1717 |
to illustrate scalability, efficiency, and manageability, as well as |
| 1718 |
traditional and novel network policies. Moreover, scenarios in this |
| 1719 |
category should specifically address how different actors have proper |
| 1720 |
incentives, not only in a pure ICN realm, but also during the |
| 1721 |
migration phase towards this final state. |
| 1722 |
|
| 1723 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Energy Efficiency</span> |
| 1724 |
|
| 1725 |
ICN has prominent features that can be taken advantage of in order to |
| 1726 |
significantly reduce the energy footprint of future communication |
| 1727 |
networks. Of course, one can argue that specific ICN network |
| 1728 |
elements may consume more energy than today's conventional network |
| 1729 |
|
| 1730 |
|
| 1731 |
|
| 1732 |
<span class="grey">Pentikousis, et al. Informational [Page 31]</span></pre> |
| 1733 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span> |
| 1734 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 1735 |
|
| 1736 |
|
| 1737 |
equipment due to the potentially higher energy demands for named-data |
| 1738 |
processing en route. On balance, however, ICN introduces an |
| 1739 |
architectural approach that may compensate on the whole and can even |
| 1740 |
achieve higher energy efficiency rates when compared to the host- |
| 1741 |
centric paradigm. |
| 1742 |
|
| 1743 |
We elaborate on the energy efficiency potential of ICN based on three |
| 1744 |
categories of ICN characteristics. Namely, we point out that a) ICN |
| 1745 |
does not rely solely on end-to-end communication, b) ICN enables |
| 1746 |
ubiquitous caching, and c) ICN brings awareness of user requests (as |
| 1747 |
well as their corresponding responses) at the network layer thus |
| 1748 |
permitting network elements to better schedule their transmission |
| 1749 |
patterns. |
| 1750 |
|
| 1751 |
First, ICN does not mandate perpetual end-to-end communication, which |
| 1752 |
introduces a whole range of energy consumption inefficiencies due to |
| 1753 |
the extensive signaling, especially in the case of mobile and |
| 1754 |
wirelessly connected devices. This opens up new opportunities for |
| 1755 |
accommodating sporadically connected nodes and could be one of the |
| 1756 |
keys to an order-of-magnitude decrease in energy consumption compared |
| 1757 |
to the potential contributions of other technological advances. For |
| 1758 |
example, web applications often need to maintain state at both ends |
| 1759 |
of a connection in order to verify that the authenticated peer is up |
| 1760 |
and running. This introduces keep-alive timers and polling behavior |
| 1761 |
with a high toll on energy consumption. Pentikousis [<a href="#ref-EEMN" title=""In Search of Energy-Efficient Mobile Networking"">EEMN</a>] discusses |
| 1762 |
several related scenarios and explains why the current host-centric |
| 1763 |
paradigm, which employs perpetual end-to-end connections, introduces |
| 1764 |
built-in energy inefficiencies, and argues that patches to make |
| 1765 |
currently deployed protocols energy-aware cannot provide for an |
| 1766 |
order-of-magnitude increase in energy efficiency. |
| 1767 |
|
| 1768 |
Second, ICN network elements come with built-in caching capabilities, |
| 1769 |
which is often referred to as "ubiquitous caching". Pushing data |
| 1770 |
objects to caches closer to end-user devices, for example, could |
| 1771 |
significantly reduce the amount of transit traffic in the core |
| 1772 |
network, thereby reducing the energy used for data transport. Guan |
| 1773 |
et al. [<a href="#ref-EECCN" title=""On the Energy Efficiency of Content Delivery Architectures"">EECCN</a>] study the energy efficiency of a CCNx architecture |
| 1774 |
(based on their proposed energy model) and compare it with |
| 1775 |
conventional content dissemination systems such as CDNs and P2P. |
| 1776 |
Their model is based on the analysis of the topological structure and |
| 1777 |
the average hop length from all consumers to the nearest cache |
| 1778 |
location. Their results show that an information-centric approach |
| 1779 |
can be more energy efficient in delivering popular and small-size |
| 1780 |
content. In particular, they also note that different network- |
| 1781 |
element design choices (e.g., the optical bypass approach) can be |
| 1782 |
more energy efficient in delivering infrequently accessed content. |
| 1783 |
|
| 1784 |
|
| 1785 |
|
| 1786 |
|
| 1787 |
|
| 1788 |
<span class="grey">Pentikousis, et al. Informational [Page 32]</span></pre> |
| 1789 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span> |
| 1790 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 1791 |
|
| 1792 |
|
| 1793 |
Lee et al. [<a href="#ref-EECD" title=""Toward energy-efficient content dissemination"">EECD</a>] investigate the energy efficiency of various |
| 1794 |
network devices deployed in access, metro, and core networks for both |
| 1795 |
CDNs and ICN. They use trace-based simulations to show that an ICN |
| 1796 |
approach can substantially improve the network energy efficiency for |
| 1797 |
content dissemination mainly due to the reduction in the number of |
| 1798 |
hops required to obtain a data object, which can be served by |
| 1799 |
intermediate nodes in ICN. They also emphasize that the impact of |
| 1800 |
cache placement (in incremental deployment scenarios) and |
| 1801 |
local/cooperative content replacement strategies needs to be |
| 1802 |
carefully investigated in order to better quantify the energy |
| 1803 |
efficiencies arising from adopting an ICN paradigm. |
| 1804 |
|
| 1805 |
Third, ICN elements are aware of the user request and its |
| 1806 |
corresponding data response; due to the nature of name-based routing, |
| 1807 |
they can employ power consumption optimization processes for |
| 1808 |
determining their transmission schedule or powering down inactive |
| 1809 |
network interfaces. For example, network coding [<a href="#ref-NCICN" title=""Network coding meets information-centric networking: an architectural case for information dispersion through native network coding"">NCICN</a>] or adaptive |
| 1810 |
video streaming [<a href="#ref-COAST" title=""File format specification and 3D video codec"">COAST</a>] can be used in individual ICN elements so |
| 1811 |
that redundant transmissions, possibly passing through intermediary |
| 1812 |
networks, could be significantly reduced, thereby saving energy by |
| 1813 |
avoiding carrying redundant traffic. |
| 1814 |
|
| 1815 |
Alternatively, approaches that aim to simplify routers, such as |
| 1816 |
[<a href="#ref-PURSUIT" title=""Developing Information Networking Further: From PSIRP to PURSUIT"">PURSUIT</a>], could also reduce energy consumption by pushing routing |
| 1817 |
decisions to a more energy-efficient entity. Along these lines, Ko |
| 1818 |
et al. [<a href="#ref-ICNDC" title=""An information-centric architecture for data center networks"">ICNDC</a>] design a data center network architecture based on ICN |
| 1819 |
principles and decouple the router control-plane and data-plane |
| 1820 |
functionalities. Thus, data forwarding is performed by simplified |
| 1821 |
network entities, while the complicated routing computation is |
| 1822 |
carried out in more energy-efficient data centers. |
| 1823 |
|
| 1824 |
To summarize, energy efficiency has been discussed in ICN evaluation |
| 1825 |
studies, but most published work is preliminary in nature. Thus, we |
| 1826 |
suggest that more work is needed in this front. Evaluating energy |
| 1827 |
efficiency does not require the definition of new scenarios or |
| 1828 |
baseline topologies, but does require the establishment of clear |
| 1829 |
guidelines so that different ICN approaches can be compared not only |
| 1830 |
in terms of scalability, for example, but also in terms of power |
| 1831 |
consumption. |
| 1832 |
|
| 1833 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Operation across Multiple Network Paradigms</span> |
| 1834 |
|
| 1835 |
Today the overwhelming majority of networks are integrated with the |
| 1836 |
well-connected Internet with IP at the "waist" of the technology |
| 1837 |
hourglass. However, there is a large amount of ongoing research into |
| 1838 |
alternative paradigms that can cope with conditions other than the |
| 1839 |
standard set assumed by the Internet. Perhaps the most advanced of |
| 1840 |
these is Delay- and Disruption-Tolerant Networking (DTN). DTN is |
| 1841 |
|
| 1842 |
|
| 1843 |
|
| 1844 |
<span class="grey">Pentikousis, et al. Informational [Page 33]</span></pre> |
| 1845 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span> |
| 1846 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 1847 |
|
| 1848 |
|
| 1849 |
considered as one of the scenarios for the deployment in <a href="#section-2.7">Section 2.7</a>, |
| 1850 |
but here we consider how ICN can operate in an integrated network |
| 1851 |
that has essentially disjoint "domains" (a highly overloaded term!) |
| 1852 |
or regions that use different network paradigms and technologies, but |
| 1853 |
with gateways that allow interoperation. |
| 1854 |
|
| 1855 |
ICN operates in terms of named data objects so that requests and |
| 1856 |
deliveries of information objects can be independent of the |
| 1857 |
networking paradigm. Some researchers have contemplated some form of |
| 1858 |
ICN becoming the new waist of the hourglass as the basis of a future |
| 1859 |
reincarnation of the Internet, e.g., [<a href="#ref-ArgICN" title=""Arguments for an information centric internetworking architecture"">ArgICN</a>], but there are a large |
| 1860 |
number of problems to resolve, including authorization, access |
| 1861 |
control, and transactional operation for applications such as |
| 1862 |
banking, before some form of ICN can be considered as ready to take |
| 1863 |
over from IP as the dominant networking technology. In the meantime, |
| 1864 |
ICN architectures will operate in conjunction with existing network |
| 1865 |
technologies as an overlay or in cooperation with the lower layers of |
| 1866 |
the "native" technology. |
| 1867 |
|
| 1868 |
It seems likely that as the reach of the "Internet" is extended, |
| 1869 |
other technologies such as DTN will be needed to handle scenarios |
| 1870 |
such as space communications where inherent delays are too large for |
| 1871 |
TCP/IP to cope with effectively. Thus, demonstrating that ICN |
| 1872 |
architectures can work effectively in and across the boundaries of |
| 1873 |
different networking technologies will be important. |
| 1874 |
|
| 1875 |
The NetInf architecture, in particular, targets the inter-domain |
| 1876 |
scenario by the use of a convergence-layer architecture [<a href="#ref-SAIL-B3" title=""Final NetInf Architecture"">SAIL-B3</a>], |
| 1877 |
and Publish-Subscribe Internet Routing Paradigm (PSIRP) and/or |
| 1878 |
Publish-Subscribe Internet Technology (PURSUIT) is envisaged as a |
| 1879 |
candidate for an IP replacement. |
| 1880 |
|
| 1881 |
The key items for evaluation over and above the satisfactory |
| 1882 |
operation of the architecture in each constituent domain will be to |
| 1883 |
ensure that requests and responses can be carried across the network |
| 1884 |
boundaries with adequate performance and do not cause malfunctions in |
| 1885 |
applications or infrastructure because of the differing |
| 1886 |
characteristics of the gatewayed domains. |
| 1887 |
|
| 1888 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Summary</span> |
| 1889 |
|
| 1890 |
This document presents a wide range of different application areas in |
| 1891 |
which the use of information-centric network designs have been |
| 1892 |
evaluated in the peer-reviewed literature. Evidently, this broad |
| 1893 |
range of scenarios illustrates the capability of ICN to potentially |
| 1894 |
address today's problems in an alternative and better way than host- |
| 1895 |
centric approaches as well as to point to future scenarios where ICN |
| 1896 |
may be applicable. We believe that by putting different ICN systems |
| 1897 |
|
| 1898 |
|
| 1899 |
|
| 1900 |
<span class="grey">Pentikousis, et al. Informational [Page 34]</span></pre> |
| 1901 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span> |
| 1902 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 1903 |
|
| 1904 |
|
| 1905 |
to the test in diverse application areas, the community will be |
| 1906 |
better equipped to judge the potential of a given ICN proposal and |
| 1907 |
therefore subsequently invest more effort in developing it further. |
| 1908 |
It is worth noting that this document collected different kinds of |
| 1909 |
considerations, as a result of our ongoing survey of the literature |
| 1910 |
and the discussion within ICNRG, which we believe would have |
| 1911 |
otherwise remained unnoticed in the wider community. As a result, we |
| 1912 |
expect that this document can assist in fostering the applicability |
| 1913 |
and future deployment of ICN over a broader set of operations, as |
| 1914 |
well as possibly influencing and enhancing the base ICN proposals |
| 1915 |
that are currently available and possibly assist in defining new |
| 1916 |
scenarios where ICN would be applicable. |
| 1917 |
|
| 1918 |
We conclude this document with a brief summary of the evaluation |
| 1919 |
aspects we have seen across a range of scenarios. |
| 1920 |
|
| 1921 |
The scalability of different mechanisms in an ICN architecture stands |
| 1922 |
out as an important concern (cf. Sections <a href="#section-2.1">2.1</a>, <a href="#section-2.2">2.2</a>, <a href="#section-2.5">2.5</a>, <a href="#section-2.6">2.6</a>, <a href="#section-2.8">2.8</a>, |
| 1923 |
2.9, and 3.1) as does network, resource, and energy efficiency (cf. |
| 1924 |
Sections <a href="#section-2.1">2.1</a>, <a href="#section-2.3">2.3</a>, <a href="#section-2.4">2.4</a>, <a href="#section-3.1">3.1</a>, and <a href="#section-3.2">3.2</a>). Operational aspects such as |
| 1925 |
network planing, manageability, reduced complexity and overhead (cf. |
| 1926 |
Sections <a href="#section-2.2">2.2</a>, <a href="#section-2.3">2.3</a>, <a href="#section-2.4">2.4</a>, <a href="#section-2.8">2.8</a>, and <a href="#section-3.1">3.1</a>) should not be neglected |
| 1927 |
especially as ICN architectures are evaluated with respect to their |
| 1928 |
potential for deployment in the real world. Accordingly, further |
| 1929 |
research in economic aspects as well as in the communication, |
| 1930 |
computation, and storage tradeoffs entailed in each ICN architecture |
| 1931 |
is needed. |
| 1932 |
|
| 1933 |
With respect to purely technical requirements, support for multicast, |
| 1934 |
mobility, and caching lie at the core of many scenarios (cf. Sections |
| 1935 |
2.1, 2.3, 2.5, and 2.6). ICN must also be able to cope when the |
| 1936 |
Internet expands to incorporate additional network paradigms (cf. |
| 1937 |
<a href="#section-3.3">Section 3.3</a>). We have also seen that being able to address stringent |
| 1938 |
QoS requirements and increase reliability and resilience should also |
| 1939 |
be evaluated following well-established methods (cf. Sections <a href="#section-2.2">2.2</a>, |
| 1940 |
2.8, and 2.9). |
| 1941 |
|
| 1942 |
Finally, we note that new applications that significantly improve the |
| 1943 |
end-user experience and forge a migration path from today's host- |
| 1944 |
centric paradigm could be the key to a sustained and increasing |
| 1945 |
deployment of the ICN paradigm in the real world (cf. Sections <a href="#section-2.2">2.2</a>, |
| 1946 |
2.3, 2.6, 2.8, and 2.9). |
| 1947 |
|
| 1948 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span> |
| 1949 |
|
| 1950 |
This document does not impact the security of the Internet. |
| 1951 |
|
| 1952 |
|
| 1953 |
|
| 1954 |
|
| 1955 |
|
| 1956 |
<span class="grey">Pentikousis, et al. Informational [Page 35]</span></pre> |
| 1957 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span> |
| 1958 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 1959 |
|
| 1960 |
|
| 1961 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Informative References</span> |
| 1962 |
|
| 1963 |
[<a id="ref-RFC5743">RFC5743</a>] Falk, A., "Definition of an Internet Research Task Force |
| 1964 |
(IRTF) Document Stream", <a href="./rfc5743">RFC 5743</a>, December 2009, |
| 1965 |
<<a href="http://www.rfc-editor.org/info/rfc5743">http://www.rfc-editor.org/info/rfc5743</a>>. |
| 1966 |
|
| 1967 |
[<a id="ref-RFC5050">RFC5050</a>] Scott, K. and S. Burleigh, "Bundle Protocol |
| 1968 |
Specification", <a href="./rfc5050">RFC 5050</a>, November 2007, |
| 1969 |
<<a href="http://www.rfc-editor.org/info/rfc5050">http://www.rfc-editor.org/info/rfc5050</a>>. |
| 1970 |
|
| 1971 |
[<a id="ref-RFC4838">RFC4838</a>] Cerf, V., Burleigh, S., Hooke, A., Torgerson, L., Durst, |
| 1972 |
R., Scott, K., Fall, K., and H. Weiss, "Delay-Tolerant |
| 1973 |
Networking Architecture", <a href="./rfc4838">RFC 4838</a>, April 2007, |
| 1974 |
<<a href="http://www.rfc-editor.org/info/rfc4838">http://www.rfc-editor.org/info/rfc4838</a>>. |
| 1975 |
|
| 1976 |
[<a id="ref-RFC5568">RFC5568</a>] Koodli, R., Ed., "Mobile IPv6 Fast Handovers", <a href="./rfc5568">RFC 5568</a>, |
| 1977 |
July 2009, <<a href="http://www.rfc-editor.org/info/rfc5568">http://www.rfc-editor.org/info/rfc5568</a>>. |
| 1978 |
|
| 1979 |
[<a id="ref-RFC6920">RFC6920</a>] Farrell, S., Kutscher, D., Dannewitz, C., Ohlman, B., |
| 1980 |
Keranen, A., and P. Hallam-Baker, "Naming Things with |
| 1981 |
Hashes", <a href="./rfc6920">RFC 6920</a>, April 2013, |
| 1982 |
<<a href="http://www.rfc-editor.org/info/rfc6920">http://www.rfc-editor.org/info/rfc6920</a>>. |
| 1983 |
|
| 1984 |
[<a id="ref-NetInf">NetInf</a>] Ahlgren, B. et al., "Design considerations for a network |
| 1985 |
of information", Proc. CoNEXT Re-Arch Workshop, ACM, 2008. |
| 1986 |
|
| 1987 |
[<a id="ref-CCN">CCN</a>] Jacobson, V., et al., "Networking Named Content", Proc. |
| 1988 |
CoNEXT, ACM, 2009. |
| 1989 |
|
| 1990 |
[<a id="ref-CCNx">CCNx</a>] Mosko, M., Solis, I., and E. Uzun, "CCN 1.0 Protocol |
| 1991 |
Architecture", Project CCNx documentation, Xerox Palo Alto |
| 1992 |
Research Center, 2013, |
| 1993 |
<<a href="http://ccnx.org/pubs/ICN_CCN_Protocols.pdf">http://ccnx.org/pubs/ICN_CCN_Protocols.pdf</a>>. |
| 1994 |
|
| 1995 |
[<a id="ref-NDNP">NDNP</a>] Zhang, L., et al., "Named Data Networking (NDN) Project", |
| 1996 |
NDN Technical Report NDN-0001, Oct. 2010, |
| 1997 |
<<a href="http://named-data.net/publications/techreports/">http://named-data.net/publications/techreports/</a>>. |
| 1998 |
|
| 1999 |
[<a id="ref-PSI">PSI</a>] Trossen, D. and G. Parisis, "Designing and realizing an |
| 2000 |
information-centric internet", IEEE Commun. Mag., vol. 50, |
| 2001 |
no. 7, July 2012. |
| 2002 |
|
| 2003 |
[<a id="ref-DONA">DONA</a>] Koponen, T., et al., "A Data-Oriented (and Beyond) Network |
| 2004 |
Architecture", Proc. SIGCOMM, ACM, 2007. |
| 2005 |
|
| 2006 |
[<a id="ref-SoA1">SoA1</a>] Ahlgren, B., et al., "A survey of information-centric |
| 2007 |
networking", IEEE Commun. Mag., vol. 50, no. 7, July 2012. |
| 2008 |
|
| 2009 |
|
| 2010 |
|
| 2011 |
|
| 2012 |
<span class="grey">Pentikousis, et al. Informational [Page 36]</span></pre> |
| 2013 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span> |
| 2014 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 2015 |
|
| 2016 |
|
| 2017 |
[<a id="ref-SoA2">SoA2</a>] Xylomenos, G., et al. "A survey of information-centric |
| 2018 |
networking research", IEEE Communications Surveys and |
| 2019 |
Tutorials (2013): 1-26. |
| 2020 |
|
| 2021 |
[<a id="ref-ICN-SN">ICN-SN</a>] Mathieu, B., et al., "Information-centric networking: a |
| 2022 |
natural design for social network applications", IEEE |
| 2023 |
Commun. Mag., vol. 50, no. 7, July 2012. |
| 2024 |
|
| 2025 |
[<a id="ref-VPC">VPC</a>] Kim, J., et al., "Content Centric Network-based Virtual |
| 2026 |
Private Community", Proc. ICCE, IEEE, 2011. |
| 2027 |
|
| 2028 |
[<a id="ref-CBIS">CBIS</a>] Jacobson, V., et al., "Custodian-Based Information |
| 2029 |
Sharing", IEEE Commun. Mag., vol. 50, no. 7, July 2012. |
| 2030 |
|
| 2031 |
[<a id="ref-VPC2">VPC2</a>] Kim, D. and J. Lee, "CCN-based virtual private community |
| 2032 |
for extended home media service", IEEE Trans. Consumer |
| 2033 |
Electronics, vol. 57, no. 2, May 2011. |
| 2034 |
|
| 2035 |
[<a id="ref-CCR">CCR</a>] Arianfar, S., et al., "On content-centric router design |
| 2036 |
and implications", Proc. CoNEXT Re-Arch Workshop, ACM, |
| 2037 |
2010. |
| 2038 |
|
| 2039 |
[<a id="ref-VoCCN">VoCCN</a>] Jacobson, V., et al., "VoCCN: Voice-over Content-Centric |
| 2040 |
Networks", Proc. CoNEXT Re-Arch Workshop, ACM, 2009. |
| 2041 |
|
| 2042 |
[<a id="ref-NDNpb">NDNpb</a>] Xuan, Y. and Z. Yan, "Enhancing Routing Efficiency in |
| 2043 |
Named Data Network with Piggybacked Interest", Proc. CFI, |
| 2044 |
ACM, 2013. |
| 2045 |
|
| 2046 |
[<a id="ref-ACT">ACT</a>] Zhu, Z., et al., "ACT: Audio Conference Tool Over Named |
| 2047 |
Data Networking", Proc. SIGCOMM ICN Workshop, ACM, 2011. |
| 2048 |
|
| 2049 |
[<a id="ref-G-COPSS">G-COPSS</a>] Chen, J., et al., "G-COPSS: A Content Centric |
| 2050 |
Communication Infrastructure for Gaming Applications", |
| 2051 |
Proc. ICDCS, IEEE, 2012. |
| 2052 |
|
| 2053 |
[<a id="ref-MMIN">MMIN</a>] Pentikousis, K., and P. Bertin., "Mobility Management in |
| 2054 |
Infrastructure Networks", IEEE Internet Computing 17, no. |
| 2055 |
5 (2013): 74-79. |
| 2056 |
|
| 2057 |
[<a id="ref-SCES">SCES</a>] Allman, M., et al., "Enabling an Energy-Efficient Future |
| 2058 |
Internet through Selectively Connected End Systems", Proc. |
| 2059 |
HotNets-VI, ACM, 2007. |
| 2060 |
|
| 2061 |
[<a id="ref-EEMN">EEMN</a>] Pentikousis, K., "In Search of Energy-Efficient Mobile |
| 2062 |
Networking", IEEE Commun. Mag., vol. 48, no. 1, Jan. 2010. |
| 2063 |
|
| 2064 |
|
| 2065 |
|
| 2066 |
|
| 2067 |
|
| 2068 |
<span class="grey">Pentikousis, et al. Informational [Page 37]</span></pre> |
| 2069 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span> |
| 2070 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 2071 |
|
| 2072 |
|
| 2073 |
[<a id="ref-MOBSURV">MOBSURV</a>] Tyson, G., et al., "A Survey of Mobility in Information- |
| 2074 |
Centric Networks: Challenges and Research Directions", |
| 2075 |
Proc. MobiHoc Workshop on Emerging Name-Oriented Mobile |
| 2076 |
Networking Design, ACM, 2012. |
| 2077 |
|
| 2078 |
[<a id="ref-N-Scen">N-Scen</a>] Dannewitz, C., et al., "Scenarios and research issues for |
| 2079 |
a Network of Information", Proc. MobiMedia, ICST, 2012. |
| 2080 |
|
| 2081 |
[<a id="ref-DTI">DTI</a>] Ott, J. and D. Kutscher, "Drive-thru Internet: IEEE |
| 2082 |
802.11b for 'automobile' users", Proc. INFOCOM, IEEE, |
| 2083 |
2004. |
| 2084 |
|
| 2085 |
[<a id="ref-PSIMob">PSIMob</a>] Xylomenos, G., et al., "Caching and Mobility Support in a |
| 2086 |
Publish-Subscribe Internet Architecture", IEEE Commun. |
| 2087 |
Mag., vol. 50, no. 7, July 2012. |
| 2088 |
|
| 2089 |
[<a id="ref-mNetInf">mNetInf</a>] Pentikousis, K. and T. Rautio, "A Multiaccess Network of |
| 2090 |
Information", Proc. WoWMoM, IEEE, 2010. |
| 2091 |
|
| 2092 |
[<a id="ref-HybICN">HybICN</a>] Lindgren, A., "Efficient content distribution in an |
| 2093 |
information-centric hybrid mobile networks", Proc. CCNC, |
| 2094 |
IEEE, 2011. |
| 2095 |
|
| 2096 |
[<a id="ref-E-CHANET">E-CHANET</a>] M. Amadeo, et al., "E-CHANET: Routing, Forwarding and |
| 2097 |
Transport in Information-Centric Multihop Wireless |
| 2098 |
Networks", Computer Communications, Elsevier, Jan. 2013 |
| 2099 |
online. |
| 2100 |
|
| 2101 |
[<a id="ref-MobiA">MobiA</a>] Meisel, M., et al., "Ad Hoc Networking via Named Data", |
| 2102 |
Proc. MobiArch, ACM 2010. |
| 2103 |
|
| 2104 |
[<a id="ref-CCNMANET">CCNMANET</a>] Oh, S. Y., et al., "Content Centric Networking in Tactical |
| 2105 |
and Emergency MANETs", Proc. Wireless Days, IFIP, 2010. |
| 2106 |
|
| 2107 |
[<a id="ref-RTIND">RTIND</a>] Wang, L., et al., "Rapid Traffic Information Dissemination |
| 2108 |
Using Named Data", Proc. MobiHoc NoM workshop, ACM, 2012. |
| 2109 |
|
| 2110 |
[<a id="ref-CCNVANET">CCNVANET</a>] Amadeo, M., et al., "Content-Centric Networking: is that a |
| 2111 |
Solution for Upcoming Vehicular Networks?", Proc. VANET, |
| 2112 |
ACM, 2012. |
| 2113 |
|
| 2114 |
[<a id="ref-ABC">ABC</a>] Gustafsson, E., and A. Jonsson. "Always best connected", |
| 2115 |
Wireless Communications, IEEE 10.1 (2003): 49-55. |
| 2116 |
|
| 2117 |
[<a id="ref-SHARE">SHARE</a>] Muscariello, L., et al., "Bandwidth and storage sharing |
| 2118 |
performance in information centric networking", Proc. |
| 2119 |
SIGCOMM ICN Workshop, ACM, 2011. |
| 2120 |
|
| 2121 |
|
| 2122 |
|
| 2123 |
|
| 2124 |
<span class="grey">Pentikousis, et al. Informational [Page 38]</span></pre> |
| 2125 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span> |
| 2126 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 2127 |
|
| 2128 |
|
| 2129 |
[<a id="ref-CL4M">CL4M</a>] Chai, W. K., et al., "Cache 'Less for More' in |
| 2130 |
Information-centric Networks", Proc. Networking, IFIP, |
| 2131 |
2012. |
| 2132 |
|
| 2133 |
[<a id="ref-CCNCT">CCNCT</a>] Psaras, I., et al., "Modelling and Evaluation of CCN- |
| 2134 |
Caching Trees", In Proc. of the 10th international IFIP |
| 2135 |
conference on Networking, Valencia, Spain, May 2011. |
| 2136 |
|
| 2137 |
[<a id="ref-BTCACHE">BTCACHE</a>] Tyson, G., et al., "A Trace-Driven Analysis of Caching in |
| 2138 |
Content-Centric Networks", Proc. ICCCN, IEEE, 2012. |
| 2139 |
|
| 2140 |
[<a id="ref-CURLING">CURLING</a>] Chai, W. K., et al., "CURLING: Content-Ubiquitous |
| 2141 |
Resolution and Delivery Infrastructure for Next-Generation |
| 2142 |
Services", IEEE Commun. Mag., vol. 49, no. 3, Mar. 2011. |
| 2143 |
|
| 2144 |
[<a id="ref-ACDICN">ACDICN</a>] Fotiou, N., et al., "Access control enforcement delegation |
| 2145 |
for information-centric networking architectures", Proc. |
| 2146 |
SIGCOMM ICN Workshop, ACM, 2012. |
| 2147 |
|
| 2148 |
[<a id="ref-EWC">EWC</a>] Bai, F. and B. Krishnamachari, "Exploiting the wisdom of |
| 2149 |
the crowd: localized, distributed information-centric |
| 2150 |
VANETs", IEEE Commun. Mag., vol. 48, no. 5, May 2010. |
| 2151 |
|
| 2152 |
[<a id="ref-DMND">DMND</a>] Wang, J., R. Wakikawa, and L. Zhang, "DMND: Collecting |
| 2153 |
data from mobiles using Named Data", Proc. Vehicular |
| 2154 |
Networking Conference (VNC), IEEE, 2010. |
| 2155 |
|
| 2156 |
[<a id="ref-DNV2V">DNV2V</a>] Wang, L., et al., "Data Naming in Vehicle-to-Vehicle |
| 2157 |
Communications", Proc. INFOCOM NOMEN workshop, IEEE, 2012. |
| 2158 |
|
| 2159 |
[<a id="ref-CCNHV">CCNHV</a>] Arnould, G., et al., "A Self-Organizing Content Centric |
| 2160 |
Network Model for Hybrid Vehicular Ad-Hoc Networks". Proc. |
| 2161 |
DIVANet, ACM, 2011. |
| 2162 |
|
| 2163 |
[<a id="ref-CCDIVN">CCDIVN</a>] TalebiFard, P. and V.C.M. Leung, "A Content Centric |
| 2164 |
Approach to Dissemination of Information in Vehicular |
| 2165 |
Networks", Proc. DIVANet, ACM, 2012. |
| 2166 |
|
| 2167 |
[<a id="ref-CRoWN">CRoWN</a>] Amadeo, M., et al., "CRoWN: Content-Centric Networking in |
| 2168 |
Vehicular Ad Hoc Networks", IEEE Communications Letters, |
| 2169 |
vol. 16, no. 9, Sept. 2012. |
| 2170 |
|
| 2171 |
[<a id="ref-SCN">SCN</a>] Hoydis, J., et al., "Green small-cell networks", IEEE |
| 2172 |
Vehicular Technology Magazine, vol. 6, no.1, pp. 37-43, |
| 2173 |
March 2011. |
| 2174 |
|
| 2175 |
|
| 2176 |
|
| 2177 |
|
| 2178 |
|
| 2179 |
|
| 2180 |
<span class="grey">Pentikousis, et al. Informational [Page 39]</span></pre> |
| 2181 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span> |
| 2182 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 2183 |
|
| 2184 |
|
| 2185 |
[<a id="ref-HetNet">HetNet</a>] Li, H., et al. "Efficient HetNet implementation using |
| 2186 |
broadband wireless access with fiber-connected massively |
| 2187 |
distributed antennas architecture", IEEE Wireless |
| 2188 |
Communications, vol. 18, no.3, pp. 72-78, June 2011. |
| 2189 |
|
| 2190 |
[<a id="ref-ArgICN">ArgICN</a>] Trossen, D., et al., "Arguments for an information centric |
| 2191 |
internetworking architecture", ACM SIGCOMM CCR, 40:26-33, |
| 2192 |
Apr. 2010. |
| 2193 |
|
| 2194 |
[<a id="ref-EconICN">EconICN</a>] Agyapong, P. and M. Sirbu, "Economic Incentives in |
| 2195 |
Information Centric Networking: Implications for Protocol |
| 2196 |
Design and Public Policy", IEEE Commun. Mag., vol. 50, no. |
| 2197 |
12, Dec. 2012. |
| 2198 |
|
| 2199 |
[<a id="ref-SAIL-B3">SAIL-B3</a>] Kutscher, D., Ed., et al., "Final NetInf Architecture", |
| 2200 |
SAIL Project Deliverable D-B.3, Jan. 2013, |
| 2201 |
<<a href="http://www.sail-project.eu/deliverables/">http://www.sail-project.eu/deliverables/</a>>. |
| 2202 |
|
| 2203 |
[<a id="ref-MLDHT">MLDHT</a>] Liu, H., et al., "A multi-level DHT routing framework with |
| 2204 |
aggregation", Proc. SIGCOMM ICN Workshop, ACM, 2012. |
| 2205 |
|
| 2206 |
[<a id="ref-NCOA">NCOA</a>] Ghodsi, A., et al., "Naming in Content-oriented |
| 2207 |
Architectures", Proc. SIGCOMM ICN Workshop, ACM, 2011. |
| 2208 |
|
| 2209 |
[<a id="ref-RP-NDN">RP-NDN</a>] DiBenedetto, S., et al., "Routing policies in named data |
| 2210 |
networking", Proc. SIGCOMM ICN Workshop, ACM, 2011. |
| 2211 |
|
| 2212 |
[<a id="ref-SAIL-A7">SAIL-A7</a>] Salo, J., Ed., et al., "New business models and business |
| 2213 |
dynamics of the future networks", SAIL Project Deliverable |
| 2214 |
D-A.7, Aug. 2011, |
| 2215 |
<<a href="http://www.sail-project.eu/deliverables/">http://www.sail-project.eu/deliverables/</a>>. |
| 2216 |
|
| 2217 |
[<a id="ref-SAIL-A8">SAIL-A8</a>] Zhang, N., Ed., et al., "Evaluation of business models", |
| 2218 |
SAIL Project Deliverable D-A.8, Jan. 2013, |
| 2219 |
<<a href="http://www.sail-project.eu/deliverables/">http://www.sail-project.eu/deliverables/</a>>. |
| 2220 |
|
| 2221 |
[<a id="ref-LIPSIN">LIPSIN</a>] Jokela, P., et al., "LIPSIN: line speed publish/subscribe |
| 2222 |
inter-networking", Proc. of ACM SIGCOMM 2009. |
| 2223 |
|
| 2224 |
[<a id="ref-LANES">LANES</a>] Visala, K., et al., "LANES: An Inter-Domain Data-Oriented |
| 2225 |
Routing Architecture", Proc. CoNEXT Re-Arch Workshop, ACM, |
| 2226 |
2009. |
| 2227 |
|
| 2228 |
[<a id="ref-PSIRP1">PSIRP1</a>] Rajahalme, J., et al., "Inter-Domain Rendezvous Service |
| 2229 |
Architecture", PSIRP Technical Report TR09-003, Dec. 2009. |
| 2230 |
|
| 2231 |
|
| 2232 |
|
| 2233 |
|
| 2234 |
|
| 2235 |
|
| 2236 |
<span class="grey">Pentikousis, et al. Informational [Page 40]</span></pre> |
| 2237 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span> |
| 2238 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 2239 |
|
| 2240 |
|
| 2241 |
[<a id="ref-ICCP">ICCP</a>] Rajahalme J., et al., "Incentive-Compatible Caching and |
| 2242 |
Peering in Data-Oriented Networks", Proc. CoNEXT Re-Arch |
| 2243 |
Workshop, ACM, 2008. |
| 2244 |
|
| 2245 |
[<a id="ref-IDMcast">IDMcast</a>] Rajahalme, J., "Incentive-informed Inter-domain |
| 2246 |
Multicast", Proc. Global Internet Symposium 2010. |
| 2247 |
|
| 2248 |
[<a id="ref-IDArch">IDArch</a>] Rajahalme, J., "Inter-domain incentives and Internet |
| 2249 |
architecture", PhD. Dissertation, Aalto University, Aug. |
| 2250 |
2012. |
| 2251 |
|
| 2252 |
[<a id="ref-PURSUIT">PURSUIT</a>] Fotiou, N., et al., "Developing Information Networking |
| 2253 |
Further: From PSIRP to PURSUIT", Proc. BROADNETS, ICST, |
| 2254 |
2010. |
| 2255 |
|
| 2256 |
[<a id="ref-EECCN">EECCN</a>] Guan, K., et al., "On the Energy Efficiency of Content |
| 2257 |
Delivery Architectures", Proc. ICC Workshops, IEEE, 2011. |
| 2258 |
|
| 2259 |
[<a id="ref-EECD">EECD</a>] Lee, U., Rimac, I., Kilper, D., and V. Hilt, "Toward |
| 2260 |
energy-efficient content dissemination", IEEE Network, |
| 2261 |
vol. 25, no. 2, March-April 2011. |
| 2262 |
|
| 2263 |
[<a id="ref-NCICN">NCICN</a>] Montpetit, M. J., Westphal, C., and D. Trossen, "Network |
| 2264 |
coding meets information-centric networking: an |
| 2265 |
architectural case for information dispersion through |
| 2266 |
native network coding", Proc. MOBIHOC NoM Workshop, ACM, |
| 2267 |
2012. |
| 2268 |
|
| 2269 |
[<a id="ref-COAST">COAST</a>] Gruneberg, K., et al., "File format specification and 3D |
| 2270 |
video codec", COAST Project Deliverable D5.1, July 2011, |
| 2271 |
<<a href="http://www.coast-fp7.eu/deliverables.html">http://www.coast-fp7.eu/deliverables.html</a>>. |
| 2272 |
|
| 2273 |
[<a id="ref-ICNDC">ICNDC</a>] Ko, B. J., Pappas, V., Raghavendra, R., Song, Y., |
| 2274 |
Dilmaghani, R. B., Lee, K.-w., and D. Verma, "An |
| 2275 |
information-centric architecture for data center |
| 2276 |
networks", Proc. SIGCOMM ICN Workshop, ACM, 2012. |
| 2277 |
|
| 2278 |
[<a id="ref-DTN">DTN</a>] Fall, K., "A delay-tolerant network architecture for |
| 2279 |
challenged internets", Proc. SIGCOMM, ACM, 2003. |
| 2280 |
|
| 2281 |
[<a id="ref-DTNICN">DTNICN</a>] Tyson, G., Bigham, J., and E. Bodanese, "Towards an |
| 2282 |
Information-Centric Delay-Tolerant Network", Proc. IEEE |
| 2283 |
INFOCOM NOMEN 2013, Turin, Italy. |
| 2284 |
|
| 2285 |
[<a id="ref-BPQ">BPQ</a>] Farrell, S., Lynch, A., Kutscher, D., and A. Lindgren, |
| 2286 |
"Bundle Protocol Query Extension Block", Work in Progress, |
| 2287 |
<a href="./draft-irtf-dtnrg-bpq-00">draft-irtf-dtnrg-bpq-00</a>, May 2012. |
| 2288 |
|
| 2289 |
|
| 2290 |
|
| 2291 |
|
| 2292 |
<span class="grey">Pentikousis, et al. Informational [Page 41]</span></pre> |
| 2293 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span> |
| 2294 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 2295 |
|
| 2296 |
|
| 2297 |
[<a id="ref-SLINKY">SLINKY</a>] Kawadia, V., Riga, N., Opper, J., and D. Sampath, "Slinky: |
| 2298 |
An adaptive protocol for content access in disruption- |
| 2299 |
tolerant ad hoc networks", in Proc. MobiHoc Workshop on |
| 2300 |
Tactical Mobile Ad Hoc Networking, 2011. |
| 2301 |
|
| 2302 |
[<a id="ref-ONE">ONE</a>] "The Opportunistic Network Environment simulator", |
| 2303 |
<<a href="http://www.netlab.tkk.fi/tutkimus/dtn/theone">http://www.netlab.tkk.fi/tutkimus/dtn/theone</a>>. |
| 2304 |
|
| 2305 |
[<a id="ref-TWIMIGHT">TWIMIGHT</a>] Hossmann, T., et al. "Twitter in disaster mode: smart |
| 2306 |
probing for opportunistic peers", Proc. 3rd ACM |
| 2307 |
International Workshop on Mobile Opportunistic Networks, |
| 2308 |
ACM, 2012. |
| 2309 |
|
| 2310 |
[<a id="ref-MODEL1">MODEL1</a>] Uddin, M.Y.S., Nicol, D.M., Abdelzaher, T.F., and R.H. |
| 2311 |
Kravets, "A post-disaster mobility model for Delay |
| 2312 |
Tolerant Networking", Simulation Conference (WSC), |
| 2313 |
Proceedings of the 2009 Winter, pp. 2785-2796, 13-16 Dec. |
| 2314 |
2009. |
| 2315 |
|
| 2316 |
[<a id="ref-MODEL2">MODEL2</a>] Aschenbruck, N., Gerhards-Padilla, E., and P. Martini, |
| 2317 |
"Modeling mobility in disaster area scenarios", |
| 2318 |
Performance Evaluation 66, no. 12 (2009): 773-790. |
| 2319 |
|
| 2320 |
[<a id="ref-MODEL3">MODEL3</a>] Cabrero, S., Paneda, X.G., Plagemann, T., Melendi, D., and |
| 2321 |
R. Garcia, "An Overlay Routing Protocol for Video over |
| 2322 |
sparse MANETs in Emergencies", Cadernos de Informatica 6, |
| 2323 |
no. 1 (2011): 195-202. |
| 2324 |
|
| 2325 |
[<a id="ref-IoTEx">IoTEx</a>] Burke, J., "Authoring Place-based Experiences with an |
| 2326 |
Internet of Things: Tussles of Expressive, Operational, |
| 2327 |
and Participatory Goals", Position Paper, Interconnecting |
| 2328 |
Smart Objects with the Internet Workshop, IAB, 2011. |
| 2329 |
|
| 2330 |
[<a id="ref-IWMT">IWMT</a>] Kutscher, D. and S. Farrell, "Towards an Information- |
| 2331 |
Centric Internet with more Things", Position Paper, |
| 2332 |
Interconnecting Smart Objects with the Internet Workshop, |
| 2333 |
IAB, 2011. |
| 2334 |
|
| 2335 |
[<a id="ref-nWSN">nWSN</a>] Heidemann, J., et al., "Building efficient wireless sensor |
| 2336 |
networks with low-level naming", Proc. SOSP, ACM, 2001. |
| 2337 |
|
| 2338 |
[<a id="ref-NDNl">NDNl</a>] Burke, J., et al., "Authenticated Lighting Control Using |
| 2339 |
Named Data Networking", NDN Technical Report NDN-0011, |
| 2340 |
Oct. 2012. |
| 2341 |
|
| 2342 |
[<a id="ref-CIBUS">CIBUS</a>] Biswas, T., et al., "Contextualized Information-Centric |
| 2343 |
Home Network", Proc. ACM SIGCOMM, ACM, 2013. |
| 2344 |
|
| 2345 |
|
| 2346 |
|
| 2347 |
|
| 2348 |
<span class="grey">Pentikousis, et al. Informational [Page 42]</span></pre> |
| 2349 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span> |
| 2350 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 2351 |
|
| 2352 |
|
| 2353 |
[<a id="ref-Homenet">Homenet</a>] Ravindran, R., et al., "Information-centric Networking |
| 2354 |
based Homenet", Proc. International Workshop on Management |
| 2355 |
of the Future Internet (ManFI), IFIP/IEEE, 2013. |
| 2356 |
|
| 2357 |
[<a id="ref-IoTScope">IoTScope</a>] Marias, G.F., et al., "Efficient information lookup for |
| 2358 |
the Internet of Things", Proc. WoWMoM, IEEE, 2012. |
| 2359 |
|
| 2360 |
[<a id="ref-ICN-DHT">ICN-DHT</a>] Katsaros, K., et al., "On inter-domain name resolution for |
| 2361 |
information-centric networks", Proc. Networking, Springer, |
| 2362 |
2012. |
| 2363 |
|
| 2364 |
[<a id="ref-SEMANT">SEMANT</a>] Sheth, A., et al., "Semantic Sensor Web," Internet |
| 2365 |
Computing, IEEE , vol. 12, no. 4, pp.78-83, July-Aug. 2008 |
| 2366 |
|
| 2367 |
[<a id="ref-CPG">CPG</a>] Cianci, I., et al., "Content Centric Services in Smart |
| 2368 |
Cities", Proc. NGMAST, IEEE, 2012. |
| 2369 |
|
| 2370 |
[<a id="ref-MVM">MVM</a>] Hernndez-Munoz, J.M., et al., "Smart cities at the |
| 2371 |
forefront of the future Internet", The Future Internet, |
| 2372 |
Springer, 2011. |
| 2373 |
|
| 2374 |
[<a id="ref-iHEMS">iHEMS</a>] Zhang, J., et al., "iHEMS: An Information-Centric Approach |
| 2375 |
to Secure Home Energy Management", Proc. SmartGridComm, |
| 2376 |
IEEE, 2012. |
| 2377 |
|
| 2378 |
[<a id="ref-ACC">ACC</a>] Andreini, F., et al., "A scalable architecture for geo- |
| 2379 |
localized service access in smart cities", Proc. Future |
| 2380 |
Network and Mobile Summit, IEEE, 2011. |
| 2381 |
|
| 2382 |
[<a id="ref-IB">IB</a>] Idowu, S. and N. Bari, "A Development Framework for Smart |
| 2383 |
City Services, Integrating Smart City Service Components", |
| 2384 |
Master's Thesis, Lulea University of Technology, 2012. |
| 2385 |
|
| 2386 |
[<a id="ref-ISODIS">ISODIS</a>] ISO/DIS, "Sustainable development and resilience of |
| 2387 |
communities --Indicators for city services and quality of |
| 2388 |
life", ISO/DIS 37120, 2013. |
| 2389 |
|
| 2390 |
[<a id="ref-EVAL-METHOD">EVAL-METHOD</a>] |
| 2391 |
Pentikousis, K., Ed., Ohlman, B., Davies, E., Spirou, S., |
| 2392 |
Boggia, G., and P. Mahadevan, "Information-centric |
| 2393 |
Networking: Evaluation Methodology", Work in Progress, |
| 2394 |
<a href="./draft-irtf-icnrg-evaluation-methodology-00">draft-irtf-icnrg-evaluation-methodology-00</a>, July 2014. |
| 2395 |
|
| 2396 |
[<a id="ref-CHALLENGES">CHALLENGES</a>] |
| 2397 |
Kutscher, D., Ed., Eum, S., Pentikousis, K., Psaras, I., |
| 2398 |
Corujo, D., Saucez, D., Schmidt, T., and M. Waehlisch, |
| 2399 |
"ICN Research Challenges", Work in Progress, <a href="./draft-irtf-icnrg-challenges-01">draft-irtf-</a> |
| 2400 |
<a href="./draft-irtf-icnrg-challenges-01">icnrg-challenges-01</a>, February 2015. |
| 2401 |
|
| 2402 |
|
| 2403 |
|
| 2404 |
<span class="grey">Pentikousis, et al. Informational [Page 43]</span></pre> |
| 2405 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span> |
| 2406 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 2407 |
|
| 2408 |
|
| 2409 |
Acknowledgments |
| 2410 |
|
| 2411 |
Dorothy Gellert contributed to an earlier draft version of this |
| 2412 |
document. |
| 2413 |
|
| 2414 |
This document has benefited from reviews, pointers to the growing ICN |
| 2415 |
literature, suggestions, comments, and proposed text provided by the |
| 2416 |
following members of the IRTF Information-Centric Networking Research |
| 2417 |
Group (ICNRG), listed in alphabetical order: Marica Amadeo, Hitoshi |
| 2418 |
Asaeda, Claudia Campolo, Luigi Alfredo Grieco, Myeong-Wuk Jang, Ren |
| 2419 |
Jing, Will Liu, Hongbin Luo, Priya Mahadevan, Ioannis Psaras, Spiros |
| 2420 |
Spirou, Dirk Trossen, Jianping Wang, Yuanzhe Xuan, and Xinwen Zhang. |
| 2421 |
|
| 2422 |
The authors would like to thank Mark Stapp, Juan Carlos Zuniga, and |
| 2423 |
G.Q. Wang for their comments and suggestions as part of their open |
| 2424 |
and independent review of this document within ICNRG. |
| 2425 |
|
| 2426 |
Authors' Addresses |
| 2427 |
|
| 2428 |
Kostas Pentikousis (editor) |
| 2429 |
EICT GmbH |
| 2430 |
Torgauer Strasse 12-15 |
| 2431 |
10829 Berlin |
| 2432 |
Germany |
| 2433 |
|
| 2434 |
EMail: [email protected] |
| 2435 |
|
| 2436 |
|
| 2437 |
Borje Ohlman |
| 2438 |
Ericsson Research |
| 2439 |
S-16480 Stockholm |
| 2440 |
Sweden |
| 2441 |
|
| 2442 |
EMail: [email protected] |
| 2443 |
|
| 2444 |
|
| 2445 |
Daniel Corujo |
| 2446 |
Instituto de Telecomunicacoes |
| 2447 |
Campus Universitario de Santiago |
| 2448 |
P-3810-193 Aveiro |
| 2449 |
Portugal |
| 2450 |
|
| 2451 |
EMail: [email protected] |
| 2452 |
|
| 2453 |
|
| 2454 |
|
| 2455 |
|
| 2456 |
|
| 2457 |
|
| 2458 |
|
| 2459 |
|
| 2460 |
<span class="grey">Pentikousis, et al. Informational [Page 44]</span></pre> |
| 2461 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span> |
| 2462 |
<span class="grey"><a href="./rfc7476">RFC 7476</a> ICN Baseline Scenarios March 2015</span> |
| 2463 |
|
| 2464 |
|
| 2465 |
Gennaro Boggia |
| 2466 |
Dep. of Electrical and Information Engineering |
| 2467 |
Politecnico di Bari |
| 2468 |
Via Orabona 4 |
| 2469 |
70125 Bari |
| 2470 |
Italy |
| 2471 |
|
| 2472 |
EMail: [email protected] |
| 2473 |
|
| 2474 |
|
| 2475 |
Gareth Tyson |
| 2476 |
School and Electronic Engineering and Computer Science |
| 2477 |
Queen Mary, University of London |
| 2478 |
United Kingdom |
| 2479 |
|
| 2480 |
EMail: [email protected] |
| 2481 |
|
| 2482 |
|
| 2483 |
Elwyn Davies |
| 2484 |
Trinity College Dublin/Folly Consulting Ltd |
| 2485 |
Dublin, 2 |
| 2486 |
Ireland |
| 2487 |
|
| 2488 |
EMail: [email protected] |
| 2489 |
|
| 2490 |
|
| 2491 |
Antonella Molinaro |
| 2492 |
Dep. of Information, Infrastructures, and Sustainable |
| 2493 |
Energy Engineering |
| 2494 |
Universita' Mediterranea di Reggio Calabria |
| 2495 |
Via Graziella 1 |
| 2496 |
89100 Reggio Calabria |
| 2497 |
Italy |
| 2498 |
|
| 2499 |
EMail: [email protected] |
| 2500 |
|
| 2501 |
|
| 2502 |
Suyong Eum |
| 2503 |
National Institute of Information and Communications Technology |
| 2504 |
4-2-1, Nukui Kitamachi, Koganei |
| 2505 |
Tokyo 184-8795 |
| 2506 |
Japan |
| 2507 |
|
| 2508 |
Phone: +81-42-327-6582 |
| 2509 |
EMail: [email protected] |
| 2510 |
|
| 2511 |
|
| 2512 |
|
| 2513 |
|
| 2514 |
|
| 2515 |
|
| 2516 |
Pentikousis, et al. Informational [Page 45] |
| 2517 |
</pre> |