Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!deimos.cis.ksu.edu!uxc!uxc.cso.uiuc.edu!m.cs.uiuc.edu!zweig
From: zweig@m.cs.uiuc.edu
Newsgroups: comp.protocols.tcp-ip
Subject: TCP socket ambiguity?
Message-ID: <30200001@m.cs.uiuc.edu>
Date: 31 May 89 06:16:00 GMT
Lines: 14
Nf-ID: #N:m.cs.uiuc.edu:30200001:000:783
Nf-From: m.cs.uiuc.edu!zweig    May 31 01:16:00 1989


  Since a gateway may have two IP address -- say 100.100.100.100 for one
network and 101.101.101.101 for the other network it's connected to -- I
don't see what the "right way" to describe an endpoint of a TCP connection is.
  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....
  If the answer is "different", would any implementations that assumes they're
the same because there is only one machine involved please raise their hands?
  If the answer is "same", would any implementations that assumed than
different <IP-address, port-#> pairs need to specify different endpoint please
say so?

-Johnny Confused