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
DNS
Click on the red underlined text to get to the source
... Authenticator is not globally and
temporally unique as required in [RADIUS]. Through DNS, Diameter
enables dynamic discovery of peers. Derivation of dynamic session
keys ...
... NAI realm names are required to be unique, and are piggybacked on
the administration of the DNS namespace. Diameter makes use of
the realm, also loosely referred to as domain ...
... routed or redirected. In RADIUS, realm names are not necessarily
piggybacked on the DNS namespace but may be independent of it.
Real-time ...
... MUST be supported by all DIAMETER nodes, while the latter two options
(SRVLOC and DNS) MAY be supported.
There are two cases where Diameter ...
... according to the requestor's network protocol capabilities. If
the DNS server returns no address records, the requestor gives up.
...
... certificate. Otherwise, an
attacker could modify the DNS records to contain replacement
values in a different domain, and the client ...
... certificate, and secured RRs may be
included in the DNS, but this does not imply that it is authorized
to act as a Diameter Server.
...
... Section 2.6) to be created. Note that entries created via DNS MUST
expire (or be refreshed) within the DNS TTL. If a peer is discovered
...
... created via DNS MUST
expire (or be refreshed) within the DNS TTL. If a peer is discovered
outside of the local realm, a routing table ...
... Gulbrandsen, A., Vixie, P. and L. Esibov, "A DNS RR for specifying the location of services (DNS SRV ...
... Mealling, M. and R. Daniel, "The naming authority pointer (NAPTR) DNS resource record," RFC 2915(-> 3404prop | 3403prop | 3402prop | 3401), September 2000. ...