RFC 3080 on The BEEP Core
RFC Editor <rfc-ed@ISI.EDU> Mon, 05 March 2001 22:52 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08681; Mon, 5 Mar 2001 17:52:06 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id RAA29946 for ietf-123-outbound.10@ietf.org; Mon, 5 Mar 2001 17:45:02 -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 QAA29339 for <all-ietf@loki.ietf.org>; Mon, 5 Mar 2001 16:42:25 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA05598 for <all-ietf@ietf.org>; Mon, 5 Mar 2001 16:42:19 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.11.2/8.11.2) with ESMTP id f25LgAG01921; Mon, 5 Mar 2001 13:42:10 -0800 (PST)
Message-Id: <200103052142.f25LgAG01921@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 3080 on The BEEP Core
Cc: rfc-ed@ISI.EDU, bxxpwg@invisible.net
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 05 Mar 2001 13:42:10 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
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. 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.
- RFC 3080 on The BEEP Core RFC Editor