[Nfd-dev] Supporting objects larger than 8KB

[Dave Oran (oran)]

It also vastly complicates resource allocation compared with the smaller dynamic range we have now - you certainly can’t do something trivial like interest counting with a such a big dynamic range. As a matter of fact, some time I’d like to discuss whether interest counting won’t work for the 4K dynamic range we have today.


On Oct 28, 2014, at 2:30 PM, Alex Afanasyev <alexander.afanasyev at ucla.edu> wrote:

> The primary motivation of keeping object (transmission unit) size small is to restrict network-level fragmentation and encourage application-level segmentation.
> 
> In other words, individual Data packet should be (generally) small enough to fit in one transmission unit.  Allowing arbitrary packet sizes would violate this property and require extensive hop-by-hop fragmentation and reassembly.
> 
> Is there a problem with segmenting larger objects into a bunch of Data packets?
> 
> ---
> Alex
> 
>> On Oct 28, 2014, at 2:25 PM, Christos Papadopoulos <christos at cs.colostate.edu> wrote:
>> 
>> In the climate domain, the datasizes of objects are quite big, and that makes the current object size restriction of 8KB very small.
>> 
>> Is there any reason not to make this configurable and support much larger object size?
>> 
>> Christos.
>> _______________________________________________
>> Nfd-dev mailing list
>> Nfd-dev at lists.cs.ucla.edu
>> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
> 
> 
> _______________________________________________
> Nfd-dev mailing list
> Nfd-dev at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev