home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!agate!stanford.edu!rutgers!ub!csn!cherokee!kdlin
- From: kdlin@advtech.uswest.com (David Lin)
- Newsgroups: comp.protocols.tcp-ip
- Subject: Flow Control
- Message-ID: <1992Nov14.012946.13136@advtech.uswest.com>
- Date: 14 Nov 92 01:29:46 GMT
- Sender: news@advtech.uswest.com (Radio Free Boulder)
- Organization: U S WEST Advanced Technologies
- Lines: 35
- Nntp-Posting-Host: colt45.advtech.uswest.com
-
- I understand that many end-to-end sliding window flow control schemes
- ( eq. in TCP/IP and in XTP ) use byte as the unit for calculation. For
- example, if the window size is 6K bytes and you have transmitted 2K bytes
- without receiving ACKs from the receiver, then you are allowed to transmit
- 4K more bytes.
-
- Now, if I change the unit for flow control calculation to packet ( or
- frame ), what is the impact to the whole system? What's the implication?
-
- Since most networks have an upper limit for the frame size ( <= MTU ),
- I cannot transmit unlimited-size packets. Consequently, I will be treating
- any packets of size in between 1 and MTU equally, as far as flow control
- is concerned.
-
- I understand that interactive traffic will be affected first. However,
- packet video and packet voice may not be affected at all, especially
- when they have real time delivery requirement.
-
- So why am I doing this? I think it will simplify the computation
- needed for the flow control mechanism. Three more questions follow:
-
- 1. Are there any circumstances that this scheme ( using packet as
- the computation unit ) is desirable?
-
- 2. When it is NOT desirable?
-
- 3. Do I really achieve anything by doing that?
-
- Many thanks.
-
- David
- --
- K. David Lin, Ph.D. | E-mail: kdlin@advtech.uswest.com
- Communication Services Research | Defend your life with style! -- Beretta
- U S WEST Advanced Technologies | Disclaimer: Only personal opinions
-