DTPCRC(5)

📦 version 3.2.1, in ubuntu jammy

💅 dtpcrc — the group chat rules for DTPC 💅

okay bestie, so this is dtpcrc, aka the Delay-Tolerant Payload Conditioning management commands file. it's the manual page for it, section 5 (that's the file-formats girlies), and honestly? she's a whole vibe. 🌸

✨ NAME ✨

dtpcrc — the Delay-Tolerant Payload Conditioning management commands file. no cap, that's literally her whole job.

🦋 DESCRIPTION 🦋

so here's the tea ☕ — DTPC management commands get handed off to dtpcadmin either from a text file full of lines, or interactively right at dtpcadmin's command prompt, which is :. commands get read line by line, and it's strictly one command per line, no sneaking two in, we don't do that here. 🙅‍♀️

the formats and the effects of every single DTPC management command? down below, babes. keep scrolling. 👇

🎀 COMMANDS 🎀

  • ? — the help command. shows you a listing of the commands and their formats. it's literally the same as the h command. twins. 👯‍♀️
  • # — comment line. anything starting with # does not get interpreted. it's giving "not me, I'm just vibing in the background." 💤
  • e { 1 | 0 } — echo control. set echo to 1 and all output printed by dtpcadmin gets logged and sent to stdout. set echo to 0 and that behavior is disabled, gone, cancelled. ✨
  • v — version number. prints out the version of ION that's currently installed. HINT: pair it with the e 1 command to log the version number at startup. iykyk. 💡
  • 1 — the initialize command. bestie listen: until this command is executed, DTPC is not in operation on the local ION node and most dtpcadmin commands will just fail on you. so do this one first, fr fr. 🔥
  • a profile profileID maxRtx aggrSizeLimit aggrTimeLimit TTL / class_of_service report_to_endpointID [statusReportFlags] — the add profile command. this one notes the definition of a single DPTC transmission profile. a transmission profile asserts the BP and DTPC configuration parameter values that get applied to all application data items (the ones encapsulated in DTPC application data units and transmitted in bundles) that are issued subject to this profile. and listen — transmission profiles are globally defined; all transmission profiles must be provided, with identical parameter values, to all inter-communicating DTPC protocol entities. no freelancing. 👑
    • profileID must be the positive integer that uniquely defines the profile.
    • maxRtx is the maximum number of times any single DTPC ADU transmitted subject to the indicated profile may be retransmitted by the DTPC entity. if maxRtx is zero, then the DTPC transport service features (in-order delivery, end-to-end acknowledgment, etc.) are disabled for this profile.
    • aggrSizeLimit is the size threshold for concluding aggregation of an outbound ADU and requesting transmission of that ADU. if aggrSizeLimit is zero, then the DTPC transmission optimization features (aggregation and elision) are disabled for this profile.
    • aggrTimeLimit is the time threshold for concluding aggregation of an outbound ADU and requesting transmission of that ADU. if aggrTimeLimit is zero, then the DTPC transmission optimization features (aggregation and elision) are disabled for this profile.
    • class_of_service is the class-of-service string as defined for bptrace(1).
    • report_to_endpointID identifies the BP endpoint to which all status reports generated from bundles transmitted subject to this profile will be sent.
    • statusReportFlags, if present, must be a sequence of status report flags, separated by commas, with no embedded whitespace. each status report flag must be one of the following: rcv, ct, fwd, dlv, del.
  • d profile profileId — the delete profile command. this one erases the definition of the DTPC transmission profile identified by profileId. bye girl, we hardly knew ye. 💀
  • i profile profileId — this command prints information (all configuration parameters) about the profile identified by profileId. the full tea. 🍵
  • l profile — this command lists all known DTPC transmission profiles. the whole roster. 📋
  • s — the start command. this one starts the DTPC clock and daemon tasks for the local BP node. let's GO. 🏁
  • x — the stop command. this one stops all DTPC tasks and notifies all DTPC applications that DTPC service has been stopped. rest era. 😴
  • w { 0 | 1 | <activity_spec> } — the DTPC watch command. this enables and disables production of a continuous stream of user-selected DTPC activity indication characters.
    • a watch parameter of 1 selects all DTPC activity indication characters
    • 0 de-selects all DTPC activity indication characters
    • any other activity_spec such as o<r> selects all activity indication characters in the string, and de-selects all the others

DTPC will print each selected activity indication character to stdout every time a processing event of the associated type occurs:

  • o — new aggregator created for profile and destination endpoint
  • \< — new ADU aggregation initiated
  • r — application data item added to aggregation
  • \> — aggregation complete, outbound ADU created
  • - — outbound ADU sent via BP
  • l — ADU end-to-end acknowledgment sent
  • m — ADU deleted due to TTL expiration
  • n — ADU queued for retransmission
  • i — inbound ADU collector created
  • u — inbound ADU received
  • v — ADU sequence gap detected
  • ? — inbound ADU discarded
  • * — ADU sequence gap deleted due to impending ADU TTL expiration
  • $ — inbound ADU collector reset
  • h — the help command. shows you a listing of the commands and their formats. it's the same as the ? command. yes, again. they're matching. 🫶

🌈 EXAMPLES 🌈

a profile 5 6 1000000 5 3600 0.1 dtn:none

okay so what is this actually saying?? lemme translate 💬 — it notes the definition of DTPC transmission profile 5:

  • transport services are enabled, with an end-to-end retransmission limit of 5
  • transmission optimization service is enabled, initiating bundle transmission whenever the aggregation of data items queued for transmission subject to this profile exceeds one million bytes or is more than five seconds old
  • the transmitted bundles will have one-hour lifetime
  • they will not be subject to custody transfer
  • they will be sent at "standard" priority
  • and they will not be tracked by any bundle status report production

she's fully specified, bestie. iconic. 👑

🔥 SEE ALSO 🔥

dtpcadmin(1), bptrace(1) — go read those too, mutuals support mutuals. 💖

and that's the whole page, mwah 💋 this was perl v5.24.1, dated 2016-07-07, filed under DTPCRC(5) — slay, stay hydrated, and always run your 1 before anything else 🧚✨

📦 where this page comes from