master-thesis/doc/Conclusion.tex

53 lines
1.5 KiB
TeX
Raw Normal View History

\chapter{\label{summary}Conclusion and Outlook}
2019-08-07 13:55:53 +00:00
%** Summary.tex: What have you achieved, what have you presented in this
% document. What are the highlights of your work.
% It should conclude by a conclusion.
Sum up what you have done and recapitulate your key findings.
p4 potential
2019-08-07 13:55:53 +00:00
Many possibilities
Protocol independent
Easy architecture
NDP parsing support
2019-08-07 13:55:53 +00:00
Can be deployed using the netpfga. Or Barefoot or Arista.
OUTLOOK What are the consequences of your work for future work?
2019-08-07 13:55:53 +00:00
Different HW
Speed only limited to line speed. Could be running at 100 Gbit/s
without modifications.
2019-08-12 15:36:43 +00:00
PMTU
handling error cases
Our algorithm uses the IPv4-Compatible IPv6 Address\cite{rfc4291} to
embed IPv4 addresses. However RFC6052\cite{rfc6052} defines different
embeddings depending on the prefix size. A future version should
support these schemes to be compatible to other implementations.
No fragmentation
No address / mac learning
**** No DNS64
has already been solved in a different domain - could even do
transparent / in network modification. DNSSEC.
**** Incomplete NDP
Very limited option support
No resolution of hardware addresses
2019-08-12 15:36:43 +00:00
While the port to NetPFGA was significantly more effort then expected,
the learnings of the different layers were very much appreciated / liked
It was a
2019-08-15 15:15:48 +00:00
NetFGPA - conclusion here
2019-08-15 14:45:56 +00:00
Very time intensive development due to usability problems and
uncertainty of functionality (compare sections
\ref{results:netpfga:usability} and \ref{results:netpfga:stability}).