SLIDE 1
BORC 2017-05-12
BORC 2017-05-12
Information-Centric Networking Stephen Wolff BORC 2017-05-12 The - - PowerPoint PPT Presentation
Information-Centric Networking Stephen Wolff BORC 2017-05-12 The - - PowerPoint PPT Presentation
Information-Centric Networking Stephen Wolff BORC 2017-05-12 The model hasnt changed Internet BORC 2017-05-12 Information - centric networking In ICN, the protocols are designed around the data, not the host computers naming data
SLIDE 2
SLIDE 3
BORC 2017-05-12
Information-centric networking
- In ICN, the protocols are designed around the
data, not the host computers
– naming data – securing data – transporting data
SLIDE 4
BORC 2017-05-12
Transporting
- There are two kinds of packets in ICN –
– Interest packets – Content packets
- ICN is a pull technology –
– every content packet – in flight or at rest – is/was responding to one or more interest packet(s)
SLIDE 5
BORC 2017-05-12
Transporting
- Interest packets “leave a trail of breadcrumbs”
- n the path to where the requested content is
- Content packets follow the trail back to the
source of the interest
- ∴No asymmetric routing
SLIDE 6
BORC 2017-05-12
Transporting
- Content packets may be cached along their route
- ∴Interests from other sites for the same content
may be met from the nearest cache
- ∴Multicast is built-in, and
- Content never traverses the same link twice
SLIDE 7
BORC 2017-05-12
Transporting
- Large content is sent in chunks, with a
manifest
- Works for streaming data too
- Interest packets may record smallest MTU, or
- Fragmentation/reassembly hop-by-hop
SLIDE 8
BORC 2017-05-12
Securing
- In ICN, every packet is validated
- E.g., each interest packet is signed with the
requestor’s private key; each content packet contains a cryptographic hash of the content
- Packet body may be encrypted
- Topic of active research
SLIDE 9
BORC 2017-05-12
Naming
- An ICN node has three elements
– PIT = Pending interest table (the breadcrumbs) – FIB = Forwarding information base (where to send interest packets) – CS = Content store (the optional cache)
SLIDE 10
BORC 2017-05-12
Naming
- Naming and forwarding must be treated
together
- The number of names is unbounded
- ∴ Routing on names alone is only feasible
locally, otherwise
- Content names must include locators
SLIDE 11
BORC 2017-05-12
Naming
- TBD: roles of discipline-specific and other
naming conventions
– NHD_H_0101_GDB (a hydrology dataset maintained by USGS) – ISSN/ISBN – DOI, e.g., 10.1126/science.1200644
SLIDE 12
BORC 2017-05-12
https://datatracker.ietf.org/rg/icnrg/documents/ https://named-data.net/publications/
Thank you
SLIDE 13
BORC 2017-05-12
SLIDE 14
BORC 2017-05-12
The last eight bytes…
+---------------|---------------|---------------|---------------+ | 0 | 1 | 3 | 4 | |0 1 2 3 4 5 6 7|8 9 0 1 2 3 4 5|6 7 8 9 0 1 2 3|4 5 6 7 8 9 0 1| +---------------|---------------|---------------|---------------+ . . . . . . . . . . . . +---------------|---------------|---------------|---------------+ | | Validation Algorithm | | +---------------|---------------|---------------|---------------+ | | Validation Payload | | +---------------|---------------|---------------|---------------+
SLIDE 15
BORC 2017-05-12
Transporting it
SLIDE 16
BORC 2017-05-12
Transporting it
SLIDE 17
BORC 2017-05-12
Transporting it
SLIDE 18
BORC 2017-05-12
Transporting it
SLIDE 19
BORC 2017-05-12
Transporting it
SLIDE 20
BORC 2017-05-12
Transporting it
SLIDE 21
BORC 2017-05-12
Transporting it
SLIDE 22
BORC 2017-05-12
Transporting it
SLIDE 23
BORC 2017-05-12
Transporting it
SLIDE 24
BORC 2017-05-12
Transporting it
SLIDE 25
BORC 2017-05-12
Transporting it
SLIDE 26
BORC 2017-05-12