From e524a3b348e73e2e886f465d081b86a633cfc408 Mon Sep 17 00:00:00 2001
From: ch <289995-netravnen@users.noreply.gitlab.com>
Date: Mon, 7 Oct 2024 17:36:02 +0200
Subject: [PATCH] Layer 3: Add initial section for ISIS

---
 chapter/layer3.tex      | 50 ++++++++++++++++++++++++++++-------------
 references-websites.bib | 11 ++++++++-
 2 files changed, 44 insertions(+), 17 deletions(-)

diff --git a/chapter/layer3.tex b/chapter/layer3.tex
index 1b19033..279a186 100644
--- a/chapter/layer3.tex
+++ b/chapter/layer3.tex
@@ -55,6 +55,24 @@ Always remember the following points for Cisco devices:\cite{wiki:Administrative
 
 \section{IS-IS}
 
+\gls{isis} is the ISO standardized routing protocol. Designed for use by intermediate systems.
+
+\gls{isis} compared to other routing protocols standardized in the \gls{ietf}.
+\begin{itemize}
+    \item Everything is \gls{tlv} based. Making the protocol very extensible by standardizing new \gls{tlv} values.
+    \item The participating nodes communicates with its neighbors on \gls{l2}. Thereby not \textit{requiring} \gls{l3} addresses on the link. And instead uses the \gls{mac} to target the neighbor node.
+    \item The connection is done on per-interface. Similar to \gls{ospf3}. Instead of the global approach in \gls{ospf2}.
+    \begin{itemize}
+        \item The per-interface is the result of deciding the area is handled per-interface. Instead of at the per-node level.
+        \item The border between areas is at the node level. Instead of the interface level in \gls{ospf2}.
+    \end{itemize}
+    \item Uses its own ethertype of 0x22F4\cite{IEEE802N51:online}.
+    \begin{itemize}
+        \item \rfc{6325}.
+    \end{itemize}
+    \item Commun
+\end{itemize}
+
 \newpage
 
 \section{EIGRP}
@@ -226,12 +244,12 @@ The version of rip supporting ipv6. different to the standard rip in the ng vers
 
 \section{Babel}
 
-Babel is built on the principles of 1) \gls{dsdv}, 2) \gls{aodv}, and 3) 
+Babel is built on the principles of 1) \gls{dsdv}, 2) \gls{aodv}, and 3)
 \gls{eigrp} protocols.
-Made for hybrid networks\footnote{network contains wired and wireless links} 
+Made for hybrid networks\footnote{network contains wired and wireless links}
 and can account for a high level of instability on wireless links.
 
-Babel has been reported to be running stable in unstable wireless networks with 
+Babel has been reported to be running stable in unstable wireless networks with
 a level of reliability and fast convergence.
 
 \begin{itemize}
@@ -239,24 +257,24 @@ a level of reliability and fast convergence.
     \item Uses distributed Bellman-Ford algorithm,
     \item \rfc{6126} in 45 pages, \textit{(28 are normative)}
     \begin{enumerate}
-        \item Updates by \rfc{7298} {\scriptsize (The Babel extension 
+        \item Updates by \rfc{7298} {\scriptsize (The Babel extension
         mechanism)}, and
-        \item \rfc{7557} {\scriptsize (Babel \gls{hmac} Cryptographic 
+        \item \rfc{7557} {\scriptsize (Babel \gls{hmac} Cryptographic
         Authentication)}.
     \end{enumerate}
     \item Highly extensible protocol,\cite{BabelDoe86:online}
     \item Supports \gls{ip4} and \gls{ip6}.
 \end{itemize}
 
-Babel on \underline{wired} networks uses by default hop-count. Can be 
+Babel on \underline{wired} networks uses by default hop-count. Can be
 configured to include several values when computing the metrics.
-On \underline{wireless} networks Babel should be configured to take into 
-account factors such as link latency, packet loss, hop-count, and radio 
+On \underline{wireless} networks Babel should be configured to take into
+account factors such as link latency, packet loss, hop-count, and radio
 diversity.
 
 \subsection{Protocol support}
 
-Currently the following projects include support for Babel: 
+Currently the following projects include support for Babel:
 \cite{Babel-al30:online}
 
 \begin{itemize}
@@ -312,26 +330,26 @@ Route-maps is used to target a select set of routes and either modify/add/remove
     \begin{enumerate}[label={\alph*)}]
         \item \Gls{bgp} communities,
         \item \Gls{ip} prefix,
-        \item \Gls{bgp} as-path, 
+        \item \Gls{bgp} as-path,
     \end{enumerate}
 \end{itemize}
 
 An simple example of using route-maps is
 
 \begin{cisco}
-ip prefix-list 1 permit 172.16.0.0/16 
-ip prefix-list 2 permit 192.168.1.0/24 
+ip prefix-list 1 permit 172.16.0.0/16
+ip prefix-list 2 permit 192.168.1.0/24
 !
-route-map RED permit 10 
- match ip address prefix-list 1 
+route-map RED permit 10
+ match ip address prefix-list 1
  set ip next hop 10.1.1.1
  continue 20              ! Continues to apply rules normally only
                           ! applied to prefix-list 2. To apply to
                           ! prefix-list 1, too.
                           ! Any attributes set in '20' will
                           ! override any set during '10'.
-route-map RED permit 20 
- match ip address prefix-list 2 
+route-map RED permit 20
+ match ip address prefix-list 2
  set ip next hop 10.2.2.2 ! Last rule overrides previous rules from
                           ! previous '10' rule-set.
 \end{cisco}
diff --git a/references-websites.bib b/references-websites.bib
index 178a544..b706b71 100644
--- a/references-websites.bib
+++ b/references-websites.bib
@@ -57,4 +57,13 @@
     month = {},
     year = {},
     note = {(Accessed on 02/18/2018)}
-}
\ No newline at end of file
+}
+
+@misc{IEEE802N51:online,
+    author = {},
+    title = {IEEE 802 Numbers - https://www.iana.org/},
+    howpublished = {\url{https://www.iana.org/assignments/ieee-802-numbers/ieee-802-numbers.xhtml#ieee-802-numbers-1}},
+    month = {},
+    year = {},
+    note = {(Accessed on 10/01/2024)}
+}