WG Review: Blocks eXtensible eXchange Protocol (bxxpwg)

The IESG <iesg-secretary@ietf.org> Mon, 19 June 2000 17:06 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15624; Mon, 19 Jun 2000 13:06:19 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id NAA21220 for ietf-123-outbound.10@ietf.org; Mon, 19 Jun 2000 13:05:01 -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 NAA21190 for <all-ietf@loki.ietf.org>; Mon, 19 Jun 2000 13:03:12 -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 NAA15329; Mon, 19 Jun 2000 13:03:06 -0400 (EDT)
Message-Id: <200006191703.NAA15329@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce:;
cc: new-work@ietf.org
Subject: WG Review: Blocks eXtensible eXchange Protocol (bxxpwg)
Date: Mon, 19 Jun 2000 13:03:06 -0400
Sender: scoya@cnri.reston.va.us

A new IETF working group has been proposed in the Applications Area.
The IESG has not made any determination as yet. 

The following Description was submitted, and is provided for
informational purposes only:

Blocks eXtensible eXchange Protocol (bxxpwg)
--------------------------------------------
 
 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 BXXP 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 shall use BXXP (as described in
draft-mrose-blocks-protocol-03) as its starting point. The working group
is authorized to make incompatible changes to BXXP providing that it
document solid technical reasons for doing so.