Re: RA "requires" DHCPv6 ?

Fernando Gont <fgont@si6networks.com> Sun, 01 April 2012 12:57 UTC

Return-Path: <fgont@si6networks.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 CD73C21F962F for <ipv6@ietfa.amsl.com>; Sun, 1 Apr 2012 05:57:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ip0MjLjM-dPb for <ipv6@ietfa.amsl.com>; Sun, 1 Apr 2012 05:57:43 -0700 (PDT)
Received: from srv01.bbserve.nl (unknown [IPv6:2a02:27f8:1025:18::232]) by ietfa.amsl.com (Postfix) with ESMTP id 111F321F99C4 for <ipv6@ietf.org>; Sun, 1 Apr 2012 05:57:43 -0700 (PDT)
Received: from llagny-156-34-49-113.w217-128.abo.wanadoo.fr ([217.128.158.113] helo=[192.168.101.212]) by srv01.bbserve.nl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <fgont@si6networks.com>) id 1SEKLT-0000GN-4x; Sun, 01 Apr 2012 14:57:23 +0200
Message-ID: <4F7850B9.3050504@si6networks.com>
Date: Sun, 01 Apr 2012 14:57:29 +0200
From: Fernando Gont <fgont@si6networks.com>
Organization: SI6 Networks
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.28) Gecko/20120313 Thunderbird/3.1.20
MIME-Version: 1.0
To: Karl Auer <kauer@biplane.com.au>
Subject: Re: RA "requires" DHCPv6 ?
References: <1333148248.2624.187.camel@karl> <4F76F41C.1000904@si6networks.com> <1333199575.11943.16.camel@karl> <4F775E55.3050905@si6networks.com> <1333233962.11943.30.camel@karl>
In-Reply-To: <1333233962.11943.30.camel@karl>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
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: Sun, 01 Apr 2012 12:57:43 -0000

On 04/01/2012 12:46 AM, Karl Auer wrote:
> On Sat, 2012-03-31 at 21:43 +0200, Fernando Gont wrote:
>>> Or you could use one's statically assigned address. 
>>
>> Oh, yeah. And you could have opted to not send the RS in the first
>> place... and what? :-)
> 
> Um, I'm not sure why we're arguing. I'll still see unsolicited RAs at
> regular intervals, and I'll see RAs sent because of other hosts' RSes.
> Also, the RA contains lots of useful stuff even if I am not doing DHCPv6
> - for example if I want to do SLAAC I'll still be sending an RS. I don't
> think my question was stupid. I'm sorry you do.

I'm not saying that your question is stupid. I'm just saying that
regardless of whether there's a SHOULD/MUST in the RFCs regarding doing
DHCPv6, truth is that you should be prepared to do it, because if the
local router wants you to do DHCPv6, you essentially have no option.



>> -- However, particularly in the case in which the local router wants
>> you to use DHCPv6, they could easily block addresses that have not
>> been leased by the DHCPv6 server. SO, at the end of the day, you're at
>> its mercy.
> 
> Absolutely. The question was just whether or not a host was *required*
> "O" flags and do DHCPv6, not whether it would be practical or
> appropriate to do so.

Well, if you mean "required" in the sense of MUST, then probably not.
But if you mean "required" as in "do you need to do DHCPv6 to get
Internet connectivity?", then the answer is "Most likely, Yes".



> And I was not saying you were wrong - I was seeking clarification (from
> you or anyone), because IMHO it is not clear from the RFCs whether a
> host SHOULD or MUST honour the "M" and "O" flags (obviously it MAY :-). 

I should double-check that. But if the RA has the "M" bit, then at least
in that case you should do DHCPv6, even if the RFCs do not say so. If
there's no "MUST" or "SHOULD" for that (which I don't recall of the top
of my head), I guess that MUST/SHOULD has more to do with whether
there's a formal requirement for every host to implement DHCPv6, than
anything else. BUt then, as with the requirement to implement IPsec,
that's, IMO, mostly "words on paper".

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492