|
|
|
@ -286,7 +286,7 @@ both support cleaning up old session entries,
|
|
|
|
|
our P4 based solution does not support this feature at the moment. |
|
|
|
|
|
|
|
|
|
In figure \ref{fig:p4switchstateful} we show the flow of a packet for |
|
|
|
|
stateful translation in a P4 switch in detail. As can be seen an IPv6 |
|
|
|
|
stateful translation in a P4 switch in detail. An IPv6 only |
|
|
|
|
host emits a packet that should be translated to IPv4. On a new |
|
|
|
|
connection there will be no table entry in the P4 switch to |
|
|
|
|
match. Thus the table mismatch causes the P4 switch to forward the |
|
|
|
@ -295,7 +295,7 @@ creates a table entry for the session and reinjects the packet into
|
|
|
|
|
the P4 switch. The P4 switch then processes the packet again, however |
|
|
|
|
this time it finds a matching table entry. This entry causes |
|
|
|
|
translation to happen to a specific IPv4 address, including higher |
|
|
|
|
level protocol changes. After processing the IPv6 packet is output as |
|
|
|
|
level protocol changes. After processing the IPv6 packet it is output as |
|
|
|
|
a translated IPv4 packet. A second packet of the same session will |
|
|
|
|
directly take the second path via table match, as the session ID will |
|
|
|
|
stay the same.\footnote{We use the quintuple (source address, |
|
|
|
|