Hi Bing > -----Original Message----- > From: Bing Zhao <bi...@nvidia.com> > Sent: Wednesday, January 31, 2024 11:38 AM > > In order to support the communication between IPv4 and IPv6 nodes in > the network, different technologies are used, like dual-stacks, > tunneling and NAT64. In some IPv4-only clients, it is hard to deploy > new software and(or) hardware to support IPv6 protocol. > > NAT64 is a choice and it will also reduce the unnecessary overhead of > the traffic in the network. The NAT64 gateways take the > responsibility of the packet headers translation between the IPv6 > clouds and IPv4-only clouds. > > The commit introduce the NAT64 flow action to offload the software > involvement to the hardware. > > This action should support the offloading of the IP headers' > translation. The following fields should be reset correctly in the > translation. > - Version > - Traffic Class / TOS > - Flow Label (0 in v4) > - Payload Length / Total length > - Next Header > - Hop Limit / TTL > > The PMD needs to support the basic conversion of the fields above, > and the well-known prefix will be used when translating IPv4 address > to IPv6 address. Another modify fields can be used after the NAT64 to > support other modes with different prefix and offset. > > The ICMP* and transport layers protocol is out of the scope of NAT64 > rte_flow action. > > Reference links: > - https://datatracker.ietf.org/doc/html/rfc6146 > - https://datatracker.ietf.org/doc/html/rfc6052 > - https://datatracker.ietf.org/doc/html/rfc6145 > > Signed-off-by: Bing Zhao <bi...@nvidia.com> > ---
Acked-by: Ori Kam <or...@nvidia.com> Best, Ori
