Blocks Extensible Exchange Protocol (beep)
------------------------------------------
Charter
Last Modified: 2002-03-24
Current Status: Concluded Working Group
Chair(s):
Pete Resnick <
[email protected]>
Applications Area Director(s):
Ned Freed <
[email protected]>
Patrik Faltstrom <
[email protected]>
Applications Area Advisor:
Ned Freed <
[email protected]>
Mailing Lists:
General Discussion:
[email protected]
To Subscribe:
[email protected]
In Body: subscribe
Archive:
http://lists.beepcore.org/mailman/listinfo/beepwg/
Description of 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.
Goals and 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.
Internet-Drafts:
No Current Internet-Drafts.
Request For Comments:
RFC Stat Published Title
------- -- ----------- ------------------------------------
RFC3081 PS MAR 01 Mapping the BEEP Core onto TCP
RFC3080 PS MAR 01 The Blocks Extensible Exchange Protocol Core
