DHC Working Group Y. Cui Internet-Draft H. Wang Intended status: Standards Track L. Sun Expires: January 4, 2016 Tsinghua University T. Lemon Nominum I. Farrer Deutsche Telekom AG July 3, 2015 YANG Data Model for DHCPv6 Configuration draft-cui-dhc-dhcpv6-yang-03 Abstract There has no unified method to configure DHCPv6 server ,relay and client itself, always pre-configured manually by operators. IETF netmod WG has developed a general data model for NETCONF protocol, YANG data model [RFC6020]. This document defines a YANG data model for the configuration and management of DHCPv6 server, DHCPv6 relay and DHCPv6 client. With this model, the operators can configure and manage the devices by using NETCONF. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." Cui, et al. Expires January 4, 2016 [Page 1] Internet-Draft YANG for DHCPv6 July 2015 This Internet-Draft will expire on January 4, 2016. Copyright Notice Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 2. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. DHCPv6 server . . . . . . . . . . . . . . . . . . . . . . 4 2.2. DHCPv6 relay . . . . . . . . . . . . . . . . . . . . . . 4 2.3. DHCPv6 client . . . . . . . . . . . . . . . . . . . . . . 4 3. DHCPv6 Tree Diagrams . . . . . . . . . . . . . . . . . . . . 4 3.1. DHCPv6 Server Tree Diagrams . . . . . . . . . . . . . . . 4 3.2. DHCPv6 Relay Tree Diagrams . . . . . . . . . . . . . . . 12 3.3. DHCPv6 Client Tree Diagrams . . . . . . . . . . . . . . . 15 3.4. Notifications Mechanism for DHCPv6 . . . . . . . . . . . 20 4. DHCPv6 YANG Model . . . . . . . . . . . . . . . . . . . . . . 22 5. Security Considerations (TBD) . . . . . . . . . . . . . . . . 63 6. IANA Considerations (TBD) . . . . . . . . . . . . . . . . . . 63 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 63 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 63 8.1. Normative References . . . . . . . . . . . . . . . . . . 63 8.2. Informative References . . . . . . . . . . . . . . . . . 64 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 65 1. Introduction This document defines a YANG data model for the configuration and management of DHCPv6 server, DHCPv6 relay and DHCPv6 client. With this model, the operators can configure and manage the devices by using NETCONF. Model include three sub-modules: Cui, et al. Expires January 4, 2016 [Page 2] Internet-Draft YANG for DHCPv6 July 2015 o DHCPv6 server o DHCPv6 relay o DHCPv6 client For DHCPv6 client configuration, it is worth noting that as DHCPv6 itself a device configuration protocol, the intention of this document is not to replace client configuration of DHCPv6 options and parameters over the DHCPv6 protocol with the configuration of DHCPv6 options and parameters over NETCONF/YANG. The DHCPv6 client model is intended for the configuration of the DHCPv6 client function and also for obtaining read-only state data from the client which has been learnt via the normal DHCPv6 message flow. This gives an operator a better method for managing DHCPv6 clients and simplifies troubleshooting. 1.1. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. The reader should be familiar with the terms defined in DHCPv6 [RFC3315] and relevant documents. DHCPv6 tree diagrams provide a concise representation of a YANG module to help readers understand the module structure. The meaning if the symbols in these diagrams is as follows: o Brackets "[" and "]" enclose list keys. o Braces "{" and "}" enclose feature content. o Parentheses "(" and ")" enclose choice and case nodes, and case nodes are also marked with a colon (":"). o Symbols after data node names: "?" means an optional node, and "*" denotes a list and leaf-list. o Abbreviations before data node names: "rw" means configuration data (read-write), and "ro" means state data (read-only). 2. Objectives This document defines a YANG data model that can be used to configure and manage DHCPv6 server, DHCPv6 relay and DHCPv6 client. Cui, et al. Expires January 4, 2016 [Page 3] Internet-Draft YANG for DHCPv6 July 2015 2.1. DHCPv6 server DHCPv6 server parameters. 2.2. DHCPv6 relay DHCPv6 relay parameters. 2.3. DHCPv6 client DHCPv6 client parameters. 3. DHCPv6 Tree Diagrams 3.1. DHCPv6 Server Tree Diagrams +--rw dhcpv6 +--rw server {dhcpv6-server}? +--rw serv-attributes | +--rw name string | +--rw duid | | +--rw duid-type uint16 | | +--rw duid-high-1 uint32 | | +--rw duid-high-2 uint32 | | +--rw duid-low-1 uint32 | | +--rw duid-low-2 uint32 | +--rw enable boolean | +--rw ipv6-address inet:ipv6-address | +--rw description? string | +--rw pd-function boolean | +--rw stateless-service boolean | +--rw rapid-commit boolean | +--rw store-client-link-layer? boolean | +--rw vendor-info | +--rw ent-num uint32 | +--rw data* string +--rw option-sets | +--rw option-set* [option-set-id] | +--rw option-set-id uint8 | +--rw user-class-value? string | +--rw enterprise-number? uint32 | +--rw store-client-link-layer? boolean | +--rw preference-option | | +--rw enable boolean | | +--rw preference-value uint8 | +--rw sip-server-option | | +--rw enable boolean | | +--rw sip-server* [sip-serv-id] Cui, et al. Expires January 4, 2016 [Page 4] Internet-Draft YANG for DHCPv6 July 2015 | | +--rw sip-serv-id uint8 | | +--rw sip-serv-domain-name string | | +--rw sip-serv-addr inet:ipv6-address | +--rw dns-config-option | | +--rw enable boolean | | +--rw dns-server* [dns-serv-id] | | | +--rw dns-serv-id uint8 | | | +--rw dns-serv-addr inet:ipv6-address | | +--rw domain-search-list string | +--rw nis-config-option | | +--rw enable boolean | | +--rw nis-server* [nis-serv-id] | | +--rw nis-serv-id uint8 | | +--rw nis-serv-addr inet:ipv6-address | +--rw nis-plus-config-option | | +--rw enable boolean | | +--rw nis-plus-server* [nis-plus-serv-id] | | +--rw nis-plus-serv-id uint8 | | +--rw nis-plus-serv-addr inet:ipv6-address | +--rw info-refresh-time-option | | +--rw enable boolean | | +--rw info-refresh-time yang:timeticks | +--rw cli-fqdn-option | | +--rw enable boolean | | +--rw server-initiate-update boolean | | +--rw client-initiate-update boolean | | +--rw modify-name-from-cli boolean | +--rw timezone-option | | +--rw enable boolean | | +--rw tz-posix string | | +--rw tz-database string | +--rw ntp-server-option | | +--rw enable boolean | | +--rw ntp-server* [ntp-serv-id] | | +--rw ntp-serv-id uint8 | | +--rw ntp-serv-addr inet:ipv6-address | | +--rw ntp-serv-mul-addr inet:ipv6-address | | +--rw ntp-serv-fqdn string | +--rw sntp-server-option | | +--rw enable boolean | | +--rw sntp-server* [sntp-serv-id] | | +--rw sntp-serv-id uint8 | | +--rw sntp-serv-addr inet:ipv6-address | +--rw network-boot-option | | +--rw enable boolean | | +--rw boot-file* [boot-file-id] | | +--rw boot-file-id uint8 | | +--rw suitable-arch-type* uint16 Cui, et al. Expires January 4, 2016 [Page 5] Internet-Draft YANG for DHCPv6 July 2015 | | +--rw suitable-net-if* uint32 | | +--rw boot-file-url string | | +--rw boot-file-paras* [para-id] | | +--rw para-id uint8 | | +--rw parameter string | +--rw dslite-option | | +--rw enable boolean | | +--rw dslite-aftr-name string | +--rw kerberos-option | | +--rw enable boolean | | +--rw default-realm-name string | | +--rw kdc-info* [kdc-id] | | +--rw kdc-id uint8 | | +--rw priority uint16 | | +--rw weight uint16 | | +--rw transport-type uint8 | | +--rw port-number uint16 | | +--rw kdc-ipv6-addr inet:ipv6-address | | +--rw realm-name string | +--rw addr-selection-option | | +--rw enable boolean | | +--rw a-bit-set boolean | | +--rw p-bit-set boolean | | +--rw policy-table* [policy-id] | | +--rw policy-id uint8 | | +--rw label uint8 | | +--rw precedence uint8 | | +--rw prefix-len uint8 | | +--rw prefix inet:ipv6-prefix | +--rw sol-max-rt-option | | +--rw enable boolean | | +--rw sol-max-rt-value yang:timeticks | +--rw inf-max-rt-option | | +--rw enable boolean | | +--rw inf-max-rt-value yang:timeticks | +--rw pcp-server-option | | +--rw enable boolean | | +--rw pcp-server* [pcp-serv-id] | | +--rw pcp-serv-id uint8 | | +--rw pcp-serv-addr* inet:ipv6-address | +--rw s46-rule-option | | +--rw enable boolean | | +--rw s46-rule* [rule-id] | | +--rw rule-id uint8 | | +--rw rule-type enumeration | | +--rw ea-len uint8 | | +--rw prefix4-len uint8 | | +--rw ipv4-prefix inet:ipv4-prefix Cui, et al. Expires January 4, 2016 [Page 6] Internet-Draft YANG for DHCPv6 July 2015 | | +--rw prefix6-len uint8 | | +--rw ipv6-prefix inet:ipv6-prefix | | +--rw port-parameter | | +--rw offset uint8 | | +--rw psid-len uint8 | | +--rw psid uint16 | +--rw s46-br-option | | +--rw enable boolean | | +--rw br* [br-id] | | +--rw br-id uint8 | | +--rw br-ipv6-addr inet:ipv6-address | +--rw s46-dmr-option | | +--rw enable boolean | | +--rw dmr* [dmr-id] | | +--rw dmr-id uint8 | | +--rw dmr-prefix6-len uint8 | | +--rw dmr-ipv6-prefix inet:ipv6-prefix | +--rw s46-v4-v6-binding-option | +--rw enable boolean | +--rw ce* [ce-id] | +--rw ce-id uint8 | +--rw ipv4-addr inet:ipv4-address | +--rw bind-prefix6-len uint8 | +--rw bind-ipv6-prefix inet:ipv6-prefix | +--rw port-parameter | +--rw offset uint8 | +--rw psid-len uint8 | +--rw psid uint16 +--rw network-ranges | +--rw option-set [option-set-id] | +--rw network-range* [network-range-id] | +--rw network-range-id uint8 | +--rw network-description string | +--rw network-prefix inet:ipv6-prefix | +--rw inherit-option-set boolean | +--rw option-set [option-set-id] | +--rw address-pools | | +--rw address-pool* [pool-id] | | | +--rw pool-id uint8 | | | +--rw pool-prefix inet:ipv6-prefix | | | +--rw start-address inet:ipv6-address | | | +--rw end-address inet:ipv6-address | | | +--rw preferred-lifetime yang:timeticks | | | +--rw valid-lifetime yang:timeticks | | | +--ro total-ipv6-count uint64 | | | +--ro used-ipv6-count uint64 | | | +--rw utilization-ratio threshold | | | +--rw inherit-option-set boolean Cui, et al. Expires January 4, 2016 [Page 7] Internet-Draft YANG for DHCPv6 July 2015 | | | +--rw option-set [option-set-id] | | | +--rw reserved-addresses | | | +--rw static-binding* [cli-id] | | | | +--rw cli-id uint32 | | | | +--rw duid | | | | | +--rw duid-type uint16 | | | | | +--rw duid-high-1 uint32 | | | | | +--rw duid-high-2 uint32 | | | | | +--rw duid-low-1 uint32 | | | | | +--rw duid-low-2 uint32 | | | | +--rw reserv-addr* inet:ipv6-address | | | +--rw other-reserv-addr* inet:ipv6-address | | +--ro binding-info* [cli-id] | | +--ro cli-id uint32 | | +--ro duid | | | +--ro duid-type uint16 | | | +--ro duid-high-1 uint32 | | | +--ro duid-high-2 uint32 | | | +--ro duid-low-1 uint32 | | | +--ro duid-low-2 uint32 | | +--ro cli-ia* [iaid] | | +--ro ia-type string | | +--ro iaid string | | +--ro cli-addr* inet:ipv6-address | | +--ro pool-id? uint8 | +--rw prefix-pools | | +--rw prefix-pool* [pool-id] | | | +--rw pool-id uint8 | | | +--rw prefix inet:ipv6-prefix | | | +--rw prefix-length uint8 | | | +--rw preferred-lifetime yang:timeticks | | | +--rw valid-lifetime yang:timeticks | | | +--rw utilization-ratio threshold | | | +--rw inherit-option-set boolean | | | +--rw option-set [option-set-id] | | | +--rw reserved-prefixes | | | +--rw static-binding* [cli-id] | | | | +--rw cli-id uint32 | | | | +--rw duid | | | | | +--rw duid-type uint16 | | | | | +--rw duid-high-1 uint32 | | | | | +--rw duid-high-2 uint32 | | | | | +--rw duid-low-1 uint32 | | | | | +--rw duid-low-2 uint32 | | | | +--rw reserv-prefix-len uint8 | | | | +--rw reserv-prefix inet:ipv6-prefix | | | +--rw exclude-prefix-len uint8 | | | +--rw exclude-prefix inet:ipv6-prefix Cui, et al. Expires January 4, 2016 [Page 8] Internet-Draft YANG for DHCPv6 July 2015 | | | +--rw other-reserv-prefix* [reserv-id] | | | +--rw reserv-id uint8 | | | +--rw prefix-len uint8 | | | +--rw prefix inet:ipv6-prefix | | +--ro binding-info* [cli-id] | | +--ro cli-id uint32 | | +--ro duid | | | +--ro duid-type uint16 | | | +--ro duid-high-1 uint32 | | | +--ro duid-high-2 uint32 | | | +--ro duid-low-1 uint32 | | | +--ro duid-low-2 uint32 | | +--ro cli-iapd* [iaid] | | +--ro iaid uint32 | | +--ro cli-prefix* uint32 | | +--ro cli-prefix-len* uint8 | | +--ro pool-id? uint8 | +--rw hosts | +--rw host* [cli-id] | +--rw cli-id uint32 | +--rw duid | | +--rw duid-type uint16 | | +--rw duid-high-1 uint32 | | +--rw duid-high-2 uint32 | | +--rw duid-low-1 uint32 | | +--rw duid-low-2 uint32 | +--rw inherit-option-set boolean | +--rw option-set [option-set-id] | +--rw nis-domain-name? string | +--rw nis-plus-domain-name? string +--rw relay-opaque-paras | +--rw relays* [relay-name] | +--rw relay-name string | +--rw interface-info* [if-name] | | +--rw if-name string | | +--rw interface-id string | +--rw subscribers* [subscriber] | | +--rw subscriber uint8 | | +--rw subscriber-id string | +--rw remote-host* [ent-num] | +--rw ent-num uint32 | +--rw remote-id string +--rw rsoo-enabled-options | +--rw rsoo-enable-option* [option-code] | +--rw option-code uint16 | +--rw description string +--ro packet-stats +--ro solicit-count uint32 Cui, et al. Expires January 4, 2016 [Page 9] Internet-Draft YANG for DHCPv6 July 2015 +--ro request-count uint32 +--ro renew-count uint32 +--ro rebind-count uint32 +--ro decline-count uint32 +--ro release-count uint32 +--ro info-req-count uint32 +--ro advertise-count uint32 +--ro confirm-count uint32 +--ro reply-count uint32 +--ro reconfigure-count uint32 +--ro relay-forward-count uint32 +--ro relay-reply-count uint32 Figure 1: DHCPv6 Data Model Structure Introduction of important nodes: o serv-attributes: This container contains basic attributes of a DHCPv6 server such as DUID, server name and so on. Some optional functions that can be provided by the server is also included. o duid: Each server and client has only one DUID (DHCP Unique Identifier). The DUID here identifies a unique DHCPv6 server for clients. DUID consists of a two-octet type field and an arbitrary length (no more than 128 bits) content field. This duid container includes a "duid-type" leaf to specify the type and following four leaf nodes to define the variable length content. o pd-function: Whether the server can act as a delegating router to perform prefix delegation ([RFC3633]). o stateless-service: A boolean value specifies whether the server support client-server exchanges involving two messages defined in ([RFC3315]). o rapid-commit: Setting the value to '1' represents the server support the Solicit-Reply message exchange. '0' means the server will simply ignore the Rapid Commit option in Solicit message. o option-sets: DHCPv6 employs various options to carry additional information and parameters in DHCP messages. This container defines all the possible options that need to be configured at the server side. The relevant RFCs that define those options include: [RFC3315], [RFC3319], [RFC3646], [RFC3898], [RFC4242], [RFC4704], [RFC4833], [RFC5908], [RFC5970], [RFC4075], [RFC6334], [RFC6784], [RFC7078], [RFC7083], [RFC7291], [I-D.ietf-softwire-map-dhcp]. Cui, et al. Expires January 4, 2016 [Page 10] Internet-Draft YANG for DHCPv6 July 2015 o option-set: A server may allow different option sets to be configured for different conditions (i.e. different networks, clients and etc). This "option-set" list enables various sets of options being defined and configured in a single server. Different sets are distinguished by the key called "option-set- id". All the possible options discussed above are defined in the list and each option is corresponding to a container. Since all the options in the list are optional, each container in this list has a boolean parameter called "enable" to indicate whether this option (container) will be included in the current option set or not. o network-ranges: This model supports a hierarchy to achieve dynamic configuration. That is to say we could configure the server at different levels through this model. The top level is a global level which is defined as the container "network-ranges". The following levels are defined as sub-containers under it. The "network-ranges" contains the parameters (e.g. option-sets) that would be allocated to all the clients served by this server. o network-range: Under the "network-ranges" container, a "network- range" list is defined to configure the server at a network level which is also considered as the second level. Different network are identified by the key "network-range-id". This is because a server may have different configuration parameters (e.g. option sets) for different networks. o address-pools: Under the "network-range" list, a container describes the DHCPv6 server's address pools for a specific network is defined. This container supports the server to be configured at a pool level. o address-pool: A DHCPv6 server can be configured with several address pools for a specific network. This list defines such address pools which are distinguish by the key called "pool-id". o binding-info: A list records a binding information for each DHCPv6 client that has already been allocated IPv6 addresses. o prefix-pools: If a server supports prefix delegation function, this container under the "network-range" list will be valid to define the delegating router's prefix pools for a specific network. This container also supports the server to be configured at a pool level. o prefix-pool: Similar to server's address pools, a delegating router can also be configured with multiple prefix pools specified by a list called "prefix-pool". Cui, et al. Expires January 4, 2016 [Page 11] Internet-Draft YANG for DHCPv6 July 2015 o binding-info: A list records a binding information for each DHCPv6 requesting router that has already been configured IPv6 prefixes. o hosts: A server may also desire to be configured at a host level under some circumstances. This container include a list called "host" to allow the server carrying different parameters (e.g. option sets) for different hosts. o relay-opaque-paras: This container contains some opaque values in Relay Agent options that need to be configured on the server side only for value match. Such Relay Agent options include Interface- Id option, Remote-Id option and Subscriber-Id option. o rsoo-enabled-options: [RFC6422] requires that the server SHOULD have an administrator-configurable list of RSOO-enabled options. This container include a list called "rsoo-enable-option" to allow new RSOO-enabled options to be defined at the server side. o packet-stats: A container presents the packet statistics related to the DHCPv6 server. 3.2. DHCPv6 Relay Tree Diagrams +--rw dhcpv6 +-- ... | +--rw relay {dhcpv6-relay}? +--rw relay-attributes | +--rw name string | +--rw enable boolean | +--rw ipv6-address inet:ipv6-address | +--rw description? string | +--rw dest-addrs* inet:ipv6-address | +--rw subscribers* [subscriber] | | +--rw subscriber uint8 | | +--rw subscriber-id string | +--rw remote-host* [entNum] | | +--rw ent-num uint32 | | +--rw remote-id string | +--rw vendor-info | +--rw ent-num uint32 | +--rw data* string +--rw relay-supplied-options-option | +--rw rsoo-set* [rsoo-set-id] | +--rw rsoo-set-id uint8 | +--rw erp-local-domain-name-option | +--rw enable boolean | +--rw erp-for-client* [cli-id] Cui, et al. Expires January 4, 2016 [Page 12] Internet-Draft YANG for DHCPv6 July 2015 | +--rw cli-id uint32 | +--rw duid | | +--rw duid-type uint16 | | +--rw duid-high-1 uint32 | | +--rw duid-high-2 uint32 | | +--rw duid-low-1 uint32 | | +--rw duid-low-2 uint32 | +--rw erp-name string +--rw relay-interfaces | +--rw relay-if* [if-name] | +--rw if-name string | +--rw enable boolean | +--rw interface-id? string | +--rw rsoo-set [rsoo-set-id] | +--rw pd-route* [pd-route-id] | | +--rw pd-route-id uint8 | | +--rw requesting-router-id uint32 | | +--rw delegating-router-id uint32 | | +--rw next-router inet:ipv6-address | | +--rw last-router inet:ipv6-address | +--rw next-entity* [dest-addr] | +--rw dest-addr inet:ipv6-address | +--rw available boolean | +--rw multicast boolean | +--rw server boolean | +--ro packet-stats | +--ro cli-packet-rvd-count uint32 | +--ro solicit-rvd-count uint32 | +--ro request-rvd-count uint32 | +--ro renew-rvd-count uint32 | +--ro rebind-rvd-count uint32 | +--ro decline-rvd-count uint32 | +--ro release-rvd-count uint32 | +--ro info-req-rvd-count uint32 | +--ro relay-for-rvd-count uint32 | +--ro relay-rep-rvd-count uint32 | +--ro packet-to-cli-count uint32 | +--ro adver-sent-count uint32 | +--ro confirm-sent-count uint32 | +--ro reply-sent-count uint32 | +--ro reconfig-sent-count uint32 | +--ro relay-for-sent-count uint32 | +--ro relay-rep-sent-count uint32 +--ro relay-stats +--ro cli-packet-rvd-count uint32 +--ro relay-for-rvd-count uint32 +--ro relay-rep-rvd-count uint32 +--ro packet-to-cli-count uint32 Cui, et al. Expires January 4, 2016 [Page 13] Internet-Draft YANG for DHCPv6 July 2015 +--ro relay-for-sent-count uint32 +--ro relay-rep-sent-count uint32 +--ro discarded-packet-count uint32 Introduction of important nodes: o relay-attributes: A container describes some basic attributes of the relay agent including some relay agent specific options data that need to be configured previously. Such options include Remote-Id option and Subscriber-Id option. o dest-addrs: Each DHCPv6 relay agent may be configured with a list of destination addresses. This node defines such a list of IPv6 addresses that may include unicast addresses, multicast addresses or other addresses. o relay-supplied-options-option: DHCPv6 relay agent could provide some information that would be useful to DHCPv6 client. Since relay agent cannot provide options directly to the client, [RFC6422] defines RSOO-enabled options to propose options for the server to send to the client. This container modelled such RSOO- enabled options. o rsoo-set: This list under the "relay-supplied-options-option" container is similar to the "option-set" defined in server feature. It allows the relay to implement several sets of RSOO- enabled options for different interfaces. The list only include the EAP Re-authentication Protocol (ERP) Local Domain Name DHCPv6 Option defined in [RFC6440], since it is the only one RSOO-enabled options accepted by IANA so far. o relay-interfaces: The "realy-interfaces" defines common configuration and state parameters of the interfaces belonging to a DHCPv6 relay agent. o relay-if: A list under "relay-interfaces" container that describes a specific interface and its corresponding parameters. Here we use a string called "ifName" as the key of list. o pd-route: A sub-container of "relay-if" which describes the route for delegated prefixes into the provider edge router. o next-entity: This node defines a list that is used to describe the next hop entity of this relay agent. Different entities are distinguished by their addresses. o packet-stats: A container shows packet state information of a specific data communication. Cui, et al. Expires January 4, 2016 [Page 14] Internet-Draft YANG for DHCPv6 July 2015 o relay-stats: The "relayStats" container records and presents the overall packet statistics of the relay agent. 3.3. DHCPv6 Client Tree Diagrams +--rw dhcpv6 +-- ... | +--rw client {dhcpv6-client}? +--rw client-interfaces +--rw client-if* [if-name] +--rw if-name string +--rw cli-id uint32 +--rw duid | +--rw duid-type uint16 | +--rw duid-high-1 uint32 | +--rw duid-high-2 uint32 | +--rw duid-low-1 uint32 | +--rw duid-low-2 uint32 +--rw enable boolean +--rw description? string +--rw pd-function boolean +--rw rapid-commit boolean +--rw mo-tab | +--rw m-tab boolean | +--rw o-tab boolean +--rw oro-options | +--rw oro-option* [option-code] | +--rw option-code uint16 | +--rw description string +--rw client-cofigured-options | +--rw user-class-option | | +--rw enable boolean | | +--rw user-class* [user-class-id] | | +--rw user-class-id uint8 | | +--rw user-class-info string | +--rw vendor-class-option | | +--rw enable boolean | | +--rw ent-num uint32 | | +--rw data* string | +--rw client-fqdn-option | | +--rw enable boolean | | +--rw fqdn string | | +--rw server-initiate-update boolean | | +--rw client-initiate-update boolean | +--rw client-architecture-type-option | | +--rw enable boolean | | +--rw architecture-types* [type-id] Cui, et al. Expires January 4, 2016 [Page 15] Internet-Draft YANG for DHCPv6 July 2015 | | | +--rw type-id uint16 | | | +--rw most-preferred boolean | +--rw client-network-interface-option | | +--rw enable booelan | | +--rw type uint8 | | +--rw major uint8 | | +--rw minor uint8 | +--rw kerberos-principal-name-option | | +--rw enable boolean | | +--rw principal-name string | +--rw client-link-layer-addr-option | +--rw enable boolean | +--rw link-layer-type uint16 | +--rw link-layer-addr string +--ro identity-associations | +--ro identity-association* [iaid] | +--ro iaid uint32 | +--ro ia-type string | +--ro ipv6-addr* inet:ipv6-address | +--ro ipv6-prefix* inet:ipv6-prefix | +--ro prefix-length* uint8 | +--ro t1-time yang:date-and-time | +--ro t2-time yang:date-and-time | +--ro preferred-lifetime yang:timeticks | +--ro valid-lifetime yang:timeticks +--ro if-other-paras | +--ro uni-dhcpv6-serv-addr inet:ipv6-address | +--ro dns-paras | | +--ro domain-search-list string | | +--ro dns-servers* [dns-serv-id] | | +--ro dns-serv-id uint8 | | +--ro dns-serv-addr inet:ipv6-address | +--ro sip-paras | | +--ro sip-servers* [sip-serv-id] | | +--ro sip-serv-id uint8 | | +--ro sip-serv-addr inet:ipv6-address | | +--ro sip-serv-domain-name string | +--ro nis-paras | | +--ro nis-domain-name string | | +--ro nis-server* [nis-serv-id] | | +--ro nis-serv-id uint8 | | +--ro nis-serv-addr inet:ipv6-address | +--ro nis-plus-paras | | +--ro nis-plus-domain-name string | | +--ro nis-plus-server* [nis-plus-serv-id] | | +--ro nis-plus-serv-id uint8 | | +--ro nis-plus-serv-addr inet:ipv6-address | +--ro info-refresh-time yang:timeticks Cui, et al. Expires January 4, 2016 [Page 16] Internet-Draft YANG for DHCPv6 July 2015 | +--ro time-zone-paras | | +--ro tz-posix string | | +--ro tz-database string | +--ro cli-fqdn string | +--ro ntp-paras | | +--ro ntp-server* [ntp-serv-id] | | +--ro ntp-serv-id uint8 | | +--ro ntp-serv-addr inet:ipv6-address | | +--ro ntp-serv-mul-addr inet:ipv6-address | | +--ro ntp-serv-fqdn string | +--ro sntp-paras | | +--ro sntp-server* [sntp-serv-id] | | +--ro sntp-serv-id uint8 | | +--ro sntp-serv-addr inet:ipv6-address | +--ro network-boot-paras | | +--ro boot-file* [boot-file-id] | | +--ro boot-file-id uint8 | | +--ro suitable-arch-type* uint16 | | +--ro suitable-net-if* uint32 | | +--ro boot-file-url string | | +--ro boot-file-paras* [para-id] | | +--ro para-id uint8 | | +--ro parameter string | +--ro kerberos-paras | | +--ro default-realm-name string | | +--ro kdc-info* [kdc-id] | | +--ro kdc-id uint8 | | +--ro priority uint16 | | +--ro weight uint16 | | +--ro transport-type uint8 | | +--ro port-number uint16 | | +--ro kdc-ipv6-addr inet:ipv6-address | | +--ro realm-name string | +--ro addr-selection-paras | | +--ro automatic-row-add boolean | | +--ro prefer-temporary-addr boolean | | +--ro policy-table* [policy-id] | | +--ro policy-id uint8 | | +--ro label uint8 | | +--ro precedence uint8 | | +--ro prefix-len uint8 | | +--ro prefix inet:ipv6-prefix | +--ro sol-max-rt yang:timeticks | +--ro inf-max-rt yang:timeticks | +--ro pcp-paras | | +--ro pcp-server* [pcp-serv-id] | | +--ro pcp-serv-id uint8 | | +--ro pcp-serv-addr inet:ipv6-address Cui, et al. Expires January 4, 2016 [Page 17] Internet-Draft YANG for DHCPv6 July 2015 | +--ro s46-rule-paras | | +--ro s46-rule* [rule-id] | | +--ro rule-id uint8 | | +--ro rule-type enumeration | | +--ro ea-len uint8 | | +--ro prefix4-len uint8 | | +--ro ipv4-prefix inet:ipv4-prefix | | +--ro prefix6-len uint8 | | +--ro ipv6-prefix inet:ipv6-prefix | | +--ro port-parameter | | +--ro offset uint8 | | +--ro psid-len uint8 | | +--ro psid uint16 | +--ro s46-br-paras | | +--ro br* [br-id] | | +--ro br-id uint8 | | +--ro br-ipv6-addr inet:ipv6-address | +--ro s46-dmr-paras | | +--ro dmr* [dmr-id] | | +--ro dmr-id uint8 | | +--ro dmr-prefix6-len uint8 | | +--ro dmr-ipv6-prefix inet:ipv6-prefix | +--ro s46-v4-v6-binding-paras | | +--ro ipv4-addr inet:ipv6-address | | +--ro bind-prefix6-len uint8 | | +--ro port-parameter | | +--ro offset uint8 | | +--ro psid-len uint8 | | +--ro psid uint16 | +--ro erp-local-domain-name string +--ro supported-options | +--ro supported-option* [option-code] | +--ro option-code uint16 | +--ro description string +--ro packet-stats +--ro solicit-count uint32 +--ro request-count uint32 +--ro renew-count uint32 +--ro rebind-count uint32 +--ro decline-count uint32 +--ro release-count uint32 +--ro info-req-count uint32 +--ro advertise-count uint32 +--ro confirm-count uint32 +--ro reply-count uint32 +--ro reconfigure-count uint32 Introduction of important nodes: Cui, et al. Expires January 4, 2016 [Page 18] Internet-Draft YANG for DHCPv6 July 2015 o client-interfaces: A client may have several interfaces, it is more reasonable to configure and manage parameters on the interface-level. This container includes configuration and state data of a DHCPv6 client in a per-interface manner. o client-if: The list defines a specific client interface and its data. Different interfaces are distinguished by the "ifName" key which is a configurable string value. o duid: Each server and client has only one DUID (DHCP Unique Identifier). The DUID here will be carried in the Client ID option to identify a specific DHCPv6 client. This container are same as the "duid" container in "dhcpv6-server" feature. o pd-function: Whether the client can act as a requesting router to request prefixes using prefix delegation ([RFC3633]). o rapid-commit: '1' indicates a client can initiate a Solicit-Reply message exchange by adding a Rapid Commit option in Solicit message. '0' means the client is not allowed to add a Rapid Commit option to request addresses in a two-message exchange pattern. o mo-tab: The management tab label indicates the operation mode of the DHCPv6 client. 'm'=1 and 'o'=1 indicate the client will use DHCPv6 to obtain all the configuration data. 'm'=1 and 'o'=0 are a meaningless combination. 'm'=0 and 'o'=1 indicate the client will use stateless DHCPv6 to obtain configuration data apart from addresses/prefixes data. 'm'=0 and 'o'=0 represent the client will not use DHCPv6 but use SLAAC to achieve configuration. o oro-options: This container provide a way to configure the list of options that the client will request in its ORO option. o client-configured-options: Similar to the server, the client also need to configure some options to fulfil some desired functions. This container include all the potential options that need to be configured at the client side. The relevant RFCs that define those options include: [RFC3315], [RFC4704], [RFC5970], [RFC6784], [RFC6939]. o identity-association: IA is a construct through which a server and a client can identify, group, and manage a set of related IPv6 addresses. The key of the "identity-association" list is a 4-byte number IAID defined in [RFC3315] . o if-other-paras: A client can obtain extra configuration data other than address and prefix information through DHCPv6 options. This container describes such data the client was configured through Cui, et al. Expires January 4, 2016 [Page 19] Internet-Draft YANG for DHCPv6 July 2015 DHCPv6. The potential configuration data may include DNS server parameters, SIP server parameters and etc. o supported-options: This state data container defines a list of options supported by the client for administrator to interrogate a client's capabilities. o packet-stats: A container records all the packet status information of a specific interface. 3.4. Notifications Mechanism for DHCPv6 +--rw dhcpv6 +-- ... | +--n notifications +--n dhcpv6-server-event {dhcpv6-server}? | +--n pool-running-out | | +--ro utilization-ratio uint16 | | +--ro duid | | | +--ro duid-type uint16 | | | +--ro duid-high-1 uint32 | | | +--ro duid-high-2 uint32 | | | +--ro duid-low-1 uint32 | | | +--ro duid-low-2 uint32 | | +--ro serv-name? string | | +--ro pool-name string | +--n invalid-client-detected | +--ro duid | | +--ro duid-type uint16 | | +--ro duid-high-1 uint32 | | +--ro duid-high-2 uint32 | | +--ro duid-low-1 uint32 | | +--ro duid-low-2 uint32 | +--ro description? string +--n dhcpv6-relay-event {dhcpv6-relay}? | +--n topo-changed | +--ro relay-if-name string | +--ro first-hop boolean | +--ro last-entity-addr inet:ipv6-address +--n dhcpv6-client-event {dhcpv6-client}? +--n ia-lease-event | +--ro event-type enumeration | +--ro duid | | +--ro duid-type uint16 | | +--ro duid-high-1 uint32 | | +--ro duid-high-2 uint32 | | +--ro duid-low-1 uint32 Cui, et al. Expires January 4, 2016 [Page 20] Internet-Draft YANG for DHCPv6 July 2015 | | +--ro duid-low-2 uint32 | +--ro iaid uint32 | +--ro serv-name? string | +--ro description? string +--n invalid-ia-detected | +--ro duid | | +--ro duid-type uint16 | | +--ro duid-high-1 uint32 | | +--ro duid-high-2 uint32 | | +--ro duid-low-1 uint32 | | +--ro duid-low-2 uint32 | +--ro iaid uint32 | +--ro serv-name? string | +--ro description? string +--n retransmission-failed | +--ro duid | | +--ro duid-type uint16 | | +--ro duid-high-1 uint32 | | +--ro duid-high-2 uint32 | | +--ro duid-low-1 uint32 | | +--ro duid-low-2 uint32 | +--ro description enumeration +--n failed-status-turn-up +--ro duid | +--ro duid-type uint16 | +--ro duid-high-1 uint32 | +--ro duid-high-2 uint32 | +--ro duid-low-1 uint32 | +--ro duid-low-2 uint32 +--ro status-code enumeration Introduction of notifications: o pool-running-out: raised when the address/prefix pool is going to run out. A threshold for utilization ratio of the pool has been defined in the server feature so that it will notify the administrator when the utilization ratio reaches the threshold, and such threshold is a settable parameter. o ia-lease-event: raised when the client was allocated a new IA from the server or it renew/rebind/release its current IA. o invalid-client-detected: raised when the server has found a client which can be regarded as a potential attacker. Some description could also be included. o topo-changed: raised when the topology of the relay agent is changed. Cui, et al. Expires January 4, 2016 [Page 21] Internet-Draft YANG for DHCPv6 July 2015 o invalid-ia-detected: raised when the identity association of the client can be proved to be invalid. Possible condition includes duplicated address, illegal address, etc. o retransmission-failed: raised when the retransmission mechanism defined in [RFC3315] is failed. o failed-status-turn-up: raised when the client receives a message includes an unsuccessful Status Code option. 4. DHCPv6 YANG Model This module imports typedefs from [RFC6991]. file "ietf-dhcpv6@2015-07-01.yang" module ietf-dhcpv6 { namespace "urn:ietf:params:xml:ns:yang:dhc:dhcpv6"; prefix "dhcpv6"; import ietf-inet-types { prefix inet; revision-date "2013-07-15"; } import ietf-yang-types { prefix yang; revision-date "2013-07-15"; } organization "dhc wg"; contact "yong@csnet1.cs.tsinghua.edu.cn wangh13@mails.tsinghua.edu.cn lh.sunlinh@gmail.com Ted.Lemon@nominum.com ian.farrer@telekom.de"; description "This model defines a YANG data model that can be used to configure and manage DHCPv6 server, DHCPv6 relay and DHCPv6 client."; revision 2015-07-01 { description "version03: Correct grammar errors."; } revision 2015-04-13 { description "version02: Correct grammar errors."; } revision 2015-04-02 { description "version01: Correct grammar errors, Reuse groupings, Update 'dhcpv6-realy' feature, Add notifications.";} revision 2015-03-04 { description "Initial revision."; } /* * Features */ feature dhcpv6-server { Cui, et al. Expires January 4, 2016 [Page 22] Internet-Draft YANG for DHCPv6 July 2015 description "Server in DHCPv6."; reference "RFC3315"; } feature dhcpv6-relay { description "Relay agent in DHCPv6."; reference "RFC3315"; } feature dhcpv6-client { description "Client in DHCPv6."; reference "RFC3315"; } /* * Typedef */ typedef threshold { description "Threshold value in percent"; type union { type uint16 { range 0..100; } type enumeration { enum "disabled" { description "No threshold"; } } } } /* * Grouping */ grouping vendor-infor { container vendor-info { description ""; leaf ent-num { mandatory true; type uint32; } leaf-list data { Cui, et al. Expires January 4, 2016 [Page 23] Internet-Draft YANG for DHCPv6 July 2015 type string; } } } grouping portset-para { container port-parameter { leaf offset { mandatory true; type uint8; } leaf psid-len { mandatory true; type uint8; } leaf psid { mandatory true; type uint16; } } } grouping duid-para { container duid { leaf duid-type { mandatory true; type uint16; } leaf duid-high-1 { mandatory true; type uint32; } leaf duid-high-2 { mandatory true; type uint32; } leaf duid-low-1 { mandatory true; type uint32; } leaf duid-low-2 { mandatory true; type uint32; } } } /* Cui, et al. Expires January 4, 2016 [Page 24] Internet-Draft YANG for DHCPv6 July 2015 * Data Nodes */ container server { if-feature dhcpv6-server; container serv-attributes { description "This container contains basic attributes of a DHCPv6 server such as DUID, server name and so on. Some optional functions that can be provided by the server is also included."; leaf name { mandatory true; type string; } container duid { leaf duid-type { mandatory true; type uint16; } leaf duid-high-1 { mandatory true; type uint32; } leaf duid-high-2 { mandatory true; type uint32; } leaf duid-low-1 { mandatory true; type uint32; } leaf duid-low-2 { mandatory true; type uint32; } leaf enable { mandatory true; type boolean; } leaf ipv6-address { mandatory true; type inet:ipv6-address; } leaf description { type string; } leaf pd-function { description "Whether the server can act as a delegating router to perform prefix delegation ([RFC3633])."; mandatory true; type boolean; } Cui, et al. Expires January 4, 2016 [Page 25] Internet-Draft YANG for DHCPv6 July 2015 leaf stateless-service { description "A boolean value specifies whether the server support client-server exchanges involving two messages defined in ([RFC3315])."; mandatory true; type boolean; } leaf rapid-commit { description "A boolean value specifies whether the server support client-server exchanges involving two messages defined in ([RFC3315])."; mandatory true; type boolean; } leaf store-client-link-layer { description "."; type boolean; } uses vendor-infor; } container option-sets { list option-set { key option-set-id; leaf option-set-id { mandatory true; type uint8; } leaf user-class-value { type string; } leaf enterprise-number { type uint32; } leaf store-client-link-layer { type boolean; } container preference-option { leaf enable { mandatory true; type boolean; } leaf preference-value { mandatory true; type uint8; } } container sip-server-option { leaf enable { mandatory true; type boolean; } list sip-server { Cui, et al. Expires January 4, 2016 [Page 26] Internet-Draft YANG for DHCPv6 July 2015 key sip-serv-id; leaf sip-serv-id { mandatory true; type uint8; } leaf sip-serv-domain-name { mandatory true; type string; } leaf sip-serv-addr { mandatory true; type inet:ipv6-address; } } } container dns-config-option { leaf enable { mandatory true; type boolean; } list dns-server { key dns-serv-id; leaf dns-serv-id { mandatory true; type uint8; } leaf dns-serv-addr { mandatory true; type inet:ipv6-address; } } leaf domain-search-list { mandatory true; type string; } } container nis-config-option { leaf enable { mandatory true; type boolean; } list nis-server { key nis-serv-id; leaf nis-serv-id { mandatory true; type uint8; } leaf nis-serv-addr { Cui, et al. Expires January 4, 2016 [Page 27] Internet-Draft YANG for DHCPv6 July 2015 mandatory true; type inet:ipv6-address; } } } container nis-plus-config-option { leaf enable { mandatory true; type boolean; } list nis-plus-server { key nis-plus-serv-id; leaf nis-plus-serv-id { mandatory true; type uint8; } leaf nis-plus-serv-addr { mandatory true; type inet:ipv6-address; } } } container info-refresh-time-option { leaf enable { mandatory true; type boolean; } leaf info-refresh-time { mandatory true; type yang:timeticks; } } container cli-fqdn-option { leaf enable { mandatory true; type boolean; } leaf server-initiate-update { mandatory true; type boolean; } leaf client-initiate-update { mandatory true; type boolean; } leaf modify-name-from-cli { mandatory true; type boolean; Cui, et al. Expires January 4, 2016 [Page 28] Internet-Draft YANG for DHCPv6 July 2015 } } container timezone-option { leaf enable { mandatory true; type boolean; } leaf tz-posix { mandatory true; type string; } leaf tz-database { mandatory true; type string; } } container ntp-server-option { leaf enable { mandatory true; type boolean; } list ntp-server { key ntp-serv-id; leaf ntp-serv-id { mandatory true; type uint8; } leaf ntp-serv-addr { mandatory true; type inet:ipv6-address; } leaf ntp-serv-mul-addr { mandatory true; type inet:ipv6-address; } leaf ntp-serv-fqdn { mandatory true; type string; } } } container sntp-server-option { leaf enable { mandatory true; type boolean; } list sntp-server { key sntp-serv-id; Cui, et al. Expires January 4, 2016 [Page 29] Internet-Draft YANG for DHCPv6 July 2015 leaf sntp-serv-id { mandatory true; type uint8; } leaf sntp-serv-addr { mandatory true; type inet:ipv6-address; } } } container network-boot-option { leaf enable { mandatory true; type boolean; } list boot-file { key boot-file-id; leaf boot-file-id { mandatory true; type uint8; } leaf-list suitable-arch-type { type uint16; } leaf-list suitable-net-if { type uint32; } leaf boot-file-url { mandatory true; type string; } list boot-file-paras { key para-id; leaf id { mandatory true; type uint8; } leaf parameter { mandatory true; type string; } } } } container dslite-option { leaf enable { mandatory true; type boolean; Cui, et al. Expires January 4, 2016 [Page 30] Internet-Draft YANG for DHCPv6 July 2015 } leaf dslite-aftr-name { mandatory true; type string; } } container kerveros-option { leaf enable { mandatory true; type boolean; } leaf default-realm-name { mandatory true; type string; } list kdc-info { key kdc-id; leaf kdc-id { mandatory true; type uint8; } leaf priority { mandatory true; type uint16; } leaf weight { mandatory true; type uint16; } leaf transport-type { mandatory true; type uint8; } leaf port-number { mandatory true; type uint16; } leaf kdc-ipv6-addr { mandatory true; type inet:ipv6-address; } leaf realm-name { mandatory true; type string; } } } container addr-selection-option { Cui, et al. Expires January 4, 2016 [Page 31] Internet-Draft YANG for DHCPv6 July 2015 leaf enable { mandatory true; type boolean; } leaf a-bit-set { description ""; mandatory true; type boolean; } leaf p-bit-set { mandatory true; type boolean; } list policy-table { key policy-id; leaf policy-id { mandatory true; type uint8; } leaf label { mandatory true; type uint8; } leaf precedence { mandatory true; type uint8; } leaf prefix-len { mandatory true; type uint8; } leaf prefix { mandatory true; type inet:ipv6-prefix; } } } container sol-max-rt-option { leaf enable { mandatory true; type boolean; } leaf sol-max-rt-value { mandatory true; type yang:timeticks; } } container inf-max-rt-option { Cui, et al. Expires January 4, 2016 [Page 32] Internet-Draft YANG for DHCPv6 July 2015 leaf enable { mandatory true; type boolean; } leaf inf-max-rt-value { mandatory true; type yang:timeticks; } } container pcp-server-option { leaf enable { mandatory true; type boolean; } list pcp-server { key pcp-serv-id; leaf pcp-serv-id { mandatory true; type uint8; } leaf pcp-serv-addr { mandatory true; type inet:ipv6-address; } } } container s46-rule-option { leaf enable { mandatory true; type boolean; } list s46-rule { key rule-id; leaf rule-id { mandatory true; type uint8; } leaf rule-type { mandatory true; type enumeration { enum "BMR"; enum "FMR"; } } leaf prefix4-len { mandatory true; type uint8; } Cui, et al. Expires January 4, 2016 [Page 33] Internet-Draft YANG for DHCPv6 July 2015 leaf ipv4-prefix { mandatory true; type inet:ipv4-prefix; } leaf prefix6-len { mandatory true; type uint8; } leaf ipv6-prefix { mandatory true; type inet:ipv6-prefix; } uses portset-para; } } container s46-br-option { leaf enable { mandatory true; type boolean; } list br { key br-id; leaf br-id { mandatory true; type uint8; } leaf br-ipv6-addr { mandatory true; type inet:ipv6-address; } } } container s46-dmr-option { leaf enable { description ""; mandatory true; type boolean; } list dmr { key dmr-id; leaf dmr-id { mandatory true; type uint8; } leaf dmr-prefix-len { mandatory true; type uint8; } Cui, et al. Expires January 4, 2016 [Page 34] Internet-Draft YANG for DHCPv6 July 2015 leaf dmr-ipv6-prefix { mandatory true; type inet:ipv6-prefix; } } } container s46-v4-v6-binding-option { leaf enable { mandatory true; type boolean; } list ce { key ce-id; leaf ce-id { mandatory true; type uint8; } leaf ipv4-addr { mandatory true; type inet:ipv4-address; } leaf bind-prefix6-len { mandatory true; type uint8; } leaf bind-ipv6-prefix { mandatory true; type inet:ipv6-prefix; } uses portset-para; } } } } container network-range { leaf-list option-set { type uint8; } list network-range { key network-range-id; leaf network-range-id { mandatory true; type uint8; } leaf network-description { mandatory true; type string; } Cui, et al. Expires January 4, 2016 [Page 35] Internet-Draft YANG for DHCPv6 July 2015 leaf network-prefix { mandatory true; type inet:ipv6-prefix; } leaf inherit-option-set { mandatory true; type boolean; } leaf-list option-set { type uint8; } container address-pools { description "A container describes the DHCPv6 server's address pools."; list address-pool { description "A DHCPv6 server can be configured with several address pools. This list defines such address pools which are distinguish by the key called 'pool-name'."; key pool-id; leaf pool-id { mandatory true; type uint8; } leaf pool-prefix { mandatory true; type inet:ipv6-prefix; } leaf start-address { mandatory true; type inet:ipv6-address-no-zone; } leaf end-address { mandatory true; type inet:ipv6-address-no-zone; } leaf preferred-lifetime { mandatory true; type yang:timeticks; } leaf valid-lifetime { mandatory true; type yang:timeticks; } leaf total-ipv6-count { config "false"; mandatory true; type uint64; } leaf used-ipv6-count { config "false"; mandatory true; Cui, et al. Expires January 4, 2016 [Page 36] Internet-Draft YANG for DHCPv6 July 2015 type uint64; } leaf utilization-ratio { mandatory true; type threshold; } leaf inherit-option-set { mandatory true; type boolean; } leaf-list option-set { type uint8; } container reserved-addresses { list static-binding { key cli-id; leaf cli-id { mandatory true; type uint32; } uses duid-para; leaf-list reserv-addr { type inet:ipv6-address; } } leaf-list other-reserv-addr { type inet:ipv6-address; } } } list binding-info { config "false"; description "A list records a binding information for each DHCPv6 client that has already been allocated IPv6 addresses."; key cli-id; leaf cli-id { mandatory true; type uint32; } uses duid-para; list cli-ia { key iaid; leaf ia-type { mandatory true; type string; } leaf iaid { mandatory true; type string; Cui, et al. Expires January 4, 2016 [Page 37] Internet-Draft YANG for DHCPv6 July 2015 } leaf-list cli-addr { type inet:ipv6-address; } leaf pool-id { mandatory true; type uint8; } } } } container prefix-pools { description "If a server supports prefix delegation function, this container will be used to define the delegating router's refix pools."; list prefix-pool { description "Similar to server's address pools, a delegating router can also be configured with multiple prefix pools specified by a list called 'prefix-pool'."; key pool-id; leaf pool-id { mandatory true; type uint8; } leaf prefix { mandatory true; type inet:ipv6-prefix; } leaf prefix-length { mandatory true; type uint8; } leaf preferred-lifetime { mandatory true; type yang:timeticks; } leaf valid-lifetime { mandatory true; type yang:timeticks; } leaf utilization-ratio { mandatory true; type threshold; } leaf inherit-option-set { mandatory true; type boolean; } leaf-list option-set { type uint8; } container reserved-prefixes { Cui, et al. Expires January 4, 2016 [Page 38] Internet-Draft YANG for DHCPv6 July 2015 list static-binding { key cli-id; leaf cli-id { mandatory true; type uint32; } uses duid-para; leaf reserv-prefix-len { mandatory true; type uint8; } leaf reserv-prefix { mandatory true; type inet:ipv6-prefix; } } leaf exclude-prefix-len { mandatory true; type uint8; } leaf exclude-prefix { mandatory true; type inet:ipv6-prefix; } list other-reserv-prefix { key reserv-id; leaf reserv-id { mandatory true; type uint8; } leaf prefix-len { mandatory true; type uint8; } leaf prefix { mandatory true; type inet:ipv6-prefix; } } } } list binding-info { config "false"; description "A list records a binding information for each DHCPv6 client that has already been allocated IPv6 addresses."; key cli-id; leaf cli-id { mandatory true; type uint32; Cui, et al. Expires January 4, 2016 [Page 39] Internet-Draft YANG for DHCPv6 July 2015 } uses duid-para; list cli-iapd { key iaid; leaf iaid { mandatory true; type uint8; } leaf-list cli-prefix { type inet:ipv6-prefix; } leaf-list cli-prefix-len { type uint8; } leaf pool-id { mandatory true; type uint8; } } } } container hosts { list host { key cli-id; leaf cli-id { mandatory true; type uint32; } uses duid-para; leaf inherit-option-set { mandatory true; type boolean; } leaf-list option-set { type uint8; } leaf nis-domain-name { type string; } leaf nis-plus-domain-name { type string; } } } } } container relay-opaque-paras { description "This container contains some opaque values in Relay Agent options that need to be configured on the server side only for value match. Cui, et al. Expires January 4, 2016 [Page 40] Internet-Draft YANG for DHCPv6 July 2015 Such Relay Agent options include Interface-Id option, Remote-Id option and Subscriber-Id option."; list relays { key relay-name; leaf relay-name { mandatory true; type string; } list interface-info { key if-name; leaf if-name { mandatory true; type string; } leaf interface-id { mandatory true; type string; } } list subscribers { key subscriber; leaf subscriber { mandatory true; type uint8; } leaf subscriber-id { mandatory true; type string; } } list remote-host { key ent-num; leaf ent-num { mandatory true; type uint32; } leaf remote-id { mandatory true; type string; } } } } container rsoo-enabled-options { list rsoo-enable-option{ key option-code; leaf option-code { mandatory true; Cui, et al. Expires January 4, 2016 [Page 41] Internet-Draft YANG for DHCPv6 July 2015 type uint16; } leaf description { mandatory true; type string; } } } container packet-stats { config "false"; description "A container presents the packet statistics related to the DHCPv6 server."; leaf solicit-count { mandatory true; type uint32; } leaf request-count { mandatory true; type uint32; } leaf renew-count { mandatory true; type uint32; } leaf rebind-count { mandatory true; type uint32; } leaf decline-count { mandatory true; type uint32; } leaf release-count { mandatory true; type uint32; } leaf info-req-count { mandatory true; type uint32; } leaf advertise-count { mandatory true; type uint32; } leaf confirm-count { mandatory true; type uint32; } leaf reply-count { Cui, et al. Expires January 4, 2016 [Page 42] Internet-Draft YANG for DHCPv6 July 2015 mandatory true; type uint32; } leaf reconfigure-count { mandatory true; type uint32; } leaf relay-forward-count { mandatory true; type uint32; } leaf relay-reply-count { mandatory true; type uint32; } } } } container relay { if-feature dhcpv6-relay; container relay-attributes { description "A container describes some basic attributes of the relay agent including some relay agent specific options data that need to be configured previously. Such options include Remote-Id option and Subscriber-Id option."; leaf name { mandatory true; type string; } leaf enable { mandatory true; type boolean; } leaf ipv6-address { mandatory true; type inet:ipv6-address; } leaf description { type string; } leaf-list dest-addrs { description "Each DHCPv6 relay agent may be configured with a list of destination addresses. This node defines such a list of IPv6 addresses that may include unicast addresses, multicast addresses or other addresses."; type inet:ipv6-address; } list subscribers { key subscriber; leaf subscriber { mandatory true; type uint8; } leaf subscriber-id { Cui, et al. Expires January 4, 2016 [Page 43] Internet-Draft YANG for DHCPv6 July 2015 mandatory true; type string; } } list remote-host { key ent-num; leaf ent-num { mandatory true; type uint32; } leaf remote-id { mandatory true; type string; } } uses vendor-infor; container relay-supplied-options-option { list rsoo-set { key rsoo-set-id; leaf rsoo-set-id { mandatory true; type uint8; } container erp-local-domain-name-option { leaf enable { mandatory true; type boolean; } list erp-for-client { key cli-id; leaf cli-id { mandatory true; type uint32; } uses duid-para; leaf erp-name { mandatory true; type string; } } } } } container relay-interfaces { description "It is a container that defines common configuration and state parameters in the interfaces of a DHCPv6 relay agent. In this YANG data model for DHCPv6 relay agent, the parameters are configured in a per-interface manner."; list relay-if { description "A list describes a specific interface and its corresponding parameters. Here we use a string called 'ifName' as the key of list."; key if-name; Cui, et al. Expires January 4, 2016 [Page 44] Internet-Draft YANG for DHCPv6 July 2015 leaf if-name { mandatory true; type string; } leaf enable { mandatory true; type boolean; } leaf interface-id { type string; } leaf-list rsoo-set { type uint8; } list pd-route { key pd-route-id; leaf pd-route-id { mandatory true; type uint8; } leaf requesting-router-id { mandatory true; type uint32; } leaf delegating-router-id { mandatory true; type uint32; } leaf next-router { mandatory true; type inet:ipv6-address; } leaf last-router { mandatory true; type inet:ipv6-address; } } list next-entity { description "This node defines a list that is used to describe the next hop entity of this relay distinguished by their addresses."; key dest-addr; leaf dest-addr { mandatory true; type inet:ipv6-address; } leaf available { mandatory true; type boolean; } Cui, et al. Expires January 4, 2016 [Page 45] Internet-Draft YANG for DHCPv6 July 2015 leaf multicast { mandatory true; type boolean; } leaf server { mandatory true; type boolean; } container packet-stats { config "false"; leaf cli-packet-rvd-count { mandatory true; type uint32; } leaf solicit-rvd-count { mandatory true; type uint32; } leaf request-rvd-count { mandatory true; type uint32; } leaf renew-rvd-count { mandatory true; type uint32; } leaf rebind-rvd-count { mandatory true; type uint32; } leaf decline-rvd-count { mandatory true; type uint32; } leaf release-rvd-count { mandatory true; type uint32; } leaf info-req-rvd-count { mandatory true; type uint32; } leaf relay-for-rvd-count { mandatory true; type uint32; } leaf relay-rep-rvd-count { mandatory true; Cui, et al. Expires January 4, 2016 [Page 46] Internet-Draft YANG for DHCPv6 July 2015 type uint32; } leaf packet-to-cli-count { mandatory true; type uint32; } leaf adver-sent-count { mandatory true; type uint32; } leaf confirm-sent-count { mandatory true; type uint32; } leaf reply-sent-count { mandatory true; type uint32; } leaf reconfig-sent-count { mandatory true; type uint32; } leaf relay-for-sent-count { mandatory true; type uint32; } leaf relay-rep-sent-count { mandatory true; type uint32; } } } } } container relay-stats { config "false"; leaf cli-packet-rvd-count { mandatory true; type uint32; } leaf relay-for-rvd-count { mandatory true; type uint32; } leaf relay-rep-rvd-count { mandatory true; type uint32; } Cui, et al. Expires January 4, 2016 [Page 47] Internet-Draft YANG for DHCPv6 July 2015 leaf packet-to-cli-count { mandatory true; type uint32; } leaf relay-for-sent-count { mandatory true; type uint32; } leaf relay-rep-sent-count { mandatory true; type uint32; } leaf discarded-packet-count { mandatory true; type uint32; } } } } container client { if-feature dhcpv6-client; container client-interfaces { description "A client may have several interfaces, it is more reasonable to configure and manage parameters on the interface-level. This container includes configuration and state data of a DHCPv6 client in a per-interface manner."; list client-if { description "The list defines a specific client interface and its data. Different interfaces are distinguished by the key which is a configurable string value."; key if-name; leaf if-name { mandatory true; type string; } leaf cli-id { mandatory true; type uint32; } uses duid-para; leaf enable { mandatory true; type boolean; } leaf description { type string; } leaf pd-function { description "Whether the client can act as a requesting router to request prefixes using prefix delegation ([RFC3633])."; mandatory true; type boolean; } leaf rapid-commit { Cui, et al. Expires January 4, 2016 [Page 48] Internet-Draft YANG for DHCPv6 July 2015 description "'1' indicates a client can initiate a Solicit-Reply message exchange by adding a Rapid Commit option in Solicit message. '0' means the client is not allowed to add a Rapid Commit option to request addresses in a two-message exchange pattern."; mandatory true; type boolean; } container mo-tab { description "The management tab label indicates the operation mode of the DHCPv6 client. 'm'=1 and 'o'=1 indicate the client will use DHCPv6 to obtain all the configuration data. 'm'=1 and 'o'=0 are a meaningless combination. 'm'=0 and 'o'=1 indicate the client will use stateless DHCPv6 to obtain configuration data apart from addresses/prefixes data. 'm'=0 and 'o'=0 represent the client will not use DHCPv6 but use SLAAC to achieve configuration."; leaf m-tab { mandatory true; type boolean; } leaf o-tab { mandatory true; type boolean; } } container oro-options { list oro-option { key option-code; leaf option-code { mandatory true; type uint16; } leaf description { mandatory true; type string; } } } container client-cofigured-options { container user-class-option { leaf enable { mandatory true; type boolean; } list user-class { key user-class-id; leaf user-class-id { mandatory true; type uint8; } leaf user-class-info { mandatory true; type string; } } } container vendor-class-option { leaf enable { Cui, et al. Expires January 4, 2016 [Page 49] Internet-Draft YANG for DHCPv6 July 2015 mandatory true; type boolean; } leaf ent-num { mandatory true; type uint32; } leaf-list data { type string; } } container client-fqdn-option { leaf enable { mandatory true; type boolean; } leaf fqdn { mandatory true; type string; } leaf server-initiate-update { mandatory true; type boolean; } leaf client-initiate-update { mandatory true; type boolean; } } container client-architecture-type-option { leaf enable { mandatory true; type boolean; } list architecture-types { key type-id; leaf type-id { mandatory true; type uint16; } leaf most-preferred { mandatory true; type boolean; } } } container client-network-interface-option { leaf enable { Cui, et al. Expires January 4, 2016 [Page 50] Internet-Draft YANG for DHCPv6 July 2015 mandatory true; type boolean; } leaf type { mandatory true; type uint8; } leaf major { mandatory true; type uint8; } leaf minor { mandatory true; type uint8; } } container kerberos-principal-name-option { leaf enable { mandatory true; type boolean; } leaf principal-name { mandatory true; type string; } } container client-link-layer-addr-option { leaf enable { mandatory true; type boolean; } leaf link-layer-type { mandatory true; type uint16; } leaf link-layer-addr { mandatory true; type string; } } } container identity-associations { config "false"; description "IA is a construct through which a server and a client can identify, group, and manage a set of related IPv6 addresses. The key of the list is a 4-byte number IAID defined in [RFC3315] ."; list identity-association { key iaid; leaf iaid { mandatory true; Cui, et al. Expires January 4, 2016 [Page 51] Internet-Draft YANG for DHCPv6 July 2015 type uint32; } leaf ia-type { mandatory true; type string; } leaf-list ipv6-addr { type inet:ipv6-address; } leaf-list ipv6-prefix { type inet:ipv6-prefix; } leaf-list prefix-length { type uint8; } leaf t1-time { mandatory true; type yang:date-and-time; } leaf t2-time { mandatory true; type yang:date-and-time; } leaf preferred-lifetime { mandatory true; type yang:timeticks; } leaf valid-lifetime { mandatory true; type yang:timeticks; } } } container if-other-paras { config "false"; description "A client can obtain extra configuration data other than address and prefix information through DHCPv6. This container describes such data the client was configured. The potential configuration data may include DNS server addresses, SIP server domain names, etc."; leaf-list uni-dhcpv6-serv-addr { type inet:ipv6-address; } container dns-paras { leaf domain-search-list { mandatory true; type string; } list dns-servers { key dns-serv-id; leaf dns-serv-id { mandatory true; Cui, et al. Expires January 4, 2016 [Page 52] Internet-Draft YANG for DHCPv6 July 2015 type uint8; } leaf dns-serv-addr { mandatory true; type inet:ipv6-address; } } } container sip-paras { list sip-servers { key sip-serv-id; leaf sip-serv-id { mandatory true; type uint8; } leaf sip-serv-addr { mandatory true; type inet:ipv6-address; } leaf sip-serv-domain-name { mandatory true; type string; } } } container nis-paras { leaf nis-domain-name { mandatory true; type string; } list nis-server { key nis-serv-id; leaf nip-serv-id { mandatory true; type uint8; } leaf nip-serv-addr { mandatory true; type inet:ipv6-address; } } } container nis-plus-paras { leaf nis-plus-domain-name { mandatory true; type string; } list nis-plus-server { Cui, et al. Expires January 4, 2016 [Page 53] Internet-Draft YANG for DHCPv6 July 2015 key nis-plus-serv-id; leaf nip-plus-serv-id { mandatory true; type uint8; } leaf nip-plus-serv-addr { mandatory true; type inet:ipv6-address; } } } leaf info-refresh-time { type yang:timeticks; } container time-zone-paras { leaf tz-posix { mandatory true; type string; } leaf tz-database { mandatory true; type string; } } leaf cli-fqdn { type string; } container ntp-paras { list ntp-server { key ntp-serv-id; leaf ntp-serv-id { mandatory true; type uint8; } leaf ntp-serv-addr { mandatory true; type inet:ipv6-address; } leaf ntp-serv-mul-addr { mandatory true; type inet:ipv6-address; } leaf ntp-serv-fqdn { mandatory true; type string; } } } Cui, et al. Expires January 4, 2016 [Page 54] Internet-Draft YANG for DHCPv6 July 2015 container sntp-paras { list sntp-server { key sntp-serv-id; leaf sntp-serv-id { mandatory true; type uint8; } leaf sntp-serv-addr { mandatory true; type inet:ipv6-address; } } } container network-boot-paras { list boot-file { key boot-file-id; leaf boot-file-id { mandatory true; type uint8; } leaf-list suitable-arch-type { type uint16; } leaf-list suitable-net-if { type uint32; } leaf boot-file-url { mandatory true; type string; } list boot-file-paras { key para-id; leaf para-id { mandatory true; type uint8; } leaf parameter { mandatory true; type string; } } } } container kerveros-paras { leaf default-realm-name { mandatory true; type string; } Cui, et al. Expires January 4, 2016 [Page 55] Internet-Draft YANG for DHCPv6 July 2015 list kdc-info { key kdc-id; leaf kdc-id { mandatory true; type uint8; } leaf priority { mandatory true; type uint16; } leaf weight { mandatory true; type uint16; } leaf transport-type { mandatory true; type uint8; } leaf port-number { mandatory true; type uint16; } leaf kdc-ipv6-addr { mandatory true; type inet:ipv6-address; } leaf realm-name { mandatory true; type string; } } } container addr-selection-paras { leaf automatic-row-add { mandatory true; type boolean; } leaf prefer-temporary-addr { mandatory true; type boolean; } list policy-table { key policy-id; leaf policy-id { mandatory true; type uint8; } leaf label { Cui, et al. Expires January 4, 2016 [Page 56] Internet-Draft YANG for DHCPv6 July 2015 mandatory true; type uint8; } leaf precedence { mandatory true; type uint8; } leaf prefix-len { mandatory true; type uint8; } leaf prefix { mandatory true; type inet:ipv6-prefix; } } } leaf sol-max-rt { mandatory true; type yang:timeticks; } leaf inf-max-rt { mandatory true; type yang:timeticks; } container pcp-server-paras { list pcp-server { key pcp-serv-id; leaf pcp-serv-id { mandatory true; type uint8; } leaf pcp-serv-addr { mandatory true; type inet:ipv6-address; } } } container s46-rule-paras { list s46-rule { key rule-id; leaf rule-id { mandatory true; type uint8; } leaf rule-type { mandatory true; type enumeration { Cui, et al. Expires January 4, 2016 [Page 57] Internet-Draft YANG for DHCPv6 July 2015 enum "BMR"; enum "FMR"; } } leaf ea-len { mandatory true; type uint8; } leaf prefix4-len { mandatory true; type uint8; } leaf ipv4-prefix { mandatory true; type inet:ipv4-prefix; } leaf prefix6-len { mandatory true; type uint8; } leaf ipv6-prefix { mandatory true; type inet:ipv6-prefix; } uses portset-para; } } container s46-br-paras { list br { key br-id; leaf br-id { mandatory true; type uint8; } leaf br-ipv6-addr { mandatory true; type inet:ipv6-address; } } } container s46-dmr-paras { list dmr { key dmr-id; leaf dmr-id { mandatory true; type uint8; } leaf dmr-prefix-len { Cui, et al. Expires January 4, 2016 [Page 58] Internet-Draft YANG for DHCPv6 July 2015 mandatory true; type uint8; } leaf dmr-ipv6-prefix { mandatory true; type inet:ipv6-prefix; } } } container s46-v4-v6-binding-paras { leaf ipv4-addr { mandatory true; type inet:ipv4-address; } leaf bind-prefix6-len { mandatory true; type uint8; } uses portset-para; leaf erp-local-domain-name { mandatory true; type string; } } container supported-options { list supported-option { key option-code; leaf option-code { mandatory true; type uint16; } leaf description { mandatory true; type string; } } } } container packet-stats { config "false"; description "A container records all the packet status information of a specific interface."; leaf solicit-count { mandatory true; type uint32; } leaf request-count { mandatory true; type uint32; Cui, et al. Expires January 4, 2016 [Page 59] Internet-Draft YANG for DHCPv6 July 2015 } leaf renew-count { mandatory true; type uint32; } leaf rebind-count { mandatory true; type uint32; } leaf decline-count { mandatory true; type uint32; } leaf release-count { mandatory true; type uint32; } leaf info-req-count { mandatory true; type uint32; } leaf advertise-count { mandatory true; type uint32; } leaf confirm-count { mandatory true; type uint32; } leaf reply-count { mandatory true; type uint32; } leaf reconfigure-count { mandatory true; type uint32; } } } } } /* * Notifications */ notification notifications { container dhcpv6-server-event { Cui, et al. Expires January 4, 2016 [Page 60] Internet-Draft YANG for DHCPv6 July 2015 if-feature dhcpv6-server; container pool-running-out { leaf utilization-ratio { mandatory true; type uint16; } uses duid-para; leaf serv-name { type string; } leaf pool-name { mandatory true; type string; } } container invalid-client-detected { uses duid-para; leaf description { type string; } } } container dhcpv6-relay-event { if-feature dhcpv6-relay; container topo-changed { leaf relay-if-name { mandatory true; type string; } leaf first-hop { mandatory true; type boolean; } leaf last-entity-addr { mandatory true; type inet:ipv6-address; } } } container dhcpv6-client-event { if-feature dhcpv6-client; container ia-lease-event { leaf event-type { mandatory true; type enumeration{ enum "allocation"; enum "rebind"; enum "renew"; Cui, et al. Expires January 4, 2016 [Page 61] Internet-Draft YANG for DHCPv6 July 2015 enum "release"; } } uses duid-para; leaf iaid { mandatory true; type uint32; } leaf serv-name { type string; } leaf description { type string; } } container invalid-ia-detected { uses duid-para; leaf cli-duid { mandatory true; type uint32; } leaf iaid { mandatory true; type uint32; } leaf serv-name { type string; } leaf description { type string; } } container retransmission-failed { uses duid-para; leaf description { mandatory true; type enumeration { enum "MRC failed"; enum "MRD failed"; } } } container failed-status-turn-up { uses duid-para; leaf status-code { mandatory true; type enumeration { enum "1" { Cui, et al. Expires January 4, 2016 [Page 62] Internet-Draft YANG for DHCPv6 July 2015 description "UnspecFail"; } enum "2" { description "NoAddrAvail"; } enum "3" { description "NoBinding"; } enum "4" { description "NotOnLink"; } enum "5" { description "UseMulticast"; } } } } } } } 5. Security Considerations (TBD) TBD 6. IANA Considerations (TBD) TBD 7. Acknowledgements The authors would like to thank Qi Sun, Lishan Li and Sladjana Zoric for their valuable contributions to this work. 8. References 8.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3315, July 2003. Cui, et al. Expires January 4, 2016 [Page 63] Internet-Draft YANG for DHCPv6 July 2015 [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6", RFC 3633, December 2003. [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, October 2010. [RFC6087] Bierman, A., "Guidelines for Authors and Reviewers of YANG Data Model Documents", RFC 6087, January 2011. [RFC6991] Schoenwaelder, J., "Common YANG Data Types", RFC 6991, July 2013. 8.2. Informative References [I-D.ietf-softwire-map-dhcp] Mrugalski, T., Troan, O., Farrer, I., Perreault, S., Dec, W., Bao, C., Yeh, L., and X. Deng, "DHCPv6 Options for configuration of Softwire Address and Port Mapped Clients", draft-ietf-softwire-map-dhcp-12 (work in progress), March 2015. [RFC3319] Schulzrinne, H. and B. Volz, "Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers", RFC 3319, July 2003. [RFC3646] Droms, R., "DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3646, December 2003. [RFC3898] Kalusivalingam, V., "Network Information Service (NIS) Configuration Options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3898, October 2004. [RFC4075] Kalusivalingam, V., "Simple Network Time Protocol (SNTP) Configuration Option for DHCPv6", RFC 4075, May 2005. [RFC4242] Venaas, S., Chown, T., and B. Volz, "Information Refresh Time Option for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 4242, November 2005. [RFC4704] Volz, B., "The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Client Fully Qualified Domain Name (FQDN) Option", RFC 4704, October 2006. [RFC4833] Lear, E. and P. Eggert, "Timezone Options for DHCP", RFC 4833, April 2007. Cui, et al. Expires January 4, 2016 [Page 64] Internet-Draft YANG for DHCPv6 July 2015 [RFC5908] Gayraud, R. and B. Lourdelet, "Network Time Protocol (NTP) Server Option for DHCPv6", RFC 5908, June 2010. [RFC5970] Huth, T., Freimann, J., Zimmer, V., and D. Thaler, "DHCPv6 Options for Network Boot", RFC 5970, September 2010. [RFC6334] Hankins, D. and T. Mrugalski, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Option for Dual-Stack Lite", RFC 6334, August 2011. [RFC6422] Lemon, T. and Q. Wu, "Relay-Supplied DHCP Options", RFC 6422, December 2011. [RFC6440] Zorn, G., Wu, Q., and Y. Wang, "The EAP Re-authentication Protocol (ERP) Local Domain Name DHCPv6 Option", RFC 6440, December 2011. [RFC6784] Sakane, S. and M. Ishiyama, "Kerberos Options for DHCPv6", RFC 6784, November 2012. [RFC6939] Halwasia, G., Bhandari, S., and W. Dec, "Client Link-Layer Address Option in DHCPv6", RFC 6939, May 2013. [RFC7078] Matsumoto, A., Fujisaki, T., and T. Chown, "Distributing Address Selection Policy Using DHCPv6", RFC 7078, January 2014. [RFC7083] Droms, R., "Modification to Default Values of SOL_MAX_RT and INF_MAX_RT", RFC 7083, November 2013. [RFC7291] Boucadair, M., Penno, R., and D. Wing, "DHCP Options for the Port Control Protocol (PCP)", RFC 7291, July 2014. Authors' Addresses Yong Cui Tsinghua University Beijing 100084 P.R.China Phone: +86-10-6260-3059 Email: yong@csnet1.cs.tsinghua.edu.cn Cui, et al. Expires January 4, 2016 [Page 65] Internet-Draft YANG for DHCPv6 July 2015 Hao Wang Tsinghua University Beijing 100084 P.R.China Phone: +86-10-6278-5822 Email: wangh13@mails.tsinghua.edu.cn Linhui Sun Tsinghua University Beijing 100084 P.R.China Phone: +86-10-6278-5822 Email: lh.sunlinh@gmail.com Ted Lemon Nominum, Inc. 950 Charter St. Redwood City, CA 94043 USA Email: Ted.Lemon@nominum.com Ian Farrer Deutsche Telekom AG CTO-ATI, Landgrabenweg 151 Bonn, NRW 53227 Germany Email: ian.farrer@telekom.de Cui, et al. Expires January 4, 2016 [Page 66]