idnits 2.17.1
draft-faq-netmod-cpe-yang-profile-01.txt:
Checking boilerplate required by RFC 5378 and the IETF Trust (see
https://trustee.ietf.org/license-info):
----------------------------------------------------------------------------
No issues found here.
Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
----------------------------------------------------------------------------
No issues found here.
Checking nits according to https://www.ietf.org/id-info/checklist :
----------------------------------------------------------------------------
No issues found here.
Miscellaneous warnings:
----------------------------------------------------------------------------
== The copyright year in the IETF Trust and authors Copyright Line does not
match the current year
== The document seems to lack the recommended RFC 2119 boilerplate, even if
it appears to use RFC 2119 keywords.
(The document does seem to have the reference to RFC 2119 which the
ID-Checklist requires).
-- The document date (March 13, 2017) is 2601 days in the past. Is this
intentional?
Checking references for intended status: Informational
----------------------------------------------------------------------------
== Unused Reference: 'I-D.ietf-netconf-call-home' is defined on line 566,
but no explicit reference was found in the text
== Unused Reference: 'I-D.ietf-netconf-server-model' is defined on line
576, but no explicit reference was found in the text
== Unused Reference: 'RFC2119' is defined on line 647, but no explicit
reference was found in the text
== Unused Reference: 'RFC7659' is defined on line 686, but no explicit
reference was found in the text
== Outdated reference: A later version (-25) exists of
draft-ietf-dhc-dhcpv6-yang-03
== Outdated reference: A later version (-42) exists of
draft-ietf-isis-yang-isis-cfg-15
== Outdated reference: A later version (-36) exists of
draft-ietf-netconf-netconf-client-server-01
== Outdated reference: A later version (-29) exists of
draft-ietf-netconf-zerotouch-12
== Outdated reference: A later version (-21) exists of
draft-ietf-netmod-acl-model-10
== Outdated reference: A later version (-13) exists of
draft-ietf-netmod-intf-ext-yang-04
== Outdated reference: A later version (-10) exists of
draft-ietf-netmod-sub-intf-vlan-model-00
== Outdated reference: A later version (-15) exists of
draft-ietf-pim-igmp-mld-yang-03
== Outdated reference: A later version (-17) exists of
draft-ietf-pim-yang-07
== Outdated reference: A later version (-17) exists of
draft-ietf-softwire-dslite-yang-02
== Outdated reference: A later version (-16) exists of
draft-ietf-softwire-yang-01
== Outdated reference: A later version (-07) exists of
draft-liu-dhc-dhcp-yang-model-06
== Outdated reference: A later version (-07) exists of
draft-sivakumar-yang-nat-05
** Obsolete normative reference: RFC 7223 (Obsoleted by RFC 8343)
** Obsolete normative reference: RFC 7277 (Obsoleted by RFC 8344)
** Obsolete normative reference: RFC 8022 (Obsoleted by RFC 8349)
Summary: 3 errors (**), 0 flaws (~~), 19 warnings (==), 1 comment (--).
Run idnits with the --verbose option for more detailed information about
the items above.
--------------------------------------------------------------------------------
2 NETMOD WG I. Farrer
3 Internet-Draft Q. Sun
4 Intended status: Informational S. Zoric
5 Expires: September 14, 2017 Deutsche Telekom AG
6 M. Abrahamsson
7 T-Systems
8 March 13, 2017
10 YANG Models Required for Managing Residential Gateway (RG) Devices
11 draft-faq-netmod-cpe-yang-profile-01
13 Abstract
15 This document collects together the set of YANG models necessary for
16 managing NETCONF-enabled Residential Gateway (RG) devices.
18 Status of This Memo
20 This Internet-Draft is submitted in full conformance with the
21 provisions of BCP 78 and BCP 79.
23 Internet-Drafts are working documents of the Internet Engineering
24 Task Force (IETF). Note that other groups may also distribute
25 working documents as Internet-Drafts. The list of current Internet-
26 Drafts is at http://datatracker.ietf.org/drafts/current/.
28 Internet-Drafts are draft documents valid for a maximum of six months
29 and may be updated, replaced, or obsoleted by other documents at any
30 time. It is inappropriate to use Internet-Drafts as reference
31 material or to cite them other than as "work in progress."
33 This Internet-Draft will expire on September 14, 2017.
35 Copyright Notice
37 Copyright (c) 2017 IETF Trust and the persons identified as the
38 document authors. All rights reserved.
40 This document is subject to BCP 78 and the IETF Trust's Legal
41 Provisions Relating to IETF Documents
42 (http://trustee.ietf.org/license-info) in effect on the date of
43 publication of this document. Please review these documents
44 carefully, as they describe your rights and restrictions with respect
45 to this document. Code Components extracted from this document must
46 include Simplified BSD License text as described in Section 4.e of
47 the Trust Legal Provisions and are provided without warranty as
48 described in the Simplified BSD License.
50 Table of Contents
52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
53 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
54 3. Management Requirements . . . . . . . . . . . . . . . . . . . 3
55 3.1. General Requirements . . . . . . . . . . . . . . . . . . 3
56 3.1.1. Requirements . . . . . . . . . . . . . . . . . . . . 4
57 3.1.2. Development Status of Relevant YANG Models . . . . . 4
58 3.2. Interfaces . . . . . . . . . . . . . . . . . . . . . . . 4
59 3.2.1. Requirements . . . . . . . . . . . . . . . . . . . . 4
60 3.2.2. Development Status of Relevant YANG Models . . . . . 5
61 3.3. IP Management . . . . . . . . . . . . . . . . . . . . . . 5
62 3.3.1. Requirements . . . . . . . . . . . . . . . . . . . . 5
63 3.3.2. Development Status of Relevant YANG Models . . . . . 6
64 3.4. Routing and Multicast Management . . . . . . . . . . . . 6
65 3.4.1. Requirements . . . . . . . . . . . . . . . . . . . . 6
66 3.4.2. Development of Relevant YANG Models . . . . . . . . . 6
67 3.5. RG NETCONF Server Management . . . . . . . . . . . . . . 7
68 3.5.1. Requirements . . . . . . . . . . . . . . . . . . . . 7
69 3.5.2. Development Status of Relevant YANG Models . . . . . 7
70 3.6. DHCP/SLAAC/ND Management . . . . . . . . . . . . . . . . 7
71 3.6.1. Requirements . . . . . . . . . . . . . . . . . . . . 7
72 3.6.2. Development Status of Relevant YANG Models . . . . . 8
73 3.7. NAT Management . . . . . . . . . . . . . . . . . . . . . 8
74 3.7.1. Requirements . . . . . . . . . . . . . . . . . . . . 8
75 3.7.2. Development Status of Relevant YANG Models . . . . . 9
76 3.8. IPv6 Transition Mechanisms Management . . . . . . . . . . 9
77 3.8.1. Requirements . . . . . . . . . . . . . . . . . . . . 9
78 3.8.2. Development of Relevant YANG Models . . . . . . . . . 9
79 3.9. Management of Specific Services . . . . . . . . . . . . . 10
80 3.9.1. Requirements . . . . . . . . . . . . . . . . . . . . 10
81 3.9.2. Development of Relevant YANG Models . . . . . . . . . 10
82 3.10. Management of Security Components . . . . . . . . . . . . 10
83 3.10.1. Requirements . . . . . . . . . . . . . . . . . . . . 10
84 3.10.2. Development of Relevant YANG Models . . . . . . . . 11
85 3.11. Remote RG Software Upgrade . . . . . . . . . . . . . . . 11
86 3.11.1. Requirements . . . . . . . . . . . . . . . . . . . . 11
87 3.11.2. Development of Relevant YANG Models . . . . . . . . 11
88 4. Security Considerations . . . . . . . . . . . . . . . . . . . 12
89 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
90 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
91 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
92 7.1. Normative References . . . . . . . . . . . . . . . . . . 12
93 7.2. Informative References . . . . . . . . . . . . . . . . . 15
94 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
96 1. Introduction
98 This document defines the requirements and specifies the necessary
99 YANG models for managing RG devices using NETCONF [RFC6241] and YANG
100 [RFC6020]. Implementing NETCONF on RG devices, along with the
101 relevant YANG models, provides operators with a flexible and
102 extensible management interface.
104 Many of the YANG models referenced here are in various stages in the
105 development process. In some cases there is currently no existing
106 work. The aim of this document is to catalog which models are
107 necessary, and for each referenced YANG model, provide information
108 about the current status of the existing work. It is intended as a
109 'living document', which will be updated as the required / referenced
110 YANG models progress. Once finalised, the goal of the document is to
111 serve as a RG YANG 'Device profile' that can be used as a reference
112 for operators and implementors who are adding YANG management
113 capabilities to their devices.
115 2. Terminology
117 RG Residential Gateway; provides access between a
118 customer's LAN connected devices and their ISP's
119 network. In the context of this document, the RG
120 device implements NETCONF/YANG. This document
121 focuses on the type of Residential Gateway that
122 typically exists between the Internet Service
123 Provider access line and residential customer home,
124 performing functions such as those described in
125 [RFC7084].
126 Existing RFCs Lists YANG models defined in published RFCs.
127 Work In Progress YANG models under development in active Internet
128 Drafts, or relevant documents being produced by
129 SDOs other than the IETF.
130 To Be Defined YANG models that are identified as necessary for RG
131 management, but are not currently known to be in
132 development at the time of writing.
134 3. Management Requirements
136 3.1. General Requirements
138 The following requirements are necessary for basic RG hardware
139 management.
141 3.1.1. Requirements
143 GEN-1 The RG YANG implementation MUST provide a model for the
144 management of hardware.
146 3.1.2. Development Status of Relevant YANG Models
148 Existing RFCs:
150 o None
152 Work In Progress:
154 o A YANG Data Model for Hardware Management:
155 [I-D.han-netmod-intf-ext-ppp-yang]
157 To Be Defined (and SDOs that might be responsible for the standards)
159 o None
161 3.2. Interfaces
163 A RG has a number of network interfaces, usually including some of
164 the following interface types: Ethernet LAN, Ethernet WAN, Ethernet
165 802.1q, Ethernet 802.1ag, and WLAN (802.11a/b/n/g/ac). [RFC7223]
166 defines a YANG model for general interface management, which
167 identifies these (and other) interface types.
169 NB - The list of interface types necessary for a complete, general
170 HGW model needs to include xDSL (BBF) and DOCSIS (ITU) interfaces.
171 These will be included in a future version of this document.
173 3.2.1. Requirements
175 The following requirements are necessary for basic RG interface
176 management functionality.
178 INT-1: The RG YANG implementation MUST implement general interface
179 management.
180 INT-2: The RG YANG implementation MUST enable the configuration and
181 management (incl operational information) for the following
182 interface types:
183 o Ethernet LAN
184 o Ethernet 802.1q
185 o Ethernet 802.1ag (including Ethernet CFM)
186 o Ethernet WAN
187 o WLAN (802.11a/b/n/g/ac)
189 INT-3: The RG YANG implementation MUST provide support for optical
190 parameter configuration for the Ethernet WAN interface YANG
191 model.
192 INT-4 The RG YANG implementation MUST provide a model for the
193 management of hardware.
195 3.2.2. Development Status of Relevant YANG Models
197 Existing RFCs:
199 o YANG Data Model for Interface Management [RFC7223].
200 o IANA Interface Type YANG Module [RFC7224].
202 Work In Progress:
204 o IEEE 802.1q YANG Model [IEEE-ETH-YANG]
205 o Interface VLAN YANG Data Models:
206 [I-D.ietf-netmod-sub-intf-vlan-model].
207 o Common Interface Extension YANG Data Models:
208 [I-D.ietf-netmod-intf-ext-yang]
209 o YANG Model for the PPP Protocol:
210 [I-D.han-netmod-intf-ext-ppp-yang]
211 o A YANG Data Model for Hardware Management:
212 [I-D.han-netmod-intf-ext-ppp-yang]
214 To Be Defined (and SDOs that might be responsible for the standards)
216 o Ethernet WAN (IEEE/BBF)
217 o Ethernet 802.1ag (IEEE)
218 o Ethernet LAN (IEEE/BBF)
219 o WLAN (802.11a/b/n/g/ac) (IEEE/WFA/BBF)
221 3.3. IP Management
223 3.3.1. Requirements
225 The following requirements are necessary for the management and
226 configuration of IPv4 and IPv6.
228 IP-1: The RG YANG implementation MUST enable the configuration and
229 management of IPv4 addresses and associated parameters on L3
230 interfaces.
231 IP-2: The RG YANG implementation MUST enable the configuration and
232 management of IPv6 addresses and associated parameters on L3
233 interfaces.
234 IP-3 The RG YANG implementation MUST allow for the configuration of
235 differentiated services [RFC2474] related parameters on its
236 interfaces.
238 3.3.2. Development Status of Relevant YANG Models
240 Existing RFCs:
242 o YANG Data Model for IP Management [RFC7277].
244 Work In Progress:
246 o YANG Model for DiffServ: [I-D.asechoud-netmod-diffserv-model].
248 To Be Defined:
250 o None
252 3.4. Routing and Multicast Management
254 3.4.1. Requirements
256 The following requirements are necessary for routing management.
258 ROUT-1: The RG YANG implementation MUST provide support for the
259 configuration and management of relevant IPv4/IPv6 dynamic
260 routing protocols (for instance the ones relevant to IETF
261 HOMENET WG).
262 ROUT-2: The RG YANG implementation MUST include YANG models for the
263 management of static IPv4/IPv6 routes.
264 ROUT-3: The RG YANG implementation MUST provide support for the
265 management of Protocol Independent Multicast (PIM).
266 ROUT-4: The RG YANG implementation MUST provide support for the
267 management of static multicast routes.
269 3.4.2. Development of Relevant YANG Models
271 Existing RFCs:
273 o None
275 Work In Progress:
277 o YANG Data Model for Routing Management: [RFC8022].
278 o YANG model for static IPv4/IPv6 route: Appendix B in [RFC8022].
279 o YANG Data Model for ISIS protocol: [I-D.ietf-isis-yang-isis-cfg].
280 o YANG model for PIM: [I-D.ietf-pim-yang].
281 o YANG model for IGMP and MLD: [I-D.ietf-pim-igmp-mld-yang].
283 To Be Defined:
285 o Static Multicast Route
286 o What is the HOMENET relevant dynamic routing protocol(s).
288 3.5. RG NETCONF Server Management
290 3.5.1. Requirements
292 The following requirements are necessary for management of the RG's
293 NETCONF Server.
295 NETCONF-1: The RG YANG implementation MUST provide support for
296 management and configuration of its local NETCONF server
297 using the NETCONF protocol.
298 NETCONF-2: The RG YANG implementation MUST provide support for the
299 base notification function in order to allow a NETCONF
300 client to retrieve notifications for common system
301 events.
302 NETCONF-3: The RG YANG implementation MUST be able to retrieve
303 NETCONF server configuration automatically during the
304 bootstrap process (ZeroTouch).
305 NETCONF-4: The RG YANG implementation as a NETCONF server MUST
306 provide support for the Call Home function so that a
307 secure connection to a NETCONF client can be initiated.
309 3.5.2. Development Status of Relevant YANG Models
311 Existing RFCs:
313 o YANG Module for NETCONF Monitoring: [RFC6022].
314 o NETCONF Base Notifications: [RFC6470].
316 Work In Progress:
318 o ZeroTouch: [I-D.ietf-netconf-zerotouch].
319 o NETCONF Call Home: [RFC8071].
320 o NETCONF Server Configuration Models:
321 [I-D.ietf-netconf-netconf-client-server].
323 To Be Defined:
325 o None
327 3.6. DHCP/SLAAC/ND Management
329 3.6.1. Requirements
331 The following requirements are necessary for management of DHCP,
332 SLAAC and ND.
334 V6CONF-1: The RG YANG implementation MUST provide support for
335 management of its DHCPv4 server, which typically runs at
336 the IPv4 LAN side.
337 V6CONF-2: The RG YANG implementation MUST provide support for the
338 management of its DHCPv6 server, which can run at the IPv6
339 LAN side.
340 V6CONF-3: The RG YANG implementation MUST provide support for the
341 management of its DHCPv6 client, which typically runs at
342 the IPv6 WAN side.
343 V6CONF-4: The RG YANG implementation MUST provide support for the
344 management of its DHCPv6 Prefix Delegation configuration
345 (as a requesting router).
346 V6CONF-5: The RG YANG implementation MUST provide support for the
347 management of SLAAC for stateless IPv6 configuration (as
348 router on its LAN interfaces).
350 3.6.2. Development Status of Relevant YANG Models
352 Existing RFCs:
354 o IPv6 Router Advertisements: [RFC8022]
356 Work In Progress:
358 o YANG Data Model for DHCPv4 Configuration:
359 [I-D.liu-dhc-dhcp-yang-model].
360 o YANG Data Model for DHCPv6 Configuration:
361 [I-D.ietf-dhc-dhcpv6-yang].
363 To Be Defined:
365 o YANG model for SLAAC (Router Advertisement). (IETF)
366 o YANG model for Neighbour Discovery Protocol (NDP). (IETF)
367 o YANG model for DHCPv6 Prefix Delegation (requesting router).
368 (IETF)
369 o YANG model for IPCP. (IETF)
370 o YANG model for IPv6CP. (IETF)
372 3.7. NAT Management
374 3.7.1. Requirements
376 The following requirements are necessary for NAT Management.
378 NAT-1: The RG YANG implementation MUST provide support for
379 management of NAT44 configuration, as well as NAPT44
380 configuration.
382 3.7.2. Development Status of Relevant YANG Models
384 Existing RFCs:
386 o None
388 Work In Progress:
390 o YANG Data Model for NAT44 and stateful NAT64 function
391 [I-D.sivakumar-yang-nat].
393 To Be Defined:
395 o None
397 3.8. IPv6 Transition Mechanisms Management
399 3.8.1. Requirements
401 The following requirements are necessary for management of IPv6
402 Transition Mechanisms.
404 TRAN-2: The RG YANG implementation must include configuration and
405 management for 6rd [RFC5969].
406 TRAN-2: The RG YANG implementation must include configuration and
407 management for DS-Lite [RFC6333].
408 TRAN-3: The RG YANG implementation must include configuration and
409 management for Lightweight 4over6 [RFC7596].
410 TRAN-4: The RG YANG implementation must include configuration and
411 management for MAP-E [RFC7597].
412 TRAN-5: The RG YANG implementation must include configuration and
413 management for MAP-T [RFC7599].
415 3.8.2. Development of Relevant YANG Models
417 Existing RFCs:
419 o None
421 Work In Progress:
423 o YANG model for IPv4-in-IPv6 Softwire: [I-D.ietf-softwire-yang].
424 o YANG Data Model for the DS-Lite Address Family Transition Router
425 (AFTR): [I-D.ietf-softwire-dslite-yang].
427 To Be Defined:
429 o YANG model for 6rd. (IETF)
430 o DHCP 4o6 client: May be combined in DHCPv6 YANG model as a
431 feature. (IETF)
432 o DNS64. (IETF)
433 o Stateless NAT64 (required for MAP-T and 464xlat). (IETF)
435 3.9. Management of Specific Services
437 3.9.1. Requirements
439 The following requirements are necessary for management of specific
440 services which the RG may offer.
442 SERVICE-1: The RG YANG implementation MUST provide support for the
443 management of a SIP client.
444 SERVICE-2: The RG YANG implementation MUST provide support for the
445 management of a the RG Web server (used to provide a
446 local management interface).
447 SERVICE-3: The RG YANG implementation MUST provide support for the
448 management of an NTP client and server.
449 SERVICE-4: The RG YANG implementation MUST provide support for the
450 management of the SSH server.
452 3.9.2. Development of Relevant YANG Models
454 Existing RFCs:
456 o NTP Client: [RFC7317]
458 Work In Progress:
460 o None
462 To Be Defined:
464 o SIP/VoIP Client. (IETF)
465 o Web server, used by the customer for configuring their RG. (?)
466 o NTP server. (IETF)
467 o SSH server. (IETF)
469 3.10. Management of Security Components
471 3.10.1. Requirements
473 The following requirements are necessary for management of security
474 components.
476 SEC-1: The RG YANG implementation MUST provide support for the
477 management of IPv4 firewall and ACL functions.
479 SEC-1: The RG YANG implementation MUST provide support for the
480 management of IPv6 firewall and ACL functions.
482 3.10.2. Development of Relevant YANG Models
484 Existing RFCs:
486 o None
488 Work In Progress:
490 o IPv4 Firewall configuration: [I-D.ietf-netmod-acl-model]
491 o IPv6 Firewall configuration: [I-D.ietf-netmod-acl-model]
492 o Access Control List (ACL): [I-D.ietf-netmod-acl-model]
494 To Be Defined:
496 o IPv4/v6 Firewall (if needed in addition to the above) (IETF?)
497 o Parental controls (?)
499 3.11. Remote RG Software Upgrade
501 3.11.1. Requirements
503 The following requirements are necessary to perform remote RG
504 Software file transfer and software upgrades.
506 SWUPG-1: The RG implementation must provide a YANG model for the
507 upgrade of firmware and software packages in order to fix
508 bugs, enable new features, and resolve security issues.
509 SWUPG-2: The RG YANG implementation MUST enable RPCs for file
510 transfer in order to retrieve files from an operator-
511 managed data centre, or upload logging.
513 3.11.2. Development of Relevant YANG Models
515 Existing RFCs:
517 o None
519 Work In Progress:
521 o File transfer: [I-D.sf-netmod-file-transfer-yang]
523 To Be Defined:
525 o YANG model for firmware upgrade RPCs. (BBF?)
527 4. Security Considerations
529 A NETCONF/YANG managed RG should follow the Section 3.10 for enabling
530 and managing IPv4/IPv6 firewalls. Security considerations from the
531 related documents should be followed.
533 5. IANA Considerations
535 There are no IANA considerations for this document.
537 6. Acknowledgements
539 The authors would like to thank xxx for their contributions to this
540 work.
542 7. References
544 7.1. Normative References
546 [I-D.asechoud-netmod-diffserv-model]
547 Choudhary, A., Shah, S., Jethanandani, M., Liu, B., and N.
548 Strahle, "YANG Model for Diffserv", draft-asechoud-netmod-
549 diffserv-model-03 (work in progress), June 2015.
551 [I-D.han-netmod-intf-ext-ppp-yang]
552 Han, H., Gu, X., Lv, H., and J. Zhang, "Yang Data Model
553 for PPP Protocol", draft-han-netmod-intf-ext-ppp-yang-02
554 (work in progress), February 2017.
556 [I-D.ietf-dhc-dhcpv6-yang]
557 Cui, Y., Wang, H., Sun, L., Lemon, T., Farrer, I., and S.
558 Zoric, "YANG Data Model for DHCPv6 Configuration", draft-
559 ietf-dhc-dhcpv6-yang-03 (work in progress), June 2016.
561 [I-D.ietf-isis-yang-isis-cfg]
562 Litkowski, S., Yeung, D., Lindem, A., Zhang, Z., and L.
563 Lhotka, "YANG Data Model for IS-IS protocol", draft-ietf-
564 isis-yang-isis-cfg-15 (work in progress), February 2017.
566 [I-D.ietf-netconf-call-home]
567 Watsen, K., "NETCONF Call Home and RESTCONF Call Home",
568 draft-ietf-netconf-call-home-17 (work in progress),
569 December 2015.
571 [I-D.ietf-netconf-netconf-client-server]
572 Watsen, K., Wu, G., and J. Schoenwaelder, "NETCONF Client
573 and Server Models", draft-ietf-netconf-netconf-client-
574 server-01 (work in progress), November 2016.
576 [I-D.ietf-netconf-server-model]
577 Watsen, K. and J. Schoenwaelder, "NETCONF Server and
578 RESTCONF Server Configuration Models", draft-ietf-netconf-
579 server-model-09 (work in progress), March 2016.
581 [I-D.ietf-netconf-zerotouch]
582 Watsen, K. and M. Abrahamsson, "Zero Touch Provisioning
583 for NETCONF or RESTCONF based Management", draft-ietf-
584 netconf-zerotouch-12 (work in progress), January 2017.
586 [I-D.ietf-netmod-acl-model]
587 Bogdanovic, D., Koushik, K., Huang, L., and D. Blair,
588 "Network Access Control List (ACL) YANG Data Model",
589 draft-ietf-netmod-acl-model-10 (work in progress), March
590 2017.
592 [I-D.ietf-netmod-intf-ext-yang]
593 Wilton, R., Ball, D., tsingh@juniper.net, t., and S.
594 Sivaraj, "Common Interface Extension YANG Data Models",
595 draft-ietf-netmod-intf-ext-yang-04 (work in progress),
596 March 2017.
598 [I-D.ietf-netmod-sub-intf-vlan-model]
599 Wilton, R., Ball, D., tapsingh@cisco.com, t., and S.
600 Sivaraj, "Sub-interface VLAN YANG Data Models", draft-
601 ietf-netmod-sub-intf-vlan-model-00 (work in progress),
602 February 2017.
604 [I-D.ietf-pim-igmp-mld-yang]
605 Liu, X., Guo, F., Sivakumar, M., McAllister, P., and A.
606 Peter, "A YANG data model for Internet Group Management
607 Protocol (IGMP) and Multicast Listener Discovery (MLD)",
608 draft-ietf-pim-igmp-mld-yang-03 (work in progress), March
609 2017.
611 [I-D.ietf-pim-yang]
612 Liu, X., McAllister, P., Peter, A., Sivakumar, M., Liu,
613 Y., and f. hu, "A YANG data model for Protocol-Independent
614 Multicast (PIM)", draft-ietf-pim-yang-07 (work in
615 progress), March 2017.
617 [I-D.ietf-softwire-dslite-yang]
618 Boucadair, M., Jacquenet, C., and S. Sivakumar, "A YANG
619 Data Model for the DS-Lite", draft-ietf-softwire-dslite-
620 yang-02 (work in progress), January 2017.
622 [I-D.ietf-softwire-yang]
623 Sun, Q., Wang, H., Cui, Y., Farrer, I., Zoric, S.,
624 Boucadair, M., and R. Asati, "A YANG Data Model for IPv4-
625 in-IPv6 Softwires", draft-ietf-softwire-yang-01 (work in
626 progress), October 2016.
628 [I-D.liu-dhc-dhcp-yang-model]
629 Liu, B., Lou, K., and C. Chen, "Yang Data Model for DHCP
630 Protocol", draft-liu-dhc-dhcp-yang-model-06 (work in
631 progress), March 2017.
633 [I-D.sf-netmod-file-transfer-yang]
634 Sun, Q. and I. Farrer, "A YANG Data Model for Transferring
635 Files", draft-sf-netmod-file-transfer-yang-00 (work in
636 progress), March 2015.
638 [I-D.sivakumar-yang-nat]
639 Sivakumar, S., Boucadair, M., and S. <>, "YANG Data Model
640 for Network Address Translation (NAT)", draft-sivakumar-
641 yang-nat-05 (work in progress), September 2016.
643 [IEEE-ETH-YANG]
644 "IEEE 802.1q YANG Model",
645 .
647 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
648 Requirement Levels", BCP 14, RFC 2119,
649 DOI 10.17487/RFC2119, March 1997,
650 .
652 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
653 the Network Configuration Protocol (NETCONF)", RFC 6020,
654 DOI 10.17487/RFC6020, October 2010,
655 .
657 [RFC6022] Scott, M. and M. Bjorklund, "YANG Module for NETCONF
658 Monitoring", RFC 6022, DOI 10.17487/RFC6022, October 2010,
659 .
661 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
662 and A. Bierman, Ed., "Network Configuration Protocol
663 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
664 .
666 [RFC6470] Bierman, A., "Network Configuration Protocol (NETCONF)
667 Base Notifications", RFC 6470, DOI 10.17487/RFC6470,
668 February 2012, .
670 [RFC7223] Bjorklund, M., "A YANG Data Model for Interface
671 Management", RFC 7223, DOI 10.17487/RFC7223, May 2014,
672 .
674 [RFC7224] Bjorklund, M., "IANA Interface Type YANG Module",
675 RFC 7224, DOI 10.17487/RFC7224, May 2014,
676 .
678 [RFC7277] Bjorklund, M., "A YANG Data Model for IP Management",
679 RFC 7277, DOI 10.17487/RFC7277, June 2014,
680 .
682 [RFC7317] Bierman, A. and M. Bjorklund, "A YANG Data Model for
683 System Management", RFC 7317, DOI 10.17487/RFC7317, August
684 2014, .
686 [RFC7659] Perreault, S., Tsou, T., Sivakumar, S., and T. Taylor,
687 "Definitions of Managed Objects for Network Address
688 Translators (NATs)", RFC 7659, DOI 10.17487/RFC7659,
689 October 2015, .
691 [RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing
692 Management", RFC 8022, DOI 10.17487/RFC8022, November
693 2016, .
695 [RFC8071] Watsen, K., "NETCONF Call Home and RESTCONF Call Home",
696 RFC 8071, DOI 10.17487/RFC8071, February 2017,
697 .
699 7.2. Informative References
701 [RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black,
702 "Definition of the Differentiated Services Field (DS
703 Field) in the IPv4 and IPv6 Headers", RFC 2474,
704 DOI 10.17487/RFC2474, December 1998,
705 .
707 [RFC5969] Townsley, W. and O. Troan, "IPv6 Rapid Deployment on IPv4
708 Infrastructures (6rd) -- Protocol Specification",
709 RFC 5969, DOI 10.17487/RFC5969, August 2010,
710 .
712 [RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual-
713 Stack Lite Broadband Deployments Following IPv4
714 Exhaustion", RFC 6333, DOI 10.17487/RFC6333, August 2011,
715 .
717 [RFC7084] Singh, H., Beebee, W., Donley, C., and B. Stark, "Basic
718 Requirements for IPv6 Customer Edge Routers", RFC 7084,
719 DOI 10.17487/RFC7084, November 2013,
720 .
722 [RFC7596] Cui, Y., Sun, Q., Boucadair, M., Tsou, T., Lee, Y., and I.
723 Farrer, "Lightweight 4over6: An Extension to the Dual-
724 Stack Lite Architecture", RFC 7596, DOI 10.17487/RFC7596,
725 July 2015, .
727 [RFC7597] Troan, O., Ed., Dec, W., Li, X., Bao, C., Matsushima, S.,
728 Murakami, T., and T. Taylor, Ed., "Mapping of Address and
729 Port with Encapsulation (MAP-E)", RFC 7597,
730 DOI 10.17487/RFC7597, July 2015,
731 .
733 [RFC7599] Li, X., Bao, C., Dec, W., Ed., Troan, O., Matsushima, S.,
734 and T. Murakami, "Mapping of Address and Port using
735 Translation (MAP-T)", RFC 7599, DOI 10.17487/RFC7599, July
736 2015, .
738 Authors' Addresses
740 Ian Farrer
741 Deutsche Telekom AG
742 CTO-ATI, Landgrabenweg 151
743 Bonn, NRW 53227
744 Germany
746 Email: ian.farrer@telekom.de
748 Qi Sun
749 Deutsche Telekom AG
750 CTO-ATI, Landgrabenweg 151
751 Bonn, NRW 53227
752 Germany
754 Email: sunqi.ietf@gmail.com
756 Sladjana Zoric
757 Deutsche Telekom AG
758 CTO-ATI, Landgrabenweg 151
759 Bonn, NRW 53227
760 Germany
762 Email: sladjana.zoric@telekom.de
763 Mikael Abrahamsson
764 T-Systems
766 Email: mikael.abrahamsson@t-systems.se