tobast/talk-v4ov6-ietf108
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Integrate more feedback

Browse source
This commit is contained in:
Théophile Bastian 2020-07-26 22:01:12 +02:00
parent 9d7b8bcd04
commit ed36931f76
1 changed files with 25 additions and 19 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

44
slides.tex
View file

@ -63,7 +63,7 @@ draft-bastian-babel-v4ov6}}
\midrule
10.0.0.0/24 & & 10.0.0.1 \\
10.0.0.0/16 & & 10.0.1.1 \\
10.0.0.0/8 & & \xcancel{fd80::f0} \\
10.0.0.0/8 & & \xcancel{fe80::f0} \\
\bottomrule
\end{tabular}
\end{table}
@ -101,12 +101,10 @@ draft-bastian-babel-v4ov6}}
\vspace{2em}
\begin{itemize}
\item Supporting both v4 and v6 is cumbersome: twice the configuration
\item v6-only core, still serve v4 to clients
\item IPv6 has \alert{link-local addresses}
\begin{itemize}
\item no need for DHCP or IP addresses configuration \emph{at all}!
\end{itemize}
\item Useful to go through a \alert{router with no v4 address}
configured
\item Possible use: v6-only core, still serve v4 to clients
\emph{without tunnel}
\end{itemize}
\vspace{2em}
@ -147,14 +145,16 @@ draft-bastian-babel-v4ov6}}
\section{Babel protocol extension}
\begin{frame}{Advertising v4-over-v6 routes}
\textbf{An IPv4 interface} never announces v4-over-v6 routes
\textbf{Interface with v4 address:} no changes; just as unextended babel.
\vspace{1em}
\textbf{A v6-only interface}
\textbf{Interface with only v6 addresses:}
\begin{itemize}
\item{} \alert{Installs a v4 route} nevertheless when receiving it
\item{} \alert{Announces a v4-over-v6 route} for each v4 route
\item{} \alert{Receiving} a v4 route: \alert{install it anyway}, the
router's address is irrelevant.
\item{} \alert{Announcing} a v4 route: use \alert{v4-over-v6}; we need
a next-hop and only have v6 at hand.
\end{itemize}
\end{frame}
@ -218,16 +218,22 @@ draft-bastian-babel-v4ov6}}
%%%%%%%%%%% Conclusion frame %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}{To sum up}
\begin{frame}{Conclusion}
\begin{itemize}
\item While routing, next-hop address is \alert{only useful to get layer 2
address}
\item New type of route: \alert{v4-over-v6}, v4 destination, v6 next-hop
\item Less network configuration, same features! Yay!
\item We have \alert{an extension draft} and \alert{an implementation}
\item Route IPv4 over an IPv6 network core. \textit{Look, Ma! No tunnels!}
\item Protocol \alert{described and drafted}
\item \alert{Production-ready implementation} available on the babeld
repository
\end{itemize}
\vspace{2em}
\vspace{1em}
\begin{itemize}
\item \textbf{Intended status: \alert{experimental}}
\item Opinions: should it be adopted by workgroup or carried alone?
\end{itemize}
\vspace{1em}
\begin{columns}[T]
\begin{column}{0.5\textwidth}
@ -236,7 +242,7 @@ draft-bastian-babel-v4ov6}}
\href{https://datatracker.ietf.org/doc/draft-bastian-babel-v4ov6/}{\texttt{\large huit.re/draft-v4ov6}}
\includegraphics[width=0.25\textwidth]{imgs/pdf/qr_draft.pdf}
\includegraphics[width=0.2\textwidth]{imgs/pdf/qr_draft.pdf}
\end{column}
\begin{column}{0.5\textwidth}
@ -245,7 +251,7 @@ draft-bastian-babel-v4ov6}}
\href{https://tobast.fr/files/ietf108-v40v6.pdf}{\texttt{\large huit.re/ietf108-v4ov6}}
\includegraphics[width=0.25\textwidth]{imgs/pdf/qr_slide.pdf}
\includegraphics[width=0.2\textwidth]{imgs/pdf/qr_slide.pdf}
\end{column}
\end{columns}
\end{frame}