draft-ietf-softwire-dslite-yang-14.txt   draft-ietf-softwire-dslite-yang-15.txt 
Network Working Group M. Boucadair Network Working Group M. Boucadair
Internet-Draft C. Jacquenet Internet-Draft C. Jacquenet
Intended status: Standards Track Orange Intended status: Standards Track Orange
Expires: July 13, 2018 S. Sivakumar Expires: August 30, 2018 S. Sivakumar
Cisco Systems Cisco Systems
January 9, 2018 February 26, 2018
A YANG Data Module for Dual-Stack Lite (DS-Lite) A YANG Data Module for Dual-Stack Lite (DS-Lite)
draft-ietf-softwire-dslite-yang-14 draft-ietf-softwire-dslite-yang-15
Abstract Abstract
This document defines a YANG module for the DS-Lite Address Family This document defines a YANG module for the DS-Lite Address Family
Transition Router (AFTR) and Basic Bridging BroadBand (B4) elements. Transition Router (AFTR) and Basic Bridging BroadBand (B4) elements.
Editorial Note (To be removed by RFC Editor) Editorial Note (To be removed by RFC Editor)
Please update these statements with the RFC number to be assigned to Please update these statements with the RFC number to be assigned to
this document: this document:
o "This version of this YANG module is part of RFC XXXX;" o "This version of this YANG module is part of RFC XXXX;"
o "RFC XXXX: A YANG Data Module for Dual-Stack Lite (DS-Lite)"; o "RFC XXXX: A YANG Data Module for Dual-Stack Lite (DS-Lite)";
o "reference: RFC XXXX" o "reference: RFC XXXX"
Please update the "revision" date of the YANG module.
Also, update this sentence with the RFC number to be assigned to this
document:
o "RFC YYYY: A YANG Module for Network Address Translation (NAT) and
Network Prefix Translation (NPT)"
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 July 13, 2018. This Internet-Draft will expire on August 30, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 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
skipping to change at page 2, line 26 skipping to change at page 2, line 30
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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
2. DS-Lite YANG Module: An Overview . . . . . . . . . . . . . . 4 2. DS-Lite YANG Module: An Overview . . . . . . . . . . . . . . 4
3. DS-Lite YANG Module . . . . . . . . . . . . . . . . . . . . . 6 3. DS-Lite YANG Module . . . . . . . . . . . . . . . . . . . . . 6
4. Security Considerations . . . . . . . . . . . . . . . . . . . 14 4. Security Considerations . . . . . . . . . . . . . . . . . . . 15
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 16
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
7.1. Normative references . . . . . . . . . . . . . . . . . . 16 7.1. Normative references . . . . . . . . . . . . . . . . . . 16
7.2. Informative references . . . . . . . . . . . . . . . . . 17 7.2. Informative references . . . . . . . . . . . . . . . . . 17
Appendix A. B4 Example . . . . . . . . . . . . . . . . . . . . . 18 Appendix A. B4 Example . . . . . . . . . . . . . . . . . . . . . 19
Appendix B. AFTR Examples . . . . . . . . . . . . . . . . . . . 18 Appendix B. AFTR Examples . . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
This document defines a data model for DS-Lite [RFC6333], using the This document defines a data model for DS-Lite [RFC6333], using the
YANG data modeling language [RFC7950]. Both the Address Family YANG data modeling language [RFC7950]. Both the Address Family
Transition Router (AFTR) and Basic Bridging BroadBand (B4) elements Transition Router (AFTR) and Basic Bridging BroadBand (B4) elements
are covered by this specification. are covered by this specification.
As a reminder, Figure 1 illustrates an overview of the DS-Lite As a reminder, Figure 1 illustrates an overview of the DS-Lite
architecture that involves AFTR and B4 elements. architecture that involves AFTR and B4 elements.
skipping to change at page 4, line 32 skipping to change at page 4, line 32
2. DS-Lite YANG Module: An Overview 2. DS-Lite YANG Module: An Overview
As shown in Figure 1: As shown in Figure 1:
o The AFTR element is a combination of an IPv4-in-IPv6 tunnel and a o The AFTR element is a combination of an IPv4-in-IPv6 tunnel and a
NAPT function (Section 2.2 of [RFC3022]). NAPT function (Section 2.2 of [RFC3022]).
o The B4 element is an IPv4-in-IPv6 tunnel. o The B4 element is an IPv4-in-IPv6 tunnel.
Therefore, the DS-Lite YANG module is designed to augment both the Therefore, the DS-Lite YANG module is designed to augment both the
Interfaces YANG module [RFC7223] and the NAT YANG module Interfaces YANG module [I-D.ietf-netmod-rfc7223bis] and the NAT YANG
[I-D.ietf-opsawg-nat-yang] with DS-Lite specific features. module [I-D.ietf-opsawg-nat-yang] with DS-Lite specific features.
The YANG "feature" statement is used to distinguish which of the DS- The YANG "feature" statement is used to distinguish which of the DS-
Lite elements ('aftr' or 'b4') is relevant for a specific data node. Lite elements ('aftr' or 'b4') is relevant for a specific data node.
Concretely, the DS-Lite YANG module (Figure 2) augments the Concretely, the DS-Lite YANG module (Figure 2) augments the
Interfaces YANG module with the following: Interfaces YANG module with the following:
o An IPv6 address used by the tunnel endpoint (AFTR or B4) for o An IPv6 address used by the tunnel endpoint (AFTR or B4) for
sending and receiving IPv4-in-IPv6 packets (ipv6-address). sending and receiving IPv4-in-IPv6 packets (ipv6-address).
skipping to change at page 6, line 9 skipping to change at page 6, line 9
packet upstream. packet upstream.
Access Control List (ACL) and Quality of Service (QoS) policies Access Control List (ACL) and Quality of Service (QoS) policies
discussed in Section 2.5 of [RFC6908] are out of scope. A YANG discussed in Section 2.5 of [RFC6908] are out of scope. A YANG
module for ACLs is documented in [I-D.ietf-netmod-acl-model]. module for ACLs is documented in [I-D.ietf-netmod-acl-model].
Likewise, PCP-related considerations discussed in Section 8.5 of Likewise, PCP-related considerations discussed in Section 8.5 of
[RFC6333] are out of scope. A YANG module for PCP is documented in [RFC6333] are out of scope. A YANG module for PCP is documented in
[I-D.boucadair-pcp-yang]. [I-D.boucadair-pcp-yang].
The YANG module "ietf-dslite" has the following structure:
module: ietf-dslite module: ietf-dslite
augment /if:interfaces/if:interface: augment /if:interfaces/if:interface:
+--rw ipv6-address? inet:ipv6-address +--rw ipv6-address? inet:ipv6-address
+--rw ipv4-address? inet:ipv4-address +--rw ipv4-address? inet:ipv4-address
+--rw aftr-ipv6-addr? inet:ipv6-address {b4}? +--rw aftr-ipv6-addr? inet:ipv6-address {b4}?
+--rw tunnel-mtu? uint16 +--rw tunnel-mtu? uint16
+--rw v6-v4-dscp-preservation? boolean +--rw v6-v4-dscp-preservation? boolean
augment /nat:nat/nat:instances/nat:instance/nat:policy: augment /nat:nat/nat:instances/nat:instance/nat:policy:
+--rw max-softwires-per-subscriber? uint8 {aftr}? +--rw max-softwires-per-subscriber? uint8 {aftr}?
+--rw state-migrate? boolean {aftr}? +--rw state-migrate? boolean {aftr}?
skipping to change at page 6, line 41 skipping to change at page 6, line 43
augment /nat:nat/nat:instances/nat:instance augment /nat:nat/nat:instances/nat:instance
/nat:statistics/nat:mappings-statistics: /nat:statistics/nat:mappings-statistics:
+--ro active-softwires? yang:gauge32 {aftr}? +--ro active-softwires? yang:gauge32 {aftr}?
notifications: notifications:
+---n b4-address-change-limit-policy-violation {aftr}? +---n b4-address-change-limit-policy-violation {aftr}?
+--ro id -> /nat:nat/instances/instance/id +--ro id -> /nat:nat/instances/instance/id
+--ro policy-id -> /nat:nat/instances/instance/policy/id +--ro policy-id -> /nat:nat/instances/instance/policy/id
+--ro address inet:ipv6-address +--ro address inet:ipv6-address
Figure 2: YANG Module for DS-Lite Figure 2: DS-Lite YANG tree diagram
Examples to illustrate the use of this module are provided in Examples to illustrate the use of the "ietf-dslite" module are
Appendix A and Appendix B. provided in Appendix A and Appendix B.
3. DS-Lite YANG Module 3. DS-Lite YANG Module
<CODE BEGINS> file "ietf-dslite@2018-01-10.yang" This module uses the tunnel interface identity defined in [RFC7224].
<CODE BEGINS> file "ietf-dslite@2018-02-26.yang"
module ietf-dslite { module ietf-dslite {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-dslite"; namespace "urn:ietf:params:xml:ns:yang:ietf-dslite";
prefix dslite; prefix dslite;
import ietf-inet-types { prefix inet; } import ietf-inet-types {
import ietf-interfaces { prefix if; } prefix inet;
import iana-if-type { prefix ianaift; } reference
import ietf-nat {prefix nat;} "Section 4 of RFC 6991";
import ietf-yang-types { prefix yang; } }
import ietf-interfaces {
prefix if;
reference
"RFC 8343: A YANG Data Model for Interface Management";
}
import iana-if-type {
prefix ianaift;
reference
"RFC 7224: IANA Interface Type YANG Module";
}
import ietf-nat {
prefix nat;
reference
"RFC YYYY: A YANG Module for Network Address Translation (NAT)
and Network Prefix Translation (NPT)";
}
import ietf-yang-types {
prefix yang;
reference
"Section 3 of RFC 6991";
}
organization "IETF Softwire Working Group"; organization "IETF Softwire Working Group";
contact contact
"WG Web: <https://datatracker.ietf.org/wg/softwire/> "WG Web: <https://datatracker.ietf.org/wg/softwire/>
WG List: <mailto:softwires@ietf.org> WG List: <mailto:softwires@ietf.org>
Editor: Mohamed Boucadair Editor: Mohamed Boucadair
<mailto:mohamed.boucadair@orange.com> <mailto:mohamed.boucadair@orange.com>
Editor: Christian Jacquenet Author: Christian Jacquenet
<mailto:christian.jacquenet@orange.com> <mailto:christian.jacquenet@orange.com>
Editor: Senthil Sivakumar Author: Senthil Sivakumar
<mailto:ssenthil@cisco.com>"; <mailto:ssenthil@cisco.com>";
description description
"This module is a YANG module for DS-Lite AFTR and B4 "This module is a YANG module for DS-Lite AFTR and B4
implementations. implementations.
Copyright (c) 2017 IETF Trust and the persons identified as Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
revision 2018-01-10 { revision 2018-02-26 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: A YANG Data Module for Dual-Stack Lite (DS-Lite)"; "RFC XXXX: A YANG Data Module for Dual-Stack Lite (DS-Lite)";
} }
/* /*
* Features * Features
*/ */
skipping to change at page 14, line 18 skipping to change at page 15, line 4
leaf address { leaf address {
type inet:ipv6-address; type inet:ipv6-address;
mandatory true; mandatory true;
description description
"B4's IPv6 address."; "B4's IPv6 address.";
} }
} }
} }
<CODE ENDS> <CODE ENDS>
4. Security Considerations 4. Security Considerations
The YANG module defined in this document is designed to be accessed The YANG module defined in this document is designed to be accessed
via network management protocols such as NETCONF [RFC6241] or via network management protocols such as NETCONF [RFC6241] or
RESTCONF [RFC8040]. The lowest NETCONF layer is the secure transport RESTCONF [RFC8040]. The lowest NETCONF layer is the secure transport
layer, and the mandatory-to-implement secure transport is Secure layer, and the mandatory-to-implement secure transport is Secure
Shell (SSH) [RFC6242]. The lowest RESTCONF layer is HTTPS, and the Shell (SSH) [RFC6242]. The lowest RESTCONF layer is HTTPS, and the
mandatory-to-implement secure transport is TLS [RFC5246]. mandatory-to-implement secure transport is TLS [RFC5246].
The NETCONF access control model [RFC6536] provides the means to The NETCONF access control model [I-D.ietf-netconf-rfc6536bis]
restrict access for particular NETCONF or RESTCONF users to a provides the means to restrict access for particular NETCONF or
preconfigured subset of all available NETCONF or RESTCONF protocol RESTCONF users to a preconfigured subset of all available NETCONF or
operations and content. RESTCONF protocol operations and content.
All data nodes defined in the YANG module which can be created, All data nodes defined in the YANG module which can be created,
modified and deleted (i.e., config true, which is the default) are modified and deleted (i.e., config true, which is the default) are
considered sensitive. Write operations (e.g., edit-config) applied considered sensitive. Write operations (e.g., edit-config) applied
to these data nodes without proper protection can negatively affect to these data nodes without proper protection can negatively affect
network operations. An attacker who is able to access to the B4/AFTR network operations. An attacker who is able to access to the B4/AFTR
can undertake various attacks, such as: can undertake various attacks, such as:
o Set the value of 'aftr-ipv6-addr' on the B4 to point to an o Set the value of 'aftr-ipv6-addr' on the B4 to point to an
illegitimate AFTR so that it can intercept all the traffic sent by illegitimate AFTR so that it can intercept all the traffic sent by
skipping to change at page 15, line 43 skipping to change at page 16, line 28
the "YANG Module Names" registry [RFC7950]. the "YANG Module Names" registry [RFC7950].
name: ietf-dslite name: ietf-dslite
namespace: urn:ietf:params:xml:ns:yang:ietf-dslite namespace: urn:ietf:params:xml:ns:yang:ietf-dslite
prefix: dslite prefix: dslite
reference: RFC XXXX reference: RFC XXXX
6. Acknowledgements 6. Acknowledgements
Thanks to Qin Wu, Benoit Claise, and Andy Bierman who helped for Thanks to Qin Wu, Benoit Claise, and Andy Bierman who helped for
identifying compiling errors. Mahesh Jethanandani provided an early identifying compiling errors. Mahesh Jethanandani provided early
yangdoctors review; many thanks to him. yangdoctors reviews; many thanks to him.
Many thanks to Ian Farrer for the review and comments. Many thanks to Ian Farrer and Tom Petch for the review and comments.
7. References 7. References
7.1. Normative references 7.1. Normative references
[I-D.ietf-netconf-rfc6536bis]
Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Module", draft-ietf-netconf-rfc6536bis-09
(work in progress), December 2017.
[I-D.ietf-netmod-rfc7223bis]
Bjorklund, M., "A YANG Data Model for Interface
Management", draft-ietf-netmod-rfc7223bis-03 (work in
progress), January 2018.
[I-D.ietf-opsawg-nat-yang] [I-D.ietf-opsawg-nat-yang]
Boucadair, M., Sivakumar, S., Jacquenet, C., Vinapamula, Boucadair, M., Sivakumar, S., Jacquenet, C., Vinapamula,
S., and Q. Wu, "A YANG Data Model for Network Address S., and Q. Wu, "A YANG Module for Network Address
Translation (NAT) and Network Prefix Translation (NPT)", Translation (NAT) and Network Prefix Translation (NPT)",
draft-ietf-opsawg-nat-yang-09 (work in progress), November draft-ietf-opsawg-nat-yang-13 (work in progress), February
2017. 2018.
[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>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, (TLS) Protocol Version 1.2", RFC 5246,
DOI 10.17487/RFC5246, August 2008, DOI 10.17487/RFC5246, August 2008,
<https://www.rfc-editor.org/info/rfc5246>. <https://www.rfc-editor.org/info/rfc5246>.
skipping to change at page 16, line 39 skipping to change at page 17, line 28
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/info/rfc6242>. <https://www.rfc-editor.org/info/rfc6242>.
[RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual- [RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual-
Stack Lite Broadband Deployments Following IPv4 Stack Lite Broadband Deployments Following IPv4
Exhaustion", RFC 6333, DOI 10.17487/RFC6333, August 2011, Exhaustion", RFC 6333, DOI 10.17487/RFC6333, August 2011,
<https://www.rfc-editor.org/info/rfc6333>. <https://www.rfc-editor.org/info/rfc6333>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536,
DOI 10.17487/RFC6536, March 2012,
<https://www.rfc-editor.org/info/rfc6536>.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
RFC 6991, DOI 10.17487/RFC6991, July 2013, RFC 6991, DOI 10.17487/RFC6991, July 2013,
<https://www.rfc-editor.org/info/rfc6991>. <https://www.rfc-editor.org/info/rfc6991>.
[RFC7223] Bjorklund, M., "A YANG Data Model for Interface [RFC7224] Bjorklund, M., "IANA Interface Type YANG Module",
Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, RFC 7224, DOI 10.17487/RFC7224, May 2014,
<https://www.rfc-editor.org/info/rfc7223>. <https://www.rfc-editor.org/info/rfc7224>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>. <https://www.rfc-editor.org/info/rfc8040>.
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-acl-model] [I-D.ietf-netmod-acl-model]
Jethanandani, M., Huang, L., Agarwal, S., and D. Blair, Jethanandani, M., Huang, L., Agarwal, S., and D. Blair,
"Network Access Control List (ACL) YANG Data Model", "Network Access Control List (ACL) YANG Data Model",
draft-ietf-netmod-acl-model-14 (work in progress), October draft-ietf-netmod-acl-model-16 (work in progress),
2017. February 2018.
[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-04 (work in progress), ietf-netmod-yang-tree-diagrams-06 (work in progress),
December 2017. February 2018.
[RFC3022] Srisuresh, P. and K. Egevang, "Traditional IP Network [RFC3022] Srisuresh, P. and K. Egevang, "Traditional IP Network
Address Translator (Traditional NAT)", RFC 3022, Address Translator (Traditional NAT)", RFC 3022,
DOI 10.17487/RFC3022, January 2001, DOI 10.17487/RFC3022, January 2001,
<https://www.rfc-editor.org/info/rfc3022>. <https://www.rfc-editor.org/info/rfc3022>.
[RFC6087] Bierman, A., "Guidelines for Authors and Reviewers of YANG [RFC6087] Bierman, A., "Guidelines for Authors and Reviewers of YANG
Data Model Documents", RFC 6087, DOI 10.17487/RFC6087, Data Model Documents", RFC 6087, DOI 10.17487/RFC6087,
January 2011, <https://www.rfc-editor.org/info/rfc6087>. January 2011, <https://www.rfc-editor.org/info/rfc6087>.
 End of changes. 30 change blocks. 
48 lines changed or deleted 89 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/