datatracker.ietf.org
Sign in
Version 5.6.2.p3, 2014-07-31
Report a bug

Blocks Extensible Exchange Protocol (beep)
(concluded WG)

Note: The data for concluded WGs is occasionally incorrect.
Group
Name: Blocks Extensible Exchange Protocol
Acronym:beep
Area:Applications Area (app)
State: Concluded
Charter: charter-ietf-beep-01 (Approved)
Personnel
Chair: Pete Resnick <presnick@qualcomm.com>
Mailing List
Address:beepwg@lists.beepcore.org
To Subscribe:beepwg-request@lists.beepcore.org
Archive:http://lists.beepcore.org/mailman/listinfo/beepwg/

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.

Milestones

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.