IETF Logo Mail Archive

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

Ted Lemon <mellon@fugue.com> Mon, 20 October 2014 13:31 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 C49521A87AF for <dhcwg@ietfa.amsl.com>; Mon, 20 Oct 2014 06:31: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 xkVHCVaDrTLG for <dhcwg@ietfa.amsl.com>; Mon, 20 Oct 2014 06:31:40 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 561A41A87D2 for <dhcwg@ietf.org>; Mon, 20 Oct 2014 06:27:39 -0700 (PDT)
Received: from [10.0.10.40] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id 2578E2380481; Mon, 20 Oct 2014 09:27:37 -0400 (EDT)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <909EC0B6-9EBE-45E3-8CD2-1AC7C1FA0984@iol.unh.edu>
Date: Mon, 20 Oct 2014 09:27:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F50C0AF9-10E0-47EC-9EF1-4115FAA25325@fugue.com>
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> <4CBB1B29-B5BA-46B2-8E16-6CE22D0396A7@thehobsons.co.uk> <909EC0B6-9EBE-45E3-8CD2-1AC7C1FA0984@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/VdOxc0H_Xt1aZ8iQlh6sePwjuZ0
Cc: dhcwg <dhcwg@ietf.org>, Bernie Volz <volz@cisco.com>
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 13:31:42 -0000

On Oct 20, 2014, at 9:06 AM, Timothy Winters <twinters@iol.unh.edu> wrote:
> 	After some quick research here at the UNH-IOL, we don’t have any OS that will send a DHCPv6 Information Request when a new prefix arrives in an RA.   It would seem that most implementations only trigger it when the O flag changes.   There might be some other cases that send DHCPv6 Information Request depending on what parameters change, Router lifetime for example.   Let me know if you want us to look into other things.

Wow, thanks for the quick response!   I guess we have our work cut out for us!

v2.23.0 | Report a Bug | By Email