On the Design of Application Protocols
draft-mrose-beep-design-03

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3117.
Author Dr. Marshall T. Rose
Last updated 2013-03-02 (Latest revision 2001-03-30)
RFC stream Legacy stream
Intended RFC status Informational
Formats
txt htmlized pdf bibtex bibxml
Stream Legacy state (None)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Became RFC 3117 (Informational)
Telechat date (None)
Responsible AD (None)
Send notices to (None)
Email authors IPR References Referenced by Nits Search email archive
draft-mrose-beep-design-03 
A new Request for Comments is now available in online RFC libraries.

        RFC 3117

        Title:      On the Design of Application Protocols
        Author(s):  M. Rose
        Status:     Informational
        Date:       November 2001
        Mailbox:    mrose@dbc.mtview.ca.us
        Pages:      25
        Characters: 57279
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-mrose-beep-design-03.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3117.txt

This memo describes the design principles for the Blocks eXtensible
eXchange Protocol (BXXP).  BXXP is a generic application protocol
framework for connection-oriented, asynchronous interactions.  The
framework permits simultaneous and independent exchanges within the
context of a single application user-identity, supporting both
textual and binary messages.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.