Project

General

Profile

NameComponentType » History » Revision 21

Revision 20 (Alex Afanasyev, 10/26/2021 02:32 PM) → Revision 21/29 (Alex Afanasyev, 10/26/2021 02:35 PM)

# Name Component Type Assignment 

 This document lists the assigned Name Component types as well as the reserves ranges of types for experimentation purposes. 

 ## Assigned types 

 Component Type                         |     TLV-TYPE     | TLV-VALUE Format     | Description                             | Alternate URI Format    | Reference 
 -------------------------------------|--------------|--------------------|---------------------------------------|-----------------------|---------- 
 Invalid                                |      0 (0x00)    | N/A                  | Invalid name component type             | N/A                     | [NDN packet spec](https://named-data.net/doc/NDN-packet-spec/current/name.html) 
 ImplicitSha256DigestComponent          |      1 (0x01)    | 32OCTET              | Implicit SHA-256 digest component       | `sha256digest=<hex>`    | [NDN packet spec](https://named-data.net/doc/NDN-packet-spec/current/name.html) 
 ParametersSha256DigestComponent        |      2 (0x02)    | 32OCTET              | SHA-256 digest of Interest Parameters | `params-sha256=<hex>` | [NDN packet spec](https://named-data.net/doc/NDN-packet-spec/current/name.html) 
 GenericNameComponent                   |      8 (0x08)    | *OCTET               | Generic name component                  | "`8=`" prefix omitted | [NDN packet spec](https://named-data.net/doc/NDN-packet-spec/current/name.html) 
 KeywordNameComponent                   |     48 (0x30)    | *OCTET               | Well-known keyword                      | (not defined)           | 
 SegmentNameComponent                   |     50 (0x32)    | NonNegativeInteger | Segment number                          | `seg=<dec>`             | [NDN naming conventions](https://named-data.net/publications/techreports/ndn-tr-22-2-ndn-memo-naming-conventions/) 
 ByteOffsetNameComponent                |     52 (0x34)    | NonNegativeInteger | Byte offset                             | `off=<dec>`             | [NDN naming conventions](https://named-data.net/publications/techreports/ndn-tr-22-2-ndn-memo-naming-conventions/) 
 VersionNameComponent                   |     54 (0x36)    | NonNegativeInteger | Version number                          | `v=<dec>`               | [NDN naming conventions](https://named-data.net/publications/techreports/ndn-tr-22-2-ndn-memo-naming-conventions/) 
 TimestampNameComponent                 |     56 (0x38)    | NonNegativeInteger | Unix timestamp in microseconds          | `t=<dec>`               | [NDN naming conventions](https://named-data.net/publications/techreports/ndn-tr-22-2-ndn-memo-naming-conventions/) 
 SequenceNumNameComponent               |     58 (0x3a)    | NonNegativeInteger | Sequence number                         | `seq=<dec>`             | [NDN naming conventions](https://named-data.net/publications/techreports/ndn-tr-22-2-ndn-memo-naming-conventions/) 

 ## Reserved ranges 

 The reserved ranges are superset of TLV code reservations of the [NDN packet specification](https://named-data.net/doc/NDN-packet-spec/current/types.html#tlv-type-number-reservations) with the following additions: 

 Type (dec)    | Description 
 ------------|---------------------------------------------------------------------------------------- 
 [128, 252]    | For future assignment (1-byte encoding, application range in NDN packet spec) 
 >32767 	     | For future assignment (3-byte or 5-byte encoding, application range in NDN packet spec) ------------|--------------------------------------- 
 65536+        | Invalid values (5+-byte encoding) 

 ## References 

 https://named-data.net/doc/NDN-packet-spec/current/name.html