CCSDS 734.2-R-1, CCSDS Bundle Protocol Specification (Red ...

DRAFT CCSDS RECOMMENDED STANDARD FOR CCSDS BUNDLE PROTOCOL SPECIFICATION3.5 SANA REGISTRY CONSIDERATIONS3.5.1 GENERALSANA shall establish a registry of BP CBHE Node Numbers as defined by IANA whichshall be used to denote agency manage BP CBHE Node Numbers and LTP engine IDs whichare coincident.NOTE – The purpose of this registry is to ensure uniqueness of BP CBHE Node Numbersthat are used in space missions.3.5.2 VALUE RANGE FOR BP CBHE NODE NUMBERSThe value range for BP CBHE Node Numbers shall be integers greater than 0 (reference [5],‘Bundle Protocol Compressed Bundle Header Encoding Node Numbers’).3.5.3 CCSDS BP CBHE NODE NUMBER REGISTRATION POLICYThe registration policy for the registry shall be: no engineering review required; requestmust come from the official CCSDS representative of a member agency.NOTE – For missions utilizing LTP and BP protocols, requests to SANA should attemptto utilize identical numbers for LTP Protocol Engine Identifiers and BP CBHENode Numbers to minimize confusion between missions.3.5.4 INITIAL CCSDS BP CBHE NODE NUMBER REGISTRY3.5.4.1 The initial content of the CCSDS BP CBHE Node Number Registry shall asspecified in table 3-1.Table 3-1: CCSDS BP CBHE Node Number RegistryValue Description Reference0 – 2 14 -1 Reserved This document2 14 – 2 21 -1 Assignable by SANA; blocks from this spaceallocated in units of 2 14 starting with 2 15 (see note)This document>=2 21 -1 Reserved This documentNOTE – The purpose of the block allocation scheme is to allocate 2 bytes of SDNVnumbering space (16,383 CBHE node numbers) per request. Each allocationcorresponds to a single number in the third octet of SDNV number space identifyingthe registrant, who is then responsible for managing the 16,383 numbers identifiedby the low order 2 octets of SDNV space.CCSDS 734.2-R-1 Page 3-2 February 2012