52 lines
1.6 KiB
TeX
52 lines
1.6 KiB
TeX
\chapter{\label{summary}Conclusion and Outlook}
|
|
%** 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
|
|
Many possibilities
|
|
Protocol independent
|
|
Easy architecture
|
|
|
|
NDP parsing support
|
|
|
|
Can be deployed using the netpfga. Or Barefoot or Arista.
|
|
|
|
OUTLOOK What are the consequences of your work for future work?
|
|
|
|
Different HW
|
|
|
|
Speed only limited to line speed. Could be running at 100 Gbit/s
|
|
without modifications.
|
|
|
|
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
|
|
|
|
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
|
|
|
|
NetFGPA - conclusion here}
|
|
Very time intensive development due to usability problems and
|
|
uncertainty of functionality (compare sections
|
|
\ref{results:netpfga:usability} and \ref{results:netpfga:stability}).
|