Re: About TCP

[kfall@ee.lbl.gov]

>
> From:  Shaogang Chen <shaogang@ecn.purdue.edu>
> To:    neelsh@ruf.rice.edu (Ramesh Neelamani)
> cc:    ns-users@mash.CS.Berkeley.EDU
> Subject: About TCP
> Date:  Fri, 21 Nov 1997 11:59:46 PST
>
> For those of you who are familiar with ns:
> 
> >From my understanding to current version ns, the connection between two
> agents is set up staticly. The data is not actually transmitted from
> a sender to a receiver. The data length is just used to compute transmission
> time. 

There are two major variants of TCP in the simulator.  The "regular one",
and "full tcp", where full tcp has (nearly) the full state machine
a regular TCP has.  Full TCP can handle connection establishment and teardown;
it doesn't actually transfer data, although that would be a tiny change.
The "API" to TCP is not quite there yet (there is something rudimentary),
but it's on the list.  Bug fixes and changes to full-tcp's connection
establishment/teardown are still in progress [it works ok when SYNs aren't
lost, but in certain such cases it doesn't behave exactly as a real TCP
would].

> Right now, I might want to implement TCP state machine in ns, so connections
> can be set up on request. Also data is transmitted from a sender to a receive
r.
> My question is how hard it is to do this? Do you have any intention to
> implement ns as this way in the future?

I think you might want to have a look at full-tcp and see if it comes
close to what you are looking for; if not, perhaps you could provide a bit
more detail and we can work from there...

- K