Cisco Cisco Packet Data Interworking Function (PDIF)
Diameter Dictionaries and Attribute Definitions
Diameter Attributes ▀
AAA Interface Administration and Reference, StarOS Release 17 ▄
53
This represents the number of seconds since 0h on 1 January 1900 with respect to the Coordinated Universal Time
(UTC).
(UTC).
On 6h 28m 16s UTC, 7 February 2036 the time value will overflow. SNTP describes a procedure to extend the time to
2104. This procedure MUST be supported by all DIAMETER nodes.
2104. This procedure MUST be supported by all DIAMETER nodes.
UTF8String
The UTF8String format is derived from the OctetString AVP Base Format. This is a human readable string represented
using the ISO/IEC IS 10646-1 character set, encoded as an OctetString using the UTF-8 [UFT8] transformation format
described in RFC 2279.
using the ISO/IEC IS 10646-1 character set, encoded as an OctetString using the UTF-8 [UFT8] transformation format
described in RFC 2279.
Since additional code points are added by amendments to the 10646 standard from time to time, implementations
MUST be prepared to encounter any code point from 0x00000001 to 0x7fffffff. Byte sequences that do not correspond
to the valid encoding of a code point into UTF-8 charset or are outside this range are prohibited.
MUST be prepared to encounter any code point from 0x00000001 to 0x7fffffff. Byte sequences that do not correspond
to the valid encoding of a code point into UTF-8 charset or are outside this range are prohibited.
The use of control codes SHOULD be avoided. When it is necessary to represent a new line, the control code sequence
CR LF SHOULD be used.
CR LF SHOULD be used.
The use of leading or trailing white space SHOULD be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display,
such as hexadecimal, MAY be provided.
such as hexadecimal, MAY be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 charset is identical to the US-ASCII charset.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of an UTF8String in octets
may be different from the number of characters encoded.
may be different from the number of characters encoded.
Note that the AVP Length field of an UTF8String is measured in octets, not characters.
DiameterIdentity
The DiameterIdentity (DIAMIDENT) format is derived from the OctetString AVP Base Format.
DiameterIdentity = FQDN
DiameterIdentity value is used to uniquely identify a Diameter node for purposes of duplicate connection and routing
loop detection.
loop detection.
The contents of the string MUST be the FQDN of the Diameter node. If multiple Diameter nodes run on the same host,
each Diameter node MUST be assigned a unique DiameterIdentity. If a Diameter node can be identified by several
FQDNs, a single FQDN should be picked at startup, and used as the only DiameterIdentity for that node, whatever the
connection it is sent on.
each Diameter node MUST be assigned a unique DiameterIdentity. If a Diameter node can be identified by several
FQDNs, a single FQDN should be picked at startup, and used as the only DiameterIdentity for that node, whatever the
connection it is sent on.
DiameterURI
The DiameterURI (DIAMURI) MUST follow the Uniform Resource Identifiers (URI) syntax [URI] rules specified
below:
below:
"aaa://" FQDN [ port ] [ transport ] [ protocol ]
– or –
"aaas://" FQDN [ port ] [ transport ] [ protocol ]