draft-ietf-opsawg-nat-yang-09.txt   draft-ietf-opsawg-nat-yang-10.txt 
Network Working Group M. Boucadair Network Working Group M. Boucadair
Internet-Draft Orange Internet-Draft Orange
Intended status: Standards Track S. Sivakumar Intended status: Standards Track S. Sivakumar
Expires: May 19, 2018 Cisco Systems Expires: July 20, 2018 Cisco Systems
C. Jacquenet C. Jacquenet
Orange Orange
S. Vinapamula S. Vinapamula
Juniper Networks Juniper Networks
Q. Wu Q. Wu
Huawei Huawei
November 15, 2017 January 16, 2018
A YANG Data Model for Network Address Translation (NAT) and Network A YANG Data Model for Network Address Translation (NAT) and Network
Prefix Translation (NPT) Prefix Translation (NPT)
draft-ietf-opsawg-nat-yang-09 draft-ietf-opsawg-nat-yang-10
Abstract Abstract
For the sake of network automation and the need for programming For the sake of network automation and the need for programming
Network Address Translation (NAT) function in particular, a data Network Address Translation (NAT) function in particular, a data
model for configuring and managing the NAT is essential. This model for configuring and managing the NAT is essential. This
document defines a YANG module for the NAT function. document defines a YANG module for the NAT function.
NAT44, Network Address and Protocol Translation from IPv6 Clients to NAT44, Network Address and Protocol Translation from IPv6 Clients to
IPv4 Servers (NAT64), Customer-side transLATor (CLAT), Stateless IP/ IPv4 Servers (NAT64), Customer-side transLATor (CLAT), Stateless IP/
skipping to change at page 2, line 15 skipping to change at page 2, line 15
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 19, 2018. This Internet-Draft will expire on July 20, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 20, line 9 skipping to change at page 20, line 9
| | {basic-nat44 or napt44 or nat64}? | | {basic-nat44 or napt44 or nat64}?
| +--rw notify-addresses-usage? percent | +--rw notify-addresses-usage? percent
| | {basic-nat44 or napt44 or nat64}? | | {basic-nat44 or napt44 or nat64}?
| +--rw notify-ports-usage? percent | +--rw notify-ports-usage? percent
| | {napt44 or nat64}? | | {napt44 or nat64}?
| +--rw notify-subscribers-limit? uint32 | +--rw notify-subscribers-limit? uint32
| {basic-nat44 or napt44 or nat64}? | {basic-nat44 or napt44 or nat64}?
+--rw logging-enable? boolean +--rw logging-enable? boolean
| {basic-nat44 or napt44 or nat64}? | {basic-nat44 or napt44 or nat64}?
+--rw mapping-table +--rw mapping-table
| {basic-nat44 or napt44 or nat64 or clat or dst-nat}? | {basic-nat44 or napt44 or nat64 or clat or dst-nat}?
| +--rw mapping-entry* [index] | +--rw mapping-entry* [index]
| +--rw index uint32 | +--rw index uint32
| +--rw type? enumeration | +--rw type? enumeration
| +--rw transport-protocol? uint8 | +--rw transport-protocol? uint8
| +--rw internal-src-address? inet:ip-prefix | +--rw internal-src-address? inet:ip-prefix
| +--rw internal-src-port | +--rw internal-src-port
| | +--rw start-port-number? inet:port-number | | +--rw start-port-number? inet:port-number
| | +--rw end-port-number? inet:port-number | | +--rw end-port-number? inet:port-number
| +--rw external-src-address? inet:ip-prefix | +--rw external-src-address? inet:ip-prefix
| +--rw external-src-port | +--rw external-src-port
skipping to change at page 21, line 35 skipping to change at page 21, line 35
| +--ro dropped-subscriber-limit-packets? | +--ro dropped-subscriber-limit-packets?
| | yang:zero-based-counter64 | | yang:zero-based-counter64
| | {basic-nat44 or napt44 or nat64}? | | {basic-nat44 or napt44 or nat64}?
| +--ro dropped-subscriber-limit-bytes? | +--ro dropped-subscriber-limit-bytes?
| yang:zero-based-counter64 | yang:zero-based-counter64
| {basic-nat44 or napt44 or nat64}? | {basic-nat44 or napt44 or nat64}?
+--ro mappings-statistics +--ro mappings-statistics
| +--ro total-active-subscribers? yang:gauge32 | +--ro total-active-subscribers? yang:gauge32
| | {basic-nat44 or napt44 or nat64}? | | {basic-nat44 or napt44 or nat64}?
| +--ro total-address-mappings? yang:gauge32 | +--ro total-address-mappings? yang:gauge32
| | {basic-nat44 or napt44 or nat64 or clat or dst-nat}? | |{basic-nat44 or napt44 or nat64 or clat or dst-nat}?
| +--ro total-port-mappings? yang:gauge32 | +--ro total-port-mappings? yang:gauge32
| | {napt44 or nat64}? | | {napt44 or nat64}?
| +--ro total-per-protocol* [protocol-id] | +--ro total-per-protocol* [protocol-id]
| {napt44 or nat64}? | {napt44 or nat64}?
| +--ro protocol-id uint8 | +--ro protocol-id uint8
| +--ro total? yang:gauge32 | +--ro total? yang:gauge32
+--ro pools-stats {basic-nat44 or napt44 or nat64}? +--ro pools-stats {basic-nat44 or napt44 or nat64}?
+--ro addresses-allocated? yang:gauge32 +--ro addresses-allocated? yang:gauge32
+--ro addresses-free? yang:gauge32 +--ro addresses-free? yang:gauge32
+--ro ports-stats {napt44 or nat64}? +--ro ports-stats {napt44 or nat64}?
skipping to change at page 67, line 4 skipping to change at page 67, line 4
} }
container mappings-statistics { container mappings-statistics {
description description
"Mappings statistics."; "Mappings statistics.";
leaf total-active-subscribers { leaf total-active-subscribers {
if-feature "basic-nat44 or napt44 or nat64"; if-feature "basic-nat44 or napt44 or nat64";
type yang:gauge32; type yang:gauge32;
description description
"Total number of active subscribers (that is, subscribers "Total number of active subscribers (that is,
for which the NAT maintains active mappings. subscribers for which the NAT maintains active
mappings.
A subscriber is identified by a subnet, subscriber-mask, A subscriber is identified by a subnet,
etc."; subscriber-mask, etc.";
} }
leaf total-address-mappings { leaf total-address-mappings {
if-feature "basic-nat44 or napt44 " + if-feature "basic-nat44 or napt44 " +
"or nat64 or clat or dst-nat"; "or nat64 or clat or dst-nat";
type yang:gauge32; type yang:gauge32;
description description
"Total number of address mappings present at a given "Total number of address mappings present at a given
time. It includes both static and dynamic mappings."; time. It includes both static and dynamic mappings.";
reference reference
skipping to change at page 74, line 27 skipping to change at page 74, line 32
Special thanks to Maros Marsalek and Marek Gradzki for sharing their Special thanks to Maros Marsalek and Marek Gradzki for sharing their
comments based on the FD.io implementation of an earlier version of comments based on the FD.io implementation of an earlier version of
this module. this module.
Rajiv Asati suggested to clarify how the module applies for both Rajiv Asati suggested to clarify how the module applies for both
stateless and stateful NAT64. stateless and stateful NAT64.
Juergen Schoenwaelder provided an early yandgoctors review. Many Juergen Schoenwaelder provided an early yandgoctors review. Many
thanks to him. thanks to him.
Thanks to Roni Even and Mach Chen for the directorates review. Igor
Ryzhov identified a nit in one example.
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC4787] Audet, F., Ed. and C. Jennings, "Network Address [RFC4787] Audet, F., Ed. and C. Jennings, "Network Address
Translation (NAT) Behavioral Requirements for Unicast Translation (NAT) Behavioral Requirements for Unicast
skipping to change at page 76, line 50 skipping to change at page 77, line 7
7.2. Informative References 7.2. Informative References
[I-D.boucadair-pcp-yang] [I-D.boucadair-pcp-yang]
Boucadair, M., Jacquenet, C., Sivakumar, S., and S. Boucadair, M., Jacquenet, C., Sivakumar, S., and S.
Vinapamula, "YANG Modules for the Port Control Protocol Vinapamula, "YANG Modules for the Port Control Protocol
(PCP)", draft-boucadair-pcp-yang-05 (work in progress), (PCP)", draft-boucadair-pcp-yang-05 (work in progress),
October 2017. October 2017.
[I-D.ietf-netmod-yang-tree-diagrams] [I-D.ietf-netmod-yang-tree-diagrams]
Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft- Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft-
ietf-netmod-yang-tree-diagrams-02 (work in progress), ietf-netmod-yang-tree-diagrams-04 (work in progress),
October 2017. December 2017.
[I-D.ietf-softwire-dslite-yang] [I-D.ietf-softwire-dslite-yang]
Boucadair, M., Jacquenet, C., and S. Sivakumar, "YANG Data Boucadair, M., Jacquenet, C., and S. Sivakumar, "A YANG
Modules for Dual-Stack Lite (DS-Lite)", draft-ietf- Data Module for Dual-Stack Lite (DS-Lite)", draft-ietf-
softwire-dslite-yang-09 (work in progress), November 2017. softwire-dslite-yang-14 (work in progress), January 2018.
[I-D.ietf-tsvwg-natsupp] [I-D.ietf-tsvwg-natsupp]
Stewart, R., Tuexen, M., and I. Ruengeler, "Stream Control Stewart, R., Tuexen, M., and I. Ruengeler, "Stream Control
Transmission Protocol (SCTP) Network Address Translation Transmission Protocol (SCTP) Network Address Translation
Support", draft-ietf-tsvwg-natsupp-11 (work in progress), Support", draft-ietf-tsvwg-natsupp-11 (work in progress),
July 2017. July 2017.
[RFC2663] Srisuresh, P. and M. Holdrege, "IP Network Address [RFC2663] Srisuresh, P. and M. Holdrege, "IP Network Address
Translator (NAT) Terminology and Considerations", Translator (NAT) Terminology and Considerations",
RFC 2663, DOI 10.17487/RFC2663, August 1999, RFC 2663, DOI 10.17487/RFC2663, August 1999,
skipping to change at page 79, line 23 skipping to change at page 79, line 23
192.0.2.1 192.0.2.1
</external-ip-pool> </external-ip-pool>
</external-ip-address-pool> </external-ip-address-pool>
.... ....
<mapping-table> <mapping-table>
.... ....
<external-src-address> <external-src-address>
192.0.2.1 192.0.2.1
</external-src-address> </external-src-address>
.... ....
<mapping-table> </mapping-table>
</instance> </instance>
</instances> </instances>
The following shows the XML excerpt depicting a dynamic UDP mapping The following shows the XML excerpt depicting a dynamic UDP mapping
entry maintained by a traditional NAPT44. In reference to this entry maintained by a traditional NAPT44. In reference to this
example, the UDP packet received with a source IPv4 address example, the UDP packet received with a source IPv4 address
(192.0.2.1) and source port number (1568) is translated into a UDP (192.0.2.1) and source port number (1568) is translated into a UDP
packet having a source IPv4 address (198.51.100.1) and source port packet having a source IPv4 address (198.51.100.1) and source port
(15000). The remaining lifetime of this mapping is 300 seconds. (15000). The remaining lifetime of this mapping is 300 seconds.
 End of changes. 13 change blocks. 
17 lines changed or deleted 21 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/