> On 25 May 2016, at 19:13, Roland van Rijswijk - Deij
> wrote:
Hi Roland,
> I've already run a number of benchmark tests with TLS-enabled Unbound,
That’s interesting, we are doing the same although there still are a couple of
features that are missing from Unbound for it to be fully perform
> On 25 May 2016, at 16:19, Jerry Lundström wrote:
>
> Hi Sara,
>
> On 05/25/16 11:11, Sara Dickinson wrote:
>> A number of organisations have expressed interest in running such a DNS
>> Privacy enabled server and we would like to start a discussion in the RIPE
>> community to see if there is
On Wed, May 25, 2016 at 12:32:06PM +0200,
Amreesh Phokeer wrote
a message of 110 lines which said:
> Just want to know, how far or how close YETI is as compared to the Open
> Root [1] project
No comparison possible.
1) Yeti is an actual service, running. You can use it now if you want,
you c
Hi Sara,
On 05/25/16 11:11, Sara Dickinson wrote:
> A number of organisations have expressed interest in running such a DNS
> Privacy enabled server and we would like to start a discussion in the RIPE
> community to see if there is similar interest from within this group. We
> would very much l
>> Actually Jim, first comes the poll of the community to see if this
>> fits,
> Well Joao the community already seems to be heading in that direction.
> YMMV.
i am waiting for eugene kashpureff and dianne boling to uncloak in the
meeting
randy
On 5/25/16 12:32 PM, Amreesh Phokeer wrote:
> Hi all,
>
> Just want to know, how far or how close YETI is as compared to the Open
> Root [1] project
from what I read on their website, I think they cannot be compared.
think of yeti as a testbed for research and experiments: the project
should ter
Hi all,
Just want to know, how far or how close YETI is as compared to the Open
Root [1] project
which I know for a fact that the RIR community quite vehemently voiced
against it.
--
Amreesh
[1] http://www.open-root.eu/
On Tue, May 24, 2016 at 2:41 PM, Shane Kerr
wrote:
> Dear DNS folks,
>
On Wed, May 25, 2016 at 11:50:15AM +0200, João Damas wrote:
> Actually Jim, first comes the poll of the community to see if this fits,
> later comes what you suggest, if the community decides to ask the RIPE NCC to
> look into it, or have we become the Ministry of IP?
this member of the communit
> On 25 May 2016, at 10:50, João Damas wrote:
>
> Actually Jim, first comes the poll of the community to see if this fits,
Well Joao the community already seems to be heading in that direction. YMMV.
That said, it would be helpful for the WG to have a better understanding of the
requirements
This.
On 25 May 2016 11:50:15 CEST, "João Damas" wrote:
>Actually Jim, first comes the poll of the community to see if this
>fits, later comes what you suggest,
--
Sent from Kaiten Mail. Please excuse my brevity.
Actually Jim, first comes the poll of the community to see if this fits, later
comes what you suggest, if the community decides to ask the RIPE NCC to look
into it, or have we become the Ministry of IP?
Joao
> On 25 May 2016, at 09:55, Jim Reid wrote:
>
>
>> On 24 May 2016, at 13:41, Shane K
Hi All,
As you will probably know RFC7858 "Specification for DNS over Transport Layer
Security (TLS)” was recently published as a result of work in the IETF DPRIVE
working group.
Reference implementations of this Standard (and associated supporting features
such as those specified in RFC7766
On 5/24/16 2:41 PM, Shane Kerr wrote:
> Please let us know what you think about this idea. I'm happy to answer
> any questions about the project or what it would mean for the RIPE NCC
> to run a Yeti root server.
hi,
as a participant to YETI project I warmly encourage RIPE NCC (as well as
the RIP
> On 24 May 2016, at 13:41, Shane Kerr wrote:
>
> Please let us know what you think about this idea.
Before we take this idea forward, could someone please suggest metrics and
milestones that could be used to assess the success or failure of this
activity? For bonus points, it would be good
Dear colleagues,
It has been brought to our attention that the RCODE values resulting
from DNS measurements in RIPE Atlas are sometimes presented incorrectly
in DNSMON and DomainMon. We are currently examining this in more detail,
but preliminary investigations suggest that this is due to a bug in
15 matches
Mail list logo
