RFC 3588:Diameter Base Protocol
RFC-Ref

base protocol


Click on the red underlined text to get to the source

... The Diameter base protocol provides the following facilities: - Delivery ...
... The Diameter base protocol provides the minimum requirements needed for a AAA protocol ...
... for a AAA protocol, as required by [AAAREQ]. The base protocol may be used by itself for accounting purposes only, or it may be used ...
... network access [NASREQ]. It is also possible for the base protocol to be extended for use in new applications, via the addition of new commands or AVPs ...
... RADIUS. In summary, this document defines the base protocol specification for AAA, which includes support for accounting ...
... AVPs, new commands or additional mechanisms (e.g., application defined state machine), then the base protocol defined standard accounting application Id (Section 2.4) MUST be used in ACR ...
... its very nature, a Diameter Server MUST support Diameter applications in addition to the base protocol. Downstream ...


... Diameter Clients MUST support the base protocol, which includes accounting. In addition, they MUST fully support each Diameter application ...
... Diameter Servers MUST support the base protocol, which includes accounting. In addition, they MUST fully support each Diameter application ...
... agents are, by definition, protocol transparent, and MUST transparently support the Diameter base protocol, which includes accounting, and all Diameter applications. ...
... Diameter proxies MUST support the base protocol, which includes accounting. In addition, they MUST fully support each Diameter application ...
... negotiation, how messages are sent and how peers may eventually be abandoned. The base protocol also defines certain rules that apply to all exchanges of messages between Diameter nodes. ...
... Diameter application MUST have an IANA assigned Application Identifier (see Section 11.3). The base protocol does not require an Application Identifier since its support is mandatory. During the ...


... be taken for a particular message. The following Command Codes are defined in the Diameter base protocol: Command-Name Abbrev. Code Reference ...


... Diameter Base Protocol AVPs ...
... The following table describes the Diameter AVPs defined in the base protocol, their AVP Code values, types, possible flag values and whether the AVP ...


... algorithm defined in the specification in order to be compliant to the Diameter base protocol. ...


... Diameter; protocol and 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 ...


... authorization requests and answers. The base protocol does not include any authorization request messages, since these are largely application-specific ...
... 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. These are used to allow servers that maintain state ...
... state machines supported in the Diameter base protocol. The first two describe a session in which the server is maintaining session ...
... state machine depends in some cases on the particular application. The Diameter base protocol defines a default state machine that MUST be followed by all applications that ...
... However, the Diameter base protocol defines one optional server side state machine ...


... Diameter Base protocol mechanisms are used to overcome small message loss and network faults of temporary nature. ...


... Base Protocol Command AVP Table ...


... The Diameter base protocol assumes that messages are secured by using either IPSec or TLS ...



Google
Web
RFC-Ref