[Nfd-dev] Request for assigned ContentType for "FLIC manifest"

Junxiao Shi shijunxiao at email.arizona.EDU
Thu Dec 10 13:15:25 PST 2015


Hi Christian

20151210 conference call establishes guidelines for ContentType assignments.

   - 0~4 are already assigned.
   - 5~1023 are reserved for future usage.
   - 9000~9999 are reserved for private experiments and can never be
   assigned.


*FLIC is assigned ContentType 1024*.

Yours, Junxiao

On Wed, Dec 9, 2015 at 11:36 AM, <christian.tschudin at unibas.ch> wrote:

> Hi Junxiao,
>
> could you please allocate a "ContentType" that I can use for the manifests
> I have implemented?
>
> The manifest format is called FLIC and is described in
>
> https://github.com/tschudin/icn-flic-rfc/blob/master/draft-tschudin-icnrg-flic-00.txt
>
> Here is a prototypical packet layout (assuming that the ContentType number
> would be 0xC0):
>
>    (Data/0x6
>      (Name/0x7 ...)
>      (MetaInfo/0x14
>        (ContentType/0x18 0xC0)
>      )
>      (Content/0x15
>        (HashGroup/0xC1
>          (MetaData/0xC4
>            (LocatorNm/0xC5 (NameComp/0x8 ...))
>            (BlockSize/0xC7 INT)
>            (TotalSize/0xC8 INT)
>            (TotalHash/0xC9 OCTET[32])
>          )
>          (DataPtr/0xC2 OCTET[32])
>          (MfstPtr/0xC3 OCTET[32])
>        )
>      )
>      (SignatureInfo/0x16 ...)
>      (SignatureValue/0x17 ...)
>    )
>
> An annex question is which type numbers I should use for the
> "content-internal TLVs", marked 0xC1 etc (because of NDN's global type
> policy). Should I also register them with you?
>
> I will report back on experiments regarding FLIC transport over the NDN
> testbed.
>
> Thanks! And best regards,
> christian
>
> ---
> Prof. Dr. Christian F. Tschudin | Uni Basel | Dept of Mathematics and
> Computer Science | Computer Networks Group | cn.cs.unibas.ch
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20151210/8b1f8ad0/attachment.html>


More information about the Nfd-dev mailing list