"IPv6 Unicast Address Assignment Considerations", Gunter Van de Velde, Chip Popoviciu, Tim Chown, Olaf Bonness, Christian Hahn, 7-Nov-07. ( bytes)

One fundamental aspect of any IP communications infrastructure is its addressing plan. With its new address architecture and allocation policies, the introduction of IPv6 into a network means that network designers and operators need to reconsider their existing approaches to network addressing. Lack of guidelines on handling this aspect of network design could slow down the deployment and integration of IPv6. This document aims to provide the information and recommendations relevant to planning the addressing aspects of IPv6 deployments. The document also provides IPv6 addressing case studies for both an enterprise and an ISP network.

"Requirements for address selection mechanisms", Arifumi Matsumoto, Tomohiro Fujisaki, Ruri Hiromi, Ken-ichi Kanayama, 11-May-08. ( bytes)

There are some problematic cases when using the default address selection mechanism which RFC 3484 defines. This document describes additional requirements co-working with RFC 3484 to solve the problems.

"Problem Statement of Default Address Selection in Multi-prefix Environment: Operational Issues of RFC3484 Default Rules", Arifumi Matsumoto, Tomohiro Fujisaki, Ruri Hiromi, Ken-ichi Kanayama, 14-May-08. ( bytes)

A single physical link can have multiple prefixes assigned to it. In that environment, end hosts might have multiple IP addresses and be required to use them selectively. RFC 3484 defines default source and destination address selection rules and is implemented in a variety of OS's. But, it has been too difficult to use operationally for several reasons, In some environment where multiple prefixes are assigned on a single physical link, the host with the default address selection rules will experience some trouble in communication. This document describes the possible problems that end hosts could encounter in an environment with multiple prefixes.

"Recommended Simple Security Capabilities in Customer Premises Equipment for Providing Residential IPv6 Internet Service", James Woodyatt, 13-Feb-08. ( bytes)

This document makes specific recommendations to the makers of devices that provide "simple security" capabilities at the perimeter of local-area IPv6 networks in Internet-enabled homes and small offices.

"Teredo Security Concerns", James Hoagland, Suresh Krishnan, 25-Feb-08. ( bytes)

Additional security concerns with Teredo are documented, beyond what is in RFC 4380. This is based on an independent analysis of Teredo's security implications. The primary intent of this document is to raise the awareness regarding the security issues in Teredo as deployed today.

"IPv4/IPv6 Coexistence and Transition: Requirements for solutions", Marcelo Bagnulo, Fred Baker, Iljitsch van Beijnum, 13-May-08. ( bytes)

This note presents the problem statement, analysis and requirements for solutions to IPv4/IPv6 coexistence and eventual transition in a scenario in which dual stack operation is not the norm.

Return to Internet-Draft directory.

Return to IETF home page.