IPv6 Address Accountability Considerations
draft-chown-v6ops-address-accountability-01

Document Type Expired Internet-Draft (individual)
Last updated 2011-07-11
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-chown-v6ops-address-accountability-01.txt

Abstract

Hosts in IPv4 networks typically acquire addresses by use of DHCP, and retain that address and only that address while the DHCP lease remains valid. In IPv6 networks, hosts may use DHCPv6, but may instead autoconfigure their own global addresses, and potentially use many privacy addresses over time. This behaviour places an additional burden on network operators who require address accountability for their users and devices. There has been some discussion of this issue on various mail lists; this text attempts to capture the issues to encourage further discussion.

Authors

Tim Chown (tjc@ecs.soton.ac.uk)

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