From beepwg-admin@lists.beepcore.org Thu Jul 24 09:56:05 2003 Received: from qawoor.dbc.mtview.ca.us (adsl-64-168-10-251.dsl.scrm01.pacbell.net [64.168.10.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06493 for ; Thu, 24 Jul 2003 09:55:56 -0400 (EDT) Received: from qawoor.dbc.mtview.ca.us (localhost [127.0.0.1]) by qawoor.dbc.mtview.ca.us (8.11.5/8.11.5) with ESMTP id h6ODsGX27923; Thu, 24 Jul 2003 06:54:17 -0700 (PDT) Received: from grfext.intern.adiscon.com (grfext.intern.adiscon.com [217.6.190.187] (may be forged)) by qawoor.dbc.mtview.ca.us (8.11.5/8.11.5) with SMTP id h6ODqvX27906 for ; Thu, 24 Jul 2003 06:53:01 -0700 (PDT) Received: from 172.19.0.5 by grfext.intern.adiscon.com (InterScan E-Mail VirusWall NT); Thu, 24 Jul 2003 15:52:52 +0200 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Message-ID: <28915501A44DBA4587FE1019D675F98309390E@grfint.intern.adiscon.com> Thread-Topic: RFC3081/SEQ frame Thread-Index: AcNR6t7pCVnsbD71S6iMiHStUvQD5A== From: "Rainer Gerhards" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by qawoor.dbc.mtview.ca.us id h6ODqvX27906 Subject: [BEEPwg] RFC3081/SEQ frame Sender: beepwg-admin@lists.beepcore.org Errors-To: beepwg-admin@lists.beepcore.org X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.0.6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: Date: Thu, 24 Jul 2003 15:52:51 +0200 Content-Transfer-Encoding: 8bit Hi list, I am implementing a partial BEEP stack for rfc3195 syslog. I have a question in regard to the SEQ message. RFC3081 says regarding ackn -- o an acknowledgement number, that indicates the value of the next sequence number that the sender is expecting to receive on this channel; and, -- I am doing testing against the RoadRunner library. I am sending syslog raw (Rfc 3195) messages. My initiator sees SEQ frames from the listener more or less at the end of the window, HOWEVER, the ackn points back to frames that have already been sent some time before. I have confirmed the timing with a network packet capture. For example, I see an initial SEQ after sending 4070 bytes (which is fine), but it specifies an ackno of 2839. If I look at the network trace, frame 2839 has been packed by the IP stack into a single network packet that goes up to seqno 2950. My app managed to send another two packets (each one containing more than a single frame) before the SEQ arrived. Does this mean I need to retransmit everything beginning at 2839 (which was a valid seqno)? I am right now *ignoring* the ackno at all and continue sending as long as I receive a "good" SEQ back. In doing so, all messages arrive without any one missing and in order. However, the ackno diverts more and more from the actual seqno. For example, the last SEQ has an ackno of 3453930 and I receive this frame after sending msg 3988850. I would deeply appreciate if anybody could explain/provide pointers to how this is supposed to work. Many thanks, Rainer Gerhards _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://lists.beepcore.org/mailman/listinfo/beepwg From beepwg-admin@lists.beepcore.org Thu Jul 24 12:13:44 2003 Received: from qawoor.dbc.mtview.ca.us (adsl-64-168-10-251.dsl.scrm01.pacbell.net [64.168.10.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12232 for ; Thu, 24 Jul 2003 12:13:43 -0400 (EDT) Received: from qawoor.dbc.mtview.ca.us (localhost [127.0.0.1]) by qawoor.dbc.mtview.ca.us (8.11.5/8.11.5) with ESMTP id h6OGD4X29140; Thu, 24 Jul 2003 09:13:04 -0700 (PDT) Received: from drakken.dbc.mtview.ca.us ([65.125.189.56]) by qawoor.dbc.mtview.ca.us (8.11.5/8.11.5) with ESMTP id h6OGC1X29126 for ; Thu, 24 Jul 2003 09:12:01 -0700 (PDT) Received: from drakken.dbc.mtview.ca.us (localhost [127.0.0.1]) by drakken.dbc.mtview.ca.us (8.12.9/8.12.9) with SMTP id h6OGBtsP001318; Thu, 24 Jul 2003 09:11:55 -0700 (PDT) From: Marshall Rose To: "Rainer Gerhards" Cc: Subject: Re: [BEEPwg] RFC3081/SEQ frame Message-Id: <20030724091155.1fe767b6.mrose@dbc.mtview.ca.us> In-Reply-To: <28915501A44DBA4587FE1019D675F98309390E@grfint.intern.adiscon.com> References: <28915501A44DBA4587FE1019D675F98309390E@grfint.intern.adiscon.com> Organization: Dover Beach Consulting, Inc. X-Mailer: Sylpheed version 0.8.11claws (GTK+ 1.2.10; i386--netbsdelf) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: beepwg-admin@lists.beepcore.org Errors-To: beepwg-admin@lists.beepcore.org X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.0.6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: Date: Thu, 24 Jul 2003 09:11:55 -0700 Content-Transfer-Encoding: 7bit > I am implementing a partial BEEP stack for rfc3195 syslog. groovy! > I have a > question in regard to the SEQ message. RFC3081 says regarding ackn > > -- > o an acknowledgement number, that indicates the value of the next > sequence number that the sender is expecting to receive on this > channel; and, > -- > ... two things: 1. you never re-transmit anything. tcp is giving you reliability. the SEQ frame is allowing you to share bandwidth between multiple channels being multiplexed on the same tcp connection. 2. the SEQ frame isn't supposed to be synchronized with what you're sending (unless the window goes to zero). what you do is keep track of the number of octets you've sent. the SEQ frame tells you how many more octets you're allowed to send. so, if you see SEQ 1 100 2000 the way to interpret this is the remote peer saying at the time that i had received 100 octets from you on channel 1, i was prepared to accept up to another 2000 octets from you. let's say you've gotten this after sending a total of 1900 octets on channel 1. by my math, you can now send upto 200 octets on channel 1. presumably, as the remote peer is receiving data from you, it's passing that up to the application, and sending back another SEQ. in fact, you may see a SEQ even if you haven't sent traffic for a while, simply because the application has consumed previous traffic you've sent and the window is opened up... /mtr _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://lists.beepcore.org/mailman/listinfo/beepwg From beepwg-admin@lists.beepcore.org Wed Jul 30 00:01:28 2003 Received: from qawoor.dbc.mtview.ca.us (adsl-64-168-10-251.dsl.scrm01.pacbell.net [64.168.10.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21664 for ; Wed, 30 Jul 2003 00:01:27 -0400 (EDT) Received: from qawoor.dbc.mtview.ca.us (localhost [127.0.0.1]) by qawoor.dbc.mtview.ca.us (8.11.5/8.11.5) with ESMTP id h6U40MA24406; Tue, 29 Jul 2003 21:00:32 -0700 (PDT) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by qawoor.dbc.mtview.ca.us (8.11.5/8.11.5) with ESMTP id h6U1haA23362 for ; Tue, 29 Jul 2003 18:43:37 -0700 (PDT) Received: from michael (pcp04160772pcs.wchstr01.pa.comcast.net[68.83.1.40](untrusted sender)) by comcast.net (sccrmhc11) with SMTP id <2003073001431201100obrnje>; Wed, 30 Jul 2003 01:43:12 +0000 Message-ID: <002501c3563b$d0611b70$0301000a@michael> From: "Michael J. Riggio" To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0022_01C3561A.4924C1F0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: [BEEPwg] BEEP and .Net Sender: beepwg-admin@lists.beepcore.org Errors-To: beepwg-admin@lists.beepcore.org X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.0.6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: Date: Tue, 29 Jul 2003 21:42:19 -0400 This is a multi-part message in MIME format. ------=_NextPart_000_0022_01C3561A.4924C1F0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I was wondering if there is a .Net implementation of BEEP? I = haven't worked with BEEP in a long time, and when I did it wasn't very = deep, but I do remember that there were/are several implementations in = languages such as java and c. I was wondering if there is a reason why = no one has taken the .Net (c#) approach yet? Am I missing in something = in the framework that provides functionality similar to BEEP? Any links or suggestions would be greatly appreciated. Thanks, -Mike Riggio ------=_NextPart_000_0022_01C3561A.4924C1F0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
      I was = wondering if=20 there is a .Net implementation of BEEP?  I haven't worked with BEEP = in a=20 long time, and when I did it wasn't very deep, but I do remember that = there=20 were/are several implementations in languages such as java and c.  = I was=20 wondering if there is a reason why no one has taken the .Net (c#) = approach=20 yet?  Am I missing in something in the framework that provides=20 functionality similar to BEEP?
 
      Any = links or=20 suggestions would be greatly appreciated.
 
Thanks,
-Mike Riggio
------=_NextPart_000_0022_01C3561A.4924C1F0-- _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://lists.beepcore.org/mailman/listinfo/beepwg From beepwg-admin@lists.beepcore.org Wed Jul 30 02:44:22 2003 Received: from qawoor.dbc.mtview.ca.us (adsl-64-168-10-251.dsl.scrm01.pacbell.net [64.168.10.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21442 for ; Wed, 30 Jul 2003 02:44:22 -0400 (EDT) Received: from qawoor.dbc.mtview.ca.us (localhost [127.0.0.1]) by qawoor.dbc.mtview.ca.us (8.11.5/8.11.5) with ESMTP id h6U6i3A25446; Tue, 29 Jul 2003 23:44:04 -0700 (PDT) Received: from mail.labs2.com (qmailr@mail.labs2.com [62.119.73.240]) by qawoor.dbc.mtview.ca.us (8.11.5/8.11.5) with SMTP id h6U6h5A25434 for ; Tue, 29 Jul 2003 23:43:05 -0700 (PDT) Received: (qmail 11810 invoked from network); 30 Jul 2003 06:42:48 -0000 Received: from unknown (HELO labs2.org) (62.119.73.218) by mail.labs2.com with SMTP; 30 Jul 2003 06:42:48 -0000 Received: (qmail 11630 invoked from network); 30 Jul 2003 06:42:47 -0000 Received: from unknown (HELO labs2.com) (10.50.1.18) by labs2.org with SMTP; 30 Jul 2003 06:42:47 -0000 Message-ID: <3F27682A.6070201@labs2.com> From: =?ISO-8859-1?Q?Olof_H=E4rwell?= Organization: Labs2 AB User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Michael J. Riggio" CC: beepwg@lists.beepcore.org Subject: Re: [BEEPwg] BEEP and .Net References: <002501c3563b$d0611b70$0301000a@michael> In-Reply-To: <002501c3563b$d0611b70$0301000a@michael> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Sender: beepwg-admin@lists.beepcore.org Errors-To: beepwg-admin@lists.beepcore.org X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.0.6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: Date: Wed, 30 Jul 2003 08:39:38 +0200 Content-Transfer-Encoding: 8bit Hi Intel published a P2P framework a year ago in c# that used a BEEP-based remoting provider for the .NET framework. It used to be on the www.gotdotnet.com site but now I can't find it there. Cheers Olof Härwell Michael J. Riggio wrote: > Hi, > I was wondering if there is a .Net implementation of BEEP? I > haven't worked with BEEP in a long time, and when I did it wasn't very > deep, but I do remember that there were/are several implementations in > languages such as java and c. I was wondering if there is a reason why > no one has taken the .Net (c#) approach yet? Am I missing in something > in the framework that provides functionality similar to BEEP? > > Any links or suggestions would be greatly appreciated. > > Thanks, > -Mike Riggio -- /* Olof Härwell Systems Architect Labs2 AB Direct: +46 46 540 01 10 Mobile: +46 70 941 20 10 Phone: +46 46 13 74 25 Fax: +46 46 13 74 26 Address: Winstrupsgatan 1, SE-222 22 Lund, Sweden Internet: http://www.labs2.com */ _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://lists.beepcore.org/mailman/listinfo/beepwg From beepwg-admin@lists.beepcore.org Wed Jul 30 12:13:15 2003 Received: from qawoor.dbc.mtview.ca.us (adsl-64-168-10-251.dsl.scrm01.pacbell.net [64.168.10.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06612 for ; Wed, 30 Jul 2003 12:13:14 -0400 (EDT) Received: from qawoor.dbc.mtview.ca.us (localhost [127.0.0.1]) by qawoor.dbc.mtview.ca.us (8.11.5/8.11.5) with ESMTP id h6UGD4A29817; Wed, 30 Jul 2003 09:13:04 -0700 (PDT) Received: from mandarin.kinitos.com (mandarin.kinitos.com [198.63.211.5]) by qawoor.dbc.mtview.ca.us (8.11.5/8.11.5) with ESMTP id h6UGChA29805 for ; Wed, 30 Jul 2003 09:12:43 -0700 (PDT) Received: from MIKEI ([66.46.9.57]) (authenticated) by mandarin.kinitos.com (8.11.6/8.11.6) with ESMTP id h6UGCXI32094 for ; Wed, 30 Jul 2003 11:12:33 -0500 From: "Michael Iles" To: Subject: RE: [BEEPwg] BEEP and .Net Message-ID: <006401c356b5$5b64ae20$66bba8c0@MIKEI> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal In-Reply-To: <3F27682A.6070201@labs2.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by qawoor.dbc.mtview.ca.us id h6UGChA29805 Sender: beepwg-admin@lists.beepcore.org Errors-To: beepwg-admin@lists.beepcore.org X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.0.6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: Date: Wed, 30 Jul 2003 12:12:21 -0400 Content-Transfer-Encoding: 8bit Clipcode apparently had plans to release a C# BEEP implementation, in fact someone from Clipcode announced the start of the beta on this list in Nov 2001. Does anyone know what happened to this? The project is described on their site but no code seems to be available. A BEEP implementation for .NET would be very useful: the network transports provided by .NET (remoting and web services) are both connectionless. Mike. -----Original Message----- From: beepwg-admin@lists.beepcore.org [mailto:beepwg-admin@lists.beepcore.org] On Behalf Of Olof Härwell Sent: July 30, 2003 2:40 AM To: Michael J. Riggio Cc: beepwg@lists.beepcore.org Subject: Re: [BEEPwg] BEEP and .Net Hi Intel published a P2P framework a year ago in c# that used a BEEP-based remoting provider for the .NET framework. It used to be on the www.gotdotnet.com site but now I can't find it there. Cheers Olof Härwell Michael J. Riggio wrote: > Hi, > I was wondering if there is a .Net implementation of BEEP? I > haven't worked with BEEP in a long time, and when I did it wasn't very > deep, but I do remember that there were/are several implementations in > languages such as java and c. I was wondering if there is a reason why > no one has taken the .Net (c#) approach yet? Am I missing in something > in the framework that provides functionality similar to BEEP? > > Any links or suggestions would be greatly appreciated. > > Thanks, > -Mike Riggio -- /* Olof Härwell Systems Architect Labs2 AB Direct: +46 46 540 01 10 Mobile: +46 70 941 20 10 Phone: +46 46 13 74 25 Fax: +46 46 13 74 26 Address: Winstrupsgatan 1, SE-222 22 Lund, Sweden Internet: http://www.labs2.com */ _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://lists.beepcore.org/mailman/listinfo/beepwg _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://lists.beepcore.org/mailman/listinfo/beepwg From beepwg-admin@lists.beepcore.org Thu Jul 31 09:38:36 2003 Received: from qawoor.dbc.mtview.ca.us (adsl-64-168-10-251.dsl.scrm01.pacbell.net [64.168.10.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25114 for ; Thu, 31 Jul 2003 09:38:35 -0400 (EDT) Received: from qawoor.dbc.mtview.ca.us (localhost [127.0.0.1]) by qawoor.dbc.mtview.ca.us (8.11.5/8.11.5) with ESMTP id h6VDcCA09158; Thu, 31 Jul 2003 06:38:13 -0700 (PDT) Received: from mail5.atl.registeredsite.com (nobody@mail5.atl.registeredsite.com [64.224.219.79]) by qawoor.dbc.mtview.ca.us (8.11.5/8.11.5) with ESMTP id h6VDbhA09146 for ; Thu, 31 Jul 2003 06:37:43 -0700 (PDT) Received: from mail.clipcode.com (mail.clipcode.com [64.225.30.241]) by mail5.atl.registeredsite.com (8.12.9/8.12.9) with ESMTP id h6VCd200029111 for ; Thu, 31 Jul 2003 08:39:03 -0400 Received: from ARAN [64.225.30.241] by mail.clipcode.com with ESMTP (SMTPD32-6.06) id AB8E467800F8; Thu, 31 Jul 2003 09:37:18 -0400 From: "Eamon O'Tuathail" To: Subject: [BEEPwg] BEEP and .Net Message-ID: <000a01c35768$dc77f450$fa3a869f@ARAN> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000B_01C35771.3E3C5C50" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Sender: beepwg-admin@lists.beepcore.org Errors-To: beepwg-admin@lists.beepcore.org X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.0.6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: Date: Thu, 31 Jul 2003 14:37:11 +0100 This is a multi-part message in MIME format. ------=_NextPart_000_000B_01C35771.3E3C5C50 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Clipcode will have a version of BEEP for .NET on Windows and for MONO on LINUX available in October. Eamon O'Tuathail ------=_NextPart_000_000B_01C35771.3E3C5C50 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

Clipcode will have a version of BEEP for .NET = on Windows and for MONO on LINUX available in October.

 

Eamon O’Tuathail

------=_NextPart_000_000B_01C35771.3E3C5C50-- _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://lists.beepcore.org/mailman/listinfo/beepwg