RFC 4832: Security Threats to Network-Based Localized Mobility Management (NETLMM)
In plain English — editorial summary, not part of the RFC
This document discusses security threats to network-based localized mobility management. Threats may occur on two interfaces: the interface between a localized mobility anchor and a mobile access gateway, as well as the interface between a mobile access gateway and a mobile node. Threats to the former interface impact the localized mobility management protocol itself. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4832
- Published
- April 2007
- Authors
- C. Vogt; J. Kempf
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7739Security Implications of Predictable Fragment Identification ValuesCurrent
February 2016
- RFC 5358Preventing Use of Recursive Nameservers in Reflector AttacksCurrent
October 2008
- RFC 5575Dissemination of Flow Specification RulesObsoleted
August 2009
- RFC 3704Ingress Filtering for Multihomed NetworksUpdated
March 2004
- RFC 6274Security Assessment of the Internet Protocol Version 4Current
July 2011
- RFC 2827Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address SpoofingUpdated
May 2000
- RFC 7141Byte and Packet Congestion NotificationCurrent
February 2014
- RFC 7282On Consensus and Humming in the IETFCurrent
June 2014
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?