Considerations for IPv6 Address Selection Policy Changes
draft-ietf-6man-addr-select-considerations-04

The information below is for an old version of the document
Document Type Expired Internet-Draft (6man WG)
Last updated 2012-05-03 (latest revision 2011-10-31)
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state Expired
Consensus Boilerplate Unknown
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-ietf-6man-addr-select-considerations-04.txt

Abstract

Where the source and/or destination node of an IPv6 communication is multi-addressed, a mechanism is required for the initiating node to select the most appropriate address pair for the communication. RFC 3484 (IPv6 Default Address Selection) [RFC3484] defines such a mechanism for nodes to perform source and destination address selection. While RFC3484 recognised the need for implementations to be able to change the policy table, it did not define how this could be achieved. Requirements have now emerged for administrators to be able to configure and potentially dynamically change RFC 3484 policy from a central control point, and for (nomadic) hosts to be able to obtain the policy for the network that they are currently attached to without manual user intervention. This text discusses considerations for such policy changes, including examples of cases where a change of policy is required, and the likely frequency of such policy changes. This text also includes some discussion on the need to also update RFC 3484, where default policies are currently defined.

Authors

Tim Chown (tjc@ecs.soton.ac.uk)
Arifumi Matsumoto (arifumi@nttv6.net)

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