draft-ietf-softwire-dslite-yang-05.txt   draft-ietf-softwire-dslite-yang-06.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: February 11, 2018 S. Sivakumar Expires: February 22, 2018 S. Sivakumar
Cisco Systems Cisco Systems
August 10, 2017 August 21, 2017
YANG Data Models for the DS-Lite YANG Data Models for the DS-Lite
draft-ietf-softwire-dslite-yang-05 draft-ietf-softwire-dslite-yang-06
Abstract Abstract
This document defines YANG data models for the DS-Lite Address Family This document defines YANG data models for the DS-Lite Address Family
Transition Router (AFTR) and Basic Bridging BroadBand (B4) elements . Transition Router (AFTR) and Basic Bridging BroadBand (B4) elements .
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.
skipping to change at page 1, line 33 skipping to change at page 1, line 33
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 February 11, 2018. This Internet-Draft will expire on February 22, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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 19 skipping to change at page 2, line 19
1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 4 1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 4
2. DS-Lite YANG Data Models . . . . . . . . . . . . . . . . . . 4 2. DS-Lite YANG Data Models . . . . . . . . . . . . . . . . . . 4
3. DS-Lite AFTR YANG Module . . . . . . . . . . . . . . . . . . 6 3. DS-Lite AFTR YANG Module . . . . . . . . . . . . . . . . . . 6
4. DS-Lite B4 YANG Module . . . . . . . . . . . . . . . . . . . 12 4. DS-Lite B4 YANG Module . . . . . . . . . . . . . . . . . . . 12
5. Security Considerations . . . . . . . . . . . . . . . . . . . 14 5. Security Considerations . . . . . . . . . . . . . . . . . . . 14
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
8.1. Normative references . . . . . . . . . . . . . . . . . . 15 8.1. Normative references . . . . . . . . . . . . . . . . . . 15
8.2. Informative references . . . . . . . . . . . . . . . . . 16 8.2. Informative references . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction 1. Introduction
This document defines data models for DS-Lite [RFC6333], using the This document defines data models for DS-Lite [RFC6333], using the
YANG data modeling language [RFC6020]. Both the Address Family YANG data modeling language [RFC6020]. 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. As a reminder, Figure 1 are covered by this specification. As a reminder, Figure 1
illustrates an overview of the DS-Lite architecture that involves illustrates an overview of the DS-Lite architecture that involves
AFTR and B4 elements. AFTR and B4 elements.
skipping to change at page 5, line 5 skipping to change at page 5, line 5
As shown in Figure 1: As shown in Figure 1:
o The AFTR element is a combination of an IPv4-in-IPv6 o The AFTR element is a combination of an IPv4-in-IPv6
encapsualtion/decapsulation function and a NAT function. encapsualtion/decapsulation function and a NAT function.
o The B4 element is an IPv4-in-IPv6 encapsulation function. o The B4 element is an IPv4-in-IPv6 encapsulation function.
Therefore, the AFTR YANG module is designed to augment both the Therefore, the AFTR YANG module is designed to augment both the
Interfaces YANG module [RFC7223] and the NAT YANG module Interfaces YANG module [RFC7223] and the NAT YANG module
[I-D.sivakumar-yang-nat] with DS-Lite specific features. The B4 YANG [I-D.ietf-opsawg-nat-yang] with DS-Lite specific features. The B4
module augments the interfaces YANG module. YANG module augments the interfaces YANG module.
This document assumes [RFC4787][RFC5382][RFC5508] are enabled by This document assumes [RFC4787][RFC5382][RFC5508] are enabled by
default. Also, the data model adheres to the recommendations in default. Also, the data model adheres to the recommendations in
[RFC6888] and [RFC7857]. Furthermore, the data model supports state [RFC6888] and [RFC7857]. Furthermore, the data model supports state
migration as per [RFC7785]. migration as per [RFC7785].
PCP-related considerations are out of scope of the document. A YANG PCP-related considerations are out of scope of the document. A YANG
data model for PCP is documented in [I-D.boucadair-pcp-yang]. data model for PCP is documented in [I-D.boucadair-pcp-yang].
module: ietf-dslite-aftr module: ietf-dslite-aftr
skipping to change at page 5, line 36 skipping to change at page 5, line 36
+--rw mss-clamping-enable? boolean +--rw mss-clamping-enable? boolean
+--rw mss-value? uint16 +--rw mss-value? uint16
augment /nat:nat-module/nat:nat-instances/nat:nat-instance/nat:mapping-table/nat:mapping-entry: augment /nat:nat-module/nat:nat-instances/nat:nat-instance/nat:mapping-table/nat:mapping-entry:
+--rw b4-ipv6-address? inet:ipv6-address +--rw b4-ipv6-address? inet:ipv6-address
+--rw v6-dscp? uint8 +--rw v6-dscp? uint8
+--rw internal-v4-dscp? uint8 +--rw internal-v4-dscp? uint8
+--rw external-v4-dscp? uint8 +--rw external-v4-dscp? uint8
Figure 2: YANG Data Model for DS-Lite AFTR Figure 2: YANG Data Model for DS-Lite AFTR
Examples to illustrate the use of this module are provided in
Appendix A.
A B4 instance is provided with the IPv6 address of the AFTR to use, A B4 instance is provided with the IPv6 address of the AFTR to use,
an (optional) instruction whether DSCP marking is to preserved when an (optional) instruction whether DSCP marking is to preserved when
encapsulating an IPv4 packet in an IPv6 packet, and other optional encapsulating an IPv4 packet in an IPv6 packet, and other optional
parameters shown in Figure 3. parameters shown in Figure 3.
module: ietf-dslite-b4 module: ietf-dslite-b4
augment /if:interfaces/if:interface: augment /if:interfaces/if:interface:
+--rw b4-ipv6-address? inet:ipv6-address +--rw b4-ipv6-address? inet:ipv6-address
+--rw aftr-ipv6-addr? inet:ipv6-address +--rw aftr-ipv6-addr? inet:ipv6-address
+--rw b4-ipv4-address? inet:ipv4-address +--rw b4-ipv4-address? inet:ipv4-address
skipping to change at page 15, line 47 skipping to change at page 16, line 5
7. Acknowledgements 7. Acknowledgements
Thanks to Q. Wu for identifying a compiling error. Thanks to Q. Wu for identifying a compiling error.
Many thanks to Ian Farrer for the review and comments. Many thanks to Ian Farrer for the review and comments.
8. References 8. References
8.1. Normative references 8.1. Normative references
[I-D.sivakumar-yang-nat] [I-D.ietf-opsawg-nat-yang]
Sivakumar, S., Boucadair, M., and S. Vinapamula, "YANG Boucadair, M., Sivakumar, S., Jacquenet, C., Vinapamula,
Data Model for Network Address Translation (NAT)", draft- S., and Q. Wu, "A YANG Data Model for Network Address
sivakumar-yang-nat-07 (work in progress), July 2017. Translation (NAT) and Network Prefix Translation (NPT)",
draft-ietf-opsawg-nat-yang-01 (work in progress), August
2017.
[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-
<http://www.rfc-editor.org/info/rfc3688>. editor.org/info/rfc3688>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, DOI 10.17487/RFC6020, October 2010, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc6020>. editor.org/info/rfc6020>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<http://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
[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,
<http://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,
<http://www.rfc-editor.org/info/rfc6333>. <https://www.rfc-editor.org/info/rfc6333>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536, Protocol (NETCONF) Access Control Model", RFC 6536,
DOI 10.17487/RFC6536, March 2012, DOI 10.17487/RFC6536, March 2012, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc6536>. 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,
<http://www.rfc-editor.org/info/rfc6991>. <https://www.rfc-editor.org/info/rfc6991>.
[RFC7223] Bjorklund, M., "A YANG Data Model for Interface [RFC7223] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, Management", RFC 7223, DOI 10.17487/RFC7223, May 2014,
<http://www.rfc-editor.org/info/rfc7223>. <https://www.rfc-editor.org/info/rfc7223>.
8.2. Informative references 8.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 Data Models for the Port Control Vinapamula, "YANG Data Models for the Port Control
Protocol (PCP)", draft-boucadair-pcp-yang-04 (work in Protocol (PCP)", draft-boucadair-pcp-yang-04 (work in
progress), May 2017. progress), May 2017.
[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
UDP", BCP 127, RFC 4787, DOI 10.17487/RFC4787, January UDP", BCP 127, RFC 4787, DOI 10.17487/RFC4787, January
2007, <http://www.rfc-editor.org/info/rfc4787>. 2007, <https://www.rfc-editor.org/info/rfc4787>.
[RFC5382] Guha, S., Ed., Biswas, K., Ford, B., Sivakumar, S., and P. [RFC5382] Guha, S., Ed., Biswas, K., Ford, B., Sivakumar, S., and P.
Srisuresh, "NAT Behavioral Requirements for TCP", BCP 142, Srisuresh, "NAT Behavioral Requirements for TCP", BCP 142,
RFC 5382, DOI 10.17487/RFC5382, October 2008, RFC 5382, DOI 10.17487/RFC5382, October 2008,
<http://www.rfc-editor.org/info/rfc5382>. <https://www.rfc-editor.org/info/rfc5382>.
[RFC5508] Srisuresh, P., Ford, B., Sivakumar, S., and S. Guha, "NAT [RFC5508] Srisuresh, P., Ford, B., Sivakumar, S., and S. Guha, "NAT
Behavioral Requirements for ICMP", BCP 148, RFC 5508, Behavioral Requirements for ICMP", BCP 148, RFC 5508,
DOI 10.17487/RFC5508, April 2009, DOI 10.17487/RFC5508, April 2009, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc5508>. editor.org/info/rfc5508>.
[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, <http://www.rfc-editor.org/info/rfc6087>. January 2011, <https://www.rfc-editor.org/info/rfc6087>.
[RFC6888] Perreault, S., Ed., Yamagata, I., Miyakawa, S., Nakagawa, [RFC6888] Perreault, S., Ed., Yamagata, I., Miyakawa, S., Nakagawa,
A., and H. Ashida, "Common Requirements for Carrier-Grade A., and H. Ashida, "Common Requirements for Carrier-Grade
NATs (CGNs)", BCP 127, RFC 6888, DOI 10.17487/RFC6888, NATs (CGNs)", BCP 127, RFC 6888, DOI 10.17487/RFC6888,
April 2013, <http://www.rfc-editor.org/info/rfc6888>. April 2013, <https://www.rfc-editor.org/info/rfc6888>.
[RFC6908] Lee, Y., Maglione, R., Williams, C., Jacquenet, C., and M. [RFC6908] Lee, Y., Maglione, R., Williams, C., Jacquenet, C., and M.
Boucadair, "Deployment Considerations for Dual-Stack Boucadair, "Deployment Considerations for Dual-Stack
Lite", RFC 6908, DOI 10.17487/RFC6908, March 2013, Lite", RFC 6908, DOI 10.17487/RFC6908, March 2013,
<http://www.rfc-editor.org/info/rfc6908>. <https://www.rfc-editor.org/info/rfc6908>.
[RFC7785] Vinapamula, S. and M. Boucadair, "Recommendations for [RFC7785] Vinapamula, S. and M. Boucadair, "Recommendations for
Prefix Binding in the Context of Softwire Dual-Stack Prefix Binding in the Context of Softwire Dual-Stack
Lite", RFC 7785, DOI 10.17487/RFC7785, February 2016, Lite", RFC 7785, DOI 10.17487/RFC7785, February 2016,
<http://www.rfc-editor.org/info/rfc7785>. <https://www.rfc-editor.org/info/rfc7785>.
[RFC7857] Penno, R., Perreault, S., Boucadair, M., Ed., Sivakumar, [RFC7857] Penno, R., Perreault, S., Boucadair, M., Ed., Sivakumar,
S., and K. Naito, "Updates to Network Address Translation S., and K. Naito, "Updates to Network Address Translation
(NAT) Behavioral Requirements", BCP 127, RFC 7857, (NAT) Behavioral Requirements", BCP 127, RFC 7857,
DOI 10.17487/RFC7857, April 2016, DOI 10.17487/RFC7857, April 2016, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc7857>. editor.org/info/rfc7857>.
Appendix A. Examples
The following example shows an AFTR that is reachable at 2001:db8::2.
Also, this XML snippet indicates that the AFTR is provided with an
IPv4 address (192.0.0.1) to be used for troubleshooting purposes such
as reporting problems to B4s. Moreover, the AFTR is instructed to
limit the number of softwires per subscriber to '1'.
<interface>
<name>myAFTR</name>
<type>ianaift:tunnel</type>
<enabled>true</enabled>
<aftr-ipv6-address>2001:db8::2</aftr-ipv6-address>
<aftr-ipv4-address>192.0.0.1</aftr-ipv4-address>
<max-softwire-per-subscriber>1</max-softwire-per-subscriber>
</interface>
The following shows an XML excerpt depicting a dynamic UDP mapping
entry maintained by a DS-Lite AFTR. In reference to this example,
the UDP packet received with a source IPv6 address (2001:db8::1), a
source IPv4 address (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 (15000). The lifetime of this mapping
is 300 seconds.
<mapping-entry>
<index>15</index>
<type>
dynamic-explicit
</type>
<transport-protocol>
17
</transport-protocol>
<b4-ipv6-address>
192.0.2.1
</b4-ipv6-address>
<internal-src-address>
192.0.2.1
</internal-dst-address>
<internal-src-port>
<single-port-number>
1568
</single-port-number>
</internal-dst-port>
<external-dst-address>
198.51.100.1
</external-dst-address>
<external-dst-port>
<single-port-number>
15000
</single-port-number>
</external-dst-port>
<lifetime>
300
</lifetime>
</mapping-entry>
Authors' Addresses Authors' Addresses
Mohamed Boucadair Mohamed Boucadair
Orange Orange
Rennes 35000 Rennes 35000
France France
EMail: mohamed.boucadair@orange.com EMail: mohamed.boucadair@orange.com
Christian Jacquenet Christian Jacquenet
Orange Orange
Rennes 35000 Rennes 35000
France France
EMail: christian.jacquenet@orange.com EMail: christian.jacquenet@orange.com
Senthil Sivakumar Senthil Sivakumar
Cisco Systems Cisco Systems
7100-8 Kit Creek Road 7100-8 Kit Creek Road
Research Triangle Park, North Carolina 27709 Research Triangle Park, North Carolina 27709
USA USA
Phone: +1 919 392 5158 Phone: +1 919 392 5158
EMail: ssenthil@cisco.com EMail: ssenthil@cisco.com
 End of changes. 26 change blocks. 
33 lines changed or deleted 96 lines changed or added

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