WG Action: Blocks Extensible Exchange Protocol (beep)
The IESG <iesg-secretary@ietf.org> Wed, 05 July 2000 12:18 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22888; Wed, 5 Jul 2000 08:18:02 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id IAA29092 for ietf-123-outbound.10@ietf.org; Wed, 5 Jul 2000 08:15:02 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id HAA29022 for <all-ietf@loki.ietf.org>; Wed, 5 Jul 2000 07:58:19 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20617 for <all-ietf>; Wed, 5 Jul 2000 07:58:19 -0400 (EDT)
Message-Id: <200007051158.HAA20617@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce:;
Subject: WG Action: Blocks Extensible Exchange Protocol (beep)
Date: Wed, 05 Jul 2000 07:58:19 -0400
Sender: scoya@cnri.reston.va.us
A new working group has been formed in the Applications Area of the IETF.
For additional information, contact the Area Directors
or the WG Chair.
Blocks Extensible Exchange Protocol (beep)
------------------------------------------
Current Status: Active Working Group
Chair(s):
Keith McCloghrie <kzm@cisco.com>
Applications Area Director(s):
Ned Freed <ned.freed@innosoft.com>
Patrik Faltstrom <paf@swip.net>
Applications Area Advisor:
Ned Freed <ned.freed@innosoft.com>
Mailing Lists:
General Discussion:bxxpwg@invisible.net
To Subscribe: bxxpwg-request@invisible.net
Archive: http://lists.invisible.net/pipermail/bxxpwg/
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:
Jul 00 Prepare updated specification reflecting issues and solutions
identified by the working group
Aug 00 Discuss and revise Internet-Draft at the Pittsburgh IETF
Jan 01 Submit revised specification to the IESG for consideration as a
standards-track publication.