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
NASREQ
Click on the red underlined text to get to the source
... accounting. The Mobile IPv4 and the
NASREQ documents describe applications that use this base
specification for Authentication, Authorization ...
... authorization it is
always extended for a particular application. Two Diameter
applications are defined by companion documents: NASREQ [NASREQ],
...
... Diameter Client that does not support
both NASREQ and Mobile IPv4, MUST be referred to as "Diameter X
...
... Diameter
application that is needed to implement the intended service, e.g.,
NASREQ and/or Mobile IPv4. A Diameter Server that does not support
...
... Mobile IPv4. A Diameter Server that does not support
both NASREQ and Mobile IPv4, MUST be referred to as "Diameter X
...
... Diameter
application that is needed to implement proxied services, e.g.,
NASREQ and/or Mobile IPv4. A Diameter proxy ...
... Diameter proxy which does not support
also both NASREQ and Mobile IPv4, MUST be referred to as "Diameter X
...
... service specific Diameter application
(e.g., NASREQ). The request contains a Session-Id AVP, which is used
...
... Service-Specific below refers to a message defined in a Diameter
application (e.g., Mobile IPv4, NASREQ).
There are four different authorization ...
... session that is being accounted, and MAY define the concept of a
multi-session. For instance, the NASREQ DIAMETER application treats
a single PPP connection ...
... # Application Name Defined by
# ---------------- -----------------------------------
# NASREQ Diameter Network Access Server Application
...
...
#
NASREQ,MobileIP
supported-acct-applications= string L M
...
... # Application Name Defined by
# ---------------- -----------------------------------
# NASREQ Diameter Network Access Server Application
...
