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
routing
Click on the red underlined text to get to the source
... support for inter-domain roaming and message routing (Sections 2.7
and 6), auditability [AAACMS], and transmission-layer ...
... used to encapsulate protocol-specific data (e.g., routing
information) as well as authentication, authorization or
...
... Relay Agent or Relay
Relays forward requests and responses based on routing-related
AVPs and realm routing table ...
... routing-related
AVPs and realm routing table entries. Since relays do not make
policy decisions, they do not examine or alter non-routing AVPs ...
... AVPs and realm routing table entries. Since relays do not make
policy decisions, they do not examine or alter non-routing AVPs.
As a result, relays never originate messages, do not need to
...
... As a result, relays never originate messages, do not need to
understand the semantics of messages or non-routing AVPs, and are
capable of handling any Diameter application ...
... Diameter application or message type.
Since relays make decisions based on information in routing AVPs
and realm forwarding tables they do not keep state ...
... Diameter Peer Table is used in message forwarding, and referenced
by the Realm Routing Table. A Peer Table entry contains the
following fields:
...
... Realm-Based Routing Table ...
...
All Realm-Based routing lookups are performed against what is
commonly known as the Realm Routing Table ...
... routing lookups are performed against what is
commonly known as the Realm Routing Table (see Section 12). A Realm
Routing Table Entry contains the following fields:
...
... commonly known as the Realm Routing Table (see Section 12). A Realm
Routing Table Entry contains the following fields:
Realm Name
...
... Realm Name
This is the field that is typically used as a primary key in the
routing table lookups. Note that some implementations perform
their lookups ...
... the application identification AVP of the message. This field
MUST be used as a secondary key field in routing table lookups.
...
... MUST be routed to a next hop server, without modifying any
non-routing AVPs. See Section 6.1.8 for relaying guidelines
...
... apply its local policies to the message by including new AVPs
to the message prior to routing. See Section 6.1.8 for
proxying guidelines.
...
... AVPs.
The routing table MAY include a default entry that MUST be used for
any requests not matching any of the other entries. The routing
table MAY consist of only such an entry.
...
... The routing table MAY include a default entry that MUST be used for
any requests not matching any of the other entries. The routing
table MAY consist of only such an entry.
When a request is routed, the target ...
... Diameter nodes based on information found in the
messages (e.g., Destination-Realm). This routing decision is
performed using a list of supported realms, and known peers. This is
known as the Realm Routing Table ...
... routing decision is
performed using a list of supported realms, and known peers. This is
known as the Realm Routing Table, as is defined further in Section
2.7.
...
... Relays modify Diameter messages by inserting and removing routing
information, but do not modify any other portion of a message.
Relays SHOULD NOT maintain session state ...
... Diameter messages using the
Diameter Routing Table. However, they differ since they modify
messages to implement policy enforcement. This requires that proxies
...
... Redirect agents are useful in scenarios where the Diameter routing
configuration needs to be centralized. An example is a redirect
agent ...
... not wish to be burdened with relaying all messages between realms.
This scenario is advantageous since it does not require that the
consortium provide routing updates to its members when changes are
made to a member's infrastructure.
...
... NAS, for the user bob@example.com. The message is
forwarded by the NAS to its relay, DRL, which does not have a routing
entry in its Diameter Routing Table ...
... routing
entry in its Diameter Routing Table for example.com. DRL has a
default route configured to DRD, which is a redirect agent ...
... same answer to be transmitted (modulo the hop-by-hop Identifier
field and any routing AVPs that may be present), and MUST NOT
affect any state ...
... accounting,
authorization, routing and security information as well as
configuration details for the request and reply.
...
... DiameterIdentity value is used to uniquely identify a Diameter
node for purposes of duplicate connection and routing loop
detection.
...
... DNS TTL. If a peer is discovered
outside of the local realm, a routing table entry (see Section 2.7)
for the peer's realm is created. The routing table ...
... routing table entry (see Section 2.7)
for the peer's realm is created. The routing table entry's
expiration MUST match the peer's expiration value.
...
... DIAMETER_UNABLE_TO_DELIVER to inform the downstream to take action
(e.g., re-routing request to an alternate peer).
With the exception of the Capabilities-Exchange-Request ...
...
3. The procedures listed in Section 6.1.6 are followed, which is
known as Request Routing.
4. If none of the above is successful, an answer is returned with the
...
... bit set.
For routing of Diameter messages to work within an administrative
domain, all Diameter nodes ...
...
When sending a request, originated either locally, or as the result
of a forwarding or routing operation, the following procedures MUST
be followed:
...
... Request Routing ...
... Diameter request message routing is done via realms and applications.
A Diameter message that may be forwarded by Diameter ...
... applications. When a request is received that includes a realm
and/or application that is not locally supported, the message is
routed to the peer configured in the Realm Routing Table (see Section
2.7).
...
...
When a redirect agent receives a request whose routing entry is set
to REDIRECT, it MUST reply with an answer message with the 'E' bit ...
... AVP to DIAMETER_REDIRECT_INDICATION. Each of
the servers associated with the routing entry are added in separate
Redirect-Host AVP ...
... The message is then forwarded to the next hop, as identified in the
Realm Routing Table.
Figure 6 provides an example of message routing ...
... Routing Table.
Figure 6 provides an example of message routing using the procedures
listed in these sections.
...
... AVPs defined in this section are Diameter AVPs used for routing
purposes. These AVPs change as Diameter ...
...
When present, this AVP dictates how the routing entry resulting from
the Redirect-Host is to be used. The following values are supported:
...
... host created due to a redirect indication
is no longer reachable, any associated peer and routing table entries
MUST be deleted.
...
... application errors. A protocol error is one that occurs at the base
protocol level, and MAY require per hop attention (e.g., message
routing error). Application errors, on the other hand, generally
occur due to a problem with a function specified in a Diameter
application (e.g., user authentication ...
... table of Realm Names, and the address of the peer to which the
message must be forwarded to. The routing table MAY also include
a "default route", which is typically used for all messages that
...