[Ndn-interest] Proposed deprecation: byte offset segmenting

Nick Briggs nicholas.h.briggs at gmail.com
Tue Jan 29 12:28:23 PST 2019

What is the benefit of removing it from the specification (or the cost of leaving it) ?

-- Nick

> On Jan 29, 2019, at 12:22 PM, Junxiao Shi <shijunxiao at email.arizona.edu> wrote:
> Dear folks
> NDN Naming Conventions revision 1 defines two segmenting markers: 0x00 and 0xFB.
> 0x00 is the segment number marker. Segments of a content are assigned consecutive segment numbers.
> It is commonly used in many applications, including ndnputchunks, NDNFS, and PSync.
> 0xFB is the byte offset marker. Segments of a content are given this marker followed by payload's byte offset within the content.
> We are unaware of any application that adopts the 0xFB byte offset marker.
> Moreover, unless using a manifest, the consumer cannot predict the byte offset of every segment, and thus hinders the efficiency of content retrieval because pipelining cannot be used.
> Alex has promised to discontinue byte offset segmenting in NDN Naming Conventions revision 2.
> If anyone on this mailing list has an application that currently uses 0xFB marker, please speak up within 5 days.
> Yours, Junxiao
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5280 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20190129/eba005c2/attachment.p7s>

More information about the Ndn-interest mailing list