Re-re-re-try to do checkumming based on a meta field

This commit is contained in:
Nico Schottelius 2019-03-06 15:15:46 +01:00
commit 591175db7a
3 changed files with 28 additions and 15 deletions

View file

@ -51,6 +51,7 @@
| | * Summary on Slack | |
| | * 1130 meeting now | |
| | | |
| | | |
| 2019-03-01 | Feature list / priority list / roadmap clear | x |
| | Joining P4 Slack | |
| | | |
@ -86,7 +87,7 @@
| | - Multiple branches: | |
| | * Work on checksumming / p4 | |
| | * Work on metadata passing / p4 | |
| | * Work on static mapping (w/ incorrect checksum) | |
| | * Work on static mapping (w/ incorrect checksum) 1:1 | |
| | | |
| | | |
| 2019-03-08 | NAT46 1:1 table ICMP, ICMPv6 working | |
@ -198,6 +199,10 @@ p4@ubuntu:~/master-thesis$
**** TODO Translate ipv6 --> ipv4 with a (freely programmable) prefix
***** TODO Insert prefix into switch
***** TODO Implement the calculation
***** TODO Sketch the flow for session handling for icmp6 w/o packet loss
- switch receives icmp6 packet for known prefix
- controller needs to create session entry (?)
**** TODO Translate icmp <-> icmp6
**** TODO Create table entry for mapping v4->v6 [net]
**** TODO Create table entry for mapping v6->v4 [net]
@ -539,8 +544,6 @@ performance, security and adaptivity of the solutions.
- Milestone 1: Stateless NAT64/NAT46 translations in P4
- Milestone 2: Stateful (dynamic) NAT64/NAT46 translations
- Milestone 3: Hardware adaption
** Original ideas
Proposal 1: Automating NAT64 with P4