Javascript disabled? Like other modern websites, the IETF Datatracker relies on Javascript.
Please enable Javascript for full functionality.
The Blocks Extensible Exchange Protocol Core
draft-ietf-beep-framework-11
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 3080.
|
|---|---|---|
| Author | Dr. Marshall T. Rose | |
| Last updated | 2020年01月21日 (Latest revision 2001年01月05日) | |
| RFC stream | Internet Engineering Task Force (IETF) | |
| Intended RFC status | Proposed Standard | |
| Formats | ||
| Additional resources | Mailing list discussion | |
| Stream | WG state | (None) |
| Document shepherd | (None) | |
| IESG | IESG state | Became RFC 3080 (Proposed Standard) |
| Consensus boilerplate | Unknown | |
| Telechat date | (None) | |
| Responsible AD | (None) | |
| Send notices to | (None) |
draft-ietf-beep-framework-11
A new Request for Comments is now available in online RFC libraries. RFC 3080 Title: The Blocks Extensible Exchange Protocol Core Author(s): M. Rose Status: Standards Track Date: March 2001 Mailbox: mrose@invisible.net Pages: 58 Characters: 82089 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-beep-framework-11.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3080.txt This memo describes a generic application protocol kernel for connection-oriented, asynchronous interactions called the BEEP (Blocks Extensible Exchange Protocol) core. BEEP permits simultaneous and independent exchanges within the context of a single application user-identity, supporting both textual and binary messages. This document is a product of the Blocks Extensible Exchange Protocol Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. 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.