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
Click on the red underlined text to get to the source
... packet loss may translate directly into revenue loss. In order to
provide well defined transport behavior, Diameter runs over
reliable transport mechanisms ...
... transport behavior, Diameter runs over
reliable transport mechanisms (TCP, SCTP) as defined in
...
... Currently, the Diameter specification consists of a base
specification (this document), Transport Profile [AAATRANS] and
...
... Transport Profile document [AAATRANS] discusses transport layer
issues that arise with AAA protocols and recommendations on how to
...
... hop-by-hop security, or security across a
transport connection. When relays or proxy are involved, this
hop-by-hop security ...
... Transport ...
... 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.
...
... communicate.
When connecting to a peer and either zero or more transports are
specified, SCTP SHOULD be tried first, followed by TCP ...
... Diameter implementations SHOULD also be able to interpret a reset
from the transport and timed-out connection attempts.
...
... 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 ...
...
A connection is a transport level connection between two peers, used
to send and receive Diameter ...
... 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.
...
... transport-protocol
; One of the transports used to listen
; for incoming connections. If absent,
...
... diameter.
transport-protocol = ( "tcp" / "sctp" / "udp" )
protocol = ";protocol=" aaa-protocol
...
... transport=tcp
aaa://host.example.com:6666;transport=tcp
aaa://host.example.com;protocol=diameter ...
... 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.
...
...
3.1 The services relevant for the task of transport protocol
selection are those with NAPTR service fields ...
... service fields with values
"AAA+D2x", where x is a letter that corresponds to a transport
protocol supported by the domain. This specification defines
D2T for TCP ...
... domain, to the
SRV record for contacting a server with the specific transport
protocol in the NAPTR services field. The resource record ...
... regular expression and a replacement
value, which is the SRV record for that particular transport
protocol. If the server supports multiple transport
protocols, there will be multiple NAPTR records, each with a
...
... value, which is the SRV record for that particular transport
protocol. If the server supports multiple transport
protocols, there will be multiple NAPTR records, each with a
different service ...
... resolution service whose value is not "D2X", for values of X
that indicate transport protocols supported by the client.
The NAPTR ...
... NAPTR processing as described in RFC 2915(-> 3404prop | 3403prop | 3402prop | 3401) will result in
discovery of the most preferred transport protocol of the
server that is supported by the client, as well as an SRV
record ...
...
When two Diameter peers establish a transport connection, they MUST
exchange the Capabilities Exchange messages, as specified in the peer
state machine ...
... DIAMETER_NO_COMMON_APPLICATION, and SHOULD disconnect the transport
layer connection. Note that receiving a CER ...
... 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 ...
... lifetime of the transport connection. In case of a transport
failure, all the pending transactions destined to the unknown peer
...
... Code set to 257 and the Command Flags' 'R' bit set, is sent to
exchange local capabilities. Upon detection of a transport failure,
this message MUST NOT be sent to an alternate peer.
...
...
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
...
... Request message is used by a Diameter node to
inform its peer of its intent to disconnect the transport layer, and
that the peer shouldn't reconnect unless it has a valid reason to do
...
... 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
...
... inform its intentions to shutdown the transport connection. Upon
detection of a transport failure, this message MUST NOT be sent to an
alternate peer.
...
... 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.
...
... Transport Failure Detection ...
... Given the nature of the Diameter protocol, it is recommended that
transport failures be detected as soon as possible. Detecting such
failures will minimize the occurrence of messages sent to unavailable
...
... Watchdog-Answer messages, defined in this section, are used to pro-
actively detect transport failures.
...
... traffic has been exchanged between two peers (see Section 5.5.3).
Upon detection of a transport failure, this message MUST NOT be sent
to an alternate peer.
...
...
In the event that a transport failure is detected with a peer, it is
necessary for all pending request messages to be forwarded to an
...
... is used to match the answer with the queued request.
When a transport failure is detected, if possible all messages in the
queue are sent to an alternate agent ...
... 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 ...
... local resources are freed.
Error The transport layer connection is disconnected, either
politely or abortively, in response to an error
condition ...
... Snd-DPA A DPA message is sent to the peer.
Disc The transport layer connection is disconnected, and
local resources are freed.
...
... 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.
...
... layer accounting requests
are processed one by one, transport protocols used under Diameter
typically batch several requests in the same packet under heavy
...
... Service Field: The service field being registered. An example for a
new fictitious transport protocol called NCTP might be "AAA+D2N".
...
... AAA+D2N".
Protocol: The specific transport protocol associated with that
service field. This MUST include the name and acronym ...
... acronym for the
protocol, along with reference to a document that describes the
transport protocol. For example - "New Connectionless Transport
Protocol (NCTP), RFC ...
... protocol, along with reference to a document that describes the
transport protocol. For example - "New Connectionless Transport
Protocol (NCTP), RFC ".
...
... 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.
...
... Jungmaier, A., Rescorla, E. and M. Tuexen, "Transport Layer Security over Stream Control Transmission Protocol", RFC 3436prop, December 2002. ...
... IETF Document Reading
Party. Allison Mankin, Jonathan Wood and Bernard Aboba provided
invaluable assistance in working out transport issues, and similarly
with Steven Bellovin in the security area.
...
... Diameter URL format is described in Section 2.9.
; Example: 'aaa://aaa.example.com:1812;transport=tcp
supported-auth-applications= string L M
# This attribute lists the Diameter applications ...
... SCTP
# This attribute lists the supported transports that the Diameter
# implementation accepts. Note that a compliant Diameter ...
... 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 ...