RFC 2125: The PPP Bandwidth Allocation Protocol (BAP) / The PPP Bandwidth Allocation Control Protocol (BACP)
In plain English — editorial summary, not part of the RFC
This document proposes a method to manage the dynamic bandwidth allocation of implementations supporting the PPP multilink protocol. This is done by defining the Bandwidth Allocation Protocol (BAP), as well as its associated control protocol, the Bandwidth Allocation Control Protocol (BACP). [STANDARDS-TRACK]
Document record
- Document ID
- RFC2125
- Published
- March 1997
- Authors
- C. Richards; K. Smith
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3336PPP Over Asynchronous Transfer Mode Adaptation Layer 2 (AAL2)Current
December 2002
- RFC 2118Microsoft Point-To-Point Compression (MPPC) ProtocolCurrent
March 1997
- RFC 2147TCP and UDP over IPv6 JumbogramsObsoleted
May 1997
- RFC 2097The PPP NetBIOS Frames Control Protocol (NBFCP)Current
January 1997
- RFC 2153PPP Vendor ExtensionsUpdated
May 1997
- RFC 2043The PPP SNA Control Protocol (SNACP)Current
October 1996
- RFC 1994PPP Challenge Handshake Authentication Protocol (CHAP)Updated
August 1996
- RFC 1993PPP Gandalf FZA Compression ProtocolCurrent
August 1996
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?