IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 17 August 2015 17:43 UTC

Return-Path: <mcr@sandelman.ca>
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 928341ACDF0; Mon, 17 Aug 2015 10:43:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level:
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 viyoRY2sMqIk; Mon, 17 Aug 2015 10:43:29 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6457A1ACDD6; Mon, 17 Aug 2015 10:43:29 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 9B2E2200A3; Mon, 17 Aug 2015 14:01:43 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 96D9D63B10; Mon, 17 Aug 2015 13:43:28 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 78E3663AEC; Mon, 17 Aug 2015 13:43:28 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
to: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, dhcwg <dhcwg@ietf.org>, Homenet <homenet@ietf.org>
In-Reply-To: <25711.1439826616@sandelman.ca>
References: <87pp2oioik.wl-jch@pps.univ-paris-diderot.fr> <26135.1439773503@sandelman.ca> <87k2suw6w2.wl-jch@pps.univ-paris-diderot.fr> <25711.1439826616@sandelman.ca>
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Mon, 17 Aug 2015 13:43:28 -0400
Message-ID: <16923.1439833408@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/osTLQqxZbzmXtwC2E7jc837BIEw>
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 17:43:30 -0000

Michael Richardson <mcr+ietf@sandelman.ca> wrote:
    > 1) if the v4 prefix on the link is renumbered because a different router
    > won the election, then the existing router may still have connectivity,
    > and may still be willing to route packets.

    > (b) - there may be static IPs assigned, and there may even be port
    > forwards which are linked to that first router.

To clarify, there may be static leases, where DHCP has been told to give
out the same IPv4 to the same host consistently.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email