1 - 2 - 3 - 6 - 7 - 8 - A - B - C - D - E - F - G - H - I - K - L - M - N - O - P - Q - R - S - T - U - V - W
transport connection
Click on the red underlined text to get to the source
... hop-by-hop security, or security across a
transport connection. When relays or proxy are involved, this
hop-by-hop security ...
... Diameter instance of the peer state machine MUST NOT use more than
one transport connection to communicate with a given peer, unless
multiple instances exist on the peer in which case a separate
connection ...
... connection per process is allowed.
When no transport connection exists with a peer, an attempt to
connect SHOULD be periodically made. This behavior is handled via
the Tc timer ...
... timer, whose recommended value is 30 seconds. There are
certain exceptions to this rule, such as when a peer has terminated
the transport connection stating that it does not wish to
communicate.
...
... Diameter error made by the peer, the stream is
compromised and cannot be recovered. The transport connection MUST
be closed using a RESET call (send a TCP RST ...
... information. Upon receipt of the redirect notification, DRL
establishes a transport connection with HMS, if one doesn't already
exist, and forwards the request to it.
...
... removed from the suspect peer list:
1. The peer is no longer reachable, causing the transport connection
to be shutdown. The peer is moved to the closed state.
...
...
When two Diameter peers establish a transport connection, they MUST
exchange the Capabilities Exchange messages, as specified in the peer
state machine ...
... AVP set to DIAMETER_UNKNOWN_PEER.
In both cases, the transport connection is closed. If the local
policy permits receiving CERs from unknown hosts ...
... lifetime of the peer entry is equal to the
lifetime of the transport connection. In case of a transport
failure, all the pending transactions ...
...
When a Diameter node disconnects one of its transport connections,
its peer cannot know the reason for the disconnect, and will most
likely assume that a connectivity problem occurred, or that the peer
...
... to 282 and the Command Flags' 'R' bit set, is sent to a peer to
inform its intentions to shutdown the transport connection. Upon
detection of a transport failure, this message MUST NOT be sent to an
...
... to the Disconnect-Peer-Request message. Upon receipt of this
message, the transport connection is shutdown.
Message Format ...
... AVP in the Disconnect-Peer-Request
message to inform the peer of the reason for its intention to
shutdown the transport connection. The following values are
supported:
...
... BUSY 1
The peer's internal resources are constrained, and it has
determined that the transport connection needs to be closed.
DO ...
... DO_NOT_WANT_TO_TALK_TO_YOU 2
The peer has determined that it does not see a need for the
transport connection to exist, since it does not expect any
messages to be exchanged in the near future.
...
... connection request should be
periodically attempted with the failed peer in order to re-establish
the transport connection. Once a connection has been successfully
established, messages can once again be forwarded to the peer. This
...
... AAATRANS], which is used to open, close, failover,
probe, and reopen transport connections. Note in particular that
[AAATRANS] requires the use of watchdog messages to probe ...
... R-Conn-CER An acknowledgement is received stating that the
transport connection has been established, and the
associated CER has arrived.
...
...
Rcv-Conn-Ack A positive acknowledgement is received confirming that
the transport connection is established.
Rcv-Conn-Nack A negative acknowledgement ...
... Rcv-Conn-Nack A negative acknowledgement was received stating that
the transport connection was not established.
Timeout An application-defined timer ...
... connections.
Snd-Conn-Req A transport connection is initiated with the peer.
Accept The incoming connection ...
... pending message queue (see Section 5.3) that is to be redirected. If
no transport connection exists with the new agent, one is created,
...
... ELECTION_LOST 4003
The peer has determined that it has lost the election process and
has therefore disconnected the transport connection.
...
... timer
The Tc timer controls the frequency that transport connection
attempts are done to a peer with whom no active transport
connection ...
... transport connection
attempts are done to a peer with whom no active transport
connection exists. The recommended value is 30 seconds.
...
... processing records with the T flag set until a time period
TIME_WAIT + RECORD_PROCESSING_TIME has elapsed after the closing
of the original transport connection. After this time period has
expired, then it may check the T flag marked records against the
database ...