IETF Logo Mail Archive

Re: [dhcwg] [homenet] What to do when we lose DHCPv4 election?

Mikael Abrahamsson <swmike@swm.pp.se> Mon, 17 August 2015 11:54 UTC

Return-Path: <swmike@swm.pp.se>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70D691B2CE2; Mon, 17 Aug 2015 04:54:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.961
X-Spam-Level:
X-Spam-Status: No, score=-3.961 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o2SlLjkU76xs; Mon, 17 Aug 2015 04:54:03 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ECCFE1B2CDF; Mon, 17 Aug 2015 04:54:02 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 020FCA1; Mon, 17 Aug 2015 13:54:00 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1439812441; bh=Efidk0XH1OtqndjLszReKeAQyHCD5Kehkk8WzRDOwio=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=zBNXRK6aSn3ZpWRxD2Lc153RpEOcc3ikVa0R1xpdmcgHxRxp60SZ29LXqjh8qAeyS pX8Z+u7wFGFThXUK9w6Q/+M7kEpGBhH9Tjk49rXjGeAdbKFTf0UPynK2zE4IMh5h0c FZRFJfC6w26iELfOVKl2eN6cuGsz9lXFDfFo8G3o=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id EF8D09F; Mon, 17 Aug 2015 13:54:00 +0200 (CEST)
Date: Mon, 17 Aug 2015 13:54:00 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Steven Barth <cyrus@openwrt.org>
In-Reply-To: <55D1C99A.20203@openwrt.org>
Message-ID: <alpine.DEB.2.02.1508171348170.13227@uplift.swm.pp.se>
References: <87pp2oioik.wl-jch@pps.univ-paris-diderot.fr> <26135.1439773503@sandelman.ca> <87k2suw6w2.wl-jch@pps.univ-paris-diderot.fr> <55D1C99A.20203@openwrt.org>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/oTtbU_3CayWwfmHPUiCXYcsA6Hw>
Cc: dhcwg <dhcwg@ietf.org>, Homenet <homenet@ietf.org>
Subject: Re: [dhcwg] [homenet] What to do when we lose DHCPv4 election?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Mon, 17 Aug 2015 11:54:09 -0000

On Mon, 17 Aug 2015, Steven Barth wrote:

> At first glance all 3 behaviors seem sensible, while 2 and 3 look more preferable.
> However I do not particularly remember all the implications. In any case I'm
> thinking of adding "Routers which seize to be elected DHCP
>        servers SHOULD - when applicable - invalidate remaining existing
>        bindings in order to trigger client reconfiguration."
> as a generic recommendation.

Yes, I think this makes the most sense as well.  The only other way of 
solving this would be for all routers capable of becoming HNCP Designated 
Router for the Common Link would keep all kinds of state between them (for 
instance DHCP leases), and while this would be nice, I see this as a huge 
complication that is probably not worth doing?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

v2.23.0 | Report a Bug | By Email