[dhcwg] dhcpv6-24: response to a release message
Thomas Narten <narten@us.ibm.com> Wed, 08 May 2002 15:14 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 LAA11897 for <dhcwg-archive@odin.ietf.org>; Wed, 8 May 2002 11:14:51 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id LAA05346 for dhcwg-archive@odin.ietf.org; Wed, 8 May 2002 11:14:59 -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 LAA05107; Wed, 8 May 2002 11:13:36 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA05078 for <dhcwg@optimus.ietf.org>; Wed, 8 May 2002 11:13:34 -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 LAA11715 for <dhcwg@ietf.org>; Wed, 8 May 2002 11:13:24 -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 g48FDX64050178 for <dhcwg@ietf.org>; Wed, 8 May 2002 11:13:33 -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 g48FDXQ101290 for <dhcwg@ietf.org>; Wed, 8 May 2002 11:13:33 -0400
Received: from rotala.raleigh.ibm.com (narten@localhost) by rotala.raleigh.ibm.com (8.11.6/8.11.6) with ESMTP id g48FDvW19387 for <dhcwg@ietf.org>; Wed, 8 May 2002 11:13:57 -0400
Message-Id: <200205081513.g48FDvW19387@rotala.raleigh.ibm.com>
To: dhcwg@ietf.org
Date: Wed, 08 May 2002 11:13:57 -0400
From: Thomas Narten <narten@us.ibm.com>
Subject: [dhcwg] dhcpv6-24: response to a release message
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
> After all the addresses have been processed, the server generates a > Reply message and includes a Status Code option with value Success > and a Server Identifier option with the server's DUID. The server > MUST NOT include any other options in the Reply message. > If the server cannot find a binding for the client, the server > sends a Reply message that includes a Status Code option with value > NoBinding. I can't quite tell what is supposed to happen if there are mixture of successes and failures. If there are failures, are multiple IAs returned indicating which ones were released successfully and which were not? The text seems to say no, no other options other than that Status Code. Seems like a simple success/fail for *all* the addresses will leave the client unsure of what state the various addresses are in. Thomas _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] dhcpv6-24: response to a release message Thomas Narten
- RE: [dhcwg] dhcpv6-24: response to a release mess… Bernie Volz (EUD)