improvement we might expect.
If you have any feedback about these plans, please share your feedback
on this list.
Kind regards,
Romeo Zwart
Global Information Infrastructure Manager
RIPE NCC
x27;d like to follow up on this separately.
4/ Ripen.cc is a historical artifact. RIPE NCC is not currently using it
and we are not planning any future use. Releasing the domain is an
operational decision that we may take in the future.
Kind regards,
Romeo Zwart
RIPE NCC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi David,
On 14/11/17 17:56 , David Conrad wrote:
> Romeo,
>
> On Nov 17, 2014, at 7:49 AM, Romeo Zwart
> wrote:
>> 2/ The RIPE NCC has been publishing this key material out of band
>> for historical reasons. If there is a
Hi Jim,
On 14/11/18 10:54 , Jim Reid wrote:
> On 18 Nov 2014, at 08:22, Romeo Zwart wrote:
>
>> There was an explicit suggestion on the list about using ripe.int as a
>> 'lever' to get .int signed, hence my comment.
>
> I think you are mistaken Romeo. Peter as
Hi Randy, all,
Thanks for your questions.
On 15/03/12 03:40 , Randy Bush wrote:
> hi mirjam, romeo, et alia,
>
> this looke cool, and lighter weight. but a few questions as usual.
>> In the new model, the K-root hosted node will only peer with one
>> party, the local host, and the local host is
Hi Nick,
On 15/03/12 16:44 , Nick Hilliard wrote:
> Hi Romeo,
>
> thanks for the comprehensive replies, both here and on the blog.
And likewise, thanks for the discussion. No doubt more people on the
list share your questions. :)
> On 12/03/2015 09:29, Romeo Zwart wrote:
>
s for new K-root hosted nodes in mid-May.
There will be a separate announcement about this during RIPE 70, which
will have all details about the process for becoming a host.
Best regards,
Romeo Zwart
RIPE NCC
://labs.ripe.net/Members/romeo_zwart/new-architecture-for-k-root-local-nodes
As always, we welcome your feedback on these plans.
Best regards,
Romeo Zwart
RIPE NCC
ase let us know within two weeks if you have any comments or
feedback about this process.
Kind regards,
Romeo Zwart
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
iQIcBAEBCAAGBQJVkovvAAoJEKnY9vIUvfudPR8P/0PEnpvz435gKM941vSf7j3U
rqYcnBD54MQBiw8MaUA4Q+U
cc.com
ripe-ncc.net
ripencc.com
ripencc.net
ripencc.org
ripelabs.net
ripen.cc
ripe.int
ipv6roadshow.com
ipv6roadshow.net
ipv6roadshow.org
We welcome any and all feedback from the community.
Kind regards,
Romeo Zwart
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
iQIcBAEBCA
published on RIPE Labs:
https://labs.ripe.net/Members/romeo_zwart/update-on-k-root-expansion
Kind regards,
Romeo Zwart
these guidelines in the form of a new RIPE Document*,
of which a draft version is attached to this email.
We welcome any comments you may have on this document.
Kind regards,
Romeo Zwart
* Actually, an earlier version of this document has already been
published as a RIPE Document, but this was a
your support.
Kind regards,
Romeo Zwart
updated ripe-429 - DNSMON.pdf
Description: Adobe PDF document
ffectiveness of our response
further and report about this in the near future.
Kind regards,
Romeo Zwart
Hi Nico,
On 15/11/30 13:36 , Nico CARTRON wrote:
> Hello Romeo,
>
> On 30 November 2015 at 12:05:03, Romeo Zwart (romeo.zw...@ripe.net
> <mailto:romeo.zw...@ripe.net>) wrote:
>
>> Dear colleagues,
>>
>> Between about 07:00 and 09:15 UTC today multiple r
measures shortly before 06:00 UTC. The query load dropped to normal
levels at 06:10 UTC. Our post mortem report of yesterday's event will
include today's occurrence.
Kind regards,
Romeo Zwart
request.
We welcome your feedback. Please send any feedback you have to
directly, or alternatively send your comments to
the DNS WG mailing list.
Kind regards,
Romeo Zwart
Dear colleagues,
The root DNS operators have shared a report about the events observed at
the root on 30 November and 1 December. The report is available here:
http://root-servers.org/news/events-of-20151130.txt
As mentioned earlier on this list, the RIPE NCC will separately also
publish a repor
Validation and BCP-38 should
be used wherever possible to reduce the ability to abuse networks to
transmit spoofed source packets.
Kind regards,
Romeo Zwart
have here.
However, we might be able to present more information in a somewhat
generalised way that is still useful to the community. As said, we will
consider it.
Regards,
Romeo
> Thanks
>
> Brett
>
> --
> Brett Carr
> Senior DNS Engineer
> Nominet UK
>
>> On
Hi Jaap,
On 15/12/29 13:08 , Jaap Akkerhuis wrote:
> Romeo Zwart writes:
>
> > Yesterday, Monday 14 December 2015, RIPE NCC Authoritative DNS services
> > were functioning in a severely degraded state during parts of the day.
> >
> > etc.
>
> Accordin
Hi Jaap,
> On 29 dec. 2015, at 19:58, Jaap Akkerhuis wrote:
>
> Romeo Zwart writes:
>
>> Hi Jaap,
>>
>>> On 15/12/29 13:08 , Jaap Akkerhuis wrote:
>>> Romeo Zwart writes:
>>>
>>>> Yesterday, Monday 14 December 2015, RIPE NCC
ture is increasing. This seems
to be a more general trend that readers on this list are likely to be
aware of, but this may not be the case for the community at large. For
the RIPE NCC this means that we are investigating the options to
increase the capacity and robustness of our DNS services further.
Kind regards,
Romeo Zwart
such a
high volume that it is impacting other DNS services.
We are contacting the domain owners and are investigating mitigation
capabilities at the moment. We will inform you further when we have more
information.
Kind regards,
Romeo Zwart
services seems to be part of a more
general trend, which leads us to further investigate necessary
improvements to our DNS infrastructure.
Kind regards,
Romeo Zwart
On 16/01/14 13:08 , Romeo Zwart wrote:
> Dear colleagues,
>
> As of approximately 11:20 UTC this morning, Thursday 14 Januar
announcement, we are investigating potential
improvements to our infrastructure to increase our mitigation
capabilities in case of future incidents.
Kind regards,
Romeo Zwart
Dear colleagues,
On 30 November and 1 December 2015, we observed unusually large amounts
of traffic on the K-root DNS servers, which we announced here:
https://www.ripe.net/ripe/mail/archives/dns-wg/2015-November/003173.html
Some other root server operators observed similar traffic during the
sam
any comments that you have to:
or alternatively post to the list.
Kind regards,
Romeo Zwart
Dear Jim, dear colleagues,
Apologies for the delayed response.
On 16/04/07 17:25 , Jim Reid wrote:
>
>> On 7 Apr 2016, at 13:57, Romeo Zwart wrote:
>>
>> However, to be better prepared for extreme traffic floods, we will work
>> with an external party to pro
ODE values by the end of June.
We will update you via this list when we have more information and a
more accurate ETA for the fix.
Kind regards,
Romeo Zwart
Hi Shane,
On 16/05/26 14:33 , Shane Kerr wrote:
> Hello,
>
> Anand just mentioned at his presentation at RIPE 72 that the RIPE NCC
> is now implementing RIPE 663:
>
> https://www.ripe.net/publications/docs/ripe-663
>
> There were a couple of suggestions for tweaks to that:
>
> 1. Gaurab and I
5.txt
Kind regards,
Romeo Zwart
/news/announcements/request-for-trusted-party-to-provide-secondary-dns-services
Kind regards,
Romeo Zwart
RIPE NCC
Hi Jim,
Thanks for the quick response.
On 16/07/25 17:42 , Jim Reid wrote:
>
>> On 25 Jul 2016, at 15:59, Romeo Zwart wrote:
>>
>> The RIPE NCC requests proposals for service from a DNS service provider
>> in order to improve the resiliency of the RIPE NCC'
Hi Jim,
On 16/07/25 18:49 , Jim Reid wrote:
>
>> On 25 Jul 2016, at 16:56, Romeo Zwart wrote:
[..]
>> We have tried to make these requirements as clear as possible, including
>> distinctions between mandatory and optional elements, and we have
>> documented those i
than
expected. We now expect all of the (historic) RCODE values to be
corrected by the end of August.
As mentioned in the previous announcement, there is no impact on the
actual measurement data itself.
I apologise for any inconvenience caused.
Kind regards,
Romeo Zwart
- original
submitted
proposals. We look forward to working with Verisign in the future.
Regards,
Romeo Zwart
RIPE NCC
hear more questions and feedback from the working group.
Kind regards,
Romeo
On 16/10/18 10:54 , Romeo Zwart wrote:
> Dear colleagues,
>
> In July we published a Request for Proposals (RfP) for a trusted third
> party to provide secondary DNS services for the RIPE NCC's zones:
38 matches
Mail list logo
