Timeline for Difference between CBR and FTP
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 28, 2019 at 15:24 | comment | added | Marc 'netztier' Luethi | The script - to me - seems entirely academic and lacks real-world counterparts. I uphold it, much as Ron Maupin does in his answer: One cannot compare CBR and FTP: FTP is a data/file transfer protocol, CBR is a behaviour/strategy on how to send data (intervals, packet rate). TCP has it's own strategies on how and when to send data, and these can be compared against CBR. There is no application on an end system that allows to cbr that file from there to there. There might apps like iperf, netperf, netcat or similar that show CBR-like behaviour (with UDP) or might be configured to do so. | |
| Jan 28, 2019 at 15:11 | comment | added | bekan kitaw | My friend, @Marc'netztier'Luethi ,I thought you miss the way I wanna to describe here. You see when you design or modify certain protocol in networking, there are a number of ways by which you can simulate the working of ur network/protocol using different event simulators: Packet tracer, Contiki Cooja, OMNET++,NS2 etc.. and those parameters: UDP,TCP,CBR and FTP are common there and that is why I took for you as an instance. Spare a minute and understood the diagram shown on the previous site! Then after, I hope you'll get my idea. | |
| Jan 28, 2019 at 9:09 | comment | added | Marc 'netztier' Luethi | So when comparing CBR to anythiung else, that should be against the different flow control/congestion avoidance mechanisms (Reno, Vegas, CTCP...) that the various TCP implementations have to offer. Picking "FTP" is a case of mis-labelled apple vs. not-quite-oranges. Other than that, at the traffic generator, one should pick identitcal starting conditions, for example Lets send this amount "A" of data as a 1Mpbs stream, as a sequence of chunks of 1kbyte". Let's compare the results of TCP Reno, Vegas, CTCP (etc.) and UDP-with-CBR. "FTP" is just the odd one out in this context. | |
| Jan 28, 2019 at 8:59 | comment | added | Marc 'netztier' Luethi | Well, even that document does not say what a CBR actually looks like on the host. One can infer that it is just simply an application generating a UDP stream at a given packet rate with a given packet size, subject to the serialization delay as given by the lower layer. As other commenters pointed out, CBR ("constant bit rate") is a term describing the behavior of a (UDP) traffic generator, not more. What also seems to be missing in this whole discussion (and the paper/script) is TCP's own flow control and congestion avoidance mechanisms. | |
| Jan 28, 2019 at 8:49 | comment | added | bekan kitaw | go through NS2 tutorial. For sample nile.wpi.edu/NS/simple_ns.html | |
| Jan 21, 2019 at 16:48 | comment | added | Marc 'netztier' Luethi | Can you quote a source on that, specifically for CBR? | |
| Jan 21, 2019 at 7:40 | review | Late answers | |||
| Jan 21, 2019 at 15:04 | |||||
| Jan 21, 2019 at 7:25 | review | First posts | |||
| Jan 21, 2019 at 8:36 | |||||
| Jan 21, 2019 at 7:23 | history | answered | bekan kitaw | CC BY-SA 4.0 |