[rfc-dist] RFC 4832 on Security Threats to Network-Based Localized Mobility Management (NETLMM)
rfc-editor at rfc-editor.org
Wed Apr 11 17:38:36 PDT 2007
A new Request for Comments is now available in online RFC libraries.
Title: Security Threats to Network-Based Localized
Mobility Management (NETLMM)
Author: C. Vogt, J. Kempf
Date: April 2007
Mailbox: chvogt at tm.uka.de,
kempf at docomolabs-usa.com
I-D Tag: draft-ietf-netlmm-threats-04.txt
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.
This document is a product of the Network-based Localized Mobility
Management Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution
of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
The RFC Editor Team
USC/Information Sciences Institute
More information about the rfc-dist