From owner-freebsd-net@freebsd.org Fri Oct 11 19:42:02 2019 Return-Path: Delivered-To: freebsd-net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0D6E0130AD6 for ; Fri, 11 Oct 2019 19:42:02 +0000 (UTC) (envelope-from hrs@allbsd.org) Received: from mail.allbsd.org (mx.allbsd.org [IPv6:2001:2f0:104:e001::41]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature ECDSA (P-384) client-digest SHA384) (Client CN "mail.allbsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46qdd15L1jz3ybx; Fri, 11 Oct 2019 19:41:56 +0000 (UTC) (envelope-from hrs@allbsd.org) Received: from mail-d.allbsd.org ([IPv6:2409:11:a740:4700:58:65ff:fe00:b0b]) (authenticated bits=56) by mail.allbsd.org (8.15.2/8.15.2) with ESMTPSA id x9BJfWi1038860 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=OK) (Client CN "/CN=mail-d.allbsd.org", Issuer "/C=US/O=Let's+20Encrypt/CN=Let's+20Encrypt+20Authority+20X3"); Sat, 12 Oct 2019 04:41:43 +0900 (JST) (envelope-from hrs@allbsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=allbsd.org; s=20190220; t=1570822911; bh=jNNsO3AwPPTTanAojI/Ybkg0twGF990dBSH/rIiDhuQ=; h=Date:To:Cc:From:In-Reply-To:References; b=gWzpQkckvXdR5IMYg/vrp22dWZr2BVjZxNMZHQeajhRy7FkOhMJTc68W3RGc5JuEd LbBQpfIZg8Sz+Y0HY185QRreyPX62r2OzpYhGWQKJm7/f4rG6HuW0/OTKBBgMq9Qlf x+IYBG426Ub5nrE88MgVCnJn48NIilrKS+Xb6uiI= Received: from alph.d.allbsd.org ([IPv6:2409:11:a740:4700:16:ceff:fe34:2700]) by mail-d.allbsd.org (8.15.2/8.15.2) with ESMTPS id x9BJfRmH078721 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 12 Oct 2019 04:41:27 +0900 (JST) (envelope-from hrs@allbsd.org) Received: from localhost (localhost [[UNIX: localhost]]) (authenticated bits=0) by alph.d.allbsd.org (8.15.2/8.15.2) with ESMTPA id x9BJfPSD078718; Sat, 12 Oct 2019 04:41:27 +0900 (JST) (envelope-from hrs@allbsd.org) Date: Sat, 12 Oct 2019 04:40:34 +0900 (JST) Message-Id: <20191012.044034.19725945241254130.hrs@allbsd.org> To: woodsb02@gmail.com Cc: hrs@freebsd.org, freebsd-net@freebsd.org, driesm.michiels@gmail.com, roy@marples.name Subject: Re: DHCPv6 client in base From: Hiroki Sato In-Reply-To: References: <001e01d50b49$176104d0$46230e70$@gmail.com> <20190516.032012.517661495892269813.hrs@allbsd.org> X-Old-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-PGPkey-fingerprint: 6C0D 2353 27CF 80C7 901E FDD2 DBB0 7DC6 6F1F 737F X-Mailer: Mew version 6.8 on Emacs 26.2 Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha512; boundary="--Security_Multipart(Sat_Oct_12_04_40_34_2019_118)--" Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (mail.allbsd.org [IPv6:2001:2f0:104:e001:0:0:0:41]); Sat, 12 Oct 2019 04:41:51 +0900 (JST) X-Rspamd-Queue-Id: 46qdd15L1jz3ybx X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=allbsd.org header.s=20190220 header.b=gWzpQkck; dmarc=none; spf=pass (mx1.freebsd.org: domain of hrs@allbsd.org designates 2001:2f0:104:e001::41 as permitted sender) smtp.mailfrom=hrs@allbsd.org X-Spamd-Result: default: False [-5.39 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[allbsd.org:s=20190220]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MV_CASE(0.50)[]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; TO_DN_NONE(0.00)[]; RCPT_COUNT_FIVE(0.00)[5]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[allbsd.org:+]; MID_CONTAINS_FROM(1.00)[]; SIGNED_PGP(-2.00)[]; FREEMAIL_TO(0.00)[gmail.com]; DMARC_NA(0.00)[allbsd.org]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:7514, ipnet:2001:2f0::/32, country:JP]; IP_SCORE(-2.29)[ip: (-9.09), ipnet: 2001:2f0::/32(-4.32), asn: 7514(1.98), country: JP(-0.01)] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2019 19:42:02 -0000 ----Security_Multipart(Sat_Oct_12_04_40_34_2019_118)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Ben Woods wrote in : wo> On Thu, 16 May 2019 at 2:25 am, Hiroki Sato wrote: wo> wo> > wrote wo> > in <001e01d50b49$176104d0$46230e70$@gmail.com>: wo> > wo> > dr> Has anyone ever thought or considered integrating an IPv6 DHCP client wo> > in wo> > dr> base? wo> > wo> > I have a plan to import wide-dhcp6 into the base system because it is wo> > simple enough. wo> > wo> > dr> net/dhcp6 isn't really maintained anymore from the KAME days it works wo> > for wo> > dr> basic functionality but fails when a more complex config is required. wo> > wo> > More specifics about the complex configuration? wo> > wo> > -- Hiroki wo> wo> wo> I would like to discuss whether dhcpcd is a better option to import into wo> FreeBSD base, rather than wide-dhcp6. wo> wo> dhcpcd has the following benefits that I can see: wo> - Actively maintained [1] (wide-dhcp6 seems to be stale for 11 years?) wo> - Used in NetBSD and DragonflyBSD (code sharing amongst the BSDs will wo> facilitate collective progress and lesson sharing). Roy, the upstream wo> maintainer, has committer on both NetBSD and DragonFlyBSD. wo> - more feature rich [2] wo> wo> [1] https://roy.marples.name/projects/dhcpcd/history wo> [2] https://roy.marples.name/projects/dhcpcd/features wo> wo> hrs - what are your thoughts? I do not have a strong objection on dhcpcd (I am using it on some of my FreeBSD boxes actually) but let me explain the reason why I chose wide-dhcp as the candidate. That is because it is a small, functional DHCPv6-only implementation. I am planning to rewrite it to add the missing bits and adjust it for a tighter integration with kernel, ifconfig, rtsold, rtadvd, and sandboxing with Capsicum. I feel dhcpcd (or others) is too big for that purpose. IMHO, the directions of further developments of IPv6 functionality on FreeBSD, NetBSD (dhcpcd), OpenBSD (slaacd + others), and DragonFly BSD (dhcpcd) have already been diverged. For RFC 7217 I already have an in-kernel implementation (not committed yet), and I am also working on SeND (RFC 3971, not directly related to DHCPv6 though). My goal is to integrate these small implementations into the base system and make them possible to work together. So for DHCPv6, I think an implementation of only DHCPv6 is the best. If people want a more feature-rich implementation or the same one on other systems, they can still use dhcpcd or ISC's dhclient even after the import. Of course this assumes that wide-dhcp works to some degree. If it does not, importing it to the base system does not make sense. I have used it in various scenarios for a long time such as RA + O flag on native IPv6 over Ethernet, DHCPv6-PD over PPPoE/L2TP, and others which are complex enough, and understand what works and what is missing (poor DUID format support, for example). The popular way to use DHCPv6 is IA_PD, and wide-dhcp works well with it. So I have a question. What is missing feature in wide-dhcp which you are concerned about? I know some, but it has most of the basic functionality of DHCPv6 and I think it is enough as a minimal implementation for the base system. My primary reason is that it is just for DHCPv6 as mentioned earlier and I believe it is maintainable in the base system. I would like to know other people's opinion if there is something critical. -- Hiroki ----Security_Multipart(Sat_Oct_12_04_40_34_2019_118)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iMkEABMKAC0WIQRsDSNTJ8+Ax5Ae/dLbsH3Gbx9zfwUCXaDasg8caHJzQGFsbGJz ZC5vcmcACgkQ27B9xm8fc38VOAIJAV+eXE+6+KHPDmomJiBlt6UwhKPil17OMtsw Yhgrah7wDiJGO3tE+VQ3S5g4eQELtIXYRH039EICYdin5sA56DBKAgkBQewl7wlJ jdkhsKwmghGCeiEut4LooOrZLwFZQ8ZZsb58P+VaUC2H0mWpZMh4MXadF3Kf+RV6 mAo3JJGozzg0Nwc= =BLbD -----END PGP SIGNATURE----- ----Security_Multipart(Sat_Oct_12_04_40_34_2019_118)----