Concluded WG Blocks Extensible Exchange Protocol (beep)
Note: The data for concluded WGs is occasionally incorrect.
| WG | Name | Blocks Extensible Exchange Protocol | |
|---|---|---|---|
| Acronym | beep | ||
| Area | Applications Area (app) | ||
| State | Concluded | ||
| Charter | charter-ietf-beep-01 Approved | ||
| Document dependencies | |||
| Personnel | Chair | Pete Resnick | |
| Mailing list | Address | beepwg@lists.beepcore.org | |
| To subscribe | beepwg-request@lists.beepcore.org | ||
| Archive | http://lists.beepcore.org/mailman/listinfo/beepwg/ |
Final Charter for Working Group
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 milestones
| Date | Milestone | Associated documents |
|---|---|---|
| Done | Submit revised specification to the IESG for consideration as a standards-track publication. | |
| Done | Discuss and revise Internet-Draft at the Pittsburgh IETF | |
| Done | Prepare updated specification reflecting issues and solutions identified by the working group |