RFC 5030: Mobile IPv4 RADIUS Requirements
In plain English — editorial summary, not part of the RFC
This document provides an applicability statement as well as a scope definition for specifying Remote Authentication Dial-In User Service (RADIUS) extensions to support Mobile IPv4. The goal is to allow specification of RADIUS attributes to assist the Mobile IPv4 signaling procedures. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5030
- Published
- October 2007
- Authors
- M. Nakhjiri; K. Chowdhury; A. Lior; K. Leung
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3519Mobile IP Traversal of Network Address Translation (NAT) DevicesCurrent
May 2003
- RFC 4977Problem Statement: Dual Stack MobilityCurrent
August 2007
- RFC 5265Mobile IPv4 Traversal across IPsec-Based VPN GatewaysCurrent
June 2008
- RFC 5454Dual-Stack Mobile IPv4Current
March 2009
- RFC 4225Mobile IP Version 6 Route Optimization Security Design BackgroundCurrent
December 2005
- RFC 5944IP Mobility Support for IPv4, RevisedCurrent
November 2010
- RFC 6098Generic Notification Message for Mobile IPv4Current
April 2012
- RFC 5090RADIUS Extension for Digest AuthenticationCurrent
February 2008
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?