Skip to main content

Problems with the use of IPsec as the security protocol for Mobile IPv6
draft-patil-mext-mip6issueswithipsec-04

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Basavaraj Patil , Charles E. Perkins , Hannes Tschofenig , Domagoj Premec
Last updated 2012-04-12 (Latest revision 2011-10-10)
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

Mobile IPv6 as specified in RFC3775 relies on IPsec for securing the signaling messages and user plane traffic between the mobile node and home agent. An IPsec SA between the mobile node and the home agent provides security for the mobility signaling. Use of IPsec for securing the data traffic between the mobile node and home agent is optional. This document analyses the implications of the design decision to mandate IPsec as the default security protocol for Mobile IPv6 and consequently Dual-stack Mobile IPv6 and recommends revisiting this decision in view of the experience gained from implementation and adoption in other standards bodies.

Authors

Basavaraj Patil
Charles E. Perkins
Hannes Tschofenig
Domagoj Premec

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)