From 5cf7f77cc4e5e6cf06e4264eb8f116880508f628 Mon Sep 17 00:00:00 2001
From: jaseg <git@jaseg.net>
Date: Sun, 12 Jan 2020 18:24:00 +0100
Subject: tex: add some sources

---
 ma/safety_reset.tex | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

(limited to 'ma/safety_reset.tex')

diff --git a/ma/safety_reset.tex b/ma/safety_reset.tex
index 5d25e8a..5a256af 100644
--- a/ma/safety_reset.tex
+++ b/ma/safety_reset.tex
@@ -154,7 +154,7 @@ against attacks and simplify updates. Combined with the small market sizes in sm
     cost lies in the meter's software % TODO cite?
     There exist multiple competing standards applicable to various parts of a smart electricity meter. In addition,
     most countries have their own certification regimen\cite{cenelec01}. This complexity creates a large development
-    burden for new market entrants.
+    burden for new market entrants\cite{perez01}.
 }
 this produces a high cost pressure on the software development process for smart electricity meters.
 
@@ -478,6 +478,12 @@ simple to reduce attack surface there.
 \subsection{Landline IP}
 \subsection{IP-based wireless systems}
 \subsection{Frequency modulation as a communication channel}
+
+For our system, we chose grid frequency modulation (henceforth GFC) as a low-bandwidth uni-directional communications channel. 
+Compared to traditional PLC GFC requires no additional hardware, works reliably throughout the grid and is harder to
+manipulate by a malicious actor. 
+% FIXME \cite{urtasun01}
+
 \subsubsection{The frequency dependance of grid frequency}
 \subsubsection{Control systems coupled to grid frequency}
 \subsubsection{Avoiding dangerous modes}
@@ -596,9 +602,6 @@ correctly configure than it is to simply use separate hardware and secure the in
 \chapter{Economic viability of countermeasures}
 \section{Attack cost}
 \section{Countermeasure cost}
-\section{Conclusion}
-
-\chapter{The ethics and security implications of centralized crackdown on energy theft}
 
 % FIXME maybe include a standard for the technical side of a safety reset system here, e.g. in the style of an IETF draft?
 
-- 
cgit 

