Project

General

Profile

Actions

Task #1761

closed

Ensure consistent segment and version encoding between ndn-cxx and CCL libraries

Added by Junxiao Shi over 9 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Normal
Category:
Base
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
3.00 h

Description

Currently, ndn-cxx and ndn-ccl (eg. pyndn2) encode segment number and version number differently.
A segment number NameComponent encoded in one library cannot be decoded in another library.

This Task is to agree on a common naming convention, and ensure both libraries encode segment number and version number in the same way.


Files

convention.pdf (131 KB) convention.pdf NDN Technical Memo: Naming Conventions (draft 1) Alex Afanasyev, 07/20/2014 06:40 PM
convention.pdf (167 KB) convention.pdf Draft 2 Alex Afanasyev, 07/21/2014 07:03 PM
convention.pdf (167 KB) convention.pdf Draft 3 Alex Afanasyev, 07/28/2014 04:16 PM
convention.pdf (166 KB) convention.pdf Draft 4 Alex Afanasyev, 07/28/2014 05:19 PM

Related issues 1 (0 open1 closed)

Blocks NFD - Task #1762: Revise Management protocol to use number encoding conventionClosedJunxiao Shi

Actions
Actions #1

Updated by Junxiao Shi over 9 years ago

  • Blocks Task #1762: Revise Management protocol to use number encoding convention added
Actions #2

Updated by Junxiao Shi over 9 years ago

20140714 conference call agrees that in "short term" we'll use CCNx Version and Segment Markers.

There are two potential problems.

Number encoding: should we encode the number as Non Negative Integer, or with minimum number of bytes as CCNx does?

We believe it's better to use Non Negative Integer, because it's one of two encoding schemes for numeric values defined in TLV spec.
There would be major inconsistency to use CCNx's minimum number of bytes, because that causes us to have 3 numeric encodings.

Version timestamp: CCNx uses CCNx Timestamp Format, but TLV is using milliseconds.

We believe this problem is unimportant as long as all producers of the same namespace use the same way to generate version number, because version numbers are compared with each other but not converted back to a timestamp.

Actions #3

Updated by Junxiao Shi over 9 years ago

20140715 conference call agrees that:

  • Number encoding will be Non Negative Integer, given that it's considered a better encoding than using minimum bytes.
  • Version timestamp could be milliseconds. This doesn't matter as long as producers of same namespace are using the same scheme.
Actions #4

Updated by Junxiao Shi over 9 years ago

  • Assignee set to Alex Afanasyev
  • Estimated time set to 3.00 h

Name Conversion document should be updated as part of this Task.

Actions #5

Updated by Alex Afanasyev over 9 years ago

I have created a git repo for the naming convention NDN memo:

git@git.irl.cs.ucla.edu:papers/ndn-memos-naming-conventions.git

I'm also uploading the resulting pdf.

Actions #9

Updated by Junxiao Shi over 9 years ago

  • Status changed from Feedback to Closed
Actions

Also available in: Atom PDF