RFC 2125 (rfc2125) - Page 2 of 24

The PPP Bandwidth Allocation Protocol (BAP) / The PPP Bandwidth Allocation Control Protocol (BACP)

RFC 2125                       PPP BACP                       March 1997


         5.5.3  Callback-Request ................................   13
         5.5.4  Callback-Response ...............................   13
         5.5.5  Link-Drop-Query-Request .........................   13
         5.5.6  Link-Drop-Query-Response ........................   13
         5.5.7  Call-Status-Indication ..........................   14
         5.5.8  Call-Status-Response ............................   14
   6.     BAP Datagram Options ..................................   14
      6.1       Link-Type .......................................   15
      6.2       Phone-Delta .....................................   17
         6.2.1  Phone-Delta Sub-Options .........................   18
      6.3       No-Phone-Number-Needed ..........................   19
      6.4       Reason ..........................................   20
      6.5       Link-Discriminator ..............................   21
      6.6       Call-Status .....................................   21
   Appendix - List of BAP datagrams and associated fields .......   23
   ACKNOWLEDEMENTS ..............................................   23
   SECURITY CONSIDERATIONS ......................................   23
   REFERENCES ...................................................   24
   CHAIR'S ADDRESS ..............................................   24
   EDITORS'S ADDRESSES ..........................................   24

1.  Introduction

   As PPP multilink implementations become increasingly common, there is
   a greater need for some conformity in how to manage bandwidth over
   such links. BACP and BAP provide a flexible yet robust way of
   managing bandwidth between 2 peers.  BAP does this by defining Call-
   Control packets and a protocol that allows peers to co-ordinate the
   actual bandwidth allocation and de-allocation.  Phone number deltas
   may be passed in the Call-Control packets to minimize the end user's
   configuration.

1.1.  Specification of Requirements

   In this document, several words are used to signify the requirements
   of the specification.  These words are often capitalized.

   MUST      This word, or the adjective "required", means that the
             definition is an absolute requirement of the specification.

   MUST NOT  This phrase means that the definition is an absolute
             prohibition of the specification.

   SHOULD    This word, or the adjective "recommended", means that there
             may exist valid reasons in particular circumstances to
             ignore this item, but the full implications must be
             understood and carefully weighed before choosing a
             different course.



Richards & Smith            Standards Track