RFC 3588:Diameter Base Protocol
RFC-Ref

Mobile IPv4


Click on the red underlined text to get to the source

... accounting purposes only, or it may be used with a Diameter application, such as Mobile IPv4 [DIAMMIP], or network access ...
... Profile [AAATRANS] and applications: Mobile IPv4 [DIAMMIP], and NASREQ [NASREQ ...
... state machine. The Mobile IPv4 [DIAMMIP] application defines a Diameter application ...
... that allows a Diameter server to perform AAA functions for Mobile IPv4 services to a mobile node. ...
... AAA, which includes support for accounting. The Mobile IPv4 and the NASREQ documents describe applications that use this base ...


... NASREQ], Mobile IPv4 [DIAMMIP]. These applications are introduced in this document but specified elsewhere. Additional Diameter applications ...
... service, e.g., NASREQ and/or Mobile IPv4. A Diameter Client that does not support ...
... Client that does not support both NASREQ and Mobile IPv4, MUST be referred to as "Diameter X Client ...
... service, e.g., NASREQ and/or Mobile IPv4. A Diameter Server that does not support both NASREQ ...
... Diameter Server that does not support both NASREQ and Mobile IPv4, MUST be referred to as "Diameter X Server" where X is the application which it supports, and not a ...
... services, e.g., NASREQ and/or Mobile IPv4. A Diameter proxy which does not support ...
... proxy which does not support also both NASREQ and Mobile IPv4, MUST be referred to as "Diameter X Proxy ...


... Service-Specific below refers to a message defined in a Diameter application (e.g., Mobile IPv4, NASREQ). ...


... Furthermore, there are certain applications where a user receives service from different access devices (e.g., Mobile IPv4), each with their own unique Session-Id. In such cases, the Acct-Multi-Session ...



Google
Web
RFC-Ref