information centric networking
play

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


  1. Information-Centric Networking Stephen Wolff BORC 2017-05-12

  2. The model hasn’t changed… Internet BORC 2017-05-12

  3. Information - centric networking • In ICN, the protocols are designed around the data, not the host computers – naming data – securing data – transporting data BORC 2017-05-12

  4. 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) BORC 2017-05-12

  5. Transporting • Interest packets “leave a trail of breadcrumbs” on the path to where the requested content is • Content packets follow the trail back to the source of the interest • ∴ No asymmetric routing BORC 2017-05-12

  6. 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 BORC 2017-05-12

  7. 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 BORC 2017-05-12

  8. 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 BORC 2017-05-12

  9. 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) BORC 2017-05-12

  10. 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 BORC 2017-05-12

  11. 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 BORC 2017-05-12

  12. https://datatracker.ietf.org/rg/icnrg/documents/ https://named-data.net/publications/ Thank you BORC 2017-05-12

  13. BORC 2017-05-12

  14. 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 | | +---------------|---------------|---------------|---------------+ BORC 2017-05-12

  15. Transporting it BORC 2017-05-12

  16. Transporting it BORC 2017-05-12

  17. Transporting it BORC 2017-05-12

  18. Transporting it BORC 2017-05-12

  19. Transporting it BORC 2017-05-12

  20. Transporting it BORC 2017-05-12

  21. Transporting it BORC 2017-05-12

  22. Transporting it BORC 2017-05-12

  23. Transporting it BORC 2017-05-12

  24. Transporting it BORC 2017-05-12

  25. Transporting it BORC 2017-05-12

  26. Transporting it BORC 2017-05-12

Recommend


More recommend