Re: [dns-wg] retaining ripe.int

2015-06-30 Thread Job Snijders
On Jun 30, 2015 8:16 PM, "Jim Reid" wrote: > > On 30 Jun 2015, at 18:53, Peter Koch wrote: > > > This is probably an exception for the lack of a drop catching risk, > > but keeping the domain to maintain a stake in the INT domain > > might be OK. > > That is a remarkably bad idea. The .int domain

Re: [dns-wg] PowerDNS vulnerabilities

2017-11-28 Thread Job Snijders
On Tue, Nov 28, 2017 at 11:46:18AM +, Jim Reid wrote: > I’m surprised this hasn’t been mentioned on these lists yet. I hope most people track security bulletins through other distribution channels than dns-wg@ripe.net. Most DNS vendors have dedicated 'announce' mailing lists for this type of i

Re: [dns-wg] Deletion of ns-v6.ripe.net

2018-04-24 Thread Job Snijders
On Tue, Apr 24, 2018 at 03:48:39PM +0100, Jim Reid wrote: > > On 24 Apr 2018, at 15:33, Anand Buddhdev wrote: > > > > Now that the name ns-v6.ripe.net is no longer in use by anyone, we > > are going to delete it from the ripe.net zone. > > Anand, could you clarify what you mean by “no longer in

Re: [dns-wg] NCC reverse delegation criteria

2019-06-10 Thread Job Snijders
Dear all, Is a complete overview of the current policy / testing process available? To further this discussion - I think it would be good to have a full understanding of what the current state of affairs is in this context. Kind regards, Job