Re: RFC3080 MSG/RPY Window

Rainer,

The default window size for a channel on TCP is 4096. I believe this is
specified in RFC 3081.

One side note on your example, the RPY messages have to be sent in the same
order as the MSG messages. ANS messages are the only type that can be sent
interleaved/out of order.

--Huston

----- Original Message ----- 
From: "Rainer Gerhards" <[email protected]>
To: <[email protected]>
Sent: Monday, September 15, 2003 9:18 AM
Subject: [BEEPwg] RFC3080 MSG/RPY Window


> Hello WG,
>
> sorry for the duplicate - hit enter accidently...
>
> I am implementing BEEP-based RFC 3195 (reliable syslog via BEEP). RFC
> 3195 uses MSG/RPY for message transfer. As I have seen and verified,
> MSG/RPY is full-duplex that is there can be more than one MSG send
> without an RPY.
>
> This is a sample:
>
> I: MSG 1
> I: MSG 2
> I: MSG 3
> L: RPY 2
> L: RPY 1
> L: RPY 3
>
> The sample is the exact sequence of what and when was send be initiator
> (I:) and listener (L:). I see the value of having this ability,
> especially in high-latency environments.
>
> However, I did not see any window size mentioned for this. So it falls
> back to a window of 2^32, which I think is a bit large.
>
> Although this probably is not a big issue, I suggest that a window is
> defined in the case RFC 3080 is revised some time.
>
> If I am wrong with my comment, I would obviously like to get some
> correction ;)
>
> Many thanks,
> Rainer
>
>
>
> _______________________________________________
> BEEPwg mailing list
> [email protected]
> http://lists.beepcore.org/mailman/listinfo/beepwg
>