address selection and DHCPv6

James Carlson <james.d.carlson@sun.com> Tue, 24 October 2006 19:49 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GcSHK-0001Iq-Kc; Tue, 24 Oct 2006 15:49:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GcSHI-0001GK-MB for ipv6@ietf.org; Tue, 24 Oct 2006 15:49:36 -0400
Received: from brmea-mail-1.sun.com ([192.18.98.31]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcSHD-0002iC-9y for ipv6@ietf.org; Tue, 24 Oct 2006 15:49:36 -0400
Received: from eastmail1bur.East.Sun.COM ([129.148.9.49]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id k9OJnUvF003606 for <ipv6@ietf.org>; Tue, 24 Oct 2006 13:49:30 -0600 (MDT)
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143]) by eastmail1bur.East.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL, v2.2) with ESMTP id k9OJnTMR002109 for <ipv6@ietf.org>; Tue, 24 Oct 2006 15:49:29 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.13.8+Sun/8.13.8) with ESMTP id k9OJqI7O015832 for <ipv6@ietf.org>; Tue, 24 Oct 2006 15:52:18 -0400 (EDT)
Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.13.8+Sun/8.13.8/Submit) id k9OJqI9M015829; Tue, 24 Oct 2006 15:52:18 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <17726.28402.301006.138923@gargle.gargle.HOWL>
Date: Tue, 24 Oct 2006 15:52:18 -0400
From: James Carlson <james.d.carlson@sun.com>
To: ipv6@ietf.org
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Subject: address selection and DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

I've done quite a bit of searching over the archives and over various
web resources, but I haven't seen this issue addressed directly.
Apologies if I've just missed it.

RFC 3484 ("Default Address Selection for Internet Protocol version 6
(IPv6)") section 5 gives a set of ordered comparisons for source
address selection.  However, missing from this list is a distinction
implied by RFCs 2461 and 2462: some systems may have a mix of
addresses acquired by stateless address autoconfiguration, stateful
(DHCPv6) configuration, and manual addressing.  How are these
distinguished?

Rule 7 does address the temporary (RFC 3041) addresses, but what about
these other flavors of addresses?  Are they distinguished only by
scope?

Was this issue addressed and intentionally omitted from the RFC?  (If
so, I don't see it in the archives.)

I suspect that some clients may need to distinguish among the various
flavors here.  I'd suggest amending Rule 7 to read:

   Rule 7:  Prefer stable, public addresses.
   If SA is a manually-configured address and SB is automatic or
   temporary, then prefer SA.  If SA is automatically configured via
   stateful (DHCPv6) methods and SB is automatically configured via
   stateless methods or temporary, then prefer SA.  If SA is
   automatically configured via stateless methods and SB is temporary,
   prefer SA.

   Similarly, if SB is a manually-configured address and SA is not,
   then prefer SB.  If SB is stateful and SA is stateless or
   temporary, prefer SB.  If SB is stateless and SA is temporary,
   prefer SB.

   When the application has the "prefer temporary address" flag
   enabled, all temporary addresses are (within this rule) elevated in
   preference above manually-configured addresses.  The other
   preferences are unaltered.  (In other words, the preference order
   with this flag set becomes temporary first, then manual, stateful,
   and stateless last.)

... or, to simplify, defining a "stability_of_address(A)" function
that can work here.

-- 
James Carlson, KISS Network                    <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------