<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Dec 10, 2015, at 1:15 PM, Junxiao Shi <<a href="mailto:shijunxiao@email.arizona.EDU" class="">shijunxiao@email.arizona.EDU</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi Christian<div class=""><br class=""></div><div class="">20151210 conference call establishes guidelines for ContentType assignments.</div><div class=""><ul class=""><li class="">0~4 are already assigned.<br class=""></li><li class="">5~1023 are reserved for future usage.<br class=""></li><li class="">9000~9999 are reserved for private experiments and can never be assigned.<br class=""></li></ul></div><div class=""><br class=""></div><div class=""><b class="">FLIC is assigned ContentType 1024</b>.</div><div class=""><br class=""></div><div class="">Yours, Junxiao</div></div></div></blockquote><div class=""><br class=""></div>Christian got his number to use, yes.</div><div class=""><br class=""></div><div class="">But this whole topic just *being discussed* </div><div class="">The final decision and justification for the decision will be posted once we get there.  A webpage is being built on content type listing and registrations.</div><div class=""><br class=""><blockquote type="cite" class=""><div class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On Wed, Dec 9, 2015 at 11:36 AM,  <span dir="ltr" class=""><<a href="mailto:christian.tschudin@unibas.ch" target="_blank" class="">christian.tschudin@unibas.ch</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Junxiao,<br class="">
<br class="">
could you please allocate a "ContentType" that I can use for the manifests I have implemented?<br class="">
<br class="">
The manifest format is called FLIC and is described in<br class="">
<a href="https://github.com/tschudin/icn-flic-rfc/blob/master/draft-tschudin-icnrg-flic-00.txt" rel="noreferrer" target="_blank" class="">https://github.com/tschudin/icn-flic-rfc/blob/master/draft-tschudin-icnrg-flic-00.txt</a><br class="">
<br class="">
Here is a prototypical packet layout (assuming that the ContentType number would be 0xC0):<br class="">
<br class="">
   (Data/0x6<br class="">
     (Name/0x7 ...)<br class="">
     (MetaInfo/0x14<br class="">
       (ContentType/0x18 0xC0)<br class="">
     )<br class="">
     (Content/0x15<br class="">
       (HashGroup/0xC1<br class="">
         (MetaData/0xC4<br class="">
           (LocatorNm/0xC5 (NameComp/0x8 ...))<br class="">
           (BlockSize/0xC7 INT)<br class="">
           (TotalSize/0xC8 INT)<br class="">
           (TotalHash/0xC9 OCTET[32])<br class="">
         )<br class="">
         (DataPtr/0xC2 OCTET[32])<br class="">
         (MfstPtr/0xC3 OCTET[32])<br class="">
       )<br class="">
     )<br class="">
     (SignatureInfo/0x16 ...)<br class="">
     (SignatureValue/0x17 ...)<br class="">
   )<br class="">
<br class="">
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?<br class="">
<br class="">
I will report back on experiments regarding FLIC transport over the NDN testbed.<br class="">
<br class="">
Thanks! And best regards,<br class="">
christian<br class="">
<br class="">
---<br class="">
Prof. Dr. Christian F. Tschudin | Uni Basel | Dept of Mathematics and<br class="">
Computer Science | Computer Networks Group | <a href="http://cn.cs.unibas.ch/" rel="noreferrer" target="_blank" class="">cn.cs.unibas.ch</a><br class="">
<br class="">
</blockquote></div><br class=""></div>
_______________________________________________<br class="">Nfd-dev mailing list<br class=""><a href="mailto:Nfd-dev@lists.cs.ucla.edu" class="">Nfd-dev@lists.cs.ucla.edu</a><br class=""><a href="http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev" class="">http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev</a><br class=""></div></blockquote></div><br class=""></body></html>