https://tools.ietf.org/html/draft-ietf-opsawg-nat-yang-00
fixes some issues of the ietf-nat@2015-09-08.yang we are using currently.
Advantages:
- symmetric structure (nat-current-config removed)
- destination nat, nptv6 support (but do we need them?)
Issues: - still many mandatory fields
- address prefixes vs addresses
- needs more investigation, but looks like it is not supported in vpp
- dynamic explicit vs dynamic implicit?
- migration issues:
- renaming nat-cfg and nat-state nodes, removal of nat-current-config container
- ip-prefix instead of ip-address (user needs to add /32, but rfc wrongly permits strings without slash).
It looks like the new draft is not very stable currently. Two new revisions were added in the week after 00 was published. Most current one (not analyzed yet):
https://tools.ietf.org/html/draft-ietf-opsawg-nat-yang-06
- relates to
-
HC2VPP-326 Check if NAT instance type can be used instead of nat-pool-type
-
- To Do
-
-
HC2VPP-327 Add support for external-realm container
-
- To Do
-
-
-
- Done
-
-
HC2VPP-328 Remove modifications of ietf-nat@2018-02-23.yang
-
- Blocked
-