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
Bit
Click on the red underlined text to get to the source
...
- Adding new AVPs to the command, which have the "M" bit set.
- Requiring a command that has a different number of round trips ...
... AVPs (AVPs with the "M" bit not set) to any command defined in an
application, including vendor-specific ...
... AVPs are added. A mandatory AVP is defined as one which
has the "M" bit set when sent within an accounting command,
regardless of whether it is required or optional within the ABNF ...
...
Within an accounting command, setting the "M" bit implies that a
backend server (e.g., billing server) or the accounting server itself
...
... AVP is included
within an accounting command, it MUST NOT have the "M" bit set, even
if the "M" bit is set when the same AVP ...
... accounting command, it MUST NOT have the "M" bit set, even
if the "M" bit is set when the same AVP is used within other Diameter
commands (i.e., authentication ...
... be closed using a RESET call (send a TCP RST bit) or an SCTP ABORT
message (graceful closure is compromised).
...
... Accounting AVPs may be considered sensitive. Any AVP for which
the P bit may be set or which may be encrypted may be considered
sensitive.
...
... described for this command. Messages with the 'E'
bit set are commonly referred to as error
messages. This bit MUST NOT be set in request
messages ...
... bit set are commonly referred to as error
messages. This bit MUST NOT be set in request
messages. See Section 7.2.
T(Potentially re-transmitted message)
...
... as an indication of a possible duplicate due to a
link failure. This bit MUST be cleared when
sending a request for the first time, otherwise
the sender ...
... answer messages.
r(eserved) - these flag bits are reserved for future use, and
MUST be set to zero, and ignored by the receiver ...
... The Command-Code field is three octets, and is used in order to
communicate the command associated with the message. The 24-bit
address space is managed by IANA (see Section 11.2.1).
...
... network byte order) and is used to detect duplicate messages.
Upon reboot implementations MAY set the high order 12 bits to
contain the low order 12 bits of current time, and the low order
...
... Upon reboot implementations MAY set the high order 12 bits to
contain the low order 12 bits of current time, and the low order
20 bits to a random value ...
... contain the low order 12 bits of current time, and the low order
20 bits to a random value. Senders of request messages ...
... Each command Request/Answer pair is assigned a command code, and the
sub-type (i.e., request or answer) is identified via the 'R' bit in
the Command Flags field of the Diameter ...
... ; The Command Code assigned to the command
r-bit = ", REQ"
; If present, the 'R' bit in the Command
...
... r-bit = ", REQ"
; If present, the 'R' bit in the Command
; Flags is set, indicating that the message
; is a request, as opposed to an answer.
...
... ; is a request, as opposed to an answer.
p-bit = ", PXY"
; If present, the 'P' bit in the Command
...
... p-bit = ", PXY"
; If present, the 'P' bit in the Command
; Flags is set, indicating that the message
; is proxiable ...
... bit = ", ERR"
; If present, the 'E' bit in the Command
; Flags is set, indicating that the answer
; message contains a Result-Code ...
...
Both the request and the answer for a given command share the same
command code. The request is identified by the R(equest) bit in the
Diameter header ...
... Each AVP of type OctetString MUST be padded to align on a 32-bit
boundary, while other AVP types align naturally. A number of zero-
...
... Flags field informs the receiver how each attribute must
be handled. The 'r' (reserved) bits are unused and SHOULD be set
to 0. Note that subsequent Diameter applications MAY define
...
... to 0. Note that subsequent Diameter applications MAY define
additional bits within the AVP Header, and an unrecognized bit ...
... bits within the AVP Header, and an unrecognized bit
SHOULD be considered an error. The 'P' bit indicates the need for
...
... Header, and an unrecognized bit
SHOULD be considered an error. The 'P' bit indicates the need for
encryption for end-to-end security ...
... end-to-end security.
The 'M' Bit, known as the Mandatory bit, indicates whether support
of the AVP ...
...
The 'M' Bit, known as the Mandatory bit, indicates whether support
of the AVP is required. If an AVP ...
... AVPs.
The 'M' bit MUST be set according to the rules defined for the AVP
containing it. In order to preserve interoperability ...
...
AVPs with the 'M' bit cleared are informational only and a
receiver that receives a message with such an AVP ...
... The 'V' bit, known as the Vendor-Specific bit, indicates whether
the optional Vendor-ID field is present in the AVP ...
... AVP Header contains one optional field. This field is only
present if the respective bit-flag is enabled.
Vendor ...
... otherwise noted, the AVP Length field MUST be set to at least 8
(12 if the 'V' bit is enabled). AVP Values of this type that are
not a multiple of four-octets in length is followed by the
...
... network byte order. The AVP Length field
MUST be set to 12 (16 if the 'V' bit is enabled).
Integer64 ...
... network byte order. The AVP Length field
MUST be set to 16 (20 if the 'V' bit is enabled).
Unsigned32 ...
... network byte order. The AVP Length
field MUST be set to 12 (16 if the 'V' bit is enabled).
Unsigned64 ...
... network byte order. The AVP Length
field MUST be set to 16 (20 if the 'V' bit is enabled).
Float32 ...
... This represents floating point values of single precision as
described by [FLOATPOINT]. The 32-bit value is transmitted in
network byte order. The AVP ...
... network byte order. The AVP Length field MUST be set to 12 (16 if
the 'V' bit is enabled).
Float64 ...
... This represents floating point values of double precision as
described by [FLOATPOINT]. The 64-bit value is transmitted in
network byte order. The AVP ...
... network byte order. The AVP Length field MUST be set to 16 (20 if
the 'V' bit is enabled).
Grouped
...
... headers and padding. The AVP Length field is set
to 8 (12 if the 'V' bit is enabled) plus the total length of all
included AVPs, including their headers ...
... AVP Base
Format. It is a discriminated union, representing, for example a
32-bit (IPv4) [IPV4] or 128-bit ...
... IP number will match the
rule.
ipno/bits An IP number as above with a mask
width of the form 1.2.3.4/24. In
...
... IP numbers from
1.2.3.0 to 1.2.3.255 will match.
The bit width MUST be valid for the
IP version ...
... IP version and the IP number MUST
NOT have bits set beyond the mask.
For a match to occur, the same IP
version must be present in the
...
... IP address. To test for a
particular IP version, the bits part
can be set to zero. The keyword
...
... encapsulated within a Grouped AVP has the 'M' (mandatory) bit set,
the Grouped AVP itself MUST also include the 'M' bit ...
... available peers to handle the application that corresponds to the
Command-Code. In such instances, the 'E' bit is set in the answer
message (see Section 7.) with the Result-Code AVP ...
... Capabilities-Exchange-Request (CER), indicated by the Command-
Code set to 257 and the Command Flags' 'R' bit set, is sent to
exchange local capabilities. Upon detection of a transport failure,
...
... The Capabilities-Exchange-Answer (CEA), indicated by the Command-Code
set to 257 and the Command Flags' 'R' bit cleared, is sent in
response to a CER message.
...
... The Disconnect-Peer-Request (DPR), indicated by the Command-Code set
to 282 and the Command Flags' 'R' bit set, is sent to a peer to
inform its intentions to shutdown the transport connection. Upon
...
... The Disconnect-Peer-Answer (DPA), indicated by the Command-Code set
to 282 and the Command Flags' 'R' bit cleared, is sent as a response
to the Disconnect-Peer-Request message. Upon receipt of this
...
... The Device-Watchdog-Request (DWR), indicated by the Command-Code set
to 280 and the Command Flags' 'R' bit set, is sent to a peer when no
traffic has been exchanged between two peers (see Section 5.5.3).
...
... The Device-Watchdog-Answer (DWA), indicated by the Command-Code set
to 280 and the Command Flags' 'R' bit cleared, is sent as a response
to the Device-Watchdog-Request message.
...
... routing entry is set
to REDIRECT, it MUST reply with an answer message with the 'E' bit
set, while maintaining the Hop-by-Hop Identifier ...
... AVPs are allowed. The receiver of the answer
message with the 'E' bit set selects exactly one of these hosts as
the destination ...
... answer
message, in the same order they were present in the request.
- The 'P' bit is set to the same value as the one in the request.
- The same End-to-End ...
... One or more of instances of this AVP MUST be present if the answer
message's 'E' bit is set and the Result-Code AVP is set to
...
... protocol errors MUST
only be present in answer messages whose 'E' bit is set. When a
request message is received that causes a protocol error ...
... request message is received that causes a protocol error, an answer
message is returned with the 'E' bit set, and the Result-Code AVP is
...
... Diameter
entity reporting the error clears the 'R' bit in the Command Flags,
and adds the Result-Code AVP ...
...
- An unrecognized AVP is received with the 'M' bit (Mandatory bit)
set, causes an answer to be sent with the Result-Code ...
... - An unrecognized AVP is received with the 'M' bit (Mandatory bit)
set, causes an answer to be sent with the Result-Code AVP ...
... Result-Code data field contains an IANA-managed 32-bit address
space representing errors (see Section 11.4). Diameter provides the
...
... error, if it is possible. Note that these and only these errors MUST
only be used in answer messages whose 'E' bit is set.
DIAMETER ...
... BITS 3009
A request was received that included an AVP whose flag bits are
set to an unrecognized value, or that is inconsistent with the
AVP ...
... The peer received a message that contained an AVP that is not
recognized or supported and was marked with the Mandatory bit. A
Diameter message with this error MUST contain one or more Failed-
...
... DIAMETER_INVALID_AVP_BIT_COMBO 5016
The request contained an AVP with which is not allowed to have the
...
... Error Bit ...
... header is set when the request
caused a protocol-related error (see Section 7.1.3). A message with
the 'E' bit MUST NOT be sent as a response to an answer message.
Note that a message with the 'E' bit ...
... bit MUST NOT be sent as a response to an answer message.
Note that a message with the 'E' bit set is still subjected to the
processing rules defined in Section 6.2. When set, the answer
message ...
... header is the same than the one found
in the request message, but with the 'R' bit cleared and the 'E' bit
set. The 'P' bit ...
... in the request message, but with the 'R' bit cleared and the 'E' bit
set. The 'P' bit in the header ...
... bit cleared and the 'E' bit
set. The 'P' bit in the header is set to the same value as the one
found in the request message ...
... RAR), indicated by the Command-Code set to 258
and the message flags' 'R' bit set, may be sent by any server to the
access device that is providing session service ...
... RAA), indicated by the Command-Code set to 258
and the message flags' 'R' bit clear, is sent in response to the RAR.
The Result-Code ...
... STR), indicated by the Command-Code
set to 275 and the Command Flags' 'R' bit set, is sent by the access
device to inform the Diameter Server that an authenticated ...
... STA), indicated by the Command-Code
set to 275 and the message flags' 'R' bit clear, is sent by the
Diameter Server to acknowledge the notification ...
... ASR), indicated by the Command-Code set to
274 and the message flags' 'R' bit set, may be sent by any server to
the access device that is providing session service ...
... ASA), indicated by the Command-Code set to
274 and the message flags' 'R' bit clear, is sent in response to the
ASR. The Result-Code ...
... 32 bits>[;<optional value>]
<high 32 bits> and <low 32 bits> are decimal representations of the
high and low 32 bits ...
...
<high 32 bits> and <low 32 bits> are decimal representations of the
high and low 32 bits of a monotonically increasing 64-bit ...
... 32 bits> and <low 32 bits> are decimal representations of the
high and low 32 bits of a monotonically increasing 64-bit value. The
64-bit ...
... 32 bits> are decimal representations of the
high and low 32 bits of a monotonically increasing 64-bit value. The
64-bit value is rendered in two part to simplify formatting by 32-bit
processors ...
... 32 bits of a monotonically increasing 64-bit value. The
64-bit value is rendered in two part to simplify formatting by 32-bit
processors. At startup, the high 32 bits of the 64-bit ...
... 64-bit value. The
64-bit value is rendered in two part to simplify formatting by 32-bit
processors. At startup, the high 32 bits of the 64-bit value MAY be
...
... 64-bit value is rendered in two part to simplify formatting by 32-bit
processors. At startup, the high 32 bits of the 64-bit value MAY be
initialized to the time, and the low 32 bits ...
... 64-bit value is rendered in two part to simplify formatting by 32-bit
processors. At startup, the high 32 bits of the 64-bit value MAY be
initialized to the time, and the low 32 bits MAY be initialized to
...
... 32 bits of the 64-bit value MAY be
initialized to the time, and the low 32 bits MAY be initialized to
zero. This will for practical purposes eliminate the possibility of
overlapping Session ...
... authentication
method is to be immediately initiated. The absence of this AVP, or a
value of all ones (meaning all bits in the 32 bit field are set to
one) means no re-auth is expected.
...
... AVP, or a
value of all ones (meaning all bits in the 32 bit field are set to
one) means no re-auth is expected.
...
... the same authorizing server.
This field is a bit mask, and the following bits have been defined:
...
... Session-Binding AVP with any of the bits set to a zero
value. If present, this AVP MAY inform the Diameter ...
... ACR) command, indicated by the Command-Code
field set to 271 and the Command Flags' 'R' bit set, is sent by a
Diameter node, acting as a client ...
... ACA) command, indicated by the Command-Code
field set to 271 and the Command Flags' 'R' bit cleared, is used to
acknowledge an Accounting-Request command. The Accounting-Answer ...
... AVP header, defined in
Section 4. This document assigns bit 0 ('V'endor Specific), bit 1
('M'andatory) and bit ...
... header, defined in
Section 4. This document assigns bit 0 ('V'endor Specific), bit 1
('M'andatory) and bit 2 ('P'rotected). The remaining bits ...
... bit 0 ('V'endor Specific), bit 1
('M'andatory) and bit 2 ('P'rotected). The remaining bits should
only be assigned via a Standards Action [IANA ...
... bit 1
('M'andatory) and bit 2 ('P'rotected). The remaining bits should
only be assigned via a Standards Action [IANA].
...
... bit 0 ('R'equest), bit 1 ('P'roxy),
bit 2 ('E'rror) and bit 3 ('T'). Bits 4 through 7 MUST only be
...
... bit 1 ('P'roxy),
bit 2 ('E'rror) and bit 3 ('T'). Bits 4 through 7 MUST only be
assigned via a Standards Action [IANA ...
... bit 2 ('E'rror) and bit 3 ('T'). Bits 4 through 7 MUST only be
assigned via a Standards Action [IANA].
...
... AVP (AVP Code 270)
defines the bits 1-4. All remaining bits are available for
assignment via IETF ...
... AVP Code 270)
defines the bits 1-4. All remaining bits are available for
assignment via IETF Consensus [IANA ...