RFC 3117 on On the Design of Application Protocols
RFC Editor <rfc-ed@ISI.EDU> Tue, 06 November 2001 19:03 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27400; Tue, 6 Nov 2001 14:03:34 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id NAA20187 for ietf-123-outbound.10@ietf.org; Tue, 6 Nov 2001 13:55:01 -0500 (EST)
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 NAA20138 for <all-ietf@loki.ietf.org>; Tue, 6 Nov 2001 13:46:58 -0500 (EST)
Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26655 for <all-ietf@ietf.org>; Tue, 6 Nov 2001 13:46:55 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id fA6IkvH25122; Tue, 6 Nov 2001 10:46:57 -0800 (PST)
Message-Id: <200111061846.fA6IkvH25122@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3117 on On the Design of Application Protocols
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 06 Nov 2001 10:46:57 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
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.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.