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
network
Click on the red underlined text to get to the source
... Ethernet,
routers and network access servers (NAS) have increased in complexity
and density, putting new demands on AAA protocols ...
... backward compatibility with RADIUS, so that the two protocols may
be deployed in the same network. Initially, it is expected that
Diameter will be deployed within new network ...
... network. Initially, it is expected that
Diameter will be deployed within new network devices, as well as
within gateways enabling communication between legacy RADIUS ...
... [NASREQ], enables Diameter support to be added to legacy networks,
by addition of a gateway or server speaking both RADIUS ...
... requirements [ROAMCRIT], defined the
Network Access Identifier (NAI) [NAI], and documented existing
...
... In the decade since AAA protocols were first introduced, the
capabilities of Network Access Server (NAS) devices have increased
substantially. As a result, while Diameter ...
... Mobile IPv4 [DIAMMIP], or
network access [NASREQ]. It is also possible for the base protocol
...
... commands or AVPs. At this time the focus of Diameter is network
access and accounting applications. A truly generic AAA protocol
...
... Client is a device at
the edge of the network that performs access control, such as a
Network Access Server ...
... network that performs access control, such as a
Network Access Server (NAS) or a Foreign Agent (FA ...
... Diameter Client is a device at the edge of the network that
performs access control. An example of a Diameter ...
... accounting of a user's session in the case of a device
reboot or other network problem prevents the reception of a
session summary message or session ...
... load balancing.
- A complex network will have multiple authentication sources, they
can sort requests and forward towards the correct target ...
... 2.7.
Relays MAY be used to aggregate requests from multiple Network Access
Servers (NASes) within a common geographical area (POP ...
... Diameter header format is shown below. The fields
are transmitted in network byte order.
0 1 2 3
...
... 32-bit integer field (in
network byte order) and aids in matching requests and replies.
The sender MUST ensure that the Hop-by-Hop ...
... 32-bit integer field (in
network byte order) and is used to detect duplicate messages.
Upon reboot implementations MAY set the high order 12 bits to
...
... The fields in the AVP header MUST be sent in network byte order. The
format of the header is:
...
... IANA assigned "SMI Network Management Private Enterprise Codes"
[ASSIGNNO] value, encoded in network byte order ...
... Network Management Private Enterprise Codes"
[ASSIGNNO] value, encoded in network byte order. Any vendor
wishing to implement a vendor-specific ...
... Integer32
32 bit signed value, in network byte order. The AVP Length field
MUST be set to 12 (16 if the 'V' bit ...
... Integer64
64 bit signed value, in network byte order. The AVP Length field
MUST be set to 16 (20 if the 'V' bit ...
... Unsigned32
32 bit unsigned value, in network byte order. The AVP Length
field MUST be set to 12 (16 if the 'V' bit ...
... Unsigned64
64 bit unsigned value, in network byte order. The AVP Length
field MUST be set to 16 (20 if the 'V' bit ...
... FLOATPOINT]. The 32-bit value is transmitted in
network byte order. The AVP Length field MUST be set to 12 (16 if
the 'V' bit ...
... FLOATPOINT]. The 64-bit value is transmitted in
network byte order. The AVP Length field MUST be set to 16 (20 if
the 'V' bit ...
... AAAA RR's or other similar records, chosen
according to the requestor's network protocol capabilities. If
the DNS server returns no address ...
... the IANA "SMI Network Management Private Enterprise Codes" [ASSIGNNO]
value assigned to the vendor ...
... contains the IANA "SMI Network Management Private Enterprise Codes"
[ASSIGNNO] value assigned to a vendor ...
... User-Name AVP,
which is in the form of a Network Access Identifier (NAI). The realm
portion of the NAI ...
... AVP is not intended to be useful in real-time, and
SHOULD NOT be expected to be parsed by network entities.
...
... authentication and/or authorization
portion of an application, and a user requests access to the network,
the Diameter client ...
...
When a Diameter server authorizes a user to use network resources for
a finite amount of time, and it is willing to extend the
authorization ...
... Diameter server to change to Idle state in
case of short transient network failure.
Any event not listed in the state machines ...
... management server for the purpose of issuing ASRs to administratively
remove users from the network.
An access device that receives an ASR ...
... Diameter Accounting protocol message MAY be compressed, in order
to reduce network bandwidth usage. If IPsec and IKE are used to
...
... Diameter Base protocol mechanisms are used to overcome small message
loss and network faults of temporary nature.
Diameter ...
... Diameter peers acting as clients MUST implement the use of failover
to guard against server failures and certain network failures.
Diameter peers acting as agents ...
... clients MAY have non-volatile memory for the safe storage of
accounting records over reboots or extended network failures, network
partitions ...
... accounting records over reboots or extended network failures, network
partitions, and server failures. If such memory is available, the
...
... DIAMETER application treats
a single PPP connection to a Network Access Server as one session,
and a set of Multilink PPP ...
... accounting records to the accounting server has
been temporarily prevented due to, for instance, a network problem.
DELIVER_AND_GRANT 1
...
... Diameter proxy server routes messages based on the realm portion
of a Network Access Identifier (NAI). The server MUST have a
table of Realm Names, and the address ...
... Aboba, B. and M. Beadles, "The Network Access Identifier", RFC 2486(-> 4282prop), January 1999. ...
... Aboba, B., Calhoun, P., Glass, S., Hiller, T., McCann, P., Shiino, H., Zorn, G., Dommety, G., Perkins, C., Patil, B., Mitton,
D., Manning, S., Beadles, M., Walsh, P., Chen, X., Sivalingham, S., Hameed, A., Munson, M., Jacobs, S., Lim, B., Hirschman,
B., Hsu, R., Xu, Y., Campbell, E., Baba, S. and E. Jaques, "Criteria for Evaluating AAA Protocols for Network Access", RFC 2989, November 2000. ...
... Mitton, D. and M. Beadles, "Network Access Server Requirements Next Generation (NASREQNG) NAS Model", RFC 2881 ...
... Beadles, M. and D. Mitton, "Criteria for Evaluating Network Access Server Protocols", RFC 3169, September 2001. ...
... Diameter services are
vital for network operation it is important to use SLPv2
authentication ...
...
As an example, it can be usually be assumed that duplicates appear
within a time window of longest recorded network partition or device
fault, perhaps a day. So only records within this time window need
...
... forward. This limits database searching to those records where
the T flag is set. In a well run network, network partitions and
...
... database searching to those records where
the T flag is set. In a well run network, network partitions and
device faults will presumably be rare events, so this approach
...
... process. During failover, it is possible for the original record
to be received after the T flag marked record, due to differences
in network delays experienced along the path by the original and
duplicate transmissions. The likelihood of this occurring
increases as the failover interval is decreased. In order to be
...
... use backward and forward time windows when performing duplicate
checking for the T flag marked request. For example, in order to
allow time for the original record to exit the network and be
recorded by the accounting server, the Diameter server ...