hi,Michael.Tuexen AT micmac.franken.de
It looks like what you are referring to below is a socket.
A socket is a five touple:
{Protocol, src-addr, src-port, dst-addr, dst-port}
When the server listens on a standard port, it gets the connection
request, it hands over the fd to a child process which completes
the socket (The abov five touple).
The server continutes ahead with listening on the initial port for
further socket connections.
(Refer to any TCP/IP book for this concept. Then it will be clear to you)
Hope that helps.
regards,
-Sas
--
To:
discussion AT sctp.de
From: "Natalino Biundo"
<natalino.biundo AT marconi.com>
Date: Thu, 11 Apr 2002 10:01:38 +0200
Subject: [SCTP-Discussion] Question about Ports negotiation with SCTP
Reply-To:
discussion AT sctp.de
Hi all,
First of all, I apologise for my question that may appear obvious to the
SCTP experts.
We are evaluating migration from TCP to SCTP in our embedded system based
on a Client/Server architecture.
Reading the RFC 2960 and several tutorials seems that, in order to
establish an association between two endpoints, the SCTP port number of
the Server must be known by the Client when initiates the association and
never changes.
On the contrary, TCP protocol requires a Server pre-defined port number
only during the association phase and allows to negotiate the Server
"working" port number to be used during the "stable connection" phase.
The question is : Is something similar to the TCP behaviour possible with
SCTP ?
Many thanks in advance
Natalino Biundo
Marconi Mobile S.p.A
--
Srinivasa S.A.
Wipro Technologies, 4th floor, Creator, ITPL, Bangalore
+91-80-8412224/5 ext:1266,
mailto:srinivasa.shikaripura AT wipro.com
------------------------------------------------------------------
Archive powered by MHonArc 2.6.19+.