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

Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> Mon, 17 August 2015 10:23 UTC

Return-Path: <jch@pps.univ-paris-diderot.fr>
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 EAC481A903F; Mon, 17 Aug 2015 03:23:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level:
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=no
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 eIAPHf5ihNX4; Mon, 17 Aug 2015 03:23:27 -0700 (PDT)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F29A11A903C; Mon, 17 Aug 2015 03:23:26 -0700 (PDT)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56228) with ESMTP id t7HANOCa029969; Mon, 17 Aug 2015 12:23:24 +0200
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 86F7561FAB; Mon, 17 Aug 2015 12:23:25 +0200 (CEST)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id TmGqJz3qzZyX; Mon, 17 Aug 2015 12:23:24 +0200 (CEST)
Received: from ijon.pps.univ-paris-diderot.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id A853B61FA3; Mon, 17 Aug 2015 12:23:24 +0200 (CEST)
Date: Mon, 17 Aug 2015 12:23:25 +0200
Message-ID: <87k2suw6w2.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Michael Richardson <mcr+ietf@sandelman.ca>
In-Reply-To: <26135.1439773503@sandelman.ca>
References: <87pp2oioik.wl-jch@pps.univ-paris-diderot.fr> <26135.1439773503@sandelman.ca>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Mon, 17 Aug 2015 12:23:24 +0200 (CEST)
X-Miltered: at korolev with ID 55D1B61C.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 55D1B61C.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 55D1B61C.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/6p0VDTTvo2ePIIU1zIx1L1GIwZ4>
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 10:23:28 -0000

>> When a Homenet router was previously acting as DHCPv4 server for
>> a link, and subsequently loses an election, should it:

>> 1. remain silent;
>> 2. remain silent in response to DHCPDISCOVER, but NAK any DHCPREQUEST; or
>> 3. NAK both DHCPDISCOVER and DHCPREQUEST?

> I think that #2 is probably correct

Thanks.  What after a renumbering event and the addresses that the client
requests are no longer onlink?  I'd like a precise reference, if that's
okay.

> 1) do Homenet-aware DHCPv4 servers pick the same rfc1918 address spaces to
>    give out?

Not necessarily -- if there are multiple prefixes assigned to the link,
the spec doesn't say which prefix is used by each server.  (Shncpd uses
them all, which I'm not sure is a good idea.)  Electing a single DHCPv4
server for each link works around the issue.

> 2) if a DHCPv4 server previously had given out leases, and the lease is still
>    valid, then I think that it ought to ACK a DHCP renew.

What if the prefix got renumbered, and the address is no longer being routed?