On 20/10/2022 16:40, Nick Hilliard wrote:
Hank Nussbacher wrote on 20/10/2022 14:36:
https://trust.zscaler.com/zscloud.net/posts/12256
"We are aware of a major cable cut in the South of France that has
impacted major subsea cables with connectivity to Asia, Europe, US and
potentially
https://trust.zscaler.com/zscloud.net/posts/12256
"We are aware of a major cable cut in the South of France that has
impacted major subsea cables with connectivity to Asia, Europe, US and
potentially other parts of the world. As a result of the cable cut,
customers may see packet loss and or
Notice of Inquiry into Secure Internet Routing (i.e. what is wrong with
BGP :-))
https://docs.fcc.gov/public/attachments/FCC-22-18A1.pdf
-Hank
--
To unsubscribe from this mailing list, get a password reminder, or change your
subscription options, please visit:
On 18/02/2022 10:54, Nathalie Trenaman wrote:
Hi Nick,
On 18 Feb 2022, at 09:53, Nick Hilliard wrote:
Hank Nussbacher wrote on 18/02/2022 07:39:
We are working with large network providers and registrars on mitigating the
vulnerabilities in RPKI deployments.
Has anyone from the RIPE NCC
https://www.linkedin.com/posts/shulman_inter-domain-routing-connects-the-different-activity-6899635463775145984-BaQe
"We found that the current RPKI deployments are vulnerable - cyber
criminals can disable RPKI in any network in the Internet. We evaluated
such RPKI disabling attacks in the
On 16/02/2022 19:46, Gert Doering wrote:
Hi,
On Wed, Feb 16, 2022 at 05:01:25PM +0100, Ties de Kock wrote:
This afternoon, between 13:00 UTC and 14:10 UTC rrdp.ripe.net was unavailable.
[..]
Thanks for this great postmortem writeup, and for being open about
what happened, and how things
On 13/07/2021 16:33, Nathalie Trenaman wrote:
Hi Hank,
Op 13 jul. 2021, om 14:46 heeft Hank Nussbacher <mailto:h...@interall.co.il>> het volgende geschreven:
On 13/07/2021 14:08, Job Snijders via routing-wg wrote:
On Tue, Jul 13, 2021 at 05:25:11AM +0200, Daniel Karrenberg wrote:
On 13/07/2021 14:08, Job Snijders via routing-wg wrote:
On Tue, Jul 13, 2021 at 05:25:11AM +0200, Daniel Karrenberg wrote:
It might also be that the operational community has chosen other fora to
discuss because this working group is not working.
What a strange thing to say. Of course there
RIS
table dumps, together with origin AS and number of peers that passed the
routes to RIS. You could filter on the latter to restrict the view to
"widely seen" routes.
There's an equivalent one for IPv6.
-- Rene
On 7/5/21 1:41 PM, Hank Nussbacher wrote:
On 04/07/2021 17:49, Clemens M
for one peer though (e.g. using bgpreader).
Cheers,
Clemens
On 04.07.21 16:41, Hank Nussbacher wrote:
> Apologies for previous HTML email:
>
>
> I am aware of the MRT files available from RIPE:
>
>
https://www.ripe.net/analyse/internet-measurements/routing-information-servic
Apologies for previous HTML email:
I am aware of the MRT files available from RIPE:
https://www.ripe.net/analyse/internet-measurements/routing-information-service-ris/ris-raw-data
I am aware of the MRT files available from routeviews:
http://archive.routeviews.org/
What I am looking for is an
I am aware of the MRT files available from RIPE:
https://www.ripe.net/analyse/internet-measurements/routing-information-service-ris/ris-raw-data
I am aware of the MRT files available from routeviews:
http://archive.routeviews.org/
What I am looking for is an
On 21/03/2021 13:43, Lukas Tribus wrote:
Hello,
On Sat, 20 Mar 2021 at 20:06, Hank Nussbacher wrote:
I am not sure it is possible, but I would love to see some centralized
site where all dropped ROV invalids would appear. This way I can see if
I have a problem as well as if someone tried
On 19/03/2021 10:06, Ben Maddison via routing-wg wrote:
Hi Nathalie,
On 03/18, Nathalie Trenaman wrote:
Dear Colleagues, Working Group,
As discussed previously in this mailing list, some community members
expressed that they would like to see the RIPE NCC perform Route
Origin Validation on
On 17/02/2021 17:58, Job Snijders via
routing-wg wrote:
+1.
-Hank
Dear RIPE NCC,
On Wed, Feb 17, 2021 at 11:28:32AM +0100, Nathalie Trenaman wrote:
The multitude of RPKI service impacting events as a
On 20/02/2020 16:39, Petrit Hasani wrote:
I support this proposal. Should have been done a long time ago.
Regards,
Hank
Dear colleagues,
Policy proposal 2019-08, "RPKI ROAs for Unallocated and Unassigned RIPE NCC Address
Space", is now in the Review Phase.
The goal of the proposal is to
On 28/12/2019 21:09, Randy Bush wrote:
How these things slip through is when paperwork gets submitted that is
incorrect and falsified with fake signatures.
and the ncc has a job advert out to hire even more lawyers (no blame;
it's a mess). can ripe keep from becoming arin?
randy
It would
On 31/10/2019 16:28, Petrit Hasani wrote:
Totally support this proposal.
-Hank
Dear colleagues,
A new RIPE Policy proposal, 2019-08, "RPKI ROAs for Unallocated and Unassigned RIPE
NCC Address Space"
is now available for discussion.
This proposal aims to instructs the RIPE NCC to create
On 28/05/2018 14:53, Job Snijders wrote:
> On Thu, May 17, 2018 at 07:16:34PM +0300, Hank Nussbacher wrote:
>> On 17/05/2018 17:02, Benno Overeinder wrote:
>>
>> Maybe I'm missing it when reading the website and the BCOP but where
>> does it state to *not *allow /25 or m
On 17/05/2018 17:02, Benno Overeinder wrote:
Maybe I'm missing it when reading the website and the BCOP but where
does it state to *not *allow /25 or more specifics?
The entire reason for MANRS is to prevent route hijacking. An ISP that
allows /25s or /26s to be leaked will easily circumvent all
While giving a routing lecture today someone asked me
"Why was eBGP assigned an administrative distance of 20 which is better
than OSPF's administrative distance of 110. What was the logic behind
that decision?"
I was unable to think of an answer.
Ideas?
Thanks,
Hank
I know this is *routing* WG but I figured I would try anyway.
I have seen numerous comparisons and RIPE presentations on performance
issues of BIRD vs Quagga vs FRR.
I am looking for the same thing of switch software.
Has anyone done a feature comparison between:
http://openvswitch.org/
On 02/06/2016 22:43, Job Snijders wrote:
> Dear fellow network operators,
>
> In July 2016, NTT Communications' Global IP Network AS2914 will deploy a
> new routing policy to block Bogon ASNs from its view of the default-free
> zone. This notification is provided as a courtesy to the network
>
Dear revelers,
I am looking for a program or website that can take a list of sorted,
overlapping prefixes and can reduce it to the most CIDRized format.
Example:
5.28.128.0/18
5.28.128.0/20
5.28.128.0/21
5.28.128.0/22
5.28.132.0/23
5.28.136.0/21
5.28.136.0/22
5.29.64.0/18
5.29.64.0/20
24 matches
Mail list logo
