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
node
Click on the red underlined text to get to the source
... Diameter applications.
Any node can initiate a request. In that sense, Diameter is a peer-
to-peer protocol. In this document, a Diameter ...
... Diameter
agent is a node that does not authenticate and/or authorize messages
locally; agents ...
... authentication and/or authorization of the
user. A Diameter node MAY act as an agent for certain requests while
acting as a server for others.
...
... A Diameter Agent is a Diameter node that provides either relay,
proxy, redirect or translation services ...
... Diameter Node
A Diameter node is a host process that implements the Diameter
protocol, and acts either as a Client ...
... Diameter Peer
A Diameter Peer is a Diameter Node to which a given Diameter Node
has a direct transport connection ...
... A Diameter Peer is a Diameter Node to which a given Diameter Node
has a direct transport connection.
...
... Diameter Security Exchange is a process through which two
Diameter nodes establish end-to-end security.
...
... session. End-to-end security is security between two Diameter
nodes, possibly communicating through Diameter Agents. This
...
... security protects the entire Diameter communications path from the
originating Diameter node to the terminating Diameter node.
...
... Diameter communications path from the
originating Diameter node to the terminating Diameter node.
Home Realm ...
... Agent
A translation agent is a stateful Diameter node that performs
protocol translation between Diameter ...
... abandoned. The base protocol also defines certain rules that apply
to all exchanges of messages between Diameter nodes.
Communication between Diameter ...
...
1. For interoperability: All Diameter nodes MUST be prepared to
receive Diameter messages on any SCTP stream ...
... association.
2. To prevent blocking: All Diameter nodes SHOULD utilize all SCTP
streams available to the association ...
... Application Identifier since its support is mandatory. During the
capabilities exchange, Diameter nodes inform their peers of locally
supported applications. Furthermore, all Diameter messages contain
...
... Relay and redirect agents MUST advertise the Relay Application
Identifier, while all other Diameter nodes MUST advertise locally
supported applications. The receiver of a Capabilities Exchange
...
... agents that accept requests and route
messages to other Diameter nodes based on information found in the
messages (e.g., Destination-Realm). This routing ...
... Diameter sessions
MUST be routed only through authorized nodes that have advertised
support for the Diameter application required by the session ...
... SNTP [SNTP] describes a procedure to extend the time to 2104.
This procedure MUST be supported by all DIAMETER nodes.
UTF8String
...
... FQDN
DiameterIdentity value is used to uniquely identify a Diameter
node for purposes of duplicate connection and routing loop
...
...
The contents of the string MUST be the FQDN of the Diameter node.
If multiple Diameter nodes run on the same host ...
... FQDN of the Diameter node.
If multiple Diameter nodes run on the same host, each Diameter
node MUST be assigned a unique DiameterIdentity. If a Diameter
node ...
... If multiple Diameter nodes run on the same host, each Diameter
node MUST be assigned a unique DiameterIdentity. If a Diameter
node can be identified by several FQDNs, a single FQDN ...
... Diameter nodes run on the same host, each Diameter
node MUST be assigned a unique DiameterIdentity. If a Diameter
node can be identified by several FQDNs, a single FQDN should be
...
... FQDN should be
picked at startup, and used as the only DiameterIdentity for that
node, whatever the connection it is sent on.
...
...
This section describes how Diameter nodes establish connections and
communicate with peers.
...
...
Although a Diameter node may have many possible peers that it is able
to communicate with, it may not be economical to have an established
connection ...
... to communicate with, it may not be economical to have an established
connection to all of them. At a minimum, a Diameter node SHOULD have
an established connection with two peers per realm, known as the
...
... an established connection with two peers per realm, known as the
primary and secondary peers. Of course, a node MAY have additional
connections, if it is deemed necessary. Typically, all messages for
...
... IETF standards. The first option (manual configuration)
MUST be supported by all DIAMETER nodes, while the latter two options
(SRVLOC and DNS) MAY be supported.
...
... support for the Diameter application that defines the command. A
Diameter node MUST cache the supported applications in order to
ensure that unrecognized commands and/or AVPs ...
... sender's IP address. All source
addresses that a Diameter node expects to use with SCTP [SCTP] MUST
...
...
When a Diameter node disconnects one of its transport connections,
its peer cannot know the reason for the disconnect, and will most
...
... reconnect, as stated in Section 2.1. In the event that the
disconnect was a result of either a shortage of internal resources,
or simply that the node in question has no intentions of forwarding
any Diameter messages to the peer in the foreseeable future, a
...
... connection request would not be welcomed. The
Disconnection-Reason AVP contains the reason the Diameter node issued
the Disconnect-Peer-Request message.
...
...
The Disconnect-Peer-Request message is used by a Diameter node to
inform its peer of its intent to disconnect the transport layer, and
...
... AVP (AVP Code 273) is of type Enumerated. A
Diameter node MUST include this AVP in the Disconnect-Peer-Request
message to inform the peer of the reason for its intention to
...
... failover.
In order for a Diameter node to perform failover procedures, it is
necessary for the node to maintain a pending message queue ...
... In order for a Diameter node to perform failover procedures, it is
necessary for the node to maintain a pending message queue for a
given peer. When an answer message ...
... finite state machine that MUST be observed by
all Diameter implementations. Each Diameter node MUST follow the
state machine described below when communicating with each peer.
...
... Rcv-DPA A DPA message from the peer was received.
Win-Election An election was held, and the local node was the
winner.
...
... routing of Diameter messages to work within an administrative
domain, all Diameter nodes within the realm MUST be peers.
Note the processing rules ...
... Diameter peer table contains all of the peers that the local node is
able to directly communicate with.
...
... security implications and SHOULD contain an embedded HMAC with a
node-local key. Alternatively, it MAY simply use local storage to
store state information.
...
... Upon receiving the above, the receiving Diameter node SHOULD forward
the request directly to one of the hosts identified in these AVPs ...
... Integer). For
each end-to-end peer with which a node communicates (or remembers
communicating) a different nonce value MUST be used and the counter ...
... additional AVPs to be present in the answer. In these cases, the
Diameter node that sets the Result-Code AVP to indicate the error
...
... The Result-Code AVP describes the error that the Diameter node
encountered in its processing. In case there are multiple errors,
the Diameter node ...
... Diameter node
encountered in its processing. In case there are multiple errors,
the Diameter node MUST report only the first error it encountered
(detected possibly in some implementation dependent order). The
...
... Command-Code that the receiver did not
recognize or support. This MUST be used when a Diameter node
receives an experimental command that it does not understand.
...
... DIAMETER_TOO_BUSY 3004
When returned, a Diameter node SHOULD attempt to send the message
to an alternate peer. This error MUST only be used when a
specific server is requested, and it cannot provide the requested
...
... DIAMETER_OUT_OF_SPACE 4002
A Diameter node received the accounting request but was unable to
commit it to stable storage due to a temporary lack of space.
...
... The Acct-Interim-Interval AVP, when present, instructs the Diameter
node acting as a client to produce accounting records continuously
...
... field set to 271 and the Command Flags' 'R' bit set, is sent by a
Diameter node, acting as a client, in order to exchange accounting
...
... AVP
is the nominal interval between these records in seconds. The
Diameter node that originates the accounting information, known as
the client ...
... TLS session establishment. In order to ensure mutual authentication,
the Diameter node acting as TLS server must request a certificate
...
... TLS server must request a certificate
from the Diameter node acting as TLS client, and the Diameter node ...
... Diameter implementation.
One implication of the recommended policy is that if a node is using
both TLS and IPsec ...