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 application
Click on the red underlined text to get to the source
... be used by itself for accounting purposes only, or it may be used
with a Diameter application, such as Mobile IPv4 [DIAMMIP], or
...
... The Mobile IPv4 [DIAMMIP] application defines a Diameter application
that allows a Diameter server to perform AAA ...
... The NASREQ [NASREQ] application defines a Diameter Application that
allows a Diameter server to be used in a PPP ...
... Reuse of existing AVP values, AVPs and Diameter applications are
strongly recommended. Reuse simplifies standardization and
implementation and avoids potential interoperability ...
... an existing application without requiring major changes to the
specification, it may be desirable to create a new Diameter
application. Major changes to an application include:
- Adding new AVPs ...
... In order to justify allocation of a new application identifier,
Diameter applications MUST define one Command Code, or add new
mandatory AVPs to the ABNF ...
... ABNF [ABNF] grammar (see
Section 3.2). If the Diameter application has accounting
requirements, it MUST also specify the AVPs that are to be present in
...
... accounting application id is required.
When possible, a new Diameter application SHOULD reuse existing
Diameter AVPs ...
... accounting requests for a particular realm. By
its very nature, a Diameter Server MUST support Diameter
applications in addition to the base protocol.
...
... proxies need to understand the semantics of the
messages passing through them, and may not support all Diameter
applications.
Realm
...
... routing AVPs, and are
capable of handling any Diameter application or message type.
Since relays make decisions based on information in routing ...
... authentication and authorization it is
always extended for a particular application. Two Diameter
applications are defined by companion documents: NASREQ [NASREQ],
...
... Mobile IPv4 [DIAMMIP]. These applications are introduced in this
document but specified elsewhere. Additional Diameter applications
MAY be defined in the future (see Section 11.3).
...
... base protocol, which includes
accounting. In addition, they MUST fully support each Diameter
application that is needed to implement the client's service, e.g.,
...
... base protocol, which includes
accounting. In addition, they MUST fully support each Diameter
application that is needed to implement the intended service, e.g.,
NASREQ ...
... base protocol, which includes
accounting. In addition, they MUST fully support each Diameter
application that is needed to implement proxied services, e.g.,
NASREQ ...
... Diameter peer. The set of AVPs included in the
message is determined by a particular Diameter application. One AVP
that is included to reference a user's session ...
... Diameter server or client receiving a request depends on the Diameter
application employed.
Session ...
... Session-Timeout
AVP, and according to rules established in a particular Diameter
application.
...
... Diameter Application Compliance ...
...
Each Diameter application MUST have an IANA assigned Application
Identifier (see Section 11.3). The base protocol ...
... vendor id and an application id.
For all IETF standards track Diameter applications, the vendor id
is zero. A route entry ...
... Since Relays do not perform any application level processing, they
provide relaying services for all Diameter applications, and
therefore MUST advertise the Relay Application Identifier.
...
... agents do not perform any application level
processing, they provide relaying services for all Diameter
applications, and therefore MUST advertise the Relay Application
Identifier.
...
... may be authentic, but that does not mean that it is authorized to act
as a Diameter Server advertising a set of Diameter applications.
Prior to bringing up a connection ...
... (CER/CEA) also MUST be carried out, in order to determine what
Diameter applications are supported by each peer. Diameter sessions
...
... MUST be routed only through authorized nodes that have advertised
support for the Diameter application required by the session.
...
... be handled. The 'r' (reserved) bits are unused and SHOULD be set
to 0. Note that subsequent Diameter applications MAY define
additional bits within the AVP ...
... Mandatory AVP which is neither defined in the base Diameter
protocol nor in any of the Diameter Application specifications
governing the message in which it appears. It MAY do this in one
of the following ways:
...
... which is neither defined in the base Diameter standard nor in
any of the Diameter Application specifications governing the
message in which it appears, the implementation may resend the
message without the AVP ...
... formal syntax and defined
either in the base Diameter standard or in one of the Diameter
Application specifications governing the message.
AVPs ...
... definition contains a list of valid values and their
interpretation and is described in the Diameter application
introducing the AVP.
...
... identity and its capabilities (protocol version number,
supported Diameter applications, security mechanisms, etc.)
...
... The receiver only issues commands to its peers that have advertised
support for the Diameter application that defines the command. A
Diameter node MUST cache ...
... ASSIGNNO]
value assigned to the vendor of the Diameter application. In
combination with the Supported-Vendor-Id AVP ...
...
Start The Diameter application has signaled that a
connection should be initiated with the peer.
...
... was received.
Stop The Diameter application has signaled that a
connection should be terminated (e.g., on system
...
... AVP
contains a realm the server is configured to process locally, and
the Diameter application is locally supported, or
- Both the Destination-Host ...
... applied to create the associated answer, in addition to any
additional procedures that MAY be discussed in the Diameter
application defining the command:
- The same Hop-by-Hop ...
... Grouped and is used to advertise support of a vendor-specific
Diameter Application. Exactly one of the Auth-Application-Id and
Acct-Application-Id ...
... 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, Missing AVP).
...
... client issues an auth request to its local server. The
auth request is defined in a service specific Diameter application
(e.g., NASREQ). The request contains a Session-Id ...
... request
messages, since these are largely application-specific and are
defined in a Diameter application document. However, the base
protocol does define a set of messages that is used to terminate user
sessions ...
... authentication
and/or authorization portion of a Diameter application. The term
Service-Specific below refers to a message defined in a Diameter
application ...
... Diameter application. The term
Service-Specific below refers to a message defined in a Diameter
application (e.g., Mobile IPv4, NASREQ).
...
... session MUST initiate a re-auth towards the user,
if the service supports this particular feature. Each Diameter
application MUST state whether service-initiated re-auth is
...
... The Session-Id is created by the Diameter application initiating the
session, which in most cases is done by the client ...
... Diameter. Should batched
accounting be required in the future, a new Diameter application will
need to be created, or it could be handled using another protocol.
...
... START_RECORD, followed by zero or more INTERIM_RECORD and a single
STOP_RECORD. A particular Diameter application specification MUST
define the type of sequences that MUST be used.
...
... session.
A Diameter application document MUST define the exact concept of a
session that is being accounted, and MAY define the concept of a
...
... multi-session. For instance, the NASREQ DIAMETER application treats
a single PPP connection to a Network Access Server ...
... authorization occurs. Further, additional interim record
triggers MAY be defined by application-specific Diameter
applications. The selection of whether to use INTERIM_RECORD
records is done by the Acct-Interim-Interval AVP ...
... As defined in Section 2.4, the Application Identifier is used to
identify a specific Diameter Application. There are standards-track
application ids and vendor ...
... transport=tcp
supported-auth-applications= string L M
# This attribute lists the Diameter applications supported by the
# AAA implementation. The applications currently defined are:
...
...
supported-acct-applications= string L M
# This attribute lists the Diameter applications supported by the
# AAA implementation. The applications currently defined are:
...