Differences

This shows you the differences between two versions of the page.

--- b2f:bcf_v0 [2025/02/14 10:40] – [Commands] f4hof
+++ b2f:bcf_v0 [2025/02/14 10:45] (current) – [Binary File Transfer Mode] f4hof
@@ Line 12: / Line 12: @@
 The command list almost stays the same as the ASCII Basis Protocol.
-The main change is the original ''FB'' proposal is replaced by the following proposals.
+The main change is the [[b2f:ascii#pending_mail_proposal|pending mail proposal]] is replaced by the following proposals.
 ^ Proposal ^ Usage ^
-| ''FA'' | ASCII Message Transfer |
+| ''FA'' | Pending ASCII Message Proposal |
-| ''FB'' | Binary File Transfer |
+| ''FB'' | Pending Binary File Proposal |
-The proposal format stays the same as the one described in the original ''FB'' proposal specification.
+The proposal format stays the same as the one described in the [[b2f:ascii#pending_mail_proposal|pending mail proposal]] specification:
-===== Transfer Modes =====
+==== Pending ASCII Message Proposal ====
+==== Pending Binary File Proposal ====
+===== Transfer Mode =====
 The message/file payload is transferred using a different format from the ASCII Basic Protocol.
@@ Line 26: / Line 31: @@
 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 Mode ====
+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
@@ Line 47: / Line 54: @@
 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.
-==== Binary File Transfer Mode ====
+==== Binary File Transfer Header ====
 FIXME proposal format definition