IPv6 Maintenance T.J. Chown, Ed.
Internet-Draft University of Southampton
Intended status: Informational A.M. Matsumoto, Ed.
Expires: October 03, 2013 NTT
April 01, 2013
Considerations for IPv6 Address Selection Policy Changes
draft-ietf-6man-addr-select-considerations-05
Abstract
This ducument is intended to capture the address selection design
team's considerations about the address selection issues mainly
raised in [RFC5220]. This considerations led to the revision of RFC
3484 [RFC6724], and Address Selection DHCP option. Although it does
not perfectly match the current state, this document captures the
past discussion and considerations for the historical record.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 03, 2013.
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
Chown & Matsumoto Expires October 03, 2013 [Page 1]
Internet-Draft Address Selection Considerations April 2013
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Issues to Consider . . . . . . . . . . . . . . . . . . . . . 3
3. Other Related Work . . . . . . . . . . . . . . . . . . . . . 4
4. Drivers for Policy Changes . . . . . . . . . . . . . . . . . 4
4.1. Internal vs External Triggers . . . . . . . . . . . . . . 6
4.2. Administratively Triggered Changes . . . . . . . . . . . 6
4.3. Start-up vs Running Changes . . . . . . . . . . . . . . . 7
4.4. Nomadic Nodes . . . . . . . . . . . . . . . . . . . . . . 7
4.5. Multiple Interface Nodes . . . . . . . . . . . . . . . . 8
5. How Dynamic? . . . . . . . . . . . . . . . . . . . . . . . . 9
6. Considerations when Obtaining Policy . . . . . . . . . . . . 10
6.1. Changes in Available Address(es) . . . . . . . . . . . . 10
6.2. Timeliness . . . . . . . . . . . . . . . . . . . . . . . 10
7. Solution Space . . . . . . . . . . . . . . . . . . . . . . . 10
7.1. Is default policy used? . . . . . . . . . . . . . . . . . 11
7.2. Pull model . . . . . . . . . . . . . . . . . . . . . . . 11
7.3. Push model . . . . . . . . . . . . . . . . . . . . . . . 11
7.4. Routing Hints . . . . . . . . . . . . . . . . . . . . . . 12
7.5. Policy Conflicts . . . . . . . . . . . . . . . . . . . . 12
7.6. Policy Merging . . . . . . . . . . . . . . . . . . . . . 13
8. On RFC3484 Default Policies . . . . . . . . . . . . . . . . . 14
9. Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . 14
10. Security Considerations . . . . . . . . . . . . . . . . . . . 16
datatracker.ietf.org