IPv4-Mapped Address API Considered Harmful
draft-cmetz-v6ops-v4mapped-api-harmful-01

Document Type Expired Internet-Draft (individual)
Last updated 2003-10-23
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-cmetz-v6ops-v4mapped-api-harmful-01.txt

Abstract

The IPv6 Addressing Architecture [Hinden, 1998] defines the 'IPv4-mapped IPv6 address.' This representation is used in the IPv6 basic API [Gilligan, 1999] to denote IPv4 addresses using AF_INET6 sockets. The use of IPv4-mapped addresses on AF_INET6 sockets degrades portability, complicates IPv6 systems, and is likely to create security problems. This document discusses each issue in turn. Finally, it proposes to resolve these problems by recommending deprecation of this mechanism.

Authors

Christopher Metz (cmetz@vnet.ibm.com)
Jun-ichiro Itoh (itojun@iijlab.net)

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