Verifying Correctness of Alternate Care-of Address Option
draft-arkko-mext-rfc3775-altcoa-check-01

Document Type Expired Internet-Draft (individual)
Last updated 2008-02-25
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html 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-arkko-mext-rfc3775-altcoa-check-01.txt

Abstract

This document revises the RFC 3775 rules on how Alternate Care-of Address option is processed. Alternate Care-of Address option is used to carry the current care-of address inside a Mobility Header message. This is used in addition to the source address in the packet in order to ensure that the care-of address is protected by IPsec ESP, the security mechanism that protects Mobility Header messages. Unfortunately, RFC 3775 did not require verification that the source address and care-of address are the same. This document adds that requirement.

Authors

Jari Arkko (jari.arkko@piuha.net)

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