Re: Multiple addresses [was Node Requirements: Elevating DHCPv6 from MAY to SHOULD]

james woodyatt <jhw@apple.com> Tue, 31 May 2011 16:24 UTC

Return-Path: <jhw@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B3E2E07EC for <ipv6@ietfa.amsl.com>; Tue, 31 May 2011 09:24:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wv3dDqBUlzT6 for <ipv6@ietfa.amsl.com>; Tue, 31 May 2011 09:24:33 -0700 (PDT)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id C2116E07F9 for <ipv6@ietf.org>; Tue, 31 May 2011 09:24:27 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: text/plain; CHARSET="US-ASCII"
Received: from relay14.apple.com ([17.128.113.52]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LM200IKYILW2RD1@mail-out.apple.com> for ipv6@ietf.org; Tue, 31 May 2011 09:24:27 -0700 (PDT)
X-AuditID: 11807134-b7c00ae0000074fb-7a-4de5163b327d
Received: from koseret (koseret.apple.com [17.151.62.39]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate) by relay14.apple.com (Apple SCV relay) with SMTP id 00.16.29947.B3615ED4; Tue, 31 May 2011 09:24:27 -0700 (PDT)
Received: from [17.113.33.178] (unknown [17.113.33.178]) by koseret.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPSA id <0LM2003BZIWKK050@koseret.apple.com> for ipv6@ietf.org; Tue, 31 May 2011 09:24:26 -0700 (PDT)
Subject: Re: Multiple addresses [was Node Requirements: Elevating DHCPv6 from MAY to SHOULD]
From: james woodyatt <jhw@apple.com>
In-reply-to: <4BC7CABA-D871-4B27-96BA-10A2F9D6D2B1@cisco.com>
Date: Tue, 31 May 2011 09:24:19 -0700
Message-id: <C6682761-895A-4935-8B19-39C2F3FA0929@apple.com>
References: <4DE3F87A.5060502@globis.net> <4DE40821.9030205@gmail.com> <4DE420E2.6010207@globis.net> <4BC7CABA-D871-4B27-96BA-10A2F9D6D2B1@cisco.com>
To: 6MAN <ipv6@ietf.org>
X-Mailer: Apple Mail (2.1227)
X-Brightmail-Tracker: AAAAAA==
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 May 2011 16:24:34 -0000

On May 30, 2011, at 7:38 PM, Fred Baker wrote:
> 
> [...] IPv6 systems come, at least today, with SLAAC as the default. So there is a requirement to configure DHCPv6, at least from that perspective. That said, SLAAC ain't gonna happen in the absence of RAs, and you can disable RAs on the router. So if an interface comes up and no RA is forthcoming, I could imagine the thing probing with a DHCPv6 request. [...]

For what it's worth, the behavior of Apple's iOS 4.3 and later is straightforward.  If there is no RA, then there is no IPv6.  iOS 4.3 doesn't support manual IPv6 configuration, so automatic configuration is the only way to plumb it.  The DHCPv6 client only starts if the router indicates availability with O=1.  Remember when I was complaining that we needed RFC 6106 for the O=0 case?  Given that we have that, I don't see any benefit to starting the DHCPv6 client unless a router explicitly tells us to expect service.  No router?  No need for dynamic host configuration.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking