Overall, I think the rename is a good idea. The Linux guys are used to thinking of SNAT as source NAT and DNAT as destination NAT.
Ed On Mon, Aug 21, 2017 at 12:53 AM, Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <mgrad...@cisco.com> wrote: > Hi, > > Hc2vpp uses SNAT API. The rename you suggest is very simple (I guess > snat->nat44), > so we will not mind if there will be no parallel API. > > Regards, > Marek > > -----Original Message----- > From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On > Behalf Of Ole Troan > Sent: 21 sierpnia 2017 09:40 > To: vpp-dev <vpp-dev@lists.fd.io> > Subject: [vpp-dev] VPP S-NAT rename > > Hi, > > The 'S' in VPP's S-NAT plugin name has often been confused with Linux' > "Source NAT". The 'S' originally stood for "Simple", implying that it was a > less complex implementation of NAT than the previous VCGN implementation. > > Because of this confusion (and possibly valid arguments that it isn't so > simple anymore) we'd like to rename it. > The feature supports all flavours of NAT44 and NAT64. > > The suggested new name is simply NAT. I.e. "VPP NAT". > > The proposal is to change the name in the wiki, documentation, > folder/files and CLI. > I am unsure if it is possible to change the API at this point. We might > have to put in the new message names and allow those to live in parallel > with the old ones for a release or two. Does anyone use the SNAT API? > > Opinions? > > Best regards, > Ole > _______________________________________________ > vpp-dev mailing list > vpp-dev@lists.fd.io > https://lists.fd.io/mailman/listinfo/vpp-dev >
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
