[dhcwg] dhcpv6-24: comparing client parameters and server state
Thomas Narten <narten@us.ibm.com> Wed, 08 May 2002 15:08 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11178 for <dhcwg-archive@odin.ietf.org>; Wed, 8 May 2002 11:08:56 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id LAA04302 for dhcwg-archive@odin.ietf.org; Wed, 8 May 2002 11:09:04 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA04032; Wed, 8 May 2002 11:07:00 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA04009 for <dhcwg@optimus.ietf.org>; Wed, 8 May 2002 11:06:59 -0400 (EDT)
Received: from e21.nc.us.ibm.com (e21.nc.us.ibm.com [32.97.136.227]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11008 for <dhcwg@ietf.org>; Wed, 8 May 2002 11:06:50 -0400 (EDT)
Received: from southrelay02.raleigh.ibm.com (southrelay02.raleigh.us.ibm.com [9.37.3.209]) by e21.nc.us.ibm.com (8.12.2/8.12.2) with ESMTP id g48F6w64022682 for <dhcwg@ietf.org>; Wed, 8 May 2002 11:06:58 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.9.21]) by southrelay02.raleigh.ibm.com (8.11.1m3/NCO/VER6.1) with ESMTP id g48F6wQ87058 for <dhcwg@ietf.org>; Wed, 8 May 2002 11:06:58 -0400
Received: from rotala.raleigh.ibm.com (narten@localhost) by rotala.raleigh.ibm.com (8.11.6/8.11.6) with ESMTP id g48F7M819234 for <dhcwg@ietf.org>; Wed, 8 May 2002 11:07:22 -0400
Message-Id: <200205081507.g48F7M819234@rotala.raleigh.ibm.com>
To: dhcwg@ietf.org
Date: Wed, 08 May 2002 11:07:22 -0400
From: Thomas Narten <narten@us.ibm.com>
Subject: [dhcwg] dhcpv6-24: comparing client parameters and server state
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org
> 18.2.2. Receipt of Confirm messages > > When the server receives a Confirm message, the client is requesting > confirmation that the configuration information it will use is valid. > The server locates the binding for that client and compares the > information in the Confirm message from the client to the information > associated with that client. Couple of thoughts. The document doesn't really define "compare". Do the Lifetimes have to be equal? I would assume not, but this is not stated... Also, does the Confirm include *only* IAs that were assigned by that server? If not, seems like confirm will fail (i.e, if a client has IAs from different servers). Is the text clear on this? (I don't bthink the text says only include IAs allocated from the server to which the confirm is being sent.) Some clarifying text would seem to be needed here. Thomas _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] dhcpv6-24: comparing client parameters an… Thomas Narten
- Re: [dhcwg] dhcpv6-24: comparing client parameter… Ralph Droms
- [dhcwg] dhcpv6-24: comparing client parameters an… Ralph Droms
- [dhcwg] dhcpv6-24: comparing client parameters an… Ralph Droms