IETF Logo Mail Archive

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

Timothy Winters <twinters@iol.unh.edu> Mon, 20 October 2014 13:06 UTC

Return-Path: <twinters@iol.unh.edu>
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 1F8101A8729 for <dhcwg@ietfa.amsl.com>; Mon, 20 Oct 2014 06:06:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 M0OY7PI1MnEq for <dhcwg@ietfa.amsl.com>; Mon, 20 Oct 2014 06:06:21 -0700 (PDT)
Received: from mail-qg0-f98.google.com (mail-qg0-f98.google.com [209.85.192.98]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C8AE1A8722 for <dhcwg@ietf.org>; Mon, 20 Oct 2014 06:06:20 -0700 (PDT)
Received: by mail-qg0-f98.google.com with SMTP id q108so651056qgd.5 for <dhcwg@ietf.org>; Mon, 20 Oct 2014 06:06:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=dkwSFjKUEnuTxDtCw+8G/3adtE6gsOfhZMiNKRzxKQw=; b=hz0n3JB2hsb40dTSVewShEQ0czbapBhlw1LquczgIKZCCrqMA9TmcW38UhO1BdmJv9 THjp13/Zr0eU4FWLLriYyqQmGo/0fvGchq9bz2hrD7RzRmX69Lcu5AaejBfx4U8m+tbv ZRcN8jqq+Ki9BrTf622hJhTHAoSAsaVtTdIhrBX4c9kXSkWDqc/Sd3ybHf4tQisMCWXr uMFwsCUXvGTQqFI136KYIPBbtgG+l8y2b/oWCARVnyC+EIXXzbA9vUmy3NmBAou6Dfw8 ap33DdZHuAlqQR1D00whIC5tnbC0cf0DzsRPiQlTnR+FAJhR3ArF/+TdEHM/mDV0Vw0e dq9w==
X-Gm-Message-State: ALoCoQmWwPgpbFhSk3RRYnMGrP3DdZJ9OcgYNcVNCRvZUVw25r5Eu9pcbX07iEa42Wzv3jE+mFA8XJG4qFUAV++GqooEPxqhcg==
X-Received: by 10.202.1.80 with SMTP id 77mr21908131oib.31.1413810379342; Mon, 20 Oct 2014 06:06:19 -0700 (PDT)
Received: from postal.iol.unh.edu ([2606:4100:3880:1234::84]) by mx.google.com with ESMTP id n4sm1687060qcq.2.2014.10.20.06.06.18 for <multiple recipients>; Mon, 20 Oct 2014 06:06:19 -0700 (PDT)
X-Relaying-Domain: iol.unh.edu
Received: from [IPv6:2606:4100:3880:1270:5829:fcbc:d0c2:d8] (unknown [IPv6:2606:4100:3880:1270:5829:fcbc:d0c2:d8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by postal.iol.unh.edu (Postfix) with ESMTPSA id 7723E441E9; Mon, 20 Oct 2014 09:06:18 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
From: Timothy Winters <twinters@iol.unh.edu>
In-Reply-To: <4CBB1B29-B5BA-46B2-8E16-6CE22D0396A7@thehobsons.co.uk>
Date: Mon, 20 Oct 2014 09:06:18 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <909EC0B6-9EBE-45E3-8CD2-1AC7C1FA0984@iol.unh.edu>
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>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.1990.1)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/PakR9Zln_QFqjB4-fJ4hZgcTsYY
Cc: dhcwg <dhcwg@ietf.org>, "Bernie Volz (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:06:24 -0000

Hi Ted,
	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.

~Tim

> On Oct 20, 2014, at 3:03 AM, Simon Hobson <dhcp1@thehobsons.co.uk> wrote:
> 
> 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.
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email