Re: [dhcwg] RFC3315 DECLINE definition

Ted Lemon <> Thu, 09 February 2017 15:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AAD06129AE8 for <>; Thu, 9 Feb 2017 07:40:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id pCx10uJYZBn8 for <>; Thu, 9 Feb 2017 07:40:36 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:400d:c0d::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6DF32129AD9 for <>; Thu, 9 Feb 2017 07:40:36 -0800 (PST)
Received: by with SMTP id w20so7286075qtb.1 for <>; Thu, 09 Feb 2017 07:40:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=DRCFCSfmP1UGT8FAFxDkIeIRZmriwBrLE3rYXOUT/gY=; b=i8oVqTlblPksHu86vFlBexZqtPV0opSrs98A+eUNKIwrQ+4OBl/Yufkuzcb4aFVpNe iHOr7qddOCG2zep1Q1ifJPNeJwIlVzU0QGCpFWuYuA3Y9BDOGh2a2z5wzoSLm1NgGi+L NMgMriqJtW3ZA9kfTcU7fsONkk60SrTenNqL0nV3CmBOAj+jAgzl+zvmI2ifKLHJDbVW qyLi8xb5Cc5+HxmkjBnrfO8URdE2TxSuGQd/kV9SkXGPumFJii5V3OT0nu9+cFEqP3s3 DavADXWRoT4FIDIQu30IfIGnj3Sm4VMjI+M933juIgl9OMFUzhMOOfv9OIzoxmsF1nF3 JzgA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=DRCFCSfmP1UGT8FAFxDkIeIRZmriwBrLE3rYXOUT/gY=; b=YOJlmQ//Eqith4QE0rHdstRPJvc6qzsDPRBEBSIwtWR+EjJNbPFsTYapr0GMnZZ3ki ylP6JBjE0Lf6GPg0bO2WKQh1OgCjFWlrAhW2lz6HwFminNA9biMkixl0NDo5A2nfbilu +w3ZmfgWHSfvz3l0fJMjIAs2MFuqN/CjA48GOK/M24VKx1BqQnfI+duQcFjZdopfRDl8 joWkPV0Z5DwCznQHpDzsLOTSQqQyt1Au4PRwUgVRfzgyuQc3RL4eOulHxHu3ZfZ4OPCK k+xXQ2FivvrAsZAfXoR5J1raweTrmThYnjtE6FLEUQsAEwq5VQAw4O3XzCdyGUn9t4qX +PkA==
X-Gm-Message-State: AMke39mgkhFw6srpRtbjCDvTXFBuR26W4ZloJnpdrhYVIFxLCWsixgEqwE9alei2zlL2xw==
X-Received: by with SMTP id c32mr3377462qta.70.1486654835511; Thu, 09 Feb 2017 07:40:35 -0800 (PST)
Received: from [] ( []) by with ESMTPSA id 140sm9401372qkj.19.2017. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Feb 2017 07:40:34 -0800 (PST)
From: Ted Lemon <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_49B6282A-4623-4533-9093-7ACF56B9CB96"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Thu, 9 Feb 2017 10:40:33 -0500
In-Reply-To: <>
To: "Mudric, Dusan (Dusan)" <>
References: <> <> <> <> <> <> <> <> <> <> <> <> <>
X-Mailer: Apple Mail (2.3259)
Archived-At: <>
Cc: dhcwg <>, "Bernie Volz \(volz\)" <>
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: Thu, 09 Feb 2017 15:40:37 -0000

On Feb 9, 2017, at 10:38 AM, Mudric, Dusan (Dusan) <> wrote:
> 1.       When DHCPv6 client starts it sends SOLICIT with IA option (without or with IPv6 address). The server sends ADVERTISE message offering IPv6 address(es). If the server offers IPv6 address(es) that client cannot use (e.g. an address with wrong semantics, a multicast address, a reserved address, … , a second address and the client can support only one address), the client should be able to respond to the server indicating which address it cannot use.

Let me stop you here.   This is a server misconfiguration.   The server is not artificially intelligent, so the client can't usefully tell the server it is misconfigured.   If the server is configured to hand out addresses with the wrong semantics, the solution is to fix the server, not complicate the protocol with a way for the client to tell the server something it can't do anything about.   This also needlessly complicates the client.

So why do you think this is a useful thing to do?   What non-hypothetical problem are you trying to solve here?