[BXXPwg] proposed draft for BXXP working group

Marshall Rose mrose@dbc.mtview.ca.us
Sat, 3 Jun 2000 12:11:10 -0700


This is a multi-part message in MIME format.

------=_NextPart_000_017B_01BFCD54.CE1B3620
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_017C_01BFCD54.CE1B3620"


------=_NextPart_001_017C_01BFCD54.CE1B3620
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit



------=_NextPart_001_017C_01BFCD54.CE1B3620
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3017.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_001_017C_01BFCD54.CE1B3620--

------=_NextPart_000_017B_01BFCD54.CE1B3620
Content-Type: text/plain;
	name="bxxpwg-charter.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="bxxpwg-charter.txt"

Blocks eXtensible eXchange Protocol (bxxpwg)
    
Chair:
    Keith McCloghrie <kzm@cisco.com>
    
Applications Area Director(s): 
    Patrik Faltstrom <paf@swip.net>
    Ned Freed <ned.freed@innosoft.com>
    
Applications Area Advisor: 
    Patrik Faltstrom <paf@swip.net>

Mailing Lists: 
    General Discussion: bxxpwg@invisible.net
    To Subscribe:       bxxpwg-request@invisible.net
    Archive:	        http://lists.invisible.net/pipermail/bxxpwg/
    
Description:
    
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.
    
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 00    Submit revised specification to the IESG for consideration
              as a standards-track publication.
    
    
Current Internet-Drafts
    draft-mrose-blocks-protocol-03
    
Request For Comments
    none

------=_NextPart_000_017B_01BFCD54.CE1B3620--