IETF Logo Mail Archive

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

Ted Lemon <mellon@fugue.com> Thu, 16 October 2014 15:25 UTC

Return-Path: <mellon@fugue.com>
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 3D88C1A1BF5 for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 08:25:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 4g0hEts_uceV for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 08:25:38 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 660ED1A1C02 for <dhcwg@ietf.org>; Thu, 16 Oct 2014 08:25:37 -0700 (PDT)
Received: from [192.168.1.63] (c-71-201-198-58.hsd1.il.comcast.net [71.201.198.58]) by toccata.fugue.com (Postfix) with ESMTPSA id EA11F238050E; Thu, 16 Oct 2014 11:25:35 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <E0CD6B78-0BE6-438D-8B88-3C933C5624CB@iol.unh.edu>
Date: Thu, 16 Oct 2014 10:25:34 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <9E2CCAA8-3045-4AEC-85BB-37E9C20BB026@fugue.com>
References: <E37A320E-203D-408D-87E2-9A1D04A906AE@fugue.com> <E0CD6B78-0BE6-438D-8B88-3C933C5624CB@iol.unh.edu>
To: Timothy Winters <twinters@iol.unh.edu>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/E0Uh51s8r4LF1kuqmxV-EhMdr1M
Cc: dhcwg <dhcwg@ietf.org>
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: Thu, 16 Oct 2014 15:25:42 -0000

On Oct 16, 2014, at 10:01 AM, Timothy Winters <twinters@iol.unh.edu> wrote:
> 	 At the IOL I'm not aware of many DHCPv6 clients that trigger the DHCPv6 Information Request based on addresses being added.  I could see the case of when you lose all Global address (including ULA) a device might send one, but I would be surprised if they send when when new prefixes are found.   I can look closer into this to see what triggers it, give me a couple of days and I'll report back. 

That seems broken, because you probably want to refresh the source address selection policy table whenever you see a new prefix.

v2.23.0 | Report a Bug | By Email