Re: SCTP association startup(destination IP address ??)
sajuars@xxxxxxxxx wrote:
I was going through the RFC2960 for SIGTRAN.During an association
startup , how does it identify a destination .There's a destination
port number in the SCTP common header .But where is the destination IP
address ?
In the IP-Header "under" the SCTP-Packet, or in the Init-Message:
Section 3.3.2.1 "Optional/Variable Length Parameters in INIT" in RFC
2960:
+++++++++++
If the INIT contains at least one IP Address parameter, then the
source address of the IP datagram containing the INIT chunk and
any additional address(es) provided within the INIT can be used as
destinations by the endpoint receiving the INIT. If the INIT does
not contain any IP Address parameters, the endpoint receiving the
INIT MUST use the source address associated with the received IP
datagram as its sole destination address for the association.
+++++++++++
.
Relevant Pages
- Re: SCTP association startup(destination IP address ??)
... how does it identify a destination .There's a destination ... port number in the SCTP common header .But where is the destination IP ... Section 3.3.2.1 "Optional/Variable Length Parameters in INIT" in RFC ... destinations by the endpoint receiving the INIT. ...
(comp.dcom.sys.cisco) - Re: SCTP association startup(destination IP address ??)
... how does it identify a destination .There's a destination ... Section 3.3.2.1 "Optional/Variable Length Parameters in INIT" in RFC ... source address of the IP datagram containing the INIT chunk and ... destinations by the endpoint receiving the INIT. ...
(comp.dcom.sys.cisco) - Re: strange behavior when the client bind its UDP socket to a local address
... From my observations of the behaviour of the Linux IPv4 stack, I did not see any evidence that the default source adresse selection is based on "closeness" to the destination address. ... Because the client sent a datagram to 127.0.0.1 and expects datagrams from the same address, ... Although UDP is connectionless, it is rather common that bidirectional UDP communications use source and destination adresses in the same way as TCP does. ... As a client, when nc sends a UDP datagram to address A it expects to receive datagrams from the same address A. However as a server, when nc receives a UDP datagram on address A it may send datagrams from a different address. ...
(comp.os.linux.networking) - Re: Determining UDP datagram destination IP
... > to some IP address or broadcast. ... > to get to know received datagram comes ... the destination IP address; however, the typical way to do it is to bind one ... UDP socket to each local/broadcast address. ...
(comp.unix.programmer) - Re: strange behavior when the client bind its UDP socket to a local address
... received datagram just because the source address isn't what 'nc' ... Here is what netstat prints when the nc client is ... address that matches the received destination address. ... The nc server socket has the local addresse 127.7.8.9 instead of ...
(comp.os.linux.networking) |
|
