**********************************************************************
FTSC                             FIDONET TECHNICAL STANDARDS COMMITTEE
**********************************************************************

Publication:    FSP-1021
Revision:       draft-2.
Title:          Binkp/1.0 optional protocol extension Multiple Batch.
Authors:        Michiel Broek
Issue Date:     06 Sept 2003
Review Date:    06 Sept 2005
----------------------------------------------------------------------
Contents:
                1. Binkp Multiple Batch mode
                A. References
                B. History
----------------------------------------------------------------------

Status of this document
-----------------------

   This document is a Fidonet Standards Proposal (FSP).

   This document specifies an optional Fidonet standard protocol for
   the Fidonet community, and requests discussion and suggestions for
   improvements.

   This document is released to the public domain, and may be used,
   copied or modified for any purpose whatever.


1. Binkp Multiple Batch Mode
----------------------------

   The session is in MB mode if both sides set "MB" flag in any of
   M_NUL "OPT" packets exchanged before sending of M_OK/M_PWD packets.
|  This extension may only be used in protocol version binkp/1.0,
|  not in any later version. Since binkp/1.1 there is another method
|  to have multiple batches, this method is not compatible with this
|  protocol extension.

|  In MB mode both sides restart session from RxDone and TxDone into
   InitTransfer state if there were any files sent or received by any
   side between starting at InitTransfer and exchanging of M_EOB by
   the sides (RxDone state). Otherwise, the session terminates as
|  usual. The new batch may not start before both sides have send the
|  M_EOB frame and have received the M_EOB frame, in other words the
|  mailer must be in the state RxDone and TxDone.

   Multiple batches mode is intended to handle WaZOO [FTS-0006] file
   requests. If there were any WaZOO request files transferred in a
   batch, sides MAY process them and send resulting files in the next
   batch. Mailers MAY also generate list of files to send in
   additional batches by other techniques -- including rescanning of
   their spools or processing of other magic files transferred before
   in the same session.


A. References
-------------
   [FTS-0006]
          YOOHOO and YOOHOO/2U2

   [FSP-1018]
           Binkp 1.0 Protocol specification.


B. History
----------
   Rev.1, 20030630:
          First release, protocol extension separated from FSP-1011.

   Rev.1, 20030906:
          Added limitation for binkp/1.0 use only.
          Fixed description so that MB mode is forced to run in sync
          on both sides.