IETF Logo Mail Archive

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

Timothy Winters <twinters@iol.unh.edu> Thu, 16 October 2014 15:01 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 94B531A1BC0 for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 08:01:56 -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 OrESoDaBorWW for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 08:01:53 -0700 (PDT)
Received: from mail-qg0-f99.google.com (mail-qg0-f99.google.com [209.85.192.99]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7186C1A1B2B for <dhcwg@ietf.org>; Thu, 16 Oct 2014 08:01:53 -0700 (PDT)
Received: by mail-qg0-f99.google.com with SMTP id e89so458847qgf.6 for <dhcwg@ietf.org>; Thu, 16 Oct 2014 08:01:52 -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=0e6/vwsuq26s8nf2zRdXHGgMYxmt+JlLNhJaKQ1vnh4=; b=GA2oV5Z5gYdLETKquHNX62yI9+kSBPChiSyH3nZngzC06xmPUvVcfyQeeIXMW9MM5e 0J8x0Kl+qzVYjK79d32JSbgJDM4+79CNM0tQfTXTocoQ7CLpoTy+IjA39ZkgCQfyX8c2 j2AHyYlMN5JErw66BZvavGLk/w0UzbdvogDA+z4JAVI0dlQZ15i2T95biiJO8i655xw7 mhr+YpVBeXCieNXi2rTBhQu96XcwcvvnUpRZ2iekaLGjSBForD/QHNvPVFujq3q+ZlQt XQHLeru9oQ+BlSrzE/me2DkKkxXgYnoXUe+IZlGLW0ut5F+TFeCh/67XbixPMFYxzQNz //XQ==
X-Gm-Message-State: ALoCoQkTsRQ689LABia0TtJqUpQ5JhpqpzU+OsO5zL5E6ywRo3Ubm7JKa+ljDZ9RxpOEn+njE6sof+lAXVF9UNzqvLuNrjwz1Q==
X-Received: by 10.140.39.11 with SMTP id u11mr2909756qgu.32.1413471712546; Thu, 16 Oct 2014 08:01:52 -0700 (PDT)
Received: from postal.iol.unh.edu ([2606:4100:3880:1234::84]) by mx.google.com with ESMTP id ig9sm4322313qcb.0.2014.10.16.08.01.51 for <multiple recipients>; Thu, 16 Oct 2014 08:01:52 -0700 (PDT)
X-Relaying-Domain: iol.unh.edu
Received: from optimus.iol.unh.edu (optimus.iol.unh.edu [132.177.118.15]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by postal.iol.unh.edu (Postfix) with ESMTPSA id B81F442DAF; Thu, 16 Oct 2014 11:01:51 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Timothy Winters <twinters@iol.unh.edu>
In-Reply-To: <E37A320E-203D-408D-87E2-9A1D04A906AE@fugue.com>
Date: Thu, 16 Oct 2014 11:01:49 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E0CD6B78-0BE6-438D-8B88-3C933C5624CB@iol.unh.edu>
References: <E37A320E-203D-408D-87E2-9A1D04A906AE@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/6efyoLLSC7QliFyayP0b0TUH7II
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:01:56 -0000

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

~Tim

On Oct 16, 2014, at 10:53 AM, Ted Lemon <mellon@fugue.com> wrote:

> When a new router is seen that sets the 'O' bit in its RA?   When a new prefix is seen, for the same router?   Only when a new link is detected?
> 
> I think that it should happen whenever a new prefix is seen for a router that's set the O bit, but Lorenzo Colitti thinks that a new prefix doesn't (and shouldn't) trigger a new Information Request.
> 
> Any thoughts about this?
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email