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
IANA
Click on the red underlined text to get to the source
...
In order to allocate a new AVP value, a request MUST be sent to IANA
[IANA], along with an explanation of the new AVP value ...
... [IANA], along with an explanation of the new AVP value. IANA
considerations for Diameter are discussed in Section 11.
...
... In order to create a new AVP, a request MUST be sent to IANA, with a
specification for the AVP. The request MUST include the commands
...
...
Every Diameter application specification MUST have an IANA assigned
Application Identifier (see Section 2.4) or a vendor ...
... Diameter accounting application specification MUST
have an IANA assigned Application Identifier (see Section 2.4) or a
vendor ...
...
Each Diameter application MUST have an IANA assigned Application
Identifier (see Section 11.3). The base protocol does not require an
...
... 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).
Command-Code values ...
... AVP numbers 256 and above are used for Diameter, which are
allocated by IANA (see Section 11.1).
AVP ...
... Flags field. The optional four-octet Vendor-ID field contains the
IANA assigned "SMI Network Management Private Enterprise Codes"
...
... vendor ID value of zero (0) corresponds to the IETF adopted AVP
values, as managed by the IANA. Since the absence of the vendor
ID field implies that the AVP in question is not vendor ...
... D2T for TCP and D2S for SCTP. We also establish an IANA
registry for NAPTR service name to transport protocol ...
... AVP Code 266) is of type Unsigned32 and contains
the IANA "SMI Network Management Private Enterprise Codes" [ASSIGNNO ...
... AVP Code 265) is of type Unsigned32 and
contains the IANA "SMI Network Management Private Enterprise Codes"
...
... The Result-Code data field contains an IANA-managed 32-bit address
space representing errors (see Section 11.4). Diameter ...
... IANA Considerations ...
...
This section provides guidance to the Internet Assigned Numbers
Authority (IANA) regarding registration of values related to the
Diameter protocol ...
... IETF Consensus", "Standards Action".
This section explains the criteria to be used by the IANA for
assignment of numbers within namespaces defined within this document.
...
... Vendor-ID or a Vendor-ID value of zero (0) identifies the IETF IANA
controlled AVP Codes namespace ...
... AVP Codes and sometimes also
possible values in an AVP are controlled and maintained by IANA.
AVP Code ...
... Diameter header contains two fields that
require IANA namespace management; Command Code and Command Flags.
...
... vendor specific application ids.
IANA [IANA] has assigned the range 0x00000001 to 0x00ffffff for
...
... Vendor-Specific Application Identifiers are assigned on a First Come,
First Served basis by IANA.
...
... meanings. For attributes other than those specified in this section,
adding additional values to the list can be done on a First Come,
First Served basis by IANA.
...
... Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. ...
... IANA, "Number assignment", http://www.iana.org ...