Re: [dhcwg] DHCPv6 router option
Iljitsch van Beijnum <iljitsch@muada.com> Wed, 11 March 2009 17:16 UTC
Return-Path: <iljitsch@muada.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E10823A6885 for <dhcwg@core3.amsl.com>; Wed, 11 Mar 2009 10:16:51 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M3H-UH0ETB+G for <dhcwg@core3.amsl.com>; Wed, 11 Mar 2009 10:16:51 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 92D833A67D1 for <dhcwg@ietf.org>; Wed, 11 Mar 2009 10:16:50 -0700 (PDT)
Received: from [10.1.3.53] (wlap003.it.uc3m.es [163.117.139.45]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id n2BHGvsw086782 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 11 Mar 2009 18:16:57 +0100 (CET) (envelope-from iljitsch@muada.com)
Message-Id: <42E09C3E-1739-450E-8725-6873FFE660FB@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: sthaug@nethelp.no
In-Reply-To: <20090311.180625.41631909.sthaug@nethelp.no>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 11 Mar 2009 18:17:12 +0100
References: <E206991E-081C-4EFC-81AD-7559DCBDD864@muada.com> <20090311.175355.74747534.sthaug@nethelp.no> <6BD47EBD-E910-4C28-8921-20B9171B2710@muada.com> <20090311.180625.41631909.sthaug@nethelp.no>
X-Mailer: Apple Mail (2.930.3)
Cc: narten@us.ibm.com, dhcwg@ietf.org, rdroms@cisco.com
Subject: Re: [dhcwg] DHCPv6 router option
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Mar 2009 17:16:52 -0000
On 11 mrt 2009, at 18:06, sthaug@nethelp.no wrote: >> That's why I suggested having the DHCPv6 server tell the client WHICH >> of the available routers to select, but if and only if that router >> announces its presence. >> This way, pointing towards a black hole and hosts losing connectivity >> can't happen. > I am considerably more worried about a possible inconsistency between > the router and the DHCP server, than pointing the client towards a > black hole. It is not a problem for us today, and I see no reason why > it should be a bigger problem with IPv6. There are problems with DHCP in IPv4 all the time, especially for non- expert users. Having routers announce their own presence was one of the things that make IPv6 more reliable than IPv4. Throwing away that feature is completely unacceptable to me, so expect unrelenting opposition if that is what you intend to standardize here. However, the underlying need here is for administrators to make sure that the hosts send their traffic to the right router, and don't just randomly select any address for which there are RAs. This need is met by allowing the DHCPv6 server, if present, to impose the selection. So I don't see how this change takes away anything from the intended use. This just requires setting up the designated router to send out RAs (easy), without requiring making all other routers stop sending RAs (hard). Yes, this means that you still need to have RAs in your network. In an ideal world you would be able to get rid of those if you don't want them. But this isn't an ideal world, and RAs don't get in the way in any way that I can see, so having to live with this is more than worth having the additional robustness that hosts can still talk to the rest of the network if the DHCP server dies or someone fatfingers its config.
- [dhcwg] DHCPv6 router option Iljitsch van Beijnum
- Re: [dhcwg] DHCPv6 router option David W. Hankins
- Re: [dhcwg] DHCPv6 router option sthaug
- Re: [dhcwg] DHCPv6 router option Iljitsch van Beijnum
- Re: [dhcwg] DHCPv6 router option sthaug
- Re: [dhcwg] DHCPv6 router option David W. Hankins
- Re: [dhcwg] DHCPv6 router option Iljitsch van Beijnum
- Re: [dhcwg] DHCPv6 router option sthaug
- Re: [dhcwg] DHCPv6 router option Iljitsch van Beijnum
- Re: [dhcwg] DHCPv6 router option Ted Lemon
- Re: [dhcwg] DHCPv6 router option sthaug
- Re: [dhcwg] DHCPv6 router option David W. Hankins
- Re: [dhcwg] DHCPv6 router option Iljitsch van Beijnum
- Re: [dhcwg] DHCPv6 router option David W. Hankins
- Re: [dhcwg] DHCPv6 router option sthaug
- Re: [dhcwg] DHCPv6 router option Frank Sweetser
- Re: [dhcwg] DHCPv6 router option Ted Lemon
- Re: [dhcwg] DHCPv6 router option Ralph Droms
- Re: [dhcwg] DHCPv6 router option Mohacsi Janos
- Re: [dhcwg] DHCPv6 router option sthaug
- Re: [dhcwg] DHCPv6 router option Mohacsi Janos
- Re: [dhcwg] DHCPv6 router option sthaug
- Re: [dhcwg] DHCPv6 router option Ralph Droms
- Re: [dhcwg] DHCPv6 router option Bernie Volz (volz)
- Re: [dhcwg] DHCPv6 router option Templin, Fred L
- Re: [dhcwg] DHCPv6 router option Niall O'Reilly
- Re: [dhcwg] DHCPv6 router option Howard, Lee
- Re: [dhcwg] DHCPv6 router option David W. Hankins
- Re: [dhcwg] DHCPv6 router option David W. Hankins
- Re: [dhcwg] DHCPv6 router option Ralph Droms
- Re: [dhcwg] DHCPv6 router option David W. Hankins
- Re: [dhcwg] DHCPv6 router option JINMEI Tatuya / 神明達哉
- Re: [dhcwg] DHCPv6 router option Bernie Volz (volz)
- Re: [dhcwg] DHCPv6 router option Ralph Droms
- Re: [dhcwg] DHCPv6 router option Stig Venaas
- Re: [dhcwg] DHCPv6 router option Thomas Narten
- Re: [dhcwg] DHCPv6 router option Thomas Narten
- Re: [dhcwg] DHCPv6 router option Bernie Volz (volz)
- Re: [dhcwg] DHCPv6 router option Hemant Singh (shemant)
- Re: [dhcwg] DHCPv6 router option Hemant Singh (shemant)
- Re: [dhcwg] DHCPv6 router option Hemant Singh (shemant)
- Re: [dhcwg] DHCPv6 router option Olaf.Bonness
- Re: [dhcwg] DHCPv6 router option Olaf.Bonness
- Re: [dhcwg] DHCPv6 router option Ralph Droms
- Re: [dhcwg] DHCPv6 router option John Jason Brzozowski
- Re: [dhcwg] DHCPv6 router option John Jason Brzozowski
- Re: [dhcwg] DHCPv6 router option John Jason Brzozowski
- Re: [dhcwg] DHCPv6 router option Hemant Singh (shemant)
- Re: [dhcwg] DHCPv6 router option Frank Sweetser
- Re: [dhcwg] DHCPv6 router option John Jason Brzozowski
- Re: [dhcwg] DHCPv6 router option Hemant Singh (shemant)
- Re: [dhcwg] DHCPv6 router option Hemant Singh (shemant)
- Re: [dhcwg] DHCPv6 router option John Jason Brzozowski
- Re: [dhcwg] DHCPv6 router option John Jason Brzozowski
- Re: [dhcwg] DHCPv6 router option John Jason Brzozowski
- Re: [dhcwg] DHCPv6 router option Ralph Droms
- Re: [dhcwg] DHCPv6 router option Frank Sweetser
- Re: [dhcwg] DHCPv6 router option sthaug
- Re: [dhcwg] DHCPv6 router option Bernie Volz (volz)
- Re: [dhcwg] [Int-area] DHCPv6 router option Danny Mayer
- Re: [dhcwg] [Int-area] DHCPv6 router option David W. Hankins