Re: [dhcwg] RFC3315 DECLINE definition

"Bernie Volz (volz)" <> Wed, 08 February 2017 21:57 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2EFD41295FD for <>; Wed, 8 Feb 2017 13:57:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Status: No, score=-14.523 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id lv6r_wCxndef for <>; Wed, 8 Feb 2017 13:57:26 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id F36FF128874 for <>; Wed, 8 Feb 2017 13:57:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=1346; q=dns/txt; s=iport; t=1486591045; x=1487800645; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=fmvlvxrGt+Vi3Cu6qLGeSYubygEr+BuW4qjjGeqed0M=; b=PxC9/2+IuhYqFfy7CfyzL8TWlZKdZcI+8UVXY28dMUMWNvg5SjEoWVhn XQmXKat5aW3IHNV6JGc5BWKSZg6V200UX8lxp564GILojYmhg513b9uWC c+S4jf1XYlAlHcK6HJ2fU/4FTm0GE5pautCxDS6OD6whu1FWnWboiiPYO E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.35,348,1484006400"; d="scan'208";a="206416469"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Feb 2017 21:57:04 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id v18Lv4J6022137 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 8 Feb 2017 21:57:04 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 8 Feb 2017 15:57:03 -0600
Received: from ([]) by ([]) with mapi id 15.00.1210.000; Wed, 8 Feb 2017 15:57:03 -0600
From: "Bernie Volz (volz)" <>
To: "Mudric, Dusan (Dusan)" <>, =?iso-2022-jp?B?GyRCP0BMQEMjOkgbKEI=?= <>, Lishan Li <>
Thread-Topic: RFC3315 DECLINE definition
Thread-Index: AdKCVGJ7VzCckicuS8ujStD5DUW3kQAAXlQA
Date: Wed, 8 Feb 2017 21:57:03 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <>
Cc: dhcwg <>
Subject: Re: [dhcwg] RFC3315 DECLINE definition
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 08 Feb 2017 21:57:27 -0000


DECLINE is used after a REPLY, not after an ADVERTISE.

A client has not been assigned an address until it receives the REPLY (at which point it does DAD and may send a DECLINE).

There is no mechanism for a client to indicate to a server "I don't want your Advertised address(es)", except by not proceeding to send a REQUEST.

The server may have held the address "reserved" for a short period of time, but does that really matter? IPv6 addresses are not in short supply.

- Bernie

-----Original Message-----
From: dhcwg [] On Behalf Of Mudric, Dusan (Dusan)
Sent: Wednesday, February 08, 2017 4:47 PM
To: 神明達哉 <>jp>; Lishan Li <>
Cc: dhcwg <>
Subject: [dhcwg] RFC3315 DECLINE definition


Can DECLINE definition be extended beyond the DAD usage? I think DECLINE should be used every time DHCPV6 client decides not to assign the offered address, for any reason, not just the address is duplicate. When receiving DECLINE, DHCPV6 server should be able to immediately make the same address available in the address pool for the other clients.


dhcwg mailing list