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
RADIUS
Click on the red underlined text to get to the source
... While [RFC3162prop] defines the use of IPsec with RADIUS, support for
IPsec is not required. Since within [IKE ...
...
Server-initiated messages
While RADIUS server-initiated messages are defined in [DYNAUTH],
support is optional. This makes it difficult to implement
...
...
Auditability
RADIUS does not define data-object security mechanisms, and as a
result, untrusted proxies ...
... protocol data unit (PDU)
with RADIUS, considerable effort has been expended in enabling
backward compatibility with RADIUS ...
... RADIUS, considerable effort has been expended in enabling
backward compatibility with RADIUS, so that the two protocols may
be deployed in the same network. Initially, it is expected that
...
... network devices, as well as
within gateways enabling communication between legacy RADIUS
devices and Diameter agents ...
... error messages, capability negotiation, or
a mandatory/non-mandatory flag for attributes. Since RADIUS
clients and servers are not aware of each other's capabilities,
they may not be able to successfully negotiate a mutually
acceptable service ...
...
Peer discovery and configuration
RADIUS implementations typically require that the name or address
of servers or clients ...
... administrative burden, and creates the temptation to reuse the
RADIUS shared secret, which can result in major security
vulnerabilities if the Request Authenticator ...
... NAI) [NAI], and documented existing
implementations (and imitations) of RADIUS-based roaming
[PROXYCHAIN ...
... server, facilitating roaming between providers. However, since
RADIUS does not provide explicit support for proxies, and lacks
auditability and transmission-level security features ...
... proxies, and lacks
auditability and transmission-level security features, RADIUS-
based roaming is vulnerable to attack ...
... substantially. As a result, while Diameter is a considerably more
sophisticated protocol than RADIUS, it remains feasible to implement
within embedded devices, given improvements in processor ...
... servers that need to perform protocol conversion between Diameter and
RADIUS.
In summary, this document defines the base protocol ...
... domain, to determine
whether messages can be satisfied locally, or whether they must be
routed or redirected. In RADIUS, realm names are not necessarily
piggybacked on the DNS namespace but may be independent of it.
...
... A translation agent is a device that provides translation between two
protocols (e.g., RADIUS<->Diameter, TACACS+<->Diameter ...
...
+------+ ---------> +------+ ---------> +------+
| | RADIUS Request | | Diameter Request | |
| NAS ...
... | NAS | | TLA | | HMS |
| | RADIUS Answer | | Diameter Answer | |
+------+ <--------- +------+ <--------- +------+
...
... AVP numbers 1 through 255 are reserved for
backward compatibility with RADIUS, without setting the Vendor-Id
field. AVP ...
... whether a user is to be authenticated only, authorized only or both.
Note any value other than both MAY cause RADIUS interoperability
issues. The following values are defined:
...
... AVP Code 44) is of type OctetString is only
used when RADIUS/Diameter translation occurs. This AVP contains the
...
... Diameter translation occurs. This AVP contains the
contents of the RADIUS Acct-Session-Id attribute.
...
... AVP Code 0 is not used. AVP Codes 1-255 are managed separately as
RADIUS Attribute Types [RADTYPE]. This document defines the AVP
Codes 257-274, 276-285, 287, 291-300, 480, 483 and 485-486. See
...
... namespace is used to identify Diameter commands.
The values 0-255 are reserved for RADIUS backward compatibility, and
are defined as "RADIUS Packet ...
... RADIUS backward compatibility, and
are defined as "RADIUS Packet Type Codes" in [RADTYPE]. Values 256-
16,777,213 are for permanent, standard commands, allocated by IETF ...
... Chiba, M., Dommety, G., Eklund, M., Mitton, D. and B. Aboba, "Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS)", RFC 3576, July 2003. ...
... Rigney, C., Willens, S., Rubens, A. and W. Simpson, "Remote Authentication Dial In User Service (RADIUS)", RFC 2865draft, June 2000. ...
... gateways. Since the
retransmission behavior of RADIUS is not defined within [RADIUS],
the likelihood of duplication will vary according to the
...