Open to contributions to pdns/contrib ?

Niall O'Reilly via Pdns-users <[email protected]> Tue, 11 Nov 2025 11:07:48 +0000
Newsgroups	gmane.network.dns.powerdns.user
Message-ID	<[email protected]>
--===============5662976227395070361==
Content-Type: multipart/alternative;
 boundary="=_MailMate_F09D215C-9513-4A62-AAD9-8A24344DF8BD_="


--=_MailMate_F09D215C-9513-4A62-AAD9-8A24344DF8BD_=
Content-Type: text/plain; format=flowed; markup=markdown
Content-Transfer-Encoding: quoted-printable

Hi.

I've noticed the *contrib* directory in the pdns repo,
and wonder whether:

   - contributed code is acceptable there from outside the project;
   - and, if so, what requirements you have, that a contributor
     would have to meet.

I'm asking because we have developed tooling in the [DEfO project][]
which implements the [zone factory behaviour][] described in the current
WKECH Internet Draft. We have Python, rust, and bash implementations
of this tooling.

As people may be aware, a TLS client can obtain configuration data for
Encrypted Client Hello (ECH) from an HTTPS RRset corresponding to the
URL origin of interest. From time to time, the endpoint server for this
origin updates the ECH configuration and may publish it at a well-known
URL, as documented in the WKECH ID. The zone factory should then update
the HTTPS RRset to match, so that an ECH-aware TLS client can always
find a current configuration.

I look forward to advice on whether and how we may contribute.

Thanks and best regards,

Niall O'Reilly
Tolerant Networks Ltd

---


[DEfO project]:
https://defo.ie/

[zone Factory behaviour]:
https://www.ietf.org/archive/id/draft-ietf-tls-wkech-09.html#name-zone-fa=
ctory-behaviour


--=_MailMate_F09D215C-9513-4A62-AAD9-8A24344DF8BD_=
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html>
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body><div style=3D"font-family: sans-serif;"><div class=3D"markdown" sty=
le=3D"white-space: normal;">
<p dir=3D"auto">Hi.</p>
<p dir=3D"auto">I've noticed the <em>contrib</em> directory in the pdns r=
epo,<br>
and wonder whether:</p>
<ul>
<li>contributed code is acceptable there from outside the project;</li>
<li>and, if so, what requirements you have, that a contributor<br>
would have to meet.</li>
</ul>
<p dir=3D"auto">I'm asking because we have developed tooling in the <a hr=
ef=3D"https://defo.ie/" style=3D"color: #3983C4;">DEfO project</a><br>
which implements the <a href=3D"https://www.ietf.org/archive/id/draft-iet=
f-tls-wkech-09.html#name-zone-factory-behaviour" style=3D"color: #3983C4;=
">zone factory behaviour</a> described in the current<br>
WKECH Internet Draft. We have Python, rust, and bash implementations<br>
of this tooling.</p>
<p dir=3D"auto">As people may be aware, a TLS client can obtain configura=
tion data for<br>
Encrypted Client Hello (ECH) from an HTTPS RRset corresponding to the<br>=

URL origin of interest. From time to time, the endpoint server for this<b=
r>
origin updates the ECH configuration and may publish it at a well-known<b=
r>
URL, as documented in the WKECH ID. The zone factory should then update<b=
r>
the HTTPS RRset to match, so that an ECH-aware TLS client can always<br>
find a current configuration.</p>
<p dir=3D"auto">I look forward to advice on whether and how we may contri=
bute.</p>
<p dir=3D"auto">Thanks and best regards,</p>
<p dir=3D"auto">Niall O'Reilly<br>
Tolerant Networks Ltd</p>
<hr style=3D"border: 0; height: 1px; background: #333; background-image: =
linear-gradient(to right, #ccc, #333, #ccc);">

</div>
</div>
</body>

</html>

--=_MailMate_F09D215C-9513-4A62-AAD9-8A24344DF8BD_=--

--===============5662976227395070361==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Pdns-users mailing list
[email protected]
https://mailman.powerdns.com/mailman/listinfo/pdns-users

--===============5662976227395070361==--