IEEEtran.cls
This commit is contained in:
@@ -1,8 +1,13 @@
|
||||
%!TEX root = ../main.tex
|
||||
|
||||
In this section we describe two case study, TCP transport protocol and RAFT state machine replication protocol.
|
||||
\subsection{TCP}%
|
||||
\label{sub:TCP}
|
||||
|
||||
TCP (Transmission Control Protocol) is a transport-layer protocol designed to establish reliable, ordered communications between two peers. TCP is ubiquitous in today's internet, and therefore has seen ample formal verification efforts \cite{Cluzel_Georgiou_Moy_Zeller_2021, Smith_1997, Pacheco2022}, including using \promela and \spin \cite{Pacheco2022}. A previous version of \korg has been applied TCP in \cite{Pacheco2022, Hippel2022};
|
||||
in particular, we study our \korg extensions using the hand-written TCP \promela model from \cite{Pacheco2022}. Additionally, we construct a TCP \promela model referencing the set of TCP RFCs.
|
||||
TCP (Transmission Control Protocol) is a transport-layer protocol designed to establish reliable, ordered communications between two peers. TCP is ubiquitous in today's internet, and therefore has seen ample formal verification efforts \cite{Cluzel_Georgiou_Moy_Zeller_2021, Smith_1997, Pacheco2022}, including using \promela and \spin \cite{Pacheco2022}.
|
||||
%A previous version of \korg has been applied TCP in \cite{Pacheco2022, Hippel2022};
|
||||
%in particular, we study our \korg extensions using the hand-written TCP \promela model from \cite{Pacheco2022}.
|
||||
We construct a TCP \promela model referencing the set of TCP RFCs.
|
||||
For our analysis, we borrow the four LTL properties used in \cite{Pacheco2022}, as detailed below:
|
||||
%we study our \korg extensions using the \promela models from Pacheco et al., which includes a "gold" model whose underlying state machine is derived via an NLP-based algorithm applied to the SCTP RFC \cite{rfc9260} and a "canonical" model hand-written by domain experts \cite{Pacheco2022}.
|
||||
\[
|
||||
@@ -14,7 +19,7 @@ For our analysis, we borrow the four LTL properties used in \cite{Pacheco2022},
|
||||
\end{aligned}
|
||||
\]
|
||||
|
||||
We evaluated the our TCP \promela model and the hand-written TCP \promela model presented by \cite{Pacheco2022} against \korg's drop, replay, and reordering attacker models on a single uni-directional communication channel. The resulting breakdown of attacks discovered is shown in Figure \ref{res:tcp-table}.
|
||||
We evaluated the TCP \promela model against \korg's drop, replay, and reordering attacker models on a single uni-directional communication channel. The resulting breakdown of attacks discovered is shown in Figure \ref{res:tcp-table}.
|
||||
|
||||
%Evaluating the canonical TCP model using \korg led us to identify edge-cases in the connection establishment routine that weren't accounted for, leading us to construct a "revised" TCP model accounting for these missing edge cases.
|
||||
|
||||
@@ -22,16 +27,13 @@ We evaluated the our TCP \promela model and the hand-written TCP \promela model
|
||||
\begin{figure}[h!]
|
||||
\centering
|
||||
\begin{scriptsize}
|
||||
\begin{tabular}{|c|c|c|c|c|c|c|}
|
||||
\begin{tabular}{|c|c|c|c|}
|
||||
\hline
|
||||
& \multicolumn{2}{c|}{Drop Attacker} & \multicolumn{2}{c|}{Replay Attacker} & \multicolumn{2}{c|}{Reorder Attacker} \\
|
||||
\hline
|
||||
& Pacheco et al. & Ours & Pacheco et al. & Ours & Pacheco et al. & Ours \\
|
||||
\hline
|
||||
$\phi_1$ & & & & & & \\
|
||||
$\phi_2$ & x & x & x & x & & \\
|
||||
$\phi_3$ & & & & & & \\
|
||||
$\phi_4$ & & & & & x & \\
|
||||
& Drop Attacker & Replay Attacker & Reorder Attacker\\\hline
|
||||
$\phi_1$ & & &\\
|
||||
$\phi_2$ & x & x & \\
|
||||
$\phi_3$ & & &\\
|
||||
$\phi_4$ & & &\\
|
||||
\hline
|
||||
\end{tabular}
|
||||
\end{scriptsize}
|
||||
|
||||
Reference in New Issue
Block a user