13.07.2015 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

DRAFT <strong>CCSDS</strong> RECOMMENDED STANDARD FOR <strong>CCSDS</strong> BUNDLE PROTOCOL SPECIFICATION4.3.6 DELIVERY OPTIONS PARAMETERThe delivery options parameter shall indicate what optional procedures shall additionally befollowed when transmitting and delivering the bundle. Its value shall be a combination ofzero or more of the following:a) custody transfer;b) do-not-fragment;c) end-to-end return receipt;d) deletion receipt;e) delivery records for bundle received events;f) delivery records for bundle transmitted events;g) delivery records for custody taken events.4.3.7 LIFETIME PARAMETERThe lifetime parameter shall indicate the length of time, following initial creation time of abundle, after which bundle protocol agents may discard the bundle.4.3.8 APPLICATION DATA UNIT PARAMETERThe application data unit parameter shall indicate the location (in memory or non-volatilestorage, a local implementation matter) of the application data conveyed by the bundle.4.3.9 LOCAL BUNDLE IDThe Local <strong>Bundle</strong> ID parameter shall identify a particular bundle within the context of agiven bundle protocol agent.NOTE – This identification is provided to the user of the bundle service on submitting abundle for transmission so that the user may later reference that bundle in otherrequests, such as cancellation. The form of this identifier is entirelyimplementation-specific and should not be confused with the global <strong>Bundle</strong> IDfield used to uniquely identify bundles in the network.<strong>CCSDS</strong> <strong>734.2</strong>-R-1 Page 4-3 February 2012

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!