b2f:bcf_v0
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
b2f:bcf_v0 [2025/02/14 09:40] – [Transfer Modes] f4hof | b2f:bcf_v0 [2025/02/14 10:45] (current) – [Binary File Transfer Mode] f4hof | ||
---|---|---|---|
Line 8: | Line 8: | ||
The Binary Compressed Forward protocol MUST operate over a [[https:// | The Binary Compressed Forward protocol MUST operate over a [[https:// | ||
- | ===== Transfer Modes ===== | + | ===== Commands |
- | The control plane stays the same as the ASCII Basis Protocol, except for the original '' | + | The command list almost |
+ | |||
+ | The main change is the [[b2f: | ||
+ | |||
+ | ^ Proposal ^ Usage ^ | ||
+ | | '' | ||
+ | | '' | ||
+ | |||
+ | The proposal format stays the same as the one described in the [[b2f: | ||
+ | |||
+ | ==== Pending ASCII Message Proposal ==== | ||
+ | |||
+ | ==== Pending Binary File Proposal ==== | ||
+ | |||
+ | ===== Transfer Mode ===== | ||
The message/ | The message/ | ||
- | |||
- | This format used is derived from the YAPP protocol. | ||
Each message is made up of a header, blocks of data, an end-of-message marker, and a checksum. | Each message is made up of a header, blocks of data, an end-of-message marker, and a checksum. | ||
- | Unlike YAPP transfers, there is no individual packet acknowledgement during the transmission of messages, the protocol is thus simpler and more efficient. | + | Unlike YAPP transfers, there is no individual packet acknowledgement during the transmission of messages. The protocol is thus simpler and more efficient. |
- | ==== ASCII Message Transfer | + | As with the underlying protocol, the channel direction is immediately reversed after the completion of a transfer batch. |
+ | ==== ASCII Message Transfer | ||
FIXME proposal format definition | FIXME proposal format definition | ||
Line 41: | Line 54: | ||
Security considerations: | Security considerations: | ||
* If you're using a memory-unsafe language, you SHOULD pay extra care with the attribute size field to avoid buffer overflow attacks. | * If you're using a memory-unsafe language, you SHOULD pay extra care with the attribute size field to avoid buffer overflow attacks. | ||
- | ==== Binary File Transfer | + | ==== Binary File Transfer |
FIXME proposal format definition | FIXME proposal format definition |
b2f/bcf_v0.1739526052.txt.gz · Last modified: 2025/02/14 09:40 by f4hof