I’m a little confused. I thought the concern was about decrypting
intentionally mis-routed traffic, not a suggestion that ROV uses encryption…
Regards,
-drc
> On Oct 30, 2021, at 5:57 PM, J. Hellenthal via NANOG wrote:
>
> He answered it completely. "You" worried about interception of RPKI
He answered it completely. "You" worried about interception of RPKI exchange
over the wire are failing to see that there is nothing there important to
decrypt because the encryption in the transmission is not there !
And yet you've failed to even follow up to his question... "What's your point
Hi Matthew,
Quantum computing exists as POCs, IBM being one of those advertising them
and announced to extend their project. There are others on the market,
Amazon advertised quantum computing as a service back in 2019:
I am very grateful for the help I received from several people (mostly off
list, which is great to avoid spamming the list).
In particular, +Giotsas, Vasileios , introduced
by Joe Provo, provided a wonderful RIPE resource which provides convenient
API to data from (at least) UCEprotect and
(this is an answer to Matthew but also with a question to all NANOGers, see
below, under `is this true?')
Matthew, thanks for your feedback on our paper - always welcome - although
the email I sent wasn't about ROV++ but on our need for historical data on
blacklisted prefixes. (our use is not
On Fri, 29 Oct 2021, 15:55 A Crisan, wrote:
> Hi Matthew,
> I was reading the above exchange, and I do have a question linked to your
> last affirmation. To give you some context, the last 2021 ENISA report seem
> to suggest that internet traffic is "casually registered" by X actors to
> apply
Hi Matthew,
What you seem to have failed to understand is that most traffic hijacks on
> the internet are not malicious in nature, they are "fat finger" incidents
> where someone has accidentally announced something they did not intend to,
> either because of faulty software (the infamous "BGP
Hi,
On Fri, 29 Oct 2021 at 00:48, Amir Herzberg wrote:
> Hi NANOGers, for our research on ROV (and ROV++, our extension, NDSS'21),
> we need access to historical data of blacklisted prefixes (due to spam,
> DDoS, other), as well as suspect-hijacks list (beyond BGPstream which we
> already
Hi NANOGers, for our research on ROV (and ROV++, our extension, NDSS'21),
we need access to historical data of blacklisted prefixes (due to spam,
DDoS, other), as well as suspect-hijacks list (beyond BGPstream which we
already have).
Basically we want to measure if the overlap (and non-overlap)
9 matches
Mail list logo
