Privacy Extensions for Stateless Address Autoconfiguration in IPv6(RFC 3041) 1

Outline Introduction Previous Work Temporary address interface identifiers Problem 2

Introduction Because IPv6 address identifiers remain static, for security reasons, a method is required to provide temporary addresses. To address this concern and provide a level of anonymity, an alternative IPv6 interface identifier can be randomly generated and changed over time. 3

Previous Work IPv6 address – network prefixes, interface identifier(each 64-bits) How to get IPv6 address – Neighbor Discovery Router Solicitation Router Advertise 4

Previous Work IPv6 Auto configuration – Stateful Address Auto-configuration – StateLess Address Auto-configuration(SLACC) Interface Identifier – Derived from the Extended Unique Identifier (EUI)-64 address (RFC 2373) – Randomly generated and changed over time (RFC3041) Temporary address interface identifiers 5

Previous Work EUI-64 address-based interface identifiers – IEEE 802 MAC addresses,48-bits IEEE administered company ID Manufacturer selected extension ID – Mapping IEEE 802 addresses to EUI-64 addresses Universal/Local(U/L): which is the seventh bit in the first byte. 6

Temporary address interface identifiers previous value Compute the MD5 message digest left-most 64-bits – set bit U/L bit to zero rightmost 64-bits Perform duplicate address detection (DAD) on the generated temporary address. 7

Problem The desires of protecting individual privacy vs. the desire to effectively maintain and debug a network can conflict with each other. Having clients use addresses that change over time will make it more difficult to track down and isolate operational problems. 8