< draft-irtf-icnrg-terminology-02.txt   draft-irtf-icnrg-terminology-03.txt >
icnrg B. Wissingh icnrg B. Wissingh
Internet-Draft TNO Internet-Draft TNO
Intended status: Informational C. Wood Intended status: Informational C. Wood
Expires: August 12, 2019 University of California Irvine Expires: September 12, 2019 University of California Irvine
A. Afanasyev A. Afanasyev
Florida International University Florida International University
L. Zhang L. Zhang
UCLA UCLA
D. Oran D. Oran
Network Systems Research & Design Network Systems Research & Design
C. Tschudin C. Tschudin
University of Basel University of Basel
February 8, 2019 March 11, 2019
Information-Centric Networking (ICN): CCN and NDN Terminology Information-Centric Networking (ICN): CCN and NDN Terminology
draft-irtf-icnrg-terminology-02 draft-irtf-icnrg-terminology-03
Abstract Abstract
Information Centric Networking (ICN) is a new paradigm where network Information Centric Networking (ICN) is a new paradigm where network
communications are accomplished by requesting named content, instead communications are accomplished by requesting named content, instead
of sending packets to destination addresses. Named Data Networking of sending packets to destination addresses. Named Data Networking
(NDN) and Content-Centric Networking (CCN) are two prominent ICN (NDN) and Content-Centric Networking (CCN) are two prominent ICN
architectures. This document provides an overview of the terminology architectures. This document provides an overview of the terminology
and definitions that have been used in describing concepts in these and definitions that have been used in describing concepts in these
two projects. While there are other ICN architectures, they are not two projects. While there are other ICN architectures, they are not
skipping to change at page 1, line 47 skipping to change at page 1, line 47
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 12, 2019. This Internet-Draft will expire on September 12, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 28 skipping to change at page 2, line 28
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. A Sketch of the Big Picture of ICN . . . . . . . . . . . . . 3 2. A Sketch of the Big Picture of ICN . . . . . . . . . . . . . 3
3. Terms by category . . . . . . . . . . . . . . . . . . . . . . 5 3. Terms by category . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Generic terms . . . . . . . . . . . . . . . . . . . . . . 5 3.1. Generic terms . . . . . . . . . . . . . . . . . . . . . . 5
3.2. Terms related to ICN Nodes . . . . . . . . . . . . . . . 6 3.2. Terms related to ICN Nodes . . . . . . . . . . . . . . . 6
3.3. Terms related to the Forwarding plane . . . . . . . . . . 7 3.3. Terms related to the Forwarding plane . . . . . . . . . . 7
3.4. Terms related to Packet Types . . . . . . . . . . . . . . 9 3.4. Terms related to Packet Types . . . . . . . . . . . . . . 10
3.5. Terms related to Name Types . . . . . . . . . . . . . . . 11 3.5. Terms related to Name Types . . . . . . . . . . . . . . . 11
3.6. Terms related to Name Usage . . . . . . . . . . . . . . . 12 3.6. Terms related to Name Usage . . . . . . . . . . . . . . . 13
3.7. Terms related to Data-Centric Security . . . . . . . . . 13 3.7. Terms related to Data-Centric Security . . . . . . . . . 14
4. Semantics and Usage . . . . . . . . . . . . . . . . . . . . . 14 4. Semantics and Usage . . . . . . . . . . . . . . . . . . . . . 15
4.1. Data Transfer . . . . . . . . . . . . . . . . . . . . . . 14 4.1. Data Transfer . . . . . . . . . . . . . . . . . . . . . . 15
4.2. Data Transport . . . . . . . . . . . . . . . . . . . . . 14 4.2. Data Transport . . . . . . . . . . . . . . . . . . . . . 15
4.3. Lookup Service . . . . . . . . . . . . . . . . . . . . . 15 4.3. Lookup Service . . . . . . . . . . . . . . . . . . . . . 15
4.4. Database Access . . . . . . . . . . . . . . . . . . . . . 15 4.4. Database Access . . . . . . . . . . . . . . . . . . . . . 15
4.5. Remote Procedure Call . . . . . . . . . . . . . . . . . . 15 4.5. Remote Procedure Call . . . . . . . . . . . . . . . . . . 15
5. Informational References . . . . . . . . . . . . . . . . . . 15 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 17 6. Security Considerations . . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 7. Informational References . . . . . . . . . . . . . . . . . . 16
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
1. Introduction 1. Introduction
Information-centric networking (ICN) is an approach to evolve the Information-centric networking (ICN) is an approach to evolve the
Internet infrastructure from the existing host-centric design to a Internet infrastructure from the existing host-centric design to a
data-centric architecture, where accessing data by name becomes the data-centric architecture, where accessing data by name becomes the
essential network primitive. The goal is to let applications refer essential network primitive. The goal is to let applications refer
to data independently of their location or means of transportation, to data independently of their location or means of transportation,
which enables native multicast delivery, ubiquitous in-network which enables native multicast delivery, ubiquitous in-network
caching and replication of data objects. caching and replication of data objects.
skipping to change at page 5, line 18 skipping to change at page 5, line 18
A node within an ICN network can fulfill the role of a data A node within an ICN network can fulfill the role of a data
producer, a data consumer, and/or a forwarder for Interest and producer, a data consumer, and/or a forwarder for Interest and
Data packets. When a forwarder has connectivity to neighbor Data packets. When a forwarder has connectivity to neighbor
nodes, it performs Interest and Data packet forwarding in real nodes, it performs Interest and Data packet forwarding in real
time. It can also behave like a packet mule, that is it may carry time. It can also behave like a packet mule, that is it may carry
an Interest or Data packet for some time before forwarding it to an Interest or Data packet for some time before forwarding it to
next node. An ICN node may also run routing protocols to assist next node. An ICN node may also run routing protocols to assist
its Interest forwarding decisions. its Interest forwarding decisions.
--> add ASCII art here
(of a forwarding node
and its PIT, FIB, CS)
Figure 2: Structure of an ICN forwarding node.
*Forwarding Plane*: *Forwarding Plane*:
The canonical way of implementing packet forwarding in an ICN The canonical way of implementing packet forwarding in an ICN
network relies on three data structures that capture a node's network relies on three data structures that capture a node's
state: a Forwarding Interest Table (FIB), a Pending Interest state: a Forwarding Interest Table (FIB), a Pending Interest
Table (PIT), and a Content Store (CS). It also utilizes Interest Table (PIT), and a Content Store (CS). It also utilizes Interest
forwarding strategies which takes input from both FIB and forwarding strategies which takes input from both FIB and
measurements to make Interest forwarding decisions. When a node measurements to make Interest forwarding decisions. When a node
receives an Interest packet, it checks its CS and PIT to find a receives an Interest packet, it checks its CS and PIT to find a
matching entry; if no match is found, the node records the matching entry; if no match is found, the node records the
skipping to change at page 8, line 5 skipping to change at page 8, line 5
*Interest forwarding*: *Interest forwarding*:
A process of forwarding Interest packets using the Names carried A process of forwarding Interest packets using the Names carried
in the Interests. In case of Stateful forwarding, creating an in the Interests. In case of Stateful forwarding, creating an
entry in PIT. The forwarding decision is made by the Forwarding entry in PIT. The forwarding decision is made by the Forwarding
Strategy. Strategy.
*Interest aggregation*: *Interest aggregation*:
A process of combining multiple identical Interest packets for the A process of combining multiple Interest packets with the same
same Data into a single PIT entry. Not the same as Interest Name and additional restrictions for the same Data into a single
suppresion. PIT entry. Not the same as Interest suppression.
Common aliases include: Interest collapsing. Common aliases include: Interest collapsing.
*Data forwarding*: *Data forwarding*:
A process of forwarding the incoming Data packet to the A process of forwarding the incoming Data packet to the
interface(s) recorded in the corresponding PIT entry (entries) and interface(s) recorded in the corresponding PIT entry (entries) and
removing the corresponding PIT entry (entries). removing the corresponding PIT entry (entries).
*Satisfying an Interest*: *Satisfying an Interest*:
An overall process of returning content that satisfies the An overall process of returning content that satisfies the
constraints imposed by the Interest, most notably a match in the constraints imposed by the Interest, most notably a match in the
provided Name. provided Name.
*Interest match in FIB (longest prefix match)*:
A process of finding a FIB entry with the longest Name (in terms
of Name components) that is a prefix of the specified Name.
*Interest match in PIT (exact match)*:
A process of finding a PIT entry that stores the same Name as
specified in the Interest (including Interest restrictions, if
any).
*Data match in PIT (all match)*:
A process of finding (a set of) PIT entries that can be satisfied
with the specified Data packet.
*Interest match in CS (any match)*:
A process of finding an entry in router's Content Store that can
satisfy the specified Interest.
*Pending Interest Table (PIT)*: *Pending Interest Table (PIT)*:
A database that records received and not yet satisfied Interests A database that records received and not yet satisfied Interests
with the interfaces from where they were received. The PIT can with the interfaces from where they were received. The PIT can
also store interfaces to where Interests were forwarded, and also store interfaces to where Interests were forwarded, and
information to assess data plane performance. Interests for the information to assess data plane performance. Interests for the
same Data are aggregated into a single PIT entry. same Data are aggregated into a single PIT entry.
*Forwarding Information Base (FIB)*: *Forwarding Information Base (FIB)*:
skipping to change at page 11, line 37 skipping to change at page 12, line 14
Common aliases include: name segment (as in CCN). Common aliases include: name segment (as in CCN).
*Packet ID*: *Packet ID*:
a unique cryptographic identifier for a Data packet. Typically, a unique cryptographic identifier for a Data packet. Typically,
this is a cryptographic hash digest of a data packet (such as this is a cryptographic hash digest of a data packet (such as
SHA256), including its name, payload, meta information, and SHA256), including its name, payload, meta information, and
signature. signature.
Common aliases include: implicit digest.
*Selector*: *Selector*:
A mechanism (condition) to select an individual Data packet from a A mechanism (condition) to select an individual Data packet from a
collection of Data packets that match a given Interest that collection of Data packets that match a given Interest that
requests data using a prefix or exact Name. requests data using a prefix or exact Name.
Common aliases include: interest selector, restrictor, interest Common aliases include: interest selector, restrictor, interest
restrictor. restrictor.
*Nonce*: *Nonce*:
skipping to change at page 13, line 28 skipping to change at page 14, line 7
*Versioning*: *Versioning*:
A process of assigning a unique Name to the revision of the A process of assigning a unique Name to the revision of the
content carried in the Data packet. When using a hierarchically content carried in the Data packet. When using a hierarchically
structured Name, the version of the Data packet can be carried in structured Name, the version of the Data packet can be carried in
a dedicated Name component (e.g., prefix identifies data, unique a dedicated Name component (e.g., prefix identifies data, unique
version component identifies the revision of the data). version component identifies the revision of the data).
*Fragmentation*: *Fragmentation*:
A process of splitting data packets into frames so that they can A process of splitting PDUs into frames so that they can be
be transmitted over the link with a smaller MTU size. transmitted over the link with a smaller MTU size.
3.7. Terms related to Data-Centric Security 3.7. Terms related to Data-Centric Security
*Data-Centric Security*: *Data-Centric Security*:
A security property associated with the Data packet, including A security property associated with the Data packet, including
data (Data-Centric) integrity, authenticity, and optionally data (Data-Centric) integrity, authenticity, and optionally
confidentiality. These security properties stay with the data confidentiality. These security properties stay with the data
packet regardless where it is stored and how it is retrieved. packet regardless where it is stored and how it is retrieved.
skipping to change at page 15, line 45 skipping to change at page 16, line 21
*Data match in PIT (all match)*: *Data match in PIT (all match)*:
A process of finding (a set of) PIT entries that can be satisfied A process of finding (a set of) PIT entries that can be satisfied
with the specified Data packet. with the specified Data packet.
*Interest match in CS (any match)*: *Interest match in CS (any match)*:
A process of finding an entry in router's Content Store that can A process of finding an entry in router's Content Store that can
satisfy the specified Interest. satisfy the specified Interest.
5. Informational References 5. IANA Considerations
There are no IANA considerations related to this document.
6. Security Considerations
This document introduces no new security considerations.
7. Informational References
[I-D.irtf-icnrg-ccnxmessages] [I-D.irtf-icnrg-ccnxmessages]
Mosko, M., Solis, I., and C. Wood, "CCNx Messages in TLV Mosko, M., Solis, I., and C. Wood, "CCNx Messages in TLV
Format", draft-irtf-icnrg-ccnxmessages-08 (work in Format", draft-irtf-icnrg-ccnxmessages-09 (work in
progress), July 2018. progress), January 2019.
[I-D.irtf-icnrg-ccnxsemantics] [I-D.irtf-icnrg-ccnxsemantics]
Mosko, M., Solis, I., and C. Wood, "CCNx Semantics", Mosko, M., Solis, I., and C. Wood, "CCNx Semantics",
draft-irtf-icnrg-ccnxsemantics-09 (work in progress), June draft-irtf-icnrg-ccnxsemantics-10 (work in progress),
2018. January 2019.
[I-D.irtf-icnrg-disaster] [I-D.irtf-icnrg-disaster]
Seedorf, J., Arumaithurai, M., Tagami, A., Ramakrishnan, Seedorf, J., Arumaithurai, M., Tagami, A., Ramakrishnan,
K., and N. Blefari-Melazzi, "Research Directions for Using K., and N. Blefari-Melazzi, "Research Directions for Using
ICN in Disaster Scenarios", draft-irtf-icnrg-disaster-03 ICN in Disaster Scenarios", draft-irtf-icnrg-disaster-04
(work in progress), February 2018. (work in progress), February 2019.
[RFC7476] Pentikousis, K., Ed., Ohlman, B., Corujo, D., Boggia, G., [RFC7476] Pentikousis, K., Ed., Ohlman, B., Corujo, D., Boggia, G.,
Tyson, G., Davies, E., Molinaro, A., and S. Eum, Tyson, G., Davies, E., Molinaro, A., and S. Eum,
"Information-Centric Networking: Baseline Scenarios", "Information-Centric Networking: Baseline Scenarios",
RFC 7476, DOI 10.17487/RFC7476, March 2015, RFC 7476, DOI 10.17487/RFC7476, March 2015,
<http://www.rfc-editor.org/info/rfc7476>. <http://www.rfc-editor.org/info/rfc7476>.
[RFC7927] Kutscher, D., Ed., Eum, S., Pentikousis, K., Psaras, I., [RFC7927] Kutscher, D., Ed., Eum, S., Pentikousis, K., Psaras, I.,
Corujo, D., Saucez, D., Schmidt, T., and M. Waehlisch, Corujo, D., Saucez, D., Schmidt, T., and M. Waehlisch,
"Information-Centric Networking (ICN) Research "Information-Centric Networking (ICN) Research
 End of changes. 16 change blocks. 
31 lines changed or deleted 58 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/