IETF Logo Mail Archive

[dhcwg] What triggers a DHCP Information Request?

Ted Lemon <mellon@fugue.com> Thu, 16 October 2014 14:53 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 7FC9D1A1B01 for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 07:53:09 -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 rBSKMsnTo5m0 for <dhcwg@ietfa.amsl.com>; Thu, 16 Oct 2014 07:53:08 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 7DE701A1B9B for <dhcwg@ietf.org>; Thu, 16 Oct 2014 07:53:08 -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 E477A238050E for <dhcwg@ietf.org>; Thu, 16 Oct 2014 10:53:07 -0400 (EDT)
From: Ted Lemon <mellon@fugue.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <E37A320E-203D-408D-87E2-9A1D04A906AE@fugue.com>
Date: Thu, 16 Oct 2014 09:53:06 -0500
To: dhcwg <dhcwg@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/g_QGDQ2DRJrcHjhcDBLXf_4kiPs
Subject: [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 14:53:09 -0000

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?

v2.23.0 | Report a Bug | By Email