Blocks Extensible Exchange Protocol (beep)
This Working Group did not meet
NOTE: This charter is a snapshot of the 51st IETF Meeting in London, England. It may now be out-of-date. Last Modified: 31-Jul-01
Pete Resnick <presnick@qualcomm.com>
Ned Freed <ned.freed@mrochek.com>
Patrik Faltstrom <paf@cisco.com>
Ned Freed <ned.freed@mrochek.com>
General Discussion:bxxpwg@invisible.net
To Subscribe: bxxpwg-request@invisible.net
Archive: http://lists.invisible.net/pipermail/bxxpwg/
The IETF BEEP working group shall develop a standards-track application protocol framework for connection-oriented, asynchronous request/response interactions.
The framework must permit multiplexing of independent request/response streams over a single transport conneciton, supporting both textual and binary messages.
The working group will use BXXP (as described in draft-mrose-bxxp-framework and draft-mrose-bxxp-tcpmapping) as its starting point. Although not encouraged, non-backwards-compatible changes to BXXP will be acceptable if the working group determines that the changes are required to meet the group's technical objectives and the group clearly documents the reasons for making them.
Done |
|
Prepare updated specification reflecting issues and solutions identified by the working group |
Done |
|
Discuss and revise Internet-Draft at the Pittsburgh IETF |
Done |
|
Submit revised specification to the IESG for consideration as a standards-track publication. |
RFC |
Status |
Title |
RFC3081 |
PS |
Mapping the BEEP Core onto TCP |
RFC3080 |
PS |
The Blocks Extensible Exchange Protocol Core |