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
Diameter server
Click on the red underlined text to get to the source
... - Transporting of user authentication information, for the purposes
of enabling the Diameter server to authenticate the user.
- Transporting of service ...
... proxies, redirects and relay agents. A
Diameter server performs authentication and/or authorization of the
...
... DIAMMIP] application defines a Diameter application
that allows a Diameter server to perform AAA functions for Mobile
IPv4 services ...
... NASREQ] application defines a Diameter Application that
allows a Diameter server to be used in a PPP/SLIP Dial-Up ...
... authorization and accounting requests for a particular realm. By
its very nature, a Diameter Server MUST support Diameter
applications in addition to the base protocol.
...
... NASREQ and/or Mobile IPv4. A Diameter Server that does not support
both NASREQ and Mobile IPv4 ...
... Diameter X
Server" where X is the application which it supports, and not a
"Diameter Server".
Diameter ...
...
set to indicate an error occurred. The specific behavior of the
Diameter server or client receiving a request depends on the Diameter
application ...
... Diameter messages that fall within this category
MUST have the identity of the home Diameter server(s) appended,
and returned to the sender of the message. See Section 6.1.7
...
... lookup as NAS, and relays the message to HMS, which is
example.com's Home Diameter Server. HMS identifies that the request
can be locally supported (via the realm), processes the
authentication ...
... Diameter peer
may be authentic, but that does not mean that it is authorized to act
as a Diameter Server advertising a set of Diameter applications.
...
... identity of the peer the request was received from.
The home Diameter server, prior to authorizing a session, MUST check
the Route-Record ...
... administrators within the home
realm may not wish to honor requests that have been routed through an
untrusted realm. By authorizing a request, the home Diameter server
is implicitly indicating its willingness to engage in the business
transaction as specified by the contractual relationship between the
...
... included in the DNS, but this does not imply that it is authorized
to act as a Diameter Server.
Authorization ...
... Authorization can be achieved for example, by configuration of a
Diameter Server CA. Alternatively this can be achieved by
definition of OIDs ...
... Proxy-Info AVP in the message is targeted to the local
Diameter server, the AVP MUST be removed before the answer is
...
... Destination-Host AVP will cause a message to be
sent to any Diameter server supporting the application within the
realm specified in Destination-Realm AVP ...
... DIAMETER_MULTI_ROUND_AUTH 1001
This informational error is returned by a Diameter server to
inform the access device that the authentication mechanism being
...
... DIAMETER_CONTRADICTING_AVPS 5007
The Home Diameter server has detected AVPs in the request that
contradicted each other, and is not willing to provide service ...
... session.
When a Diameter server authorizes a user to use network resources for
a finite amount of time, and it is willing to extend the
...
... accounting session in the Diameter server to change to Idle state in
case of short transient network ...
...
For example, for pre-paid services, the Diameter server that
originally authorized a session may need some confirmation that the
...
...
It is necessary for a Diameter server that authorized a session, for
which it is maintaining state ...
... Session-
Termination-Request (STR) message to the Diameter server that
authorized the service, to notify it that the session ...
... session not to
be started MUST issue an STR to the Diameter server that authorized
the session, since the access device has no way of knowing that the
...
... session had been authorized.
A Diameter server that receives an STR message MUST clean up
resources (e.g., session ...
... Session-Termination-Answer.
A Diameter server also MUST clean up resources when the Session-
Timeout expires, or when the Authorization-Lifetime ...
... set to 275 and the Command Flags' 'R' bit set, is sent by the access
device to inform the Diameter Server that an authenticated and/or
authorized session ...
... set to 275 and the message flags' 'R' bit clear, is sent by the
Diameter Server to acknowledge the notification that the session has
...
...
Upon sending or receipt of the STA, the Diameter Server MUST release
all resources for the session indicated by the Session-Id ...
...
A Diameter server may request that the access device stop providing
service for a particular session ...
... ASR).
For example, the Diameter server that originally authorized the
session may be required to cause that session ...
... is opportunistic rather than reliable, but useful nonetheless.
When a Diameter server receives an Origin-State-Id that is greater
than the Origin-State-Id ...
... active under the lower Origin-State-
Id have been terminated. The Diameter server MAY clean up all
session state ...
... authentication AVPs that
are needed by the Diameter server to authenticate the user.
AUTHORIZE_ONLY 2
...
... AVP Code 276) is of type Unsigned32 and
contains the number of seconds the Diameter server will wait
following the expiration of the Authorization-Lifetime AVP ...
... found in any previous authorization answer message. Diameter server
implementations SHOULD NOT return Class AVPs ...
... records are created and until a positive acknowledgement of their
reception from the Diameter Server has been received. Upon a reboot,
the client MUST starting ...
... client without committing them to the non-volatile memory or
transferring them to the Diameter server.
The client ...
...
Only the target Diameter Server, known as the home Diameter Server,
SHOULD respond with the Accounting-Answer ...
... Only the target Diameter Server, known as the home Diameter Server,
SHOULD respond with the Accounting-Answer command.
...
... AVP. This AVP MAY be returned by the
Diameter server in an authorization answer, and MUST be used in all
accounting ...
... agents can mark the message as possible duplicate by setting the T
flag. Since the Diameter server is responsible for duplicate
detection, it can choose to make use of the T flag or not, in order
to optimize duplicate detection. Since the T flag does not affect
...
... by the
server to detect duplicate requests.
A Diameter server MAY check the T flag of the received message to
determine if the record is a possible duplicate. If the T flag is
set in the request message ...
... increases as the failover interval is decreased. In order to be
able to detect out of order duplicates, the Diameter server should
use backward and forward time windows when performing duplicate
checking for the T flag marked request. For example, in order to
...
... network and be
recorded by the accounting server, the Diameter server can delay
processing records with the T flag set until a time period
TIME_WAIT + RECORD_PROCESSING_TIME has elapsed after the closing
...