Re: RA "requires" DHCPv6 ?

Karl Auer <kauer@biplane.com.au> Sat, 31 March 2012 22:46 UTC

Return-Path: <kauer@biplane.com.au>
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 8A4F821F8617 for <ipv6@ietfa.amsl.com>; Sat, 31 Mar 2012 15:46:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_21=0.6]
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 cO8fMD6xDwgq for <ipv6@ietfa.amsl.com>; Sat, 31 Mar 2012 15:46:17 -0700 (PDT)
Received: from ipmail05.adl6.internode.on.net (unknown [IPv6:2001:44b8:8060:ff02:300:1:6:5]) by ietfa.amsl.com (Postfix) with ESMTP id 5D7C821F8596 for <ipv6@ietf.org>; Sat, 31 Mar 2012 15:46:15 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApMBABeId0+WZX+7/2dsb2JhbAANNYVUtkYBAQEDASNbCwsYKgICVwYTiAStHYlPkASBGAShF4dygUIH
Received: from eth4284.nsw.adsl.internode.on.net (HELO [192.168.1.202]) ([150.101.127.187]) by ipmail05.adl6.internode.on.net with ESMTP; 01 Apr 2012 08:16:04 +0930
Subject: Re: RA "requires" DHCPv6 ?
From: Karl Auer <kauer@biplane.com.au>
To: "ipv6@ietf.org" <ipv6@ietf.org>
In-Reply-To: <4F775E55.3050905@si6networks.com>
References: <1333148248.2624.187.camel@karl> <4F76F41C.1000904@si6networks.com> <1333199575.11943.16.camel@karl> <4F775E55.3050905@si6networks.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-TgQKnYcvMi2v+lh2+HID"
Date: Sun, 01 Apr 2012 08:46:02 +1000
Message-ID: <1333233962.11943.30.camel@karl>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3
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: Sat, 31 Mar 2012 22:46:18 -0000

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.

> -- 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.

> We were assuming the "regime" was controlling the local link. If they
> do, its up to them whether there are other routers on the link and/or
> whether RAs are allowed to flow on that link.

My question was unrelated to the discussion about "the regime". That's
why I started a new thread with a new subject line, and quoted only that
exact part of your statement where you said "requires you to do
DHCPv6". 

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 :-). 

Regards, K.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)
http://www.biplane.com.au/kauer

GPG fingerprint: AE1D 4868 6420 AD9A A698 5251 1699 7B78 4EEE 6017
Old fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687