2012 · 104 citations · 7 references
ComputingComputer ScienceComputer SystemsComputer NetworksDistributed SystemsNetwork SecurityCachingCommunication NetworksCongestion ControlNetwork ArchitectureNetwork ProtocolsTransport LayerCongestion Control ProtocolsCryptographic OperationsData UnitsFragmentationNetworkingPacket FragmentationTransport Layer Protocols
Content to be transported over an Information Centric Networking (ICN) infrastructure can be very variable in size, from few bytes to hundreds of gigabytes. Therefore it needs to be segmented in smaller size data units, typically called chunks, in order to be handled by ICN nodes. A chunk is the basic data unit to which caching and security (e.g. encryption and signature) functions are applied. If we consider the overhead and the number of cryptographic operations to be performed by nodes, a good choice for the chunk size would be from hundreds of KBs up to few MBs. However, if the chunk size is bigger than the Maximum Transfer Unit of a link, chunks will be fragmented. We show that if we have more than 3-4 fragments per chunk, and congestion and reliability functions are executed on a chunk by chunk basis, the efficiency of the congestion control algorithm drastically decreases. On the other side, a small chunk size would increase overhead and rate of signature checks.
7
Van Jacobson, Diana K. Smetters, James D. Thornton et al. · 2009 · 4K citations
A data-oriented (and beyond) network architecture
Teemu Koponen, Mohit Chawla, Byung-Gon Chun et al. · 2007 · 1.4K citations
Information-centric networking
Ali Ghodsi, Scott Shenker, Teemu Koponen et al. · 2011 · 321 citations