A YANG Module for Network Address Translation (NAT) and Network Prefix Translation (NPT)
draft-ietf-opsawg-nat-yang-17
Yes
(Ignas Bagdonas)
No Objection
(Adam Roach)
(Alexey Melnikov)
(Alissa Cooper)
(Alvaro Retana)
(Ben Campbell)
(Deborah Brungard)
(Martin Vigoureux)
(Terry Manderson)
Note: This ballot was opened for revision 15 and is now closed.
Ignas Bagdonas Former IESG member
Yes
Yes
(for -15)
Unknown
Adam Roach Former IESG member
No Objection
No Objection
(for -16)
Unknown
Alexey Melnikov Former IESG member
No Objection
No Objection
(for -16)
Unknown
Alissa Cooper Former IESG member
No Objection
No Objection
(for -16)
Unknown
Alvaro Retana Former IESG member
No Objection
No Objection
(for -16)
Unknown
Ben Campbell Former IESG member
No Objection
No Objection
(for -16)
Unknown
Benjamin Kaduk Former IESG member
No Objection
No Objection
(2018-09-25 for -16)
Unknown
Thanks for the easy-to-read document! I just have a few comments and potential nits I noticed. It was somewhat interesting to me that basically everything is config rw, including ports and addresses that would normally be assigned internally by the NAT, but I don't see this as problematic. Section 2.1 Considerations about instructing explicit dynamic means (e.g., [RFC6887], [RFC6736], or [RFC8045]) are out of scope. [...] I'm having trouble parsing this; is it maybe "instructing by explicit dynamic means" or "explicit dynamic mappings"? Section 3 What's the relationship between hold-down-timeout and hold-down-max -- that is, if the maximum number of ports in the pool gets hit, to the oldest ports in the pool get ejected even if they haven't timed out, or what happens? I don't expect this to need to be in the document, but I'm curious what the use case for the all-algs-enable leaf is. I may be confused, but is the ordering relationship between low-threshold and high-threshold correct? From the description it would seem like we need low < high, but I'm reading the text as requiring low >= high. Also, the error-message for that "must" stanza talks about port numbers, not percentage thresholds. container connection-limits { [...] list limit-per-protocol { [...] leaf limit { type uint32; description "Rate-limit the number of protocol-specific mappings and sessions per instance."; This is a maximum, not a rate-limit, I think? Section A.6 EAMs may be enabled jointly with statefull NAT64. This example shows a NAT64 function that supports static mappings: nit: "stateful"
Deborah Brungard Former IESG member
No Objection
No Objection
(for -16)
Unknown
Martin Vigoureux Former IESG member
No Objection
No Objection
()
Unknown
Mirja Kühlewind Former IESG member
(was Discuss)
No Objection
No Objection
(2018-09-24 for -16)
Unknown
Thanks for addressing my discuss well and quickly! Also thanks for the other changes to further consider other protocols such as DCCP and SCTP!
Suresh Krishnan Former IESG member
No Objection
No Objection
(2018-09-25 for -16)
Unknown
Shouldn't the "psid-offset" have a default value of 6 for the 'a' bits in MAP-E?
Terry Manderson Former IESG member
No Objection
No Objection
(for -16)
Unknown