D4
/
architecture
mirror of https://github.com/D4-project/architecture
2
0
Fork 0
Code Issues Releases Wiki Activity

chg: [ipasn-bgpranking] typo fixed

master
Alexandre Dulaunoy 2019-03-29 06:31:58 +01:00
parent 1e525f3e93
commit e44b7a228d
No known key found for this signature in database
GPG Key ID: 09E2CD4944E6CBCD
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/support_tools/ipasn_bgpanking/ipasn_bgpranking.tex
View File

@ -29,7 +29,7 @@
\begin{frame}
\frametitle{IPASN History - Problem statement}
\begin{itemize}
\item Rapidely figuring out the owner of a specific IP address is a common problem
\item Rapidly figuring out the owner of a specific IP address is a common problem
\item Resolving that relationship for a massive amount of IP addresses at scale is a medium hard problem
\item Doing so for a specific day in the past is somewhat more difficult
\item Comparing the resolution across sources is pretty painful
@ -53,7 +53,7 @@
\frametitle{IPASN History - (short) History}
\begin{itemize}
\item D4 Project (co-funded under INEA CEF EU program) started - 1st November 2018
\item A PoC of IPASN History was initially developped in 2012-2013 and only supported IPv4
\item A PoC of IPASN History was initially developed in 2012-2013 and only supported IPv4
\item Was used in production for BGP Ranking over many years
\item The current version was released initially in November 2018 after a complete rewrite
\item The support of multiple data source was added in March 2019
@ -76,8 +76,8 @@
\begin{itemize}
\item There are 10th of thousands of actors on the internet owning IP Addresses
\item Many of them own a very small amount of IP addresses (/24)
\item They change nem, purposes and owner relatively often
\item Their security practicies are poor, if they ever exist
\item They change name, purposes and owner relatively often
\item Their security practises are poor, if they ever exist
\item They are plain malicious and have no legitimate purpose
\item One way to find these malicious providers is to map them to lists of known malicious IPs
\end{itemize}
@ -87,7 +87,7 @@
\begin{frame}
\frametitle{BGP Ranking - Objective}
\begin{itemize}
\item Daily ranking of internet profiders by maliciousness
\item Daily ranking of internet providers by maliciousness
\item History of said rankings over a long period of time
\item Fire and forget model
\item Simple REST API
@ -99,7 +99,7 @@
\frametitle{BGP Ranking - (short) History}
\begin{itemize}
\item D4 Project (co-funded under INEA CEF EU program) started - 1st November 2018
\item A PoC of BGP Ranking was initially developped in the early 2010s and only supported IPv4
\item A PoC of BGP Ranking was initially developed in the early 2010s and only supported IPv4
\item The current version was released initially in November 2018 after a complete rewrite
\item The integration with IPASN HIstory was finalized in February 2019
\end{itemize}