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

Document Type Expired Internet-Draft (individual)
Last updated 2012-04-12 (latest revision 2011-10-10)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-patil-mext-mip6issueswithipsec-04.txt

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 (basavaraj.patil@nokia.com)
Charles Perkins (charles.perkins@tellabs.com)
Hannes Tschofenig (Hannes.Tschofenig@gmx.net)
Domagoj Premec (domagoj.premec@gmail.com)

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