If you want it to be direct, specific, and self documenting, I’d suggest
“Address Replacement Function”. Then verbalize it by saying casually “ARFing
the packet”.
Dino
> On Mar 23, 2018, at 10:36 AM, Tom Herbert wrote:
>
> On Tue, Mar 20, 2018 at 4:53 AM, Sri Gundavelli (sgundave)
> wrote:
On Tue, Mar 20, 2018 at 4:53 AM, Sri Gundavelli (sgundave)
wrote:
>
> ILA-NAT-GW, or Locator-Rewrite Function ,,,should all work I guess.
>
Sri,
I still like the term 'address transformation'. The difference between
transformation and translation is that no information is lost in
transformation (
Le 22/03/2018 à 18:49, Liaison Statement Management Tool a écrit :
[...]
SA2 would like to point out that among the four mechanisms for
address configuration delivery mentioned in your LS reply (i.e.
DHCPv4, DHCPv6, IPv6 ND and IKEv2) only the IPv6 ND mechanisms, and
in particular the Router A
Yes, in the LS response that we sent to 3GPP on 2/16, we did cite the
below work.
There are many proposals on this including:
https://www.ietf.org/id/draft-feng-dmm-ra-prefixtype-01.txt
https://www.ietf.org/id/draft-moses-dmm-dhcp-ondemand-mobility-08.txt
Also, some proposals from the pre