Re: [dhcwg] dhcpv6-24: Rapid Commit

Thomas Narten <> Thu, 09 May 2002 12:36 UTC

Received: from ( [] (may be forged)) by (8.9.1a/8.9.1a) with ESMTP id IAA17650 for <>; Thu, 9 May 2002 08:36:48 -0400 (EDT)
Received: (from daemon@localhost) by (8.9.1a/8.9.1) id IAA22355 for; Thu, 9 May 2002 08:36:57 -0400 (EDT)
Received: from (localhost []) by (8.9.1a/8.9.1) with ESMTP id IAA22302; Thu, 9 May 2002 08:34:57 -0400 (EDT)
Received: from (odin []) by (8.9.1a/8.9.1) with ESMTP id IAA22278 for <>; Thu, 9 May 2002 08:34:55 -0400 (EDT)
Received: from ( []) by (8.9.1a/8.9.1a) with ESMTP id IAA17552 for <>; Thu, 9 May 2002 08:34:46 -0400 (EDT)
Received: from (narten@localhost) by (8.11.6/8.11.6) with ESMTP id g49CXZl05388; Thu, 9 May 2002 08:33:35 -0400
Message-Id: <>
To: "Bernie Volz (EUD)" <>
Subject: Re: [dhcwg] dhcpv6-24: Rapid Commit
In-Reply-To: Message from "Bernie Volz (EUD)" <> of "Wed, 08 May 2002 11:03:41 CDT." <66F66129A77AD411B76200508B65AC69B4D3BB@EAMBUNT705>
Date: Thu, 09 May 2002 08:33:35 -0400
From: Thomas Narten <>
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <>

> - A client should be able to send this option always if it supports
>    it.

Why even have a special option requesting it? It would be nice if the
client always did the same thing, with the servers (and how they are
configured) determining whether the Rapid Commit is enabled and to be
used. It seems odd to me that the  *client* decides when it wants the
Rapid Commit. Isn't the appropriateness of tihs determined by the
envirnment to which the client connects?
> - A client that receives a Reply to a Solicit w/Rapid Commit *may*
>   use that Reply. If it doesn't, it should send a Release.

Why not a MUST, not SHOULD? If the client requests a Rapid Commit, it
should be prepared to implement it fully.

> - A client must use the normal Solicit procedure and await multiple
>   Reply messages (and Advertises). If the client receives a Reply
>   and doesn't use the information, it must send a Release. If the
>   client receives no Reply messages or doesn't choose to use any, it
>   should then follow the Advertise handling as normal.

> The option does have a value at least from the server / server
> administrator standpoint. An administrator could select not to allow
> this if there are multiple servers in the configuration. If there is
> a single server (or single set of primary/backup type servers), a
> server can be configured to allow Rapid Commit.

This indicates to me this should be under server control, not client
(as in the client decides whether to request it).


dhcwg mailing list