[RFC PATCH] ethdev: introduce NAT64 action

[Ori Kam]

Hi Bing

> -----Original Message-----
> From: Bing Zhao <bingz at nvidia.com>
> Sent: Friday, August 11, 2023 5:07 PM
> Subject: [RFC PATCH] ethdev: introduce NAT64 action
> 
> 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 hardware to support IPv6.
> 
> 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.
> 
> 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
> 
> Since there are different mapping and translating modes of the
> addresses, it will depend on the capabilities of each vendor.
> 
> 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 <bingz at nvidia.com>
> ---

Acked-by: Ori Kam <orika at nvidia.com>
Best,
Ori