Re: [dhcwg] I-D Action: draft-ietf-dhc-problem-statement-of-mredhcpv6-08.txt

Bernie Volz <> Fri, 19 November 2021 14:01 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 51A013A093D; Fri, 19 Nov 2021 06:01:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, 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 Ew5vhkqZEx0h; Fri, 19 Nov 2021 06:01:27 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::829]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 40A713A0878; Fri, 19 Nov 2021 06:01:24 -0800 (PST)
Received: by with SMTP id v22so9493589qtx.8; Fri, 19 Nov 2021 06:01:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=content-transfer-encoding:from:mime-version:subject:message-id:date :cc:to; bh=kIOCEjbybjbFZphHSQuncNs0Lsf88XH9NwEQrBEI36k=; b=TB2Vo5ao7MiPI6pYg3gMHhlqa8KpEvmP3wIuq/9R4uEy9Oci4FsuTMD62aVy0u68gh 5+xxOEjdJh84dYGNhBYP3SNEAxXcoALQENHtp14n5gkSlYjHJJd+MVTXqER8vwj2orAV CxHD4p0V1wVoulsrbusUdORuCuoGQ0px2A9FBbFLykPeFWjymP9ydmf+a+twlDZUToBp U8ClVarjVYtgNLF4nuy3FaSUNXpVcdFD6obunKPLr/0FJ/KRN1JbX81skQ9I8olHh3/T a6k2LMT78CNoynHVVUx2yMil++tdM6zDQ8J1sDxXKfS2+/sFcwNMxytV4larNfr0T6Xt R/Fg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:message-id:date:cc:to; bh=kIOCEjbybjbFZphHSQuncNs0Lsf88XH9NwEQrBEI36k=; b=ahYdMuGjHbSxjpQkO3YFJKPC1AoCNOhFTmte9f9aAqhv2qsLJ+SS3UTTBL+z2+hb06 eLbAmFt7pRPsmD5xyKSrvvvsHbRubtayPujUXSSax/e+DKPQ9l2Eu1F9jY5plmiojdby zv2KVfHGtIkZkZuEAl1sNbB1+dq0K4f2qgidKCZe6+UL8Xk3ycwlv+zjuAzOkk1vXxEz AZ9Z79QZAMRywzief5dbnf9iWXT9CGNierjrmxnkr+Qy37kOjRBP4Pz0PJpcvVLxHUC1 /WhIpFKJiPfd+XWBJlFVt90kDCdbqlh7140l1FHx4FHs7ehU90MBXTn8qyiQ+Bgm/GhW 7c5A==
X-Gm-Message-State: AOAM530kn97oSqRrBFfVKrb4B6CXlvSpAVzPSBlIOknzhIzWnuCTHf87 sFntE0SwJcu9t8FwcbGzKHgrNr7/AQ==
X-Google-Smtp-Source: ABdhPJw1WXbPs5kKvykaUrHCqdOrRx3hDhr9gzO1s6VzmtJTAguo6hh3c2jhKGj3S1WBJmldt0m02w==
X-Received: by 2002:a05:622a:19a7:: with SMTP id u39mr6210035qtc.286.1637330481955; Fri, 19 Nov 2021 06:01:21 -0800 (PST)
Received: from ( []) by with ESMTPSA id de13sm1671271qkb.81.2021. (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 19 Nov 2021 06:01:21 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Bernie Volz <>
Mime-Version: 1.0 (1.0)
Message-Id: <>
Date: Fri, 19 Nov 2021 09:01:20 -0500
To: Alan DeKok <>,,
X-Mailer: iPad Mail (19B74)
Archived-At: <>
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-problem-statement-of-mredhcpv6-08.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Dynamic Host Configuration <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 19 Nov 2021 14:01:32 -0000

This document is dead as a WG item. As chairs, we cannot stop the authors from posting new versions, though we have requested that they not do so.

- Bernie Volz, dhc wg co-chair

> On Nov 19, 2021, at 8:53 AM, Alan DeKok <> wrote:
>   I have some minor feedback.
> The link to the "ISC kea hook developers guide" is to a page which says "access denied".  Perhaps this link is better:
> Section 1 says in part:
>  Some people would suggest that administrators modify the open-source
>  DHCPv6 server to solve their problems.  However, it takes
>  considerable time to understand the code of an open-source DHCPv6
>  server, not to mention the time-consuming task of debugging errors,
> This comment isn't true of all Open Source DHCP servers.  Some can be extended only via source code changes.  Others such as FreeRADIUS support a policy language.  The policy language permits basic if / then / else functions, and option creation, validation, modification, and deletion.
> Similar text to this is in Section 3.2 and in Section 5.2.  It should clarify that there are many ways of writing policies for DHCP servers, not all of which require source code changes.
> Section 4.2.2 has good discussion of options.  But it stops at a problem statement, without addressing implementations (as is done in the other sections).  For example, Kea supports custom options:
> FreeRADIUS has similar support.  The benefit of this approach is that the software can be updated to support new options via a configuration file.  And it does not require any source code changes. 
> This practice means that a particular release of a DHCP server implementation can have a lifetime much longer than would otherwise be possible.
> Alan DeKok.
> _______________________________________________
> dhcwg mailing list