From bxxpwg-admin@lists.invisibleworlds.com Mon Mar 5 17:29:14 2001 Received: from trystero.not.invisible.net ([204.62.247.11]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA07727 for ; Mon, 5 Mar 2001 17:29:13 -0500 (EST) Received: from trystero.not.invisible.net (localhost [127.0.0.1]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with ESMTP id OAA11261; Mon, 5 Mar 2001 14:27:37 -0800 (PST) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with ESMTP id NAA10932 for ; Mon, 5 Mar 2001 13:42:29 -0800 (PST) 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: ; 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 Subject: [BXXPwg] RFC 3080 on The BEEP Core Sender: bxxpwg-admin@lists.invisibleworlds.com Errors-To: bxxpwg-admin@lists.invisibleworlds.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: Mailing list for the IETF's BEEP Working Group X-BeenThere: bxxpwg@lists.invisible.net --NextPart 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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <010305134015.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3080 --OtherAccess Content-Type: Message/External-body; name="rfc3080.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <010305134015.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- _______________________________________________ BXXPwg mailing list BXXPwg@lists.invisible.net http://lists.invisible.net/mailman/listinfo/bxxpwg From bxxpwg-admin@lists.invisibleworlds.com Mon Mar 5 17:29:16 2001 Received: from trystero.not.invisible.net ([204.62.247.11]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA07737 for ; Mon, 5 Mar 2001 17:29:15 -0500 (EST) Received: from trystero.not.invisible.net (localhost [127.0.0.1]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with ESMTP id OAA11300; Mon, 5 Mar 2001 14:28:15 -0800 (PST) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with ESMTP id NAA10961 for ; Mon, 5 Mar 2001 13:44:49 -0800 (PST) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.11.2/8.11.2) with ESMTP id f25LidG02406; Mon, 5 Mar 2001 13:44:39 -0800 (PST) Message-Id: <200103052144.f25LidG02406@boreas.isi.edu> To: IETF-Announce: ; Cc: rfc-ed@ISI.EDU, bxxpwg@invisible.net Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Mon, 05 Mar 2001 13:44:39 -0800 From: RFC Editor Subject: [BXXPwg] RFC 3081 on Mapping the BEEP Core onto TCP Sender: bxxpwg-admin@lists.invisibleworlds.com Errors-To: bxxpwg-admin@lists.invisibleworlds.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: Mailing list for the IETF's BEEP Working Group X-BeenThere: bxxpwg@lists.invisible.net --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3081 Title: Mapping the BEEP Core onto TCP Author(s): M. Rose Status: Standards Track Date: March 2001 Mailbox: mrose@invisible.net Pages: 8 Characters: 14008 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-beep-tcpmapping-06.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3081.txt This memo describes how a BEEP (Blocks Extensible Exchange Protocol) session is mapped onto a single TCP (Transmission Control Protocol) connection. 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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <010305134237.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3081 --OtherAccess Content-Type: Message/External-body; name="rfc3081.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <010305134237.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- _______________________________________________ BXXPwg mailing list BXXPwg@lists.invisible.net http://lists.invisible.net/mailman/listinfo/bxxpwg From bxxpwg-admin@lists.invisibleworlds.com Mon Mar 19 17:49:56 2001 Received: from trystero.not.invisible.net (trystero.not.invisible.net [204.62.247.11]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA24573 for ; Mon, 19 Mar 2001 17:49:56 -0500 (EST) Received: from trystero.not.invisible.net (localhost [127.0.0.1]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with ESMTP id OAA27250; Mon, 19 Mar 2001 14:48:21 -0800 (PST) Received: from hoth.ffwd.cx (host242.fastfind.com [209.153.243.242] (may be forged)) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with ESMTP id OAA27234 for ; Mon, 19 Mar 2001 14:48:20 -0800 (PST) Received: from skye by hoth.ffwd.cx with local (Exim 3.13 #1) id 14f8RK-000KFD-00 for bxxpwg@lists.invisibleworlds.com; Mon, 19 Mar 2001 14:47:50 -0800 Date: Mon, 19 Mar 2001 14:47:50 -0800 From: Skye Poier To: bxxpwg@lists.invisibleworlds.com Message-ID: <20010319144750.C71124@ffwd.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-URL: http://www.ffwd.cx/ Subject: [BXXPwg] bxxp.org? Sender: bxxpwg-admin@lists.invisibleworlds.com Errors-To: bxxpwg-admin@lists.invisibleworlds.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: Mailing list for the IETF's BEEP Working Group X-BeenThere: bxxpwg@lists.invisible.net What's the status of bxxp.org? It seems like it hasn't been updated in quite a while.... CVSweb is broken... etc Skye -- ffwd internet division - www.ffwd.cx _______________________________________________ BXXPwg mailing list BXXPwg@lists.invisible.net http://lists.invisible.net/mailman/listinfo/bxxpwg From bxxpwg-admin@lists.invisibleworlds.com Mon Mar 19 18:06:41 2001 Received: from trystero.not.invisible.net (trystero.not.invisible.net [204.62.247.11]) by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA24980 for ; Mon, 19 Mar 2001 18:06:40 -0500 (EST) Received: from trystero.not.invisible.net (localhost [127.0.0.1]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with ESMTP id PAA27404; Mon, 19 Mar 2001 15:05:38 -0800 (PST) Received: from ballistic (vpn-21.not.invisible.net [204.62.247.244]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with SMTP id PAA27390; Mon, 19 Mar 2001 15:05:06 -0800 (PST) Message-ID: <001601c0b0c9$1c6a0880$1900a8c0@ballistic> From: "Kristopher Magnusson" To: "Skye Poier" , References: <20010319144750.C71124@ffwd.cx> Subject: Re: [BXXPwg] bxxp.org? Date: Mon, 19 Mar 2001 15:04:39 -0800 Organization: Invisible Worlds, Inc. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: bxxpwg-admin@lists.invisibleworlds.com Errors-To: bxxpwg-admin@lists.invisibleworlds.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: Mailing list for the IETF's BEEP Working Group X-BeenThere: bxxpwg@lists.invisible.net Content-Transfer-Encoding: 7bit we're still in a state of transition. lots of new stuff in the works. and there's light at the end of the tunnel. bxxp.org is going away and will be replaced with beepcore.org. the ftp tarball hosting, cvs repositories, mailing lists, and bug tracking facilities at bxxp.org are being moved to sourceforge. the legacy spacekits are being phased out. their replacements will be new implementations in java, perl, tcl, and soon c--all compliant with rfc 3080. they have been designed with beepcore.org is up and running on our staging server and will be live within a matter of days. ............. kris ----- Original Message ----- From: "Skye Poier" To: Sent: Monday, March 19, 2001 2:47 PM Subject: [BXXPwg] bxxp.org? > What's the status of bxxp.org? It seems like it hasn't been updated > in quite a while.... CVSweb is broken... etc > > Skye > > -- > ffwd internet division - www.ffwd.cx > > _______________________________________________ > BXXPwg mailing list > BXXPwg@lists.invisible.net > http://lists.invisible.net/mailman/listinfo/bxxpwg > _______________________________________________ BXXPwg mailing list BXXPwg@lists.invisible.net http://lists.invisible.net/mailman/listinfo/bxxpwg From bxxpwg-admin@lists.invisibleworlds.com Mon Mar 19 19:58:49 2001 Received: from trystero.not.invisible.net (trystero.not.invisible.net [204.62.247.11]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA28119 for ; Mon, 19 Mar 2001 19:58:49 -0500 (EST) Received: from trystero.not.invisible.net (localhost [127.0.0.1]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with ESMTP id QAA28072; Mon, 19 Mar 2001 16:57:38 -0800 (PST) Received: from xomi.pair.com (xomi.pair.com [209.68.2.14]) by trystero.not.invisible.net (8.9.3+Sun/8.9.3) with SMTP id QAA28057 for ; Mon, 19 Mar 2001 16:57:36 -0800 (PST) Received: (qmail 34857 invoked by uid 3039); 20 Mar 2001 00:57:31 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 20 Mar 2001 00:57:31 -0000 Date: Mon, 19 Mar 2001 16:57:31 -0800 (PST) From: Gabe Wachob X-Sender: To: Kristopher Magnusson cc: Skye Poier , Subject: Re: [BXXPwg] bxxp.org? In-Reply-To: <001601c0b0c9$1c6a0880$1900a8c0@ballistic> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bxxpwg-admin@lists.invisibleworlds.com Errors-To: bxxpwg-admin@lists.invisibleworlds.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: Mailing list for the IETF's BEEP Working Group X-BeenThere: bxxpwg@lists.invisible.net How about those of us who had projects on bxxp.org? I already have a pybxxp project on sourceforge (you in fact convinced me to take it to bxxp.org ;-) Should we just put everything up on sourceforge? Also, Kris, I don't think you've announced what this "transition" is about! -Gabe On Mon, 19 Mar 2001, Kristopher Magnusson wrote: > we're still in a state of transition. lots of new stuff in the works. and > there's light at the end of the tunnel. > > bxxp.org is going away and will be replaced with beepcore.org. > > the ftp tarball hosting, cvs repositories, mailing lists, and bug tracking > facilities at bxxp.org are being moved to sourceforge. > > the legacy spacekits are being phased out. their replacements will be new > implementations in java, perl, tcl, and soon c--all compliant with rfc 3080. > they have been designed with > > beepcore.org is up and running on our staging server and will be live within > a matter of days. > > ............. kris > > ----- Original Message ----- > From: "Skye Poier" > To: > Sent: Monday, March 19, 2001 2:47 PM > Subject: [BXXPwg] bxxp.org? > > > > What's the status of bxxp.org? It seems like it hasn't been updated > > in quite a while.... CVSweb is broken... etc > > > > Skye > > > > -- > > ffwd internet division - www.ffwd.cx > > > > _______________________________________________ > > BXXPwg mailing list > > BXXPwg@lists.invisible.net > > http://lists.invisible.net/mailman/listinfo/bxxpwg > > > > > _______________________________________________ > BXXPwg mailing list > BXXPwg@lists.invisible.net > http://lists.invisible.net/mailman/listinfo/bxxpwg > _______________________________________________ BXXPwg mailing list BXXPwg@lists.invisible.net http://lists.invisible.net/mailman/listinfo/bxxpwg