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:17] – [Binary Compressed Forward Version 0] f4hof | b2f:bcf_v0 [2025/02/14 10:45] (current) – [Binary File Transfer Mode] f4hof | ||
---|---|---|---|
Line 6: | Line 6: | ||
* As it is an extension of the basic protocol, the SID extension field MUST also advertise the ASCII Basic Protocol with the letter F. A SID with the letter '' | * As it is an extension of the basic protocol, the SID extension field MUST also advertise the ASCII Basic Protocol with the letter F. A SID with the letter '' | ||
- | The Binary Compressed Forward protocol MUST happen | + | The Binary Compressed Forward protocol MUST operate |
- | ===== Transfer Modes ===== | + | ===== Commands |
- | The actual message content is transferred in a different format from the ASCII Basic Protocol. | + | The command list almost stays the same as the ASCII Basis Protocol. |
- | + | ||
- | The format used is derived from the YAPP protocol which is very reliable. Each message is made up of a header, blocks of data, an end of message marker and a checksum. | + | |
- | This is directly equivalent to the transfer of one message in the ASCII Basic Protocol. | + | The main change |
- | Unlike YAPP transfers, there is no individual packet acknowledgement during the transmission of messages, the protocol is thus simpler and more efficient. | + | ^ Proposal ^ Usage ^ |
+ | | '' | ||
+ | | '' | ||
- | ==== ASCII Message Transfer Mode ==== | + | The proposal format stays the same as the one described in the [[b2f: |
+ | |||
+ | ==== Pending | ||
+ | |||
+ | ==== Pending Binary File Proposal ==== | ||
+ | |||
+ | ===== Transfer Mode ===== | ||
+ | |||
+ | The message/ | ||
+ | |||
+ | 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. | ||
+ | |||
+ | As with the underlying protocol, the channel direction is immediately reversed after the completion of a transfer batch. | ||
+ | ==== ASCII Message Transfer Header ==== | ||
+ | |||
+ | FIXME proposal format definition | ||
Message header format: | Message header format: | ||
Line 37: | 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 | ||
Message header format: | Message header format: | ||
Line 94: | Line 113: | ||
< | < | ||
+ | ===== Transaction flow ===== | ||
+ | |||
+ | FIXME To be completed |
b2f/bcf_v0.1739524650.txt.gz · Last modified: 2025/02/14 09:17 by f4hof