This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[dns-wg] DNS4EU?
- Previous message (by thread): [dns-wg] DNS4EU?
- Next message (by thread): [dns-wg] DNS4EU?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Erwin Hoffmann
feh at fehcom.de
Wed Nov 10 20:51:41 CET 2021
Salut Stephane, Am Mittwoch, dem 10.11.2021 um 16:34 +0100 schrieb Stephane Bortzmeyer: > On Wed, Nov 10, 2021 at 04:24:16PM +0100, > Stephane Bortzmeyer <bortzmeyer at nic.fr> wrote > a message of 13 lines which said: > > > The data is not sensitive (the DNS is public), not the fact that you > > request it. > > Correct sentence: the data is not sensitive (the DNS is public), but > the fact that you request it *is* sensitive. 100% Ack. Any attempts to provide privacy here is welcome. I've taken over the https://datatracker.ietf.org/doc/html/draft-dempsky-dnscurve-01 Dempsky/DNSCurve approach and be glad to provide a full solution now: https://www.fehcom.de/ipnet/djbdnscurve6.html Well, I do not expect to convince people to step into this solution immediately, but for restricted networks (let's say including IoT devices) it might be a useful alternative. This is a different scope perhaps and sharp edges certainly still exist. Though it is an almost zero cost alternative w.r.t. DNSSec. Regards. --eh. -- Dr. Erwin Hoffmann | www.fehcom.de
- Previous message (by thread): [dns-wg] DNS4EU?
- Next message (by thread): [dns-wg] DNS4EU?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]