Re: [dns-privacy] OARC 43 - Call for Contribution

2024-04-17 Thread Rubens Kuhl
A distinct possibility is that it will happen in Santa Marta, Colombia, and will be colocated with LAC DNS Week and ICANN DNS Symposium. Previous editions websites: https://dnsweek.lat/en https://www.icann.org/ids Rubens > Em 17 de abr. de 2024, à(s) 12:00, Petr Špaček escreveu: > > The

Re: [dns-privacy] DTLS and OpenSSL Heartbleed bug

2014-04-13 Thread Rubens Kuhl
> Which is one of the reasons why I have been rather suspicious of the > 'just use DTLS' approach. Building on DTLS means importing all the > current and future complexity of TLS. > > That seems rather a lot of overhead when all we need to do at the DNS > layer is to take a message M, encrypt it u

Re: [dns-privacy] DTLS and OpenSSL Heartbleed bug

2014-04-13 Thread Rubens Kuhl
>> What about “Just use QUIC” ? It might have a better future with DNS than >> DTLS. > > QUIC is a replacement for TCP and it has a lot of merit for > applications where requests can be larger than a packet. > “is a replacement for” is a judgement of suitability. Over the years I heard some pe

Re: [dns-privacy] [DNSOP] Qname minimization IPR

2014-10-25 Thread Rubens Kuhl
> On Oct 25, 2014, at 2:03 PM, Phillip Hallam-Baker > wrote: > > The claims are broad, not specific to one field of use. > > But there isn't a patent yet and they may have been waiting to file after > grant. > > It is possible for someone other than the IPR holder to file but best if its >

Re: [dns-privacy] Verisign patent disclosure

2014-10-29 Thread Rubens Kuhl
> Em 29/10/2014, à(s) 16:21:000, Florian Weimer escreveu: > > * Brian Haberman: > >> https://datatracker.ietf.org/ipr/2469/ > > > > I don't think it's the only public discussion of this idea from that > time frame

Re: [dns-privacy] privacy respect... ICANN!!

2015-06-27 Thread Rubens Kuhl
> On Jun 27, 2015, at 9:42 AM, Hosnieh Rafiee wrote: > > Hello, > > I received this note from my domain registrar that ICANN is going to expose > the information of domain holder to whois requests. > > https://www.respectourprivacy.com/ > > Any comment? >From an IETF perspective, WHOIS only