RFC 4487: Mobile IPv6 and Firewalls: Problem Statement
In plain English — editorial summary, not part of the RFC
This document captures the issues that may arise in the deployment of IPv6 networks when they support Mobile IPv6 and firewalls. The issues are not only applicable to firewalls protecting enterprise networks, but are also applicable in 3G mobile networks such as General Packet Radio Service / Universal Mobile Telecommunications System (GPRS/UMTS) and CDMA2000 networks. The goal of this document is to highlight the issues with firewalls and Mobile IPv6 and act as an enabler for further discussion. Issues identified here can be solved by developing appropriate solutions. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4487
- Published
- May 2006
- Authors
- F. Le; S. Faccin; B. Patil; H. Tschofenig
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4280Dynamic Host Configuration Protocol (DHCP) Options for Broadcast and Multicast Control ServersCurrent
December 2005
- RFC 4980Analysis of Multihoming in Network Mobility SupportCurrent
October 2007
- RFC 5177Network Mobility (NEMO) Extensions for Mobile IPv4Updated
April 2008
- RFC 7458Extensible Authentication Protocol (EAP) Attributes for Wi-Fi Integration with the Evolved Packet CoreCurrent
February 2015
- RFC 4489A Method for Generating Link-Scoped IPv6 Multicast AddressesCurrent
April 2006
- RFC 4477Dynamic Host Configuration Protocol (DHCP): IPv4 and IPv6 Dual-Stack IssuesCurrent
May 2006
- RFC 4471Derivation of DNS Name Predecessor and SuccessorCurrent
September 2006
- RFC 4470Minimally Covering NSEC Records and DNSSEC On-line SigningCurrent
April 2006
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?