Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!elbereth.rutgers.edu!ron.rutgers.edu!ron
From: ron@ron.rutgers.edu (Ron Natalie)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: TCP socket ambiguity?
Message-ID: <May.31.20.06.51.1989.500@ron.rutgers.edu>
Date: 1 Jun 89 00:06:55 GMT
References: <30200001@m.cs.uiuc.edu>
Organization: Rutgers Univ., New Brunswick, N.J.
Lines: 16

>   To read RFC 793 very literally, it would seem that port <100.100.100.100,42>
> ought to specify a different socket/enpoint than <101.101.101.101,42>. But
> they obviously both refer to "TCP port 42" on the gateway machine....

They are differnt.  TCP connections are identified by the host address and
port on both ends of the connection.  Saying TCP port 42 is meaningless, it
is only valid in the context of the local IP address and the remote address/port
pair.

For example

100.100.100.100,42	101.101.101.101,42
100.100.100.100,42	200.200.200.200,42
200.200.200.200,42	101.101.101.101,42

refer to three seperate TCP connections without ambiguity.