Question: TCP is a very symmetric protocol, but the client/server model is not. Consider an asymmetric TCP-like protocol in which only the server side is assigned
TCP is a very symmetric protocol, but the client/server model is not. Consider an asymmetric TCP-like protocol in which only the server side is assigned a port number visible to the application layers.
Client-side sockets would simply be abstractions that can be connected to server ports.
(a) Propose header data and connection semantics to support this.
What will you use to replace the client port number?
(b) What form does TIME_WAIT now take? How would this be seen through the programming interface? Assume that a client socket could now be reconnected arbitrarily many times to a given server port, resources permitting.
(c) Look up the rsh/rlogin protocol. How would the above break this?
Step by Step Solution
3.39 Rating (143 Votes )
There are 3 Steps involved in it
a In a highly asymmetric TCPlike protocol where only the server side is assigned a port number visible to application layers we could replace the clie... View full answer
Get step-by-step solutions from verified subject matter experts
