IETF Logo Mail Archive

Re: [dhcwg] What triggers a DHCP Information Request?

Simon Hobson <linux@thehobsons.co.uk> Mon, 20 October 2014 08:17 UTC

Return-Path: <linux@thehobsons.co.uk>
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 5D6C21A6FE3 for <dhcwg@ietfa.amsl.com>; Mon, 20 Oct 2014 01:17:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 iHTlmgVywIP0 for <dhcwg@ietfa.amsl.com>; Mon, 20 Oct 2014 01:17:06 -0700 (PDT)
Received: from patsy.thehobsons.co.uk (patsy.thehobsons.co.uk [IPv6:2001:470:1f09:baa::21]) by ietfa.amsl.com (Postfix) with ESMTP id E68721A6FDD for <dhcwg@ietf.org>; Mon, 20 Oct 2014 01:17:04 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at patsy.thehobsons.co.uk
Received: from [192.168.1.22] (lan.furness.net [77.233.151.255]) by patsy.thehobsons.co.uk (Postfix) with ESMTPSA id 958D71BC3E for <dhcwg@ietf.org>; Mon, 20 Oct 2014 08:16:57 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Simon Hobson <linux@thehobsons.co.uk>
In-Reply-To: <EMEW3|a3691409b8087136c49e06c0136831b0q9INpX03tjc|ecs.soton.ac.uk|BB407C45-6E7F-40FC-A034-E5B8FCF85650@ecs.soton.ac.uk>
Date: Mon, 20 Oct 2014 09:17:01 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <AD83BDF3-C35B-4DCD-B32D-090BFF4AB149@thehobsons.co.uk>
References: <E37A320E-203D-408D-87E2-9A1D04A906AE@fugue.com> <E0CD6B78-0BE6-438D-8B88-3C933C5624CB@iol.unh.edu> <9E2CCAA8-3045-4AEC-85BB-37E9C20BB026@fugue.com> <489D13FBFA9B3E41812EA89F188F018E1B6D107D@xmb-rcd-x04.cisco.com> <BB407C45-6E7F-40FC-A034-E5B8FCF85650@ecs.soton.ac.uk> <EMEW3|a3691409b8087136c49e06c0136831b0q9INpX03tjc|ecs.soton.ac.uk|BB407C45-6E7F-40FC-A034-E5B8FCF85650@ecs.soton.ac.uk>
To: dhcwg <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/g2FbwZkslvNx8T5aXmWc5dn9iqw
Subject: Re: [dhcwg] What triggers a DHCP Information Request?
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: <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: Mon, 20 Oct 2014 08:17:09 -0000

Tim Chown <tjc@ecs.soton.ac.uk> wrote:

> I agree with Bernie and Ted. 
> 
> It would make sense to fetch at the very least a (potentially) new policy table when a new prefix is advertised. 

+1
IMO if the RAs being advertised change - whether that's a router appearing or disappearing, or a prefix being added or deleted - then that means "something" has changed on the network. When that happens it makes sense to ask what the current config for our devide looks like - even if the current config is "no change" from the previous config.

v2.23.0 | Report a Bug | By Email