DHC Working Group Y. Cui Internet-DraftH. WangL. Sun Intended status: Standards TrackL. Sun Expires: May 1, 2018Tsinghua University Expires: June 26, 2018 I. Farrer S. Zechlin Deutsche Telekom AGOctober 28,Z. He Tsinghua University December 23, 2017 YANG Data Model for DHCPv6 Configurationdraft-ietf-dhc-dhcpv6-yang-04draft-ietf-dhc-dhcpv6-yang-05 Abstract This document describes a YANG data model [RFC6020] for the configuration and management of DHCPv6 servers, relays, and clients. 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 https://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." This Internet-Draft will expire onMay 1,June 26, 2018. Copyright Notice Copyright (c) 2017 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 (https://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. DHCPv6 Tree Diagram . . . . . . . . . . . . . . . . . . . . . 3 2.1. DHCPv6 Server Tree Diagrams . . . . . . . . . . . . . . . 3 2.2. DHCPv6 Relay Tree Diagrams . . . . . . . . . . . . . . .1416 2.3. DHCPv6 Client Tree Diagrams . . . . . . . . . . . . . . .17 2.4. Notifications Mechanism for20 3. DHCPv6 YANG Model . . . . . . . . . . .22 3.. . . . . . . . . . . 27 3.1. DHCPv6 Server YANG Model . . . . . . . . . . . . . . . . 27 3.2. DHCPv6 Relay YANG Model . . . . . . . . . . . . . . . . . 48 3.3. DHCPv6 Client YANG Model . . . . . . . . . . . . . . . . 58 3.4. DHCPv6 Options YANG Model . . . . . . . . . .24. . . . . . 67 4. Security Considerations (TBD) . . . . . . . . . . . . . . . .9198 5. IANA Considerations (TBD) . . . . . . . . . . . . . . . . . .9198 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . .9198 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 98 8. References . . . . . . . . . . . . . . . . . . . . . . . . .91 7.1.98 8.1. Normative References . . . . . . . . . . . . . . . . . .91 7.2.98 8.2. Informative References . . . . . . . . . . . . . . . . .9299 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . .94101 1. Introduction DHCPv6 [RFC3315] is widely used for supplying configuration and other relevant parameters to clients in IPv6 networks. This document defines a DHCPv6 YANG data model, containing sub-modules for the configuration and management of DHCPv6 servers, relays and clients. A single YANG model covering all of these elements provides an operator with a common interface for the management of the entire DHCPv6 deployment in their network. Since the publication of the original DHCPv6 specification, there have been a large number of addional documents that update the protocol's operation, add new functions and define new options. The YANG model described in this document incorporates all relevent changes. A full list of the documents which have been considedered in the development of this model is included in Appendix A. IF - Commment - Does anyone have this list? It is worth noting that as DHCPv6 is itself a device configuration protocol, it is not the intention of this document to replace the configuration of DHCPv6 options and parameters using the DHCPv6 protocol with the configuration of DHCPv6 options using 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 reader should be familiar with the terms defined in DHCPv6 [RFC3315] and other relevant documents. The DHCPv6 tree diagrams provide a concise representation of a YANG module to help the reader understand the module structure. A simplified graphical representation of the data model is provided in this d cument. For a description of the symbols in these diagrams, please refer to [I-D.ietf-netmod-yang-tree-diagrams]. 2. DHCPv6 Tree Diagram 2.1. DHCPv6 Server Tree Diagrams module:ietf-dhcpv6ietf-dhcpv6-server +--rw server! +--rw server-config | +--rw serv-attributes | | +--rw name? string | | +--rw duid | | | +--rw type-code? uint16 | | | +--rw (duid-type)? | | | +--:(duid-llt) | | | | +--rw duid-llt-hardware-type? uint16 | | | | +--rw duid-llt-time? yang:timeticks | | | | +--rw duid-llt-link-layer-addr? yang:mac-address | | | +--:(duid-en) | | | | +--rw duid-en-enterprise-number? uint32 | | | | +--rw duid-en-identifier? string | | | +--:(duid-ll) | | | | +--rw duid-ll-hardware-type? uint16 | | | | +--rwduid-ll-time? yang:timeticksduid-ll-link-layer-addr? yang:mac-address | | | +--:(duid-uuid) | | | | +--rw uuid? yang:uuid | | | +--:(duid-invalid) | | | +--rw data? binary | | +--rw ipv6-address* inet:ipv6-address | | +--rw description? string | | +--rw pd-function boolean | | +--rw stateless-service boolean | | +--rw rapid-commit boolean | | +--rw interfaces-config* string | | +--rw vendor-info | | +--rw ent-num uint32 | | +--rw data* string | +--rw option-sets | | +--rw option-set*[option-set-id][id] |+--rw option-set-id uint8| +--rwnew-or-standard-option* [option-code]id uint32 | | +--rwoption-code uint16server-unicast-option! {server-unicast-op}? | |+--rw option-name string || +--rwoption-description stringserver-address? inet:ipv6-address | | +--rwoption-reference? stringsip-server-domain-name-list-option! {sip-server-domain-name-list-op}? | |+--rw option-value string| +--rwuser-class-value?sip-serv-domain-name string |+--rw enterprise-number? uint32 | +--rw store-client-link-layer? boolean | +--rw preference-option | | +--rw enable boolean || +--rwpreference-value uint8 | +--rw sip-server-option |sip-server-address-list-option! {sip-server-address-list-op}? |+--rw enable boolean| | +--rw sip-server* [sip-serv-id] | | | +--rw sip-serv-id uint8 | |+--rw sip-serv-domain-name string || +--rw sip-serv-addr inet:ipv6-address |+--rw dns-config-option || +--rwenable booleandns-config-option! {dns-config-op}? | | | +--rw dns-server* [dns-serv-id] | | | +--rw dns-serv-id uint8 | | | +--rw dns-serv-addr inet:ipv6-address |+--rw domain-searchlist-option || +--rwenable booleandomain-searchlist-option! {domain-searchlist-op}? | | | +--rw domain-searchlist* [domain-searchlist-id] | | | +--rw domain-searchlist-id uint8 | | | +--rw domain-search-list-entry string |+--rw nis-config-option || +--rwenable booleannis-config-option! {nis-config-op}? | | | +--rw nis-server* [nis-serv-id] | | | +--rw nis-serv-id uint8 | | | +--rw nis-serv-addr inet:ipv6-address |+--rw nis-plus-config-option || +--rwenable booleannis-plus-config-option! {nis-plus-config-op}? | | | +--rw nis-plus-server* [nis-plus-serv-id] | | | +--rw nis-plus-serv-id uint8 | | | +--rw nis-plus-serv-addr inet:ipv6-address | | +--rwsntp-server-optionnis-domain-name-option! {nis-domain-name-op}? | | | +--rwenable booleannis-domain-name? string | | +--rwsntp-server*nis-plus-domain-name-option!{nis-plus-domain-name-op}? | | | +--rw nis-plus-domain-name? string | | +--rw sntp-server-option! {sntp-server-op}? | | | +--rw sntp-server* [sntp-serv-id] | | | +--rw sntp-serv-id uint8 | | | +--rw sntp-serv-addr inet:ipv6-address |+--rw info-refresh-time-option || +--rwenable booleaninfo-refresh-time-option! {info-refresh-time-op}? | | | +--rw info-refresh-time yang:timeticks |+--rw cli-fqdn-option || +--rwenable booleanclient-fqdn-option! {client-fqdn-op}? | | | +--rw server-initiate-update boolean | | | +--rw client-initiate-update boolean | | | +--rw modify-name-from-cli boolean |+--rw posix-timezone-option || +--rwenable booleanposix-timezone-option! {posix-timezone-op}? | | | +--rw tz-posix string |+--rw posix-timezone-db-option || +--rwenable booleantzdb-timezone-option! {tzdb-timezone-op}? | | | +--rw tz-database string |+--rw ntp-server-option || +--rwenable booleanntp-server-option! {ntp-server-op}? | | | +--rw ntp-server* [ntp-serv-id] | | | +--rw ntp-serv-id uint8 | | | +--rwntp-serv-addr-suboption inet:ipv6-address(ntp-time-source-suboption)? | | | +--:(server-address) | | | | +--rwntp-serv-mul-addr-suboptionntp-serv-addr-suboption* inet:ipv6-address | | | +--:(server-multicast-address) | | | | +--rwntp-serv-fqdn-suboption stringntp-serv-mul-addr-suboption* inet:ipv6-address | | | +--:(server-fqdn) | | | +--rwnetwork-boot-optionntp-serv-fqdn-suboption* string | | +--rwenable booleanboot-file-url-option! {boot-file-url-op}? | | | +--rw boot-file* [boot-file-id] | | | +--rw boot-file-id uint8 | | | +--rw suitable-arch-type* uint16 | | | +--rw suitable-net-if* uint32 | | | +--rw boot-file-url string | | +--rw boot-file-param-option! {boot-file-param-op}? | | | +--rw boot-file-paras* [para-id] | | | +--rw para-id uint8 | | | +--rw parameter string |+--rw aftr-name-option || +--rwenable booleanaftr-name-option! {aftr-name-op}? | | | +--rw tunnel-endpoint-name string |+--rw kerberos-option || +--rwenable booleankbr-default-name-option! {kbr-default-name-op}? | | | +--rw default-realm-name string | | +--rw kbr-kdc-option! {kbr-kdc-op}? | | | +--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 | | +--rwaddr-selection-optionsol-max-rt-option! {sol-max-rt-op}? | | | +--rwenable booleansol-max-rt-value yang:timeticks | | +--rw inf-max-rt-option! {inf-max-rt-op}? | | | +--rw inf-max-rt-value yang:timeticks | | +--rw addr-selection-option! {addr-selection-op}? | | | +--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| +--rwpcp-server-optionpcp-server-option! {pcp-server-op}? | |+--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 || +--rwenable booleans46-rule-option! {s46-rule-op}? | | | +--rw s46-rule* [rule-id] | | | +--rw rule-id uint8 | | | +--rw rule-type enumeration | | | +--rw prefix4-len uint8 | | | +--rw ipv4-prefix inet:ipv4-prefix | | | +--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 || +--rwenable booleans46-br-option! {s46-br-op}? | | | +--rw br* [br-id] | | | +--rw br-id uint8 | | | +--rw br-ipv6-addr inet:ipv6-address | | +--rwoperator-option-ipv6-addresss46-dmr-option! {s46-dmr-op}? | | | +--rwenable booleandmr* [dmr-id] | | | +--rwoperator-ipv6-addr* [operator-ipv6-addr-id]dmr-id uint8 | | | +--rwoperator-ipv6-addr-iddmr-prefix-len uint8 | |+--rw operator-ipv6-addr inet:ipv6-address| +--rwoperator-option-single-flagdmr-ipv6-prefix inet:ipv6-prefix | | +--rwenable booleans46-v4-v6-binding-option! {s46-v4-v6-binding-op}? | | | +--rwflag* [flag-id]ce* [ce-id] | | | +--rwflag-idce-id uint8 | |+--rw flag-value boolean| +--rwoperator-option-ipv6-prefixipv4-addr inet:ipv4-address | | | +--rwenable booleanbind-prefix6-len uint8 | | | +--rwoperator-ipv6-prefix* [operator-ipv6-prefix-id]bind-ipv6-prefix inet:ipv6-prefix | | | +--rwoperator-ipv6-prefix-id uint8port-parameter | | | +--rwoperator-ipv6-prefix6-lenoffset uint8 | |+--rw operator-ipv6-prefix inet:ipv6-prefix| +--rwoperator-option-int32psid-len uint8 | | | +--rwenable booleanpsid uint16 | | +--rwint32val* [int32val-id]operator-option-ipv6-address!{operator-op-ipv6-address}? | | | +--rwint32val-id uint8operator-ipv6-addr* [operator-ipv6-addr-id] | | | +--rwint32val uint32operator-ipv6-addr-id uint8 | | | +--rwoperator-option-int16operator-ipv6-addr inet:ipv6-address | | +--rwenable booleanoperator-option-single-flag!{operator-op-single-flag}? | | | +--rwint16val* [int16val-id]flag* [flag-id] | | | +--rwint16val-idflag-id uint8 | |+--rw int16val uint16| +--rwoperator-option-int8flag-value boolean | | +--rwenable booleanoperator-option-ipv6-prefix!{operator-op-ipv6-prefix}? | | | +--rwint8val* [int8val-id]operator-ipv6-prefix* [operator-ipv6-prefix-id] | | | +--rwint8val-idoperator-ipv6-prefix-id uint8 | | | +--rwint8valoperator-ipv6-prefix6-len uint8 | | | +--rwoperator-option-urioperator-ipv6-prefix inet:ipv6-prefix | | +--rwenable booleanoperator-option-int32! {operator-op-int32}? | | | +--rwuri* [uri-id]int32val* [int32val-id] | | | +--rwuri-idint32val-id uint8 | |+--rw uri string| +--rwoperator-option-textstringint32val uint32 | | +--rwenable booleanoperator-option-int16! {operator-op-int16}? | | | +--rwtextstring* [textstring-id]int16val* [int16val-id] | | | +--rwtextstring-idint16val-id uint8 | |+--rw textstring string| +--rwoperator-option-var-dataint16val uint16 | | +--rwenable booleanoperator-option-int8! {operator-op-int8}? | | | +--rwint32val* [var-data-id]int8val* [int8val-id] | | | +--rwvar-data-idint8val-id uint8 | |+--rw var-data binary| +--rwoperator-option-dns-wireint8val uint8 | | +--rwenable booleanoperator-option-uri! {operator-op-uri}? | |+--rw operator-option-dns-wire*| +--rw uri* [uri-id] |[operator-option-dns-wire-id]| | +--rwoperator-option-dns-wire-iduri-id uint8 | |+--rw operator-option-dns-wire binary| +--rws46-dmr-optionuri string | | +--rwenable booleanoperator-option-textstring! {operator-op-textstring}? | | | +--rwdmr* [dmr-id]textstring* [textstring-id] | | | +--rwdmr-idtextstring-id uint8 | | | +--rwdmr-prefix-len uint8textstring string | | +--rwdmr-ipv6-prefix inet:ipv6-prefixoperator-option-var-data! {operator-op-var-data}? |+--rw s46-v4-v6-binding-option|+--rw enable boolean| +--rwce* [ce-id]int32val* [var-data-id] |+--rw ce-id uint8|+--rw ipv4-addr inet:ipv4-address| +--rwbind-prefix6-lenvar-data-id uint8 | | | +--rwbind-ipv6-prefix inet:ipv6-prefixvar-data binary | | +--rwport-parameteroperator-option-dns-wire! {operator-op-dns-wire}? | | +--rwoffset uint8operator-option-dns-wire* [operator-option-dns-wire-id] | | +--rwpsid-lenoperator-option-dns-wire-id uint8 | | +--rwpsid uint16operator-option-dns-wire binary | +--rw network-ranges |+--rw option-set-id? uint8| +--rw network-range* [network-range-id] | | +--rw network-range-iduint8uint32 | | +--rw network-description string | | +--rw network-prefix inet:ipv6-prefix | | +--rw inherit-option-set boolean | | +--rwoption-set-id uint8option-set-id? -> /server/server-config/option-sets/option-set/id | | +--rw reserved-addresses | | | +--rw static-binding* [cli-id] | | | | +--rw cli-id uint32 | | | | +--rw duid | | | | | +--rw(duid-type)?type-code? uint16 | | | |+--:(duid-llt)| +--rw (duid-type)? | | | |+--rw duid-llt-hardware-type? uint16| +--:(duid-llt) | | | | | | +--rwduid-llt-time?duid-llt-hardware-type? uint16 | | | | | | +--rw duid-llt-time? yang:timeticks | | | | | | +--rw duid-llt-link-layer-addr?| | | | |yang:mac-address | | | | | +--:(duid-en) | | | | | | +--rw duid-en-enterprise-number? uint32 | | | | | | +--rw duid-en-identifier? string | | | | | +--:(duid-ll) | | | | | | +--rw duid-ll-hardware-type? uint16 | | | | | | +--rwduid-ll-time?duid-ll-link-layer-addr? yang:mac-address | | | | | +--:(duid-uuid) | | | | |yang:timeticks| +--rw uuid? yang:uuid | | | | | +--:(duid-invalid) | | | | | +--rw data? binary | | | | +--rw reserv-addr* inet:ipv6-address | | | +--rw other-reserv-addr* inet:ipv6-address | | +--rw reserved-prefixes | | | +--rw static-binding* [cli-id] | | | | +--rw cli-id uint32 | | | | +--rw duid | | | | | +--rw type-code? uint16 | | | | | +--rw (duid-type)? | | | | | +--:(duid-llt) | | | | | | +--rw duid-llt-hardware-type? uint16 | | | | | | +--rw duid-llt-time? yang:timeticks | | | | | |yang:timeticks | | | | |+--rw duid-llt-link-layer-addr?| | | | |yang:mac-address | | | | | +--:(duid-en) | | | | | | +--rw duid-en-enterprise-number? uint32 | | | | | | +--rw duid-en-identifier? string | | | | | +--:(duid-ll) | | | | | | +--rw duid-ll-hardware-type? uint16 | | | | | | +--rwduid-ll-time?duid-ll-link-layer-addr? yang:mac-address | | | |yang:timeticks| +--:(duid-uuid) | | | | | | +--rw uuid? yang:uuid | | | | | +--:(duid-invalid) | | | | | +--rw data? binary | | | | +--rw reserv-prefix-len uint8 | | | | +--rw reserv-prefix inet:ipv6-prefix | | | +--rw exclude-prefix-len uint8 | | | +--rw exclude-prefix inet:ipv6-prefix | | | +--rw other-reserv-prefix* [reserv-id] | | | +--rw reserv-iduint8uint32 | | | +--rw prefix-len uint8 | | | +--rw prefix inet:ipv6-prefix | | +--rw address-pools | | | +--rw address-pool* [pool-id] | | | +--rw pool-iduint8uint32 | | | +--rwpool-prefixpool-prefi inet:ipv6-prefix | | | +--rw start-address inet:ipv6-address-no-zone | | | +--rw end-address inet:ipv6-address-no-zone | | | +--rw renew-time yang:timeticks | | | +--rw rebind-time yang:timeticks | | | +--rw preferred-lifetime yang:timeticks | | | +--rw valid-lifetime yang:timeticks | | |+--ro total-ipv6-count uint64 | | | +--ro used-ipv6-count uint64 | | |+--rwutilization-ratiomax-address-utilization-ratio threshold | | | +--rw inherit-option-set boolean | | | +--rw option-set-iduint8 | | +--ro binding-info* [cli-id] | | +--ro cli-id uint32 | | +--ro duid | | | +--ro (duid-type)? | | | +--:(duid-llt) | | | | +--ro duid-llt-hardware-type? uint16 | | | | +--ro duid-llt-time? | | | | | yang:timeticks | | | | +--ro duid-llt-link-layer-addr? | | | | yang:mac-address | | | +--:(duid-en) | |-> /server/server-config/option-sets/option-set/id | |+--ro duid-en-enterprise-number? uint32 | | | | +--ro duid-en-identifier? string | | | +--:(duid-ll) | | | +--ro duid-ll-hardware-type? uint16 | | | +--ro duid-ll-time? | | | yang:timeticks | | +--ro cli-ia* [iaid] | | +--ro ia-type string | | +--ro iaid uint32 | | +--ro cli-addr* inet:ipv6-address | | +--ro pool-id uint8 |+--rw prefix-pools | | | +--rw prefix-pool* [pool-id] | | | +--rw pool-iduint8uint32 | | | +--rw prefix inet:ipv6-prefix | | | +--rw prefix-length uint8 | | | +--rw renew-time yang:timeticks | | | +--rw rebind-time yang:timeticks | | | +--rw preferred-lifetime yang:timeticks | | | +--rw valid-lifetime yang:timeticks | | | +--rwutilization-ratiomax-prefix-utilization-ratio threshold | | | +--rw inherit-option-set boolean | | | +--rwoption-set-id uint8option-set-id? -> /server/server-config/option-sets/option-set/id | |+--ro binding-info*+--rw hosts | | +--rw host* [cli-id] | |+--ro+--rw cli-id uint32 | |+--ro+--rw duid | | |+--ro+--rw type-code? uint16 | | | +--rw (duid-type)? | | | +--:(duid-llt) | | | |+--ro+--rw duid-llt-hardware-type? uint16 | | | |+--ro+--rw duid-llt-time?| | | | |yang:timeticks | | | |+--ro+--rw duid-llt-link-layer-addr?| | | |yang:mac-address | | | +--:(duid-en) | | | |+--ro+--rw duid-en-enterprise-number? uint32 | | | |+--ro+--rw duid-en-identifier? string | | | +--:(duid-ll) | | |+--ro| +--rw duid-ll-hardware-type? uint16 | | |+--ro duid-ll-time?| +--rw duid-ll-link-layer-addr? yang:mac-address | |yang:timeticks| +--:(duid-uuid) |+--ro cli-iapd* [iaid]| |+--ro iaid uint32| +--rw uuid? yang:uuid |+--ro cli-prefix* inet:ipv6-prefix| |+--ro cli-prefix-len* uint8+--:(duid-invalid) | |+--ro pool-id uint8| +--rwhostsdata? binary |+--rw host* [cli-id] | +--rw cli-id uint32 | +--rw duid | | +--rw (duid-type)? | | +--:(duid-llt) | | | +--rw duid-llt-hardware-type? uint16 | | | +--rw duid-llt-time? | | | | yang:timeticks | | | +--rw duid-llt-link-layer-addr? | | | yang:mac-address | | +--:(duid-en) | | | +--rw duid-en-enterprise-number? uint32 | | | +--rw duid-en-identifier? string | | +--:(duid-ll) | | +--rw duid-ll-hardware-type? uint16 | | +--rw duid-ll-time? | | yang:timeticks| +--rw inherit-option-set boolean | | +--rwoption-set-id uint8option-set-id? -> /server/server-config/option-sets/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 subscriberuint8uint32 | | | +--rw subscriber-id string | | +--rw remote-host* [ent-num] | | +--rw ent-num uint32 | | +--rw remote-id string | +--rw rsoo-enabled-options | +--rw rsoo-enabled-option* [option-code] | +--rw option-code uint16 | +--rw description string +--ropacket-statsserver-state +--rosolicit-count uint32network-ranges | +--rorequest-count uint32network-range* [network-range-id] | +--rorenew-countnetwork-range-id uint32 | +--rorebind-count uint32address-pools | | +--rodecline-count uint32address-pool* [pool-id] | | | +--rorelease-countpool-id uint32 | | | +--roinfo-req-count uint32total-ipv6-count uint64 | | | +--roadvertise-count uint32used-ipv6-count uint64 | | | +--roconfirm-count uint32address-utilization-ratio uint16 | | +--roreply-countbinding-info* [cli-id] | | +--ro cli-id uint32 | | +--roreconfigure-countduid | | | +--ro type-code? uint16 | | | +--ro (duid-type)? | | | +--:(duid-llt) | | | | +--ro duid-llt-hardware-type? uint16 | | | | +--ro duid-llt-time? yang:timeticks | | | | +--ro duid-llt-link-layer-addr? yang:mac-address | | | +--:(duid-en) | | | | +--ro duid-en-enterprise-number? uint32 | | | | +--rorelay-forward-countduid-en-identifier? string | | | +--:(duid-ll) | | | | +--ro duid-ll-hardware-type? uint16 | | | | +--ro duid-ll-link-layer-addr? yang:mac-address | | | +--:(duid-uuid) | | | | +--ro uuid? yang:uuid | | | +--:(duid-invalid) | | | +--ro data? binary | | +--ro cli-ia* [iaid] | | +--ro ia-type string | | +--ro iaid uint32 | | +--rorelay-reply-countcli-addr* inet:ipv6-address | | +--ro pool-id uint32Figure 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 bytes) content field. o pd-function: Whether the server can act as a delegating router to perform prefix delegation [RFC3633]. o operator-option-ipv6-address, operator-option-single-flag, operator-option-ipv6-prefix, operator-option-int32, operator- option-int16, operator-option-int8, operator-option-uri, operator- option-textstring, operator-option-var-data, operator-option-dns- wire: are generic option formats described in [RFC7227]. 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 interfaces-config: A leaf list to denote which one or more interfaces the server should listen on. The default value is to listen on all the interfaces. This node is also used to set a unicast address for the server to listen with a specific interface. For example, if the server is being configured to listen on a unicast address assigned to a specific interface, the format "eth1/2001:db8::1" can be used. 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], [RFC7598]. 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. With the "new-or-standard-option" list, it is easy to extend the model when new options are defined. We could also use the "new-or-standard-option" list to define an IETF standard option. 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". 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-enabled-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. 2.2. DHCPv6 Relay Tree Diagrams module: ietf-dhcpv6 +--rw relay! +--rw relay-attributes|+--rw name? string+--ro prefix-pools | | +--ro prefix-pool* [pool-id] | | | +--ro pool-id uint32 | | | +--ro prefix-utilization-ratio uint16 | | +--ro binding-info* [cli-id] | | +--ro cli-id uint32 | | +--ro duid | | | +--ro type-code? uint16 | | | +--ro (duid-type)? | | | +--:(duid-llt) | | | | +--ro duid-llt-hardware-type? uint16 | | | | +--ro duid-llt-time? yang:timeticks |+--rw description? string|+--rw dest-addrs* inet:ipv6-address|+--rw subscribers* [subscriber]| +--ro duid-llt-link-layer-addr? yang:mac-address |+--rw subscriber uint8| |+--rw subscriber-id string+--:(duid-en) |+--rw remote-host* [ent-num]| |+--rw ent-num| +--ro duid-en-enterprise-number? uint32 | |+--rw remote-id| | +--ro duid-en-identifier? string |+--rw vendor-info|+--rw ent-num| +--:(duid-ll) | | | | +--ro duid-ll-hardware-type? uint16 | | | | +--ro duid-ll-link-layer-addr? yang:mac-address | | | +--:(duid-uuid) | | | | +--ro uuid? yang:uuid | | | +--:(duid-invalid) | | | +--ro data? binary | | +--ro cli-iapd* [iaid] | | +--ro iaid uint32 |+--rw data* string +--rw relay-supplied-options-option|+--rw rsoo-set* [rsoo-set-id]+--ro cli-prefix* inet:ipv6-prefix |+--rw rsoo-set-id| +--ro cli-prefix-len* uint8 |+--rw erp-local-domain-name-option|+--rw enable boolean+--ro pool-id uint32 |+--rw erp-for-client*+--ro address-prefix-assign-param* [cli-id] |+--rw+--ro cli-id uint32 |+--rw+--ro source-ipv6-addr? inet:ipv6-address | +--ro duid | | +--ro type-code? uint16 | | +--ro (duid-type)? | | +--:(duid-llt) | | | +--ro duid-llt-hardware-type? uint16 | | | +--ro duid-llt-time? yang:timeticks | | | +--ro duid-llt-link-layer-addr? yang:mac-address | | +--:(duid-en) | | | +--ro duid-en-enterprise-number? uint32 | | | +--ro duid-en-identifier? string | | +--:(duid-ll) | | | +--ro duid-ll-hardware-type? uint16 | | | +--ro duid-ll-link-layer-addr? yang:mac-address | | +--:(duid-uuid) | | | +--ro uuid? yang:uuid | | +--:(duid-invalid) | | +--ro data? binary | +--ro iaid* uint32 | +--ro preferred-addr* inet:ipv6-address | +--ro preferred-prefix-len* uint8 | +--ro client-fqdn? string | +--ro client-link-layer-addr? uint16 | +--ro client-enterprise-number? uint32 | +--ro client-sys-archi-type* uint16 +--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 +--ro relay-forward-count uint32 +--ro relay-reply-count uint32 notifications: +---n notifications +--ro dhcpv6-server-event +--ro pool-running-out | +--ro max-address-utilization-ratio uint16 | +--ro address-utilization-ratio uint16 | +--ro max-prefix-utilization-ratio uint16 | +--ro prefix-utilization-ratio uint16 | +--ro duid | |+--rw+--ro type-code? uint16 | | +--ro (duid-type)? | | +--:(duid-llt) | | |+--rw+--ro duid-llt-hardware-type? uint16 | | |+--rw+--ro duid-llt-time?| | | |yang:timeticks | | |+--rw+--ro duid-llt-link-layer-addr?| | |yang:mac-address | | +--:(duid-en) | | |+--rw+--ro duid-en-enterprise-number? uint32 | | |+--rw+--ro duid-en-identifier? string | | +--:(duid-ll) | |+--rw| +--ro duid-ll-hardware-type? uint16 | |+--rw duid-ll-time?| +--ro duid-ll-link-layer-addr? yang:mac-address | |yang:timeticks+--:(duid-uuid) |+--rw erp-name| | +--ro uuid? yang:uuid | | +--:(duid-invalid) | | +--ro data? binary | +--ro serv-name? string+--rw relay-if* [if-name]|+--rw if-name+--ro pool-name string +--ro invalid-client-detected +--ro duid |+--rw enable boolean+--ro type-code? uint16 |+--rw ipv6-address? inet:ipv6-address+--ro (duid-type)? |+--rw interface-id? string+--:(duid-llt) |+--rw rsoo-set* uint8|+--rw pd-route* [pd-route-id]+--ro duid-llt-hardware-type? uint16 | |+--rw pd-route-id uint8+--ro duid-llt-time? yang:timeticks | |+--rw requesting-router-id uint32+--ro duid-llt-link-layer-addr? yang:mac-address | +--:(duid-en) |+--rw delegating-router-id| +--ro duid-en-enterprise-number? uint32 | |+--rw next-router inet:ipv6-address+--ro duid-en-identifier? string | +--:(duid-ll) |+--rw last-router inet:ipv6-address|+--rw next-entity* [dest-addr]+--ro duid-ll-hardware-type? uint16 |+--rw dest-addr inet:ipv6-address|+--rw available boolean+--ro duid-ll-link-layer-addr? yang:mac-address |+--rw multicast+--:(duid-uuid) | | +--ro uuid? yang:uuid | +--:(duid-invalid) | +--ro data? binary +--ro description? string Figure 1: DHCPv6 Data Model Structure Introduction of important nodes: o server-config: This container contains the configuration data of a server. 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 bytes) content field. Currently there are four defined types of DUIDs in [RFC3315] and [RFC6355] - DUID- LLT, DUID-EN, DUID-LL and DUID-UUID. DUID-INVALID represents those unconventional DUIDs. o pd-function: Whether the server can act as a delegating router to perform prefix delegation [RFC3633]. o operator-option-ipv6-address, operator-option-single-flag, operator-option-ipv6-prefix, operator-option-int32, operator- option-int16, operator-option-int8, operator-option-uri, operator- option-textstring, operator-option-var-data, operator-option-dns- wire: are generic option formats described in [RFC7227]. o stateless-service: A boolean| +--rwvalue specifies whether the serverboolean | +--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 +--ro relay-for-sent-count uint32 +--ro relay-rep-sent-count uint32 +--ro discarded-packet-count uint32 Introductionsupport 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 interfaces-config: A leaf list to denote which one or more interfaces the server should listen on. The default value is to listen on all the interfaces. This node is also used to set a unicast address for the server to listen with a specific interface. For example, if the server is being configured to listen on a unicast address assigned to a specific interface, the format "eth1/2001:db8::1" can be used. 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], [RFC7598]. 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 ofimportant nodes: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 'presence' statement to indicate whether this option (container) will be included in the current option set or not. In addition, each container also has a 'if-feature' statement to indicate whether the server supports this option (container). 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. orelay-attributes: Aaddress-pools: Under the "network-range" list, a container describessome basic attributes oftherelay agent including some relay agentDHCPv6 server's address pools for a specificoptions data that neednetwork is defined. This container supports the server to be configuredpreviously. Such options include Remote-Id option and Subscriber-Id option.at a pool level. odest-addrs: Eachaddress-pool: A DHCPv6relay agent mayserver can be configured with several address pools for alist of destination addresses.specific network. Thisnodelist defines sucha listaddress pools which are distinguish by the key called "pool-id". o max-address-utilization-ratio: The threshold ofIPv6 addresses that may include unicast addresses, multicast addresses or other addresses.address pool utiliztion, the value of which is settable. orelay-supplied-options-option: DHCPv6 relay agent could provide somebinding-info: A list records a binding information for each DHCPv6 client thatwouldhas already been allocated IPv6 addresses. o prefix-pools: If a server supports prefix delegation function, this container under the "network-range" list will beuseful to DHCPv6 client. Since relay agent cannot provide options directlyvalid to define theclient, [RFC6422] defines RSOO-enabled options to propose optionsdelegating router's prefix pools for a specific network. This container also supports the server tosendbe 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". o max-prefix-utilization-ratio: The threshold of prefix pool utiliztion, theclient.value of which is settable. 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 containermodels such RSOO- enabled options. o rsoo-set: Thisinclude a listunder the "relay-supplied-options-option" container is similarcalled "host" to allow the"option-set" defined inserverfeature. It allows the relay to implement several sets of RSOO- enabled optionscarrying different parameters (e.g. option sets) for differentinterfaces. The list only include the EAP Re-authentication Protocol (ERP) Local Domain Name DHCPv6 Option definedhosts. o relay-opaque-paras: This container contains some opaque values in[RFC6440], since it is the only one RSOO-enabledRelay Agent optionsaccepted by IANA so far. o relay-if: A relay agent may have several interfaces, we should provide a waythat need toconfigure and manage parametersbe configured on theinterface- level. A list that describes specific interfacesserver side only for value match. Such Relay Agent options include Interface- Id option, Remote-Id option andtheir corresponding parameters is employed to fulfilSubscriber-Id option. o rsoo-enabled-options: [RFC6422] requires that theconfigfuration. Here we useserver SHOULD have an administrator-configurable list of RSOO-enabled options. This container include astringlist called"if-name" as"rsoo-enabled-option" to allow new RSOO-enabled options to be defined at thekey of list.server side. opd-route: A sub-container of "relay-if" which describes the route for delegated prefixes intoserver-state: This container includes theprovider edge router.state data of a server. onext-entity:address-prefix-assign-param: Thisnode defines alist includes some parameters/ identifiers thatis used to describethenext hop entity ofserver obtains from DHCPv6 options in thisrelay agent. Different entities are distinguished by their addresses.network-range. The server may take these parameters/identifiers into account when assigning a(n) address/prefix. o packet-stats: A containershows packet state information of a specific data communication. o relay-stats: The "relay-stats" container records andpresents theoverallpacket statisticsofrelated to therelay agent. 2.3.DHCPv6Client Tree Diagrams module: ietf-dhcpv6 +--rw client! +--rw duid | +--rw (duid-type)? | +--:(duid-llt) | | +--rw duid-llt-hardware-type? uint16 | | +--rw duid-llt-time? yang:timeticks | | +--rw duid-llt-link-layer-addr? yang:mac-address | +--:(duid-en) | | +--rw duid-en-enterprise-number? uint32 | | +--rw duid-en-identifier? string | +--:(duid-ll) | +--rw duid-ll-hardware-type? uint16 | +--rw duid-ll-time? yang:timeticks +--rw client-if* [if-name] +--rw if-name string +--rw cli-id uint32 +--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-configured-options | +--rw new-or-standard-cli-option* [option-code] | | +--rw option-code uint16 | | +--rw option-name string | | +--rw option-description string | | +--rw option-reference? string | | +--rw option-value string | +--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] | | +--rw type-id uint16 | | +--rw most-preferred boolean | +--rw client-network-interface-option | | +--rw enable boolean | | +--rw type uint8 | | +--rw major uint8 | | +--rw minor uint8 | +--rw kerberos-principal-name-option | | +--rw enable boolean | |server. Information about 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 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. 2.2. DHCPv6 Relay Tree Diagrams module: ietf-dhcpv6-relay +--rwprincipal-name string |relay! +--rwclient-link-layer-addr-optionrelay-config | +--rwenable booleanrelay-attributes |+--rw link-layer-type uint16| +--rwlink-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:timeticks | +--ro t2-time yang:timeticks | +--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 | +--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-fqdnname? string |+--ro sntp-paras | | +--ro sntp-server* [sntp-serv-id] ||+--ro sntp-serv-id uint8+--rw description? string | |+--ro sntp-serv-addr+--rw dest-addrs* inet:ipv6-address |+--ro network-boot-paras| +--rw subscribers* [subscriber] |+--ro boot-file* [boot-file-id]| |+--ro boot-file-id+--rw subscriber uint8 | |+--ro suitable-arch-type* uint16| +--rw subscriber-id string |+--ro suitable-net-if*| +--rw remote-host* [ent-num] | | | +--rw ent-num uint32 | |+--ro boot-file-url| +--rw remote-id string | |+--ro boot-file-paras* [para-id]+--rw vendor-info | |+--ro para-id uint8+--rw ent-num uint32 | |+--ro parameter+--rw data* string |+--ro kerberos-paras+--rw rsoo-option-sets | |+--ro default-realm-name string+--rw option-set* [id] | |+--ro kdc-info* [kdc-id]+--rw id uint32 | |+--ro kdc-id uint8+--rw erp-local-domain-name-option! {erp-local-domain-name-op}? | |+--ro priority uint16+--rw erp-for-client* [cli-id] | |+--ro weight uint16+--rw cli-id uint32 | |+--ro transport-type uint8+--rw duid | |+--ro port-number| +--rw type-code? uint16 | |+--ro kdc-ipv6-addr inet:ipv6-address| +--rw (duid-type)? |+--ro realm-name string|+--ro addr-selection-paras| +--:(duid-llt) |+--ro automatic-row-add boolean| |+--ro prefer-temporary-addr boolean| +--rw duid-llt-hardware-type? uint16 |+--ro policy-table* [policy-id]| |+--ro policy-id uint8| +--rw duid-llt-time? yang:timeticks |+--ro label uint8| |+--ro precedence uint8| +--rw duid-llt-link-layer-addr? yang:mac-address |+--ro prefix-len uint8| |+--ro prefix inet:ipv6-prefix+--:(duid-en) |+--ro sol-max-rt yang:timeticks|+--ro inf-max-rt yang:timeticks|+--ro pcp-server-paras| +--rw duid-en-enterprise-number? uint32 |+--ro pcp-server* [pcp-serv-id]| |+--ro pcp-serv-id uint8| +--rw duid-en-identifier? string |+--ro pcp-serv-addr inet:ipv6-address|+--ro s46-rule-paras| +--:(duid-ll) |+--ro s46-rule* [rule-id]| |+--ro rule-id uint8| +--rw duid-ll-hardware-type? uint16 |+--ro rule-type enumeration| |+--ro ea-len uint8| +--rw duid-ll-link-layer-addr? yang:mac-address |+--ro prefix4-len uint8| |+--ro ipv4-prefix inet:ipv4-prefix+--:(duid-uuid) | |+--ro prefix6-len uint8| |+--ro ipv6-prefix inet:ipv6-prefix+--rw uuid? yang:uuid | |+--ro port-parameter| +--:(duid-invalid) |+--ro offset uint8| |+--ro psid-len uint8+--rw data? binary | |+--ro psid uint16+--rw erp-name string |+--ro s46-br-paras+--rw relay-if* [if-name] | +--rw if-name string |+--ro br* [br-id]+--rw enable boolean | +--rw ipv6-address? inet:ipv6-address |+--ro br-id uint8+--rw interface-id? string | +--rw rsoo-option-set-id? -> /relay/relay-config/rsoo-option-sets/option-set/id |+--ro br-ipv6-addr+--rw next-entity* [dest-addr] | +--rw dest-addr inet:ipv6-address |+--ro s46-dmr-paras+--rw available boolean | +--rw multicast boolean | +--rw server boolean +--rodmr* [dmr-id]relay-state +--ro relay-if* [if-name] | +--ro if-name string | +--rodmr-id uint8pd-route* [pd-route-id] | | +--rodmr-prefix-lenpd-route-id uint8 | | +--rodmr-ipv6-prefix inet:ipv6-prefix | +--ro s46-v4-v6-binding-parasrequesting-router-id uint32 | | +--roipv4-addr inet:ipv4-addressdelegating-router-id uint32 | | +--robind-prefix6-len uint8next-router inet:ipv6-address | | +--roport-parameter |last-router inet:ipv6-address | +--ro next-entity* [dest-addr] | +--rooffset uint8dest-addr inet:ipv6-address | +--ro packet-stats | +--ro solicit-rvd-count uint32 | +--ropsid-len uint8request-rvd-count uint32 | +--ro renew-rvd-count uint32 | +--ro rebind-rvd-count uint32 | +--ropsid uint16decline-rvd-count uint32 | +--ro release-rvd-count uint32 | +--roerp-local-domain-name stringinfo-req-rvd-count uint32 | +--rosupported-optionsrelay-for-rvd-count uint32 | +--rosupported-option* [option-code]relay-rep-rvd-count uint32 | +--rooption-code uint16packet-to-cli-count uint32 | +--rodescription stringadver-sent-count uint32 | +--ropacket-statsconfirm-sent-count uint32 | +--rosolicit-countreply-sent-count uint32 | +--rorequest-countreconfig-sent-count uint32 | +--rorenew-countrelay-for-sent-count uint32 | +--rorebind-countrelay-rep-sent-count uint32 +--rodecline-countrelay-stats +--ro cli-packet-rvd-count uint32 +--rorelease-countrelay-for-rvd-count uint32 +--roinfo-req-countrelay-rep-rvd-count uint32 +--roadvertise-countpacket-to-cli-count uint32 +--roconfirm-countrelay-for-sent-count uint32 +--roreply-countrelay-rep-sent-count uint32 +--roreconfigure-countdiscarded-packet-count uint32Introduction of important nodes: o client-if: A client may have several interfaces, it is more reasonable to configure and manage parameters on the interface- level. 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 leaf are same as the "duid" leaf 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.notifications: +---n notifications +--ro dhcpv6-relay-event +--ro topo-changed +--ro relay-if-name string +--ro first-hop boolean +--ro last-entity-addr inet:ipv6-address Introduction of important nodes: omo-tab: The management tab label indicatesrelay-config: This container contains theoperation modeconfiguration data of theDHCPv6 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 indicaterelay. o relay-attributes: A container describes some basic attributes of theclient will use stateless DHCPv6 to obtain configurationrelay agent including some relay agent specific options dataapart from addresses/prefixes data. 'm'=0 and 'o'=0 represent the client will not use DHCPv6 but use SLAACthat need toachieve configuration.be configured previously. Such options include Remote-Id option and Subscriber-Id option. ooro-options:dest-addrs: Each DHCPv6 relay agent may be configured with a list of destination addresses. Thiscontainer providenode defines such away to configure thelist ofoptionsIPv6 addresses thatthe client will request in its ORO option.may include unicast addresses, multicast addresses or other addresses. oclient-configured-options: Similarrsoo-options-sets: DHCPv6 relay agent could provide some information that would be useful to DHCPv6 client. Since relay agent cannot provide options directly to theserver, the client also needclient, [RFC6422] defines RSOO-enabled options toconfigure somepropose options for the server tofulfil some desired functions.send to the client. This containerinclude allmodels such RSOO-enabled options. o option-set: This list under the "rsoo-option-sets" container is similar to thepotential optionsthatneeddefined in server module. It allows the relay tobe configured atimplement 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 theclient side. The relevant RFCs that define thoseonly one RSOO-enabled optionsinclude: [RFC3315], [RFC4704], [RFC5970], [RFC6784], [RFC6939].accepted by IANA so far. oidentity-association: IA is a construct through which a server andrelay-if: A relay agent may have several interfaces, we should provide aclient can identify, group,way to configure and managea set of related IPv6 addresses. The key ofparameters on the"identity-association"interface- level. A list that describes specific interfaces and their corresponding parameters is employed to fulfil the configfuration. Here we use a4-byte number IAID defined in [RFC3315].string called "if-name" as the key of list. oif-other-paras: A client can obtain extra configuration data other than address and prefix information through DHCPv6 options.relay-state: This containerdescribes such datacontains theclient was configured through DHCPv6. The potentialconfiguration datamay include DNS server parameters, SIP server parameters and etc.of the relay. o pd-route: A sub-container of "relay-if" which describes the route for delegated prefixes into the provider edge router. osupported-options:next-entity: Thisstate data containernode defines a list that is used to describe the next hop entity ofoptions supportedthis relay agent. Different entities are distinguished bythe client for administrator to interrogate a client's capabilities.their addresses. o packet-stats: A containerrecords all theshows packetstatusstate information of a specificinterface. 2.4. Notifications Mechanism fordata communication. o relay-stats: The "relay-stats" container records and presents the overall packet statistics of the relay agent. Information about notifications: o topo-changed: raised when the topology of the relay agent is changed. 2.3. DHCPv6 Client Tree Diagrams module: ietf-dhcpv6-client +--rw client! +--rw client-config | +--rw duid | | +--rw type-code? uint16 | | +--rw (duid-type)? | | +--:(duid-llt) | | | +--rw duid-llt-hardware-type? uint16 | | | +--rwdhcpv6 +-- ...duid-llt-time? yang:timeticks | | | +--rw duid-llt-link-layer-addr? yang:mac-address | | +--:(duid-en) | | | +--rw duid-en-enterprise-number? uint32 | | | +--rw duid-en-identifier? string | | +--:(duid-ll) | | | +--rw duid-ll-hardware-type? uint16 | | | +--rw duid-ll-link-layer-addr? yang:mac-address | | +--:(duid-uuid) | | | +--rw uuid? yang:uuid | | +--:(duid-invalid) | | +--rw data? binary | +--rw client-if* [if-name] | +--rw if-name string | +--rw cli-id uint32 | +--rw description? string | +--rw pd-function boolean | +--rw rapid-commit boolean | +--rw mo-tab | | +--rw m-tab boolean | | +--rw o-tab boolean | +--rw client-configured-options | +--rw new-or-standard-cli-option* [option-code] | | +--rw option-code uint16 | | +--rw option-name string | | +--rw option-description string | | +--rw option-reference? string | | +--rw option-value string | +--rw option-request-option! {option-request-op}? | | +--rw oro-option* [option-code] | | +--rw option-code uint16 | | +--rw description string | +--rw user-class-option! {user-class-op}? | | +--rw user-class* [user-class-id] | | +--rw user-class-id uint8 | | +--rw user-class-data string | +--rw vendor-class-option! {vendor-class-op}? | | +--rw enterprise-number uint32 | | +--rw vendor-class* [vendor-class-id] | | +--rw vendor-class-id uint8 | | +--rw vendor-class-data string | +--rw client-fqdn-option! {client-fqdn-op}? | | +--rw fqdn string | | +--rw server-initiate-update boolean | | +--rw client-initiate-update boolean | +--rw client-arch-type-option! {client-arch-type-op}? | | +--rw architecture-types* [type-id] | | +--rw type-id uint16 | | +--rw most-preferred boolean | +--rw client-network-interface-identifier-option! {client-network-interface-identifier-op}? | | +--rw type uint8 | | +--rw major uint8 | | +--rw minor uint8 | +--rw kbr-principal-name-option! {kbr-principal-name-op}? | | +--rw principle-name* [principle-name-id] | | +--rw principle-name-id uint8 | | +--rw name-type int32 | | +--rw name-string string | +--rw kbr-realm-name-option! {kbr-realm-name-op}? | | +--rw realm-name string | +--rw client-link-layer-addr-option! {client-link-layer-addr-op}? | +--rw link-layer-type uint16 | +--rw link-layer-addr string +--ro client-state +--ro if-other-paras +--ro server-unicast-option! {server-unicast-op}? | +--ro server-address? inet:ipv6-address +--ro sip-server-domain-name-list-option! {sip-server-domain-name-list-op}? | +--ro sip-serv-domain-name string +--ro sip-server-address-list-option! {sip-server-address-list-op}? | +--ro sip-server* [sip-serv-id] | +--ro sip-serv-id uint8 | +--ro sip-serv-addr inet:ipv6-address +--ro dns-config-option! {dns-config-op}? | +--ro dns-server* [dns-serv-id] | +--ro dns-serv-id uint8 | +--ro dns-serv-addr inet:ipv6-address +--ro domain-searchlist-option! {domain-searchlist-op}? | +--ro domain-searchlist* [domain-searchlist-id] | +--ro domain-searchlist-id uint8 | +--ro domain-search-list-entry string +--ro nis-config-option! {nis-config-op}? | +--ro nis-server* [nis-serv-id] | +--ro nis-serv-id uint8 | +--ro nis-serv-addr inet:ipv6-address +--ro nis-plus-config-option! {nis-plus-config-op}? | +--ro nis-plus-server* [nis-plus-serv-id] | +--ro nis-plus-serv-id uint8 | +--ro nis-plus-serv-addr inet:ipv6-address +--ro nis-domain-name-option! {nis-domain-name-op}? | +--ro nis-domain-name? string +--ro nis-plus-domain-name-option! {nis-plus-domain-name-op}? | +--ro nis-plus-domain-name? string +--ro sntp-server-option! {sntp-server-op}? | +--ro sntp-server* [sntp-serv-id] | +--ro sntp-serv-id uint8 | +--ro sntp-serv-addr inet:ipv6-address +--ro info-refresh-time-option! {info-refresh-time-op}? | +--ro info-refresh-time yang:timeticks +--ro client-fqdn-option! {client-fqdn-op}? | +--ro server-initiate-update boolean | +--ro client-initiate-update boolean | +--ro modify-name-from-cli boolean +--ro posix-timezone-option! {posix-timezone-op}? | +--ro tz-posix string +--ro tzdb-timezone-option! {tzdb-timezone-op}? | +--ro tz-database string +--ro ntp-server-option! {ntp-server-op}? | +--ro ntp-server* [ntp-serv-id] | +--ro ntp-serv-id uint8 | +--ro (ntp-time-source-suboption)? | +--:(server-address) | | +--ro ntp-serv-addr-suboption* inet:ipv6-address | +--:(server-multicast-address) | | +--ro ntp-serv-mul-addr-suboption* inet:ipv6-address | +--:(server-fqdn) | +--ro ntp-serv-fqdn-suboption* string +--ro boot-file-url-option! {boot-file-url-op}? | +--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-param-option! {boot-file-param-op}? | +--ro boot-file-paras* [para-id] | +--ro para-id uint8 | +--ro parameter string +--ro aftr-name-option! {aftr-name-op}? | +--ro tunnel-endpoint-name string +--ro kbr-default-name-option! {kbr-default-name-op}? | +--ro default-realm-name string +--ro kbr-kdc-option! {kbr-kdc-op}? | +--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 sol-max-rt-option! {sol-max-rt-op}? | +--ro sol-max-rt-value yang:timeticks +--ro inf-max-rt-option! {inf-max-rt-op}? | +--ro inf-max-rt-value yang:timeticks +--ro addr-selection-option! {addr-selection-op}? | +--ro a-bit-set boolean | +--ro p-bit-set boolean | +--ro policy-table* [policy-id] | +--ro policy-id uint8 |+--n+--ro label uint8 | +--ro precedence uint8 | +--ro prefix-len uint8 | +--ro prefix inet:ipv6-prefix +--ro pcp-server-option! {pcp-server-op}? | +--ro pcp-server* [pcp-serv-id] | +--ro pcp-serv-id uint8 | +--ro pcp-serv-addr inet:ipv6-address +--ro s46-rule-option! {s46-rule-op}? | +--ro s46-rule* [rule-id] | +--ro rule-id uint8 | +--ro rule-type enumeration | +--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-option! {s46-br-op}? | +--ro br* [br-id] | +--ro br-id uint8 | +--ro br-ipv6-addr inet:ipv6-address +--ro s46-dmr-option! {s46-dmr-op}? | +--ro dmr* [dmr-id] | +--ro dmr-id uint8 | +--ro dmr-prefix-len uint8 | +--ro dmr-ipv6-prefix inet:ipv6-prefix +--ro s46-v4-v6-binding-option! {s46-v4-v6-binding-op}? +--ro ce* [ce-id] +--ro ce-id uint8 +--ro ipv4-addr inet:ipv4-address +--ro bind-prefix6-len uint8 +--ro bind-ipv6-prefix inet:ipv6-prefix +--ro port-parameter +--ro offset uint8 +--ro psid-len uint8 +--ro psid uint16 notifications: +---n notifications+--n dhcpv6-server-event+--ro dhcpv6-client-event +--ro ia-lease-event | +--ro event-type enumeration | +--ro duid | | +--ro type-code? uint16 | | +--ro (duid-type)? | | +--:(duid-llt) | | | +--ro duid-llt-hardware-type? uint16 | | | +--ro duid-llt-time? yang:timeticks | | | +--ro duid-llt-link-layer-addr? yang:mac-address | | +--:(duid-en) | | | +--ro duid-en-enterprise-number? uint32 | | | +--ro duid-en-identifier? string | | +--:(duid-ll) | | | +--ro duid-ll-hardware-type? uint16 | | | +--ro duid-ll-link-layer-addr? yang:mac-address | | +--:(duid-uuid) | | | +--ro uuid? yang:uuid | | +--:(duid-invalid) | | +--ro data? binary | +--ro iaid uint32 | +--ro serv-name? string | +--ro description? string +--ro invalid-ia-detected | +--ro duid | | +--ro type-code? uint16 | | +--ro (duid-type)? | | +--:(duid-llt) | | | +--ro duid-llt-hardware-type? uint16 | | | +--ro duid-llt-time? yang:timeticks | | | +--ro duid-llt-link-layer-addr? yang:mac-address |+--n pool-running-out| +--:(duid-en) |+--ro utilization-ratio uint16| | +--roduid duidtypeduid-en-enterprise-number? uint32 | | | +--roserv-name?duid-en-identifier? string | |+--ro pool-name string+--:(duid-ll) |+--n invalid-client-detected|+--ro duid duidtype| +--rodescription? string +--n dhcpv6-relay-eventduid-ll-hardware-type? uint16 |+--n topo-changed|+--ro relay-if-name string| +--rofirst-hop booleanduid-ll-link-layer-addr? yang:mac-address | | +--:(duid-uuid) | | | +--rolast-entity-addr inet:ipv6-address +--n dhcpv6-client-event +--n ia-lease-eventuuid? yang:uuid | | +--:(duid-invalid) | | +--roevent-type enumerationdata? binary | +--roduid duidtypecli-duid uint32 | +--ro iaid uint32 | +--ro serv-name? string | +--ro description? string+--n invalid-ia-detected+--ro retransmission-failed | +--ro duidduidtype| | +--roiaidtype-code? uint16 | | +--ro (duid-type)? | | +--:(duid-llt) | | | +--ro duid-llt-hardware-type? uint16 | | | +--ro duid-llt-time? yang:timeticks | | | +--ro duid-llt-link-layer-addr? yang:mac-address | | +--:(duid-en) | | | +--ro duid-en-enterprise-number? uint32 | | | +--roserv-name?duid-en-identifier? string | | +--:(duid-ll) | | | +--rodescription? string +--n retransmission-failedduid-ll-hardware-type? uint16 | | | +--roduid duidtypeduid-ll-link-layer-addr? yang:mac-address | | +--:(duid-uuid) | | | +--ro uuid? yang:uuid | | +--:(duid-invalid) | | +--ro data? binary | +--ro description enumeration+--n+--ro failed-status-turn-up +--ro duidduidtype| +--ro type-code? uint16 | +--ro (duid-type)? | +--:(duid-llt) | | +--ro duid-llt-hardware-type? uint16 | | +--ro duid-llt-time? yang:timeticks | | +--ro duid-llt-link-layer-addr? yang:mac-address | +--:(duid-en) | | +--ro duid-en-enterprise-number? uint32 | | +--ro duid-en-identifier? string | +--:(duid-ll) | | +--ro duid-ll-hardware-type? uint16 | | +--ro duid-ll-link-layer-addr? yang:mac-address | +--:(duid-uuid) | | +--ro uuid? yang:uuid | +--:(duid-invalid) | +--ro data? binary +--ro status-code enumerationInformation about notifications:Introduction of important nodes: opool-running-out: raised whenclient-config: This container includes theaddress/prefix pool is going to run out. A threshold for utilization ratioconfiguration data of thepool has been defined in the server feature so thatclient. o client-if: A client may have several interfaces, itwill notify the administrator when the utilization ratio reachesis more reasonable to configure and manage parameters on thethreshold,interface- level. The list defines a specific client interface andsuch thresholdits data. Different interfaces are distinguished by the "ifName" key which is asettable parameter.configurable string value. oinvalid-client-detected: raised when theduid: Each serverhas found aand clientwhich can be regarded as a potential attacker. Some description could alsohas only one DUID (DHCP Unique Identifier). The DUID here will beincluded. o topo-changed: raised when the topology of the relay agent is changed. o ia-lease-event: raised whencarried in theclient was allocatedClient ID option to identify anew IA fromspecific DHCPv6 client. This leaf are same as theserver or it renew/rebind/release its current IA."duid" leaf in "dhcpv6-server" feature. oinvalid-ia-detected: raised when the identity association ofpd-function: Whether the client canbe provedact as a requesting router tobe invalid. Possible condition includes duplicated address, illegal address, etc. o retransmission-failed: raised when the retransmission mechanism defined in [RFC3315] is failed.request prefixes using prefix delegation ([RFC3633]). ofailed-status-turn-up: raised when therapid-commit: '1' indicates a clientreceivescan initiate a Solicit-Reply messageincludes an unsuccessful Status Code option. 3. DHCPv6 YANG Model This module imports typedefs from [RFC6991]. <CODE BEGINS> file "ietf-dhcpv6@2017-10-26.yang" module ietf-dhcpv6 { namespace "urn:ietf:params:xml:ns:yang:ietf-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 sladjana.zechlin@telekom.de"; description "This model definesexchange by adding aYANG data model that can be usedRapid Commit option in Solicit message. '0' means the client is not allowed toconfigure and manageadd 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 DHCPv6server,client. 'm'=1 and 'o'=1 indicate the client will use DHCPv6relayto obtain all the configuration data. 'm'=1 andDHCPv6 client."; revision 2017-10-26 { description "version09: resolve feedbacks from IETF96"; reference "I-D: draft-ietf-dhc-dhcpv6-yang-04"; } revision 2016-06-18 { description "version08: resolve yang compiling error: top-level node must not be mandatory, wait for YANG doctor's review"; reference "I-D: draft-ietf-dhc-dhcpv6-yang-03"; } revision 2016-06-15 { description "version07: resolve yang compiling errors, wait for YANG doctor's review"; reference "I-D: draft-ietf-dhc-dhcpv6-yang-02"; } revision 2016-03-21 { description "version06: resolve feedbacks from IETF94"; reference "I-D: draft-ietf-dhc-dhcpv6-yang-01"; } revision 2015-10-16 { description "version05: Omit'o'=0 are a meaningless combination. 'm'=0 and 'o'=1 indicate thefeature statement. Modify model accordingclient will use stateless DHCPv6 tocommentsobtain configuration data apart fromHuawei. Also correct some grammar errors."; reference "I-D: draft-ietf-dhc-dhcpv6-yang-00"; } revision 2015-09-25 { description "version04: Correct duidaddresses/prefixes data. 'm'=0 andgrammar errors."; reference "I-D: draft-cui-dhc-dhcpv6-yang-04"; } revision 2015-07-01 { description "version03: Correct grammar errors."; reference "I-D: draft-cui-dhc-dhcpv6-yang-03"; } revision 2015-04-13 { description "version02: Correct grammar errors."; reference "I-D: draft-cui-dhc-dhcpv6-yang-02"; } revision 2015-04-02 { description "version01: Correct grammar errors, Reuse groupings, Update 'dhcpv6-relay' feature, Add notifications."; reference "I-D: draft-cui-dhc-dhcpv6-yang-01"; } revision 2015-03-04 { description "version00: Initial revision."; reference "I-D: draft-cui-dhc-dhcpv6-yang-00"; } /* * Typedef */ typedef threshold { type union { type uint16 { range 0..100; } type enumeration { enum "disabled" { description "No threshold"; } } } description "Threshold value in percent"; } /* * Grouping */ grouping vendor-infor { description "Vendor information."; container vendor-info { description ""; leaf ent-num { type uint32; mandatory true; description "enterprise number"; } leaf-list data { type string; description "specific vendor info"; } } } grouping duid { description "DHCP Unique Identifier"; reference "RFC3315: Section 9"; choice duid-type { description "Selects'o'=0 represent theformat forclient will not use DHCPv6 but use SLAAC to achieve configuration. o client-configured-options: Similar to theDUID."; case duid-llt { description "DUID Based on Link-layer Address Plus Time"; reference "RFC3315 Section 9.2"; leaf duid-llt-hardware-type { type uint16; description "Hardware type as assigned by IANA (RFC826)."; } leaf duid-llt-time { type yang:timeticks; description "The time value isserver, the client also need to configure some options to fulfil some desired functions. This container include all thetimepotential options thatthe DUID is generated represented in seconds since midnight (UTC), January 1, 2000, modulo 2^32."; } leaf duid-llt-link-layer-addr { type yang:mac-address; description "Link-layer address as described in RFC2464"; } } case duid-en { description "DUID Assigned by Vendor Based on Enterprise Number"; reference "RFC3315 Section 9.3"; leaf duid-en-enterprise-number { type uint32; description "Vendor's registered Private Enterprise Number as maintained by IANA"; } leaf duid-en-identifier { type string; description "Indentifier, uniqueneed to be configured at thedeviceclient side. The relevant RFCs thatis using it"; } } case duid-ll { description "DUID Based on Link-layer Address"; reference "RFC3315 Section 9.4"; leaf duid-ll-hardware-type { type uint16; description "Hardware type as assigned by IANA (RFC826)."; } leaf duid-ll-time { type yang:timeticks; description "The time value isdefine those options include: [RFC3315], [RFC4704], [RFC5970], [RFC6784], [RFC6939]. o option-request-option: This container provide a way to configure thetimelist of options that theDUID is generated representedclient will request inseconds since midnight (UTC), January 1, 2000, modulo 2^32."; } } } } grouping portset-para { description "portset parameters";its ORO option. o client-state: This containerport-parameter { description "port parameter"; leaf offset { type uint8; mandatory true; description "offset in a port set"; } leaf psid-len { type uint8; mandatory true; description "lengthincludes the state data ofa psid"; } leaf psid { type uint16; mandatory true; description "psid value"; } } } /* * Data Nodes */the client. 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 DHCPv6. The potential configuration data may include DNS server{ presence "Enables server"; description "dhcpv6parameters, SIP serverportion"; container serv-attributes { description "Thisparameters and etc. o packet-stats: A containercontains basic attributesrecords all the packet status information of aDHCPv6 server such as DUID,specific interface. Information about notifications: o ia-lease-event: raised when the client was allocated a new IA from the servername and so on. Some optional functions thator it renew/rebind/release its current IA. o invalid-ia-detected: raised when the identity association of the client can beprovided byproved to be invalid. Possible condition includes duplicated address, illegal address, etc. o retransmission-failed: raised when theserverretransmission mechanism defined in [RFC3315] isalso included."; leaf namefailed. o failed-status-turn-up: raised when the client receives a message includes an unsuccessful Status Code option. 3. DHCPv6 YANG Model 3.1. DHCPv6 Server YANG Model This module imports typedefs from [RFC6991]. <CODE BEGINS> file "ietf-dhcpv6-server@2017-12-22.yang" module ietf-dhcpv6-server {type string; description "server's name"; } container duidyang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-dhcpv6-server"; prefix "dhcpv6-server"; import ietf-inet-types {description "Sets the DUID"; uses duid;prefix inet; revision-date "2013-07-15"; }leaf-list ipv6-addressimport ietf-yang-types {type inet:ipv6-address; description "Server's IPv6 address.";prefix yang; revision-date "2013-07-15"; }leaf descriptionimport ietf-dhcpv6-options {type string; description "Description of the server.";prefix dhcpv6-options; revision-date "2017-12-22"; }leaf pd-function { type boolean; mandatory true;organization "DHC WG"; contact "yong@csnet1.cs.tsinghua.edu.cn lh.sunlinh@gmail.com ian.farrer@telekom.de sladjana.zechlin@telekom.de hezihao9512@gmail.com"; description"Whether the server can act as"This model defines adelegating routerYANG data model that can be used toperform prefix delegation ([RFC3633]).";configure and manage a DHCPv6 server."; revision 2017-12-22 { description "Resolve most issues on Ian's github."; reference "I-D: draft-ietf-dhc-dhcpv6-yang"; }leaf stateless-servicerevision 2017-11-24 {type boolean; mandatory true;description"A boolean value specifies whether"First version of the separated serversupport client-server exchanges involving two messages defined in ([RFC3315]).";specific YANG model."; reference "I-D: draft-ietf-dhc-dhcpv6-yang"; }leaf rapid-commit/* * Typedef */ typedef threshold { typeboolean; mandatory true; description "A boolean value specifies whether the server support client-server exchanges involving two messages defined in ([RFC3315])."; } leaf-list interfaces-configunion { typestring;uint16 { range 0..100; } type enumeration { enum "disabled" { description"A leaf list to denote which one or more interfaces the server should listen on. The default value is to listen on all the interfaces. This node is also used to set a unicast address for the server to listen with a specific interface. For example, if people want the server to listen on a unicast address with a specific interface, he can use the format like 'eth1/2001:db8::1'.";"No threshold"; } }uses vendor-infor;}container option-sets {description"DHCPv6 employs various options to carry additional information and parameters"Threshold value inDHCP messages. Thispercent"; } /* * Grouping */ grouping vendor-infor { description "Vendor information."; containerdefines all the possible options that need to be configured at the server side."; list option-setvendor-info {key option-set-id;description"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.";""; leafoption-set-ident-num { typeuint8;uint32; mandatory true; description"the option-set-id key";"enterprise number"; }list new-or-standard-optionleaf-list data {key option-code;type string; description"new or standard option";"specific vendor info"; } } } grouping duid { description "DHCP Unique Identifier"; reference "RFC3315: Section 9 and RFC6355: Section 4"; leafoption-codetype-code { type uint16;mandatory true;default 65535; description"the option"Type codekey";of this DUID"; } choice duid-type { default duid-invalid; description "Selects the format for the DUID."; case duid-llt { description "DUID Based on Link-layer Address Plus Time (Type 1 - DUID-LLT)"; reference "RFC3315 Section 9.2"; leafoption-nameduid-llt-hardware-type { typestring; mandatory true;uint16; description"the new option's name";"Hardware type as assigned by IANA (RFC826)."; } leafoption-descriptionduid-llt-time { typestring; mandatory true;yang:timeticks; description"description of new option";"The time value is the time that the DUID is generated represented in seconds since midnight (UTC), January 1, 2000, modulo 2^32."; } leafoption-referenceduid-llt-link-layer-addr { typestring;yang:mac-address; description"reference to the specification";"Link-layer address as described in RFC2464"; } } case duid-en { description "DUID Assigned by Vendor Based on Enterprise Number (Type 2 - DUID-EN)"; reference "RFC3315 Section 9.3"; leafoption-valueduid-en-enterprise-number { type uint32; description "Vendor's registered Private Enterprise Number as maintained by IANA"; } leaf duid-en-identifier { type string;mandatory true;description"the new option's value";"Indentifier, unique to the device that is using it"; } } case duid-ll { description "DUID Based on Link-layer Address (Type 3 - DUID-LL)"; reference "RFC3315 Section 9.4"; leafuser-class-valueduid-ll-hardware-type { typestring;uint16; description"use class option's value";"Hardware type as assigned by IANA (RFC826)."; } leafenterprise-numberduid-ll-link-layer-addr { typeuint32;yang:mac-address; description"enterprise number";"Link-layer address as described in RFC2464"; } } case duid-uuid { description "DUID Based on Universally Unique Identifier (Type 4 - DUID-UUID)"; reference "RFC6335 Defination of the UUID-Based Unique Identifier"; leafstore-client-link-layeruuid { typeboolean;yang:uuid; description"whether to store client's link layer address";"A Universally Unique IDentifier in the string representation defined in RFC 4122. The canonical representation uses lowercase characters"; }container preference-option} case duid-invalid { description"preference option";"DUID based on free raw bytes"; leafenabledata { typeboolean; mandatory true;binary; description"indicate whether this option will"The bits to beincluded inused as theoption set";identifier"; } }leaf preference-value { type uint8; mandatory true; description "the value for this option";} } /* * Data Nodes */ containersip-server-optionserver { presence "Enables the server"; description"sip"DHCPv6 serveroption"; //Note - thisportion"; /* * Configuration data */ containeris currently modelling two options (21 & 22). It would allow the //configserver-config { description "configuration tree ofa mixed listserver"; container serv-attributes { description "This container contains basic attributes ofdomain names and addresses inawayDHCPv6 server such as IPv6 address, server name and so on. Some optional functions thatdoesn't follow the //RFC. Needs tocan bebroken into SIP Domain list and SIP Address list containers reference "RFC3319: Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers";provided by 0the server is also included."; leafenablename { typeboolean; mandatory true;string; description"indicate whether this option will be included in the option set";"server's name"; }list sip-servercontainer duid {key sip-serv-id;description"sip server info"; leaf sip-serv-id"Sets the DUID"; uses duid; } leaf-list ipv6-address { typeuint8; mandatory true;inet:ipv6-address; description"sip server id";"Server's IPv6 address."; } leafsip-serv-domain-namedescription { type string;mandatory true;description"sip server domain name";"Description of the server."; } leafsip-serv-addrpd-function { typeinet:ipv6-address;boolean; mandatory true; description"sip"Whether the serveraddr"; } }can act as a delegating router to perform prefix delegation ([RFC3633])."; }container dns-config-option { description "OPTION_DNS_SERVERS (23) DNS recursive Name Server option"; reference "RFC3646: DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)";leafenablestateless-service { type boolean; mandatory true; description"indicate"A boolean value specifies whetherthis option will be includedthe server support client-server exchanges involving two messages defined inthe option set";([RFC3315])."; }list dns-server { key dns-serv-id; description "dns server info";leafdns-serv-idrapid-commit { typeuint8;boolean; mandatory true; description"DNS"A boolean value specifies whether the serverlist entry ID.";support client-server exchanges involving two messages defined in ([RFC3315])."; }leaf dns-serv-addrleaf-list interfaces-config { // Note - this should probably be references to // entries in the ietf-interfaces model typeinet:ipv6-address; mandatory true;string; description"DNS"A leaf list to denote which one or more interfaces the serveraddress."; }should listen on. The default value is to listen on all the interfaces. This node is also used to set a unicast address for the server to listen with a specific interface. For example, if people want the server to listen on a unicast address with a specific interface, he can use the format like 'eth1/2001:db8::1'."; } uses vendor-infor; } containerdomain-searchlist-optionoption-sets { description"OPTION_DOMAIN_LIST (24) Domain Search List Option"; reference "RFC3646: DNS Configuration"DHCPv6 employs various optionsfor Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"; leaf enableto carry additional information and parameters in DHCP messages. This container defines all the possible options that need to be configured at the server side. "; list option-set {type boolean; mandatory true;key id; description"indicate"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 'presence' statement to indicate whether this option (container) will be included in the current optionset"; } list domain-searchlist { key domain-searchlist-id; description "dnsset or not. In addition, each container also has a 'if-feature' statement to indicate whether the serverinfo"; leaf domain-searchlist-id { type uint8; mandatory true; description "Domain seachlist entry ID."; }supports this option (container)."; leafdomain-search-list-entryid { typestring; mandatory true;uint32; description"Domain search list entry.";"option set id"; } uses dhcpv6-options:server-option-definitions; uses dhcpv6-options:custom-option-definitions; } } containernis-config-option { description "OPTION_NIS_SERVERS (27) Network Information Service (NIS) Servers Option."; reference "RFC3989: Network Information Service (NIS) Configuration Options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"; leaf enablenetwork-ranges {type boolean; mandatory true;description"indicate whether"This model supports a hierarchy to achieve dynamic configuration. That is to say we could configure the server at different levels through thisoption willmodel. 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 beincluded inallocated to all theoption set"; }clients served by this server."; listnis-servernetwork-range { keynis-serv-id; description "nis server info"; leaf nis-serv-id { type uint8; mandatory true; description "nis server id"; } leaf nis-serv-addr { type inet:ipv6-address; mandatory true;network-range-id; description"nis"Under the 'network-ranges' container, a 'network-range' list is defined to configure the serveraddr"; } } } container nis-plus-config-option { description "OPTION_NISP_SERVERS (28): Network Information Service V2 (NIS+) Servers Option."; reference "RFC3989: Network Information Service (NIS) Configuration Options for Dynamic Host Configuration Protocolat 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) forIPv6 (DHCPv6)";different networks."; leafenablenetwork-range-id { typeboolean;uint32; mandatory true; description"indicate whether this option will be included in the option set";"equivalent to subnet id"; }list nis-plus-server { key nis-plus-serv-id; description "NIS+ server information.";leafnis-plus-serv-idnetwork-description { typeuint8;string; mandatory true; description"nisp server id";"description of the subnet"; } leafnis-plus-serv-addrnetwork-prefix { typeinet:ipv6-address;inet:ipv6-prefix; mandatory true; description"nisp server addr"; } }"subnet prefix"; }container sntp-server-option { description "OPTION_SNTP_SERVERS (31) Simple Network Time Protocol (SNTP) Servers Option"; reference "RFC4075: Simple Network Time Protocol (SNTP) Configuration Option for DHCPv6";leafenableinherit-option-set { type boolean; mandatory true; description "indicate whetherthis option will be included into inherit theoption set";configuration from higher level"; } leaf option-set-id { type leafref { path "/server/server-config/option-sets/option-set/id"; } description "The ID field of relevant option-set to be provisioned to clients of this network-range."; } container reserved-addresses { description "reserved addresses"; listsntp-serverstatic-binding { keysntp-serv-id;cli-id; description"sntp server info";"static binding of reserved addresses"; leafsntp-serv-idcli-id { typeuint8;uint32; mandatory true; description"sntp server"client id"; }leaf sntp-serv-addrcontainer duid { description "Sets the DUID"; uses duid; } leaf-list reserv-addr { type inet:ipv6-address;mandatory true;description"sntp server"reserved addr"; } } leaf-list other-reserv-addr { type inet:ipv6-address; description "other reserved addr"; } } containerinfo-refresh-time-optionreserved-prefixes { description"OPTION_INFORMATION_REFRESH_TIME (32) Information Refresh Time option."; reference "RFC4242: Information Refresh Time Option for Dynamic Host Configuration Protocol for IPv6 (DHCPv6";"reserved prefixes"; list static-binding { key cli-id; description "static binding"; leafenablecli-id { typeboolean;uint32; mandatory true; description"indicate whether this option will be included in"client id"; } container duid { description "Sets theoption set";DUID"; uses duid; } leafinfo-refresh-timereserv-prefix-len { type uint8; mandatory true; description "reserved prefix length"; } leaf reserv-prefix { typeyang:timeticks;inet:ipv6-prefix; mandatory true; description"The refresh time.";"reserved prefix"; } }container cli-fqdn-optionleaf exclude-prefix-len { type uint8; mandatory true; description"OPTION_CLIENT_FQDN (39) DHCPv6 Client FQDN Option"; reference "RFC4704: The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Client Fully Qualified Domain Name (FQDN) Option";"exclude prefix length"; } leafenableexclude-prefix { typeboolean;inet:ipv6-prefix; mandatory true; description"indicate whether this option will be included in the option set";"exclude prefix"; } list other-reserv-prefix { key reserv-id; description "other reserved prefix"; leafserver-initiate-updatereserv-id { typeboolean;uint32; mandatory true; description"server initiate";"reserved prefix id"; } leafclient-initiate-updateprefix-len { typeboolean;uint8; mandatory true; description"client initiate";"prefix length"; } leafmodify-name-from-cliprefix { typeboolean;inet:ipv6-prefix; mandatory true; description"modify by client";"reserved prefix"; } } } containerposix-timezone-optionaddress-pools { description"OPTION_NEW_POSIX_TIMEZONE (41) Posix Timezone option"; reference "RFC4822: Timezone Options for DHCP"; leaf enable"A container that describes the DHCPv6 server's address pools."; list address-pool {type boolean; mandatory true;key pool-id; description"indicate whether this option will"A DHCPv6 server can beincluded inconfigured with several address pools. This list defines such address pools which are distinguished by theoption set"; }key called 'pool-name'."; leaftz-posixpool-id { typestring;uint32; mandatory true; description"TZ Posix IEEE 1003.1 String"; }"pool id"; }container posix-timezone-db-option { description "OPTION_NEW_TZDB_TIMEZONE (42) Timezone Database option"; reference "RFC4822: Timezone Options for DHCP";leafenablepool-prefix { typeboolean;inet:ipv6-prefix; mandatory true; description"indicate whether this option will be included in the option set";"pool prefix"; } leaftz-databasestart-address { typestring;inet:ipv6-address-no-zone; mandatory true; description"Reference to the TZ Database"; }"start address"; }container ntp-server-optionleaf end-address {//This option looks like it needs work to correctly model the //option as defined in the RFC. description "OPTION_NTP_SERVER (56) NTP Server Option for DHCPv6"; reference "RFC5908: Network Time Protocol (NTP) Server Option for DHCPv6";type inet:ipv6-address-no-zone; mandatory true; description "end address"; } leafenablerenew-time { typeboolean;yang:timeticks; mandatory true; description"indicate whether this option will be included in the option set";"renew time"; }list ntp-server { key ntp-serv-id; description "ntp server info";leafntp-serv-idrebind-time { typeuint8;yang:timeticks; mandatory true; description"ntp server id";"rebind time"; } leafntp-serv-addr-suboptionpreferred-lifetime { typeinet:ipv6-address;yang:timeticks; mandatory true; description"ntp server addr";"preferred lifetime for IA"; } leafntp-serv-mul-addr-suboptionvalid-lifetime { typeinet:ipv6-address;yang:timeticks; mandatory true; description"ntp server multicast addr";"valid liftime for IA"; } leafntp-serv-fqdn-suboptionmax-address-utilization-ratio { typestring;threshold; mandatory true; description"ntp server fqdn"; } }"address pool utilization ratio threshold"; }container network-boot-option { description "network boot option";leafenableinherit-option-set { type boolean; mandatory true; description "indicate whetherthis option will be included into inherit theoption set";configuration from higher level"; }list boot-file { key boot-file-id; description "boot file info";leafboot-file-idoption-set-id { typeuint8;leafref { path "/server/server-config/option-sets/option-set/id"; } mandatory true; description"boot file id";"The ID field of relevant option-set to be provisioned to clients of this address-pool."; }leaf-list suitable-arch-type} } container prefix-pools {type uint16;description"architecture type"; } leaf-list suitable-net-if"If a server supports prefix delegation function, this container will be used to define the delegating router's refix pools."; list prefix-pool { key pool-id; 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'."; leaf pool-id { type uint32; mandatory true; description"network interface";"pool id"; } leafboot-file-urlprefix { typestring;inet:ipv6-prefix; mandatory true; description"url for boot file";"ipv6 prefix"; }list boot-file-paras { key para-id; description "boot file parameters";leafpara-idprefix-length { type uint8; mandatory true; description"parameter id";"prefix length"; } leafparameterrenew-time { typestring;yang:timeticks; mandatory true; description"parameter value"; } } }"renew time"; }container aftr-name-optionleaf rebind-time { type yang:timeticks; mandatory true; description"OPTION_AFTR_NAME (64) AFTR-Name DHCPv6 Option"; reference "RFC6334: Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Option for Dual-Stack Lite";"rebind time"; } leafenablepreferred-lifetime { typeboolean;yang:timeticks; mandatory true; description"indicate whether this option will be included in the option set";"preferred lifetime for IA"; } leaftunnel-endpoint-namevalid-lifetime { typestring;yang:timeticks; mandatory true; description"aftr name"; }"valid lifetime for IA"; }container kerberos-optionleaf max-prefix-utilization-ratio {//This needs re-working and possibly splitting into several option //containers to follow the RFC.type threshold; mandatory true; description"kerberos option"; reference "RFC6784: Kerberos Options for DHCPv6";"prefix pool utilization ratio threshold"; } leafenableinherit-option-set { type boolean; mandatory true; description"indicate whether this option will be included in the option set";"whether to inherit configuration from higher level"; } leafdefault-realm-nameoption-set-id { typestring; mandatory true;leafref { path "/server/server-config/option-sets/option-set/id"; } description"default realm name";"The ID field of relevant option-set to be provisioned to clients of this prefix-pool."; } } } container hosts { description "hosts level"; listkdc-infohost { keykdc-id;cli-id; description"kdc info";"specific host"; leafkdc-idcli-id { typeuint8;uint32; mandatory true; description"kdc"client id"; } container duid { description "Sets the DUID"; uses duid; } leafpriorityinherit-option-set { typeuint16;boolean; mandatory true; description"priority";"whether to inherit configuration from higher level"; } leafweightoption-set-id { typeuint16; mandatory true;leafref { path "/server/server-config/option-sets/option-set/id"; } description"weight";"The ID field of relevant option-set to be provisioned to clients of this prefix-pool."; } leaftransport-typenis-domain-name { typeuint8; mandatory true;string; description"transport type";"nis domain name"; } leafport-numbernis-plus-domain-name { typeuint16; mandatory true;string; description"port number";"nisp domain name"; } } } } } 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. Such Relay Agent options include Interface-Id option, Remote-Id option and Subscriber-Id option."; list relays { key relay-name; description "relay agents"; leafkdc-ipv6-addrrelay-name { typeinet:ipv6-address;string; mandatory true; description"kdc ipv6 addr";"relay agent name"; } list interface-info { key if-name; description "interface info"; leafrealm-nameif-name { type string; mandatory true; description"realm"interface name"; }} } container addr-selection-option { description "address selection option";leafenableinterface-id { typeboolean;string; mandatory true; description"indicate whether this option will be included in the option set";"interface id"; } } list subscribers { key subscriber; description "subscribers"; leafa-bit-setsubscriber { typeboolean;uint32; mandatory true; description"a bit";"subscriber"; } leafp-bit-setsubscriber-id { typeboolean;string; mandatory true; description"p bit";"subscriber id"; } } listpolicy-tableremote-host { keypolicy-id;ent-num; description"policy table";"remote host"; leafpolicy-ident-num { typeuint8;uint32; mandatory true; description"policy id";"enterprise number"; } leaflabelremote-id { typeuint8;string; mandatory true; description"label";"remote id"; }leaf precedence} } } container rsoo-enabled-options {type uint8; mandatory true;description"precedence"; }"rsoo enabled options"; list rsoo-enabled-option{ key option-code; description "rsoo enabled option"; leafprefix-lenoption-code { typeuint8;uint16; mandatory true; description"prefix length";"option code"; } leafprefixdescription { typeinet:ipv6-prefix;string; mandatory true; description"prefix";"description of the option"; } } } } /* * State data */ containersol-max-rt-option {server-state{ config "false"; description"OPTION_SOL_MAX_RT (82) sol max rt option"; reference "RFC7083: Modification"states of server"; container network-ranges{ description "This model supports a hierarchy toDefault Valuesachieve 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."; list network-range{ key network-range-id; description "The ID field ofSOL_MAX_RT and INF_MAX_RT";relevant option-set to be provisioned to clients of this network-range."; leafenablenetwork-range-id { typeboolean;uint32; mandatory true; description"indicate whether this option will be included in the option set";"equivalent to subnet id"; } container address-pools{ description "A container that describes the DHCPv6 server's address pools"; list address-pool{ key pool-id; leafsol-max-rt-valuepool-id { typeyang:timeticks;uint32; mandatory true; description"sol max rt value"; }"pool id"; }container inf-max-rt-option {description"OPTION_INF_MAX_RT (83) inf max rt option"; reference "RFC7083: Modification to Default Values of SOL_MAX_RT and INF_MAX_RT";"..."; leafenabletotal-ipv6-count { typeboolean;uint64; mandatory true; description"indicate whether this option will be included"how many ipv6 addresses are in theoption set";pool"; } leafinf-max-rt-valueused-ipv6-count { typeyang:timeticks;uint64; mandatory true; description"inf max rt value";"how many are allocated"; } leaf address-utilization-ratio { type uint16; mandatory true; description "current address pool utilization ratio"; } }container pcp-server-optionlist binding-info { key cli-id; description"OPTION_V6_PCP_SERVER (86) pcp server option"; reference "RFC7291: DHCP Options"A list that records a binding information forthe Port Control Protocol (PCP)";each DHCPv6 client that has already been allocated IPv6 addresses."; leafenablecli-id { typeboolean;uint32; mandatory true; description"indicate whether this option will be included in"client id"; } container duid { description "Read theoption set";DUID"; uses duid; } listpcp-server {cli-ia{ keypcp-serv-id;iaid; description"pcp server info";"client IA"; leafpcp-serv-idia-type { typeuint8;string; mandatory true; description"pcp server id";"IA type"; } leafpcp-serv-addriaid { typeinet:ipv6-address;uint32; mandatory true; description"pcp server"IAID"; } leaf-list cli-addr { type inet:ipv6-address; description "client addr"; } leaf pool-id { type uint32; mandatory true; description "pool id"; } } } } containers46-rule-optionprefix-pools{ description "If a server supports prefix delegation function, this container will be used to define the delegating router's prefix pools."; list prefix-pool { key pool-id; description"s46 rule option"; reference "RFC7598: DHCPv6 Options for Configuration of Softwire Address and Port-Mapped Clients";"Similar to server's address pools, a delegating router can also be configured with multiple prefix pools specified by a list called 'prefix-pool'."; leafenablepool-id { typeboolean;uint32; mandatory true; description "pool id"; } leaf prefix-utilization-ratio { type uint16; mandatory true; description"indicate whether this option will be included in the option set";"current prefix pool utilization ratio"; } } lists46-rulebinding-info { keyrule-id;cli-id; description"s46 rule";"A list records a binding information for each DHCPv6 client that has already been alloated IPv6 addresses."; leafrule-idcli-id { typeuint8;uint32; mandatory true; description"rule"client id"; }leaf rule-type { type enumeration { enum "BMR"container duid { description"BMR";"Reads the DUID"; uses duid; }enum "FMR"list cli-iapd { key iaid; description"FMR"; } } mandatory true; description "rule type"; }"client IAPD"; leafprefix4-leniaid { typeuint8;uint32; mandatory true; description"ipv4 prefix length";"IAID"; }leaf ipv4-prefixleaf-list cli-prefix { typeinet:ipv4-prefix; mandatory true;inet:ipv6-prefix; description"ipv4"client ipv6 prefix"; }leaf prefix6-lenleaf-list cli-prefix-len { type uint8;mandatory true;description"ipv6"client prefix length"; } leafipv6-prefixpool-id { typeinet:ipv6-prefix;uint32; mandatory true; description"ipv6 prefix";"pool id"; }uses portset-para;} }container s46-br-option} list address-prefix-assign-param { // Zihao - This probably needs further updated. // But is it a way to represent the address/prefix assignment // logic? key cli-id; description"s46 br option"; reference "RFC7598:"This list includes some parameters/identifiers that the server obtains from DHCPv6Options for Configuration of Softwire Address and Port-Mapped Clients"; leaf enable { type boolean; mandatory true; description "indicate whetheroptions in thisoption willnetwork-range. These identifiers may beincluded inhelpful for theoption set"; } list br { key br-id; description "br info";server to assign addresses/prefixes."; reference "Section 3.12 of RFC7824"; leafbr-idcli-id { typeuint8;uint32; mandatory true; description"br"client id"; } leafbr-ipv6-addrsource-ipv6-addr { type inet:ipv6-address;mandatory true; description "br ipv6 addr"; } } } container operator-option-ipv6-address { description "operator ipv6 address option"; reference "RFC7227: Guidelines for Creating New DHCPv6 Options"; leaf enable { type boolean; mandatory true;description"indicate whether this option will be included in"The adrress of theoption set";link to which the client is attached."; }list operator-ipv6-addrcontainer duid {key operator-ipv6-addr-id;description"operator ipv6 address info"; leaf operator-ipv6-addr-id"The DUID supplied by the client."; uses duid; } leaf-list iaid { typeuint8; mandatory true;uint32; description"operator ipv6 address id";"IAID"; }leaf operator-ipv6-addrleaf-list preferred-addr { type inet:ipv6-address;mandatory true;description"operator ipv6"The IPv6 addressid"; } }preferred by the client."; }container operator-option-single-flagleaf-list preferred-prefix-len { type uint8; description"operator single flag"; reference "RFC7227: Guidelines for Creating New DHCPv6 Options";"The prefix length preferred by the client."; } leafenableclient-fqdn { typeboolean; mandatory true;string; description"indicate whether this option will be included in"Fully Qualified Domain Name supplied by theoption set";client."; }list flagleaf client-link-layer-addr {key flag-id;type uint16; description"operator single flag info";"Link-layer address supplied by the client."; } leafflag-idclient-enterprise-number { typeuint8; mandatory true;uint32; description"operator single flag id";"Enterprise number supplied by the client."; }leaf flag-value{leaf-list client-sys-archi-type { typeboolean; mandatory true;uint16; description"operator single flag value";"Supported system architecture type supplied by the client"; } } } } containeroperator-option-ipv6-prefixpacket-stats { description"operator ipv6 prefix option"; reference "RFC7227: Guidelines for Creating New"A container presents the packet statistics related to the DHCPv6Options";server."; leafenablesolicit-count { typeboolean;uint32; mandatory true; description"indicate whether this option will be included in the option set";"solicit counter"; }list operator-ipv6-prefix{ key operator-ipv6-prefix-id; description "operator ipv6 prefix info";leafoperator-ipv6-prefix-idrequest-count { typeuint8; mandatory true; description "operator ipv6 prefix id"; } leaf operator-ipv6-prefix6-len{ type uint8;uint32; mandatory true; description"operator ipv6 prefix length";"request counter"; } leafoperator-ipv6-prefixrenew-count { typeinet:ipv6-prefix;uint32; mandatory true; description"operator ipv6 prefix"; } }"renew counter"; }container operator-option-int32 { description "operator integer 32 option"; reference "RFC7227: Guidelines for Creating New DHCPv6 Options";leafenablerebind-count { typeboolean;uint32; mandatory true; description"indicate whether this option will be included in the option set"; } list int32val{ key int32val-id; description "operator integer 32 info";"rebind counter"; } leafint32val-iddecline-count { typeuint8;uint32; mandatory true; description"operator integer 32 id";"decline count"; } leafint32val{release-count { type uint32; mandatory true; description"operator integer 32 value"; } }"release counter"; }container operator-option-int16 { description "operator integer 16 option"; reference "RFC7227: Guidelines for Creating New DHCPv6 Options";leafenableinfo-req-count { typeboolean;uint32; mandatory true; description"indicate whether this option will be included in the option set";"information request counter"; }list int16val{ key int16val-id; description "operator integer 16 info";leafint16val-idadvertise-count { typeuint8;uint32; mandatory true; description"operator integer 16 id";"advertise counter"; } leafint16val{confirm-count { typeuint16;uint32; mandatory true; description"operator integer 16 value"; } }"confirm counter"; }container operator-option-int8leaf reply-count { type uint32; mandatory true; description"operator integer 8 option"; reference "RFC7227: Guidelines for Creating New DHCPv6 Options";"reply counter"; } leafenablereconfigure-count { typeboolean;uint32; mandatory true; description"indicate whether this option will be included in the option set";"reconfigure counter"; }list int8val{ key int8val-id; description "operator integer 8 info";leafint8val-idrelay-forward-count { typeuint8;uint32; mandatory true; description"operator integer 8 id";"relay forward counter"; } leafint8val{relay-reply-count { typeuint8;uint32; mandatory true; description"operator integer 8 value";"relay reply counter"; } } } } /* * Notifications */ notification notifications { description "dhcpv6 server notification module"; containeroperator-option-uridhcpv6-server-event { description"operator uri option"; reference "RFC7227: Guidelines for Creating New DHCPv6 Options"; leaf enable"dhcpv6 server event"; container pool-running-out {type boolean; mandatory true;description"indicate whether this option will be included"raised when the address/prefix pool is going to run out. A threshold for utilization ratio of the pool has been defined in theoption set"; } list uri{ key uri-id; description "operator uri info";server feature so that it will notify the administrator when the utilization ratio reaches the threshold, and such threshold is a settable parameter"; leafuri-idmax-address-utilization-ratio { typeuint8;uint16; mandatory true; description"operator uri id";"address pool utilization ratio threshold"; } leafuri{address-utilization-ratio { typestring;uint16; mandatory true; description"operator uri value"; } }"current address pool utilization ratio"; }container operator-option-textstringleaf max-prefix-utilization-ratio { type uint16; mandatory true; description"operator itext string option"; reference "RFC7227: Guidelines for Creating New DHCPv6 Options";"prefix pool utilization ratio threshold"; } leafenableprefix-utilization-ratio { typeboolean;uint16; mandatory true; description"indicate whether this option will be included in the option set";"current prefix pool utilization ratio"; }list textstring{ key textstring-id;container duid { description"operator text string info";"Sets the DUID"; uses duid; } leaftextstring-idserv-name { typeuint8; mandatory true;string; description"operator text string id";"server name"; } leaftextstring{pool-name { type string; mandatory true; description"operator text string value"; }"pool name"; } } containeroperator-option-var-datainvalid-client-detected { description"operator variable length data option"; reference "RFC7227: Guidelines for Creating New DHCPv6 Options"; leaf enable { type boolean; mandatory true;"raised when the server has found a client which can be regarded as a potential attacker. Some description"indicate whether this option willcould also beincluded inincluded."; container duid { description "Sets theoption set";DUID"; uses duid; }list int32val{ key var-data-id; description "operator ivariable length data info";leafvar-data-iddescription { typeuint8; mandatory true;string; description"operator variable length id";"description of the event"; }leaf var-data{ type binary; mandatory true; description "operator variable length value";} } }container operator-option-dns-wire} <CODE ENDS> 3.2. DHCPv6 Relay YANG Model This module imports typedefs from [RFC6991]. <CODE BEGINS> file "ietf-dhcpv6-relay@2017-12-22.yang" module ietf-dhcpv6-relay { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-dhcpv6-relay"; prefix "dhcpv6-client"; import ietf-inet-types { prefix inet; revision-date "2013-07-15"; } import ietf-dhcpv6-options { prefix dhcpv6-options; revision-date "2017-12-22"; } organization "DHC WG"; contact "yong@csnet1.cs.tsinghua.edu.cn lh.sunlinh@gmail.com ian.farrer@telekom.de sladjana.zechlin@telekom.de hezihao9512@gmail.com"; description "This model defines a YANG data model that can be used to configure and manage a DHCPv6 relay."; revision 2017-12-22 { description"operator dns wire format domain name list option";"Resolve most issues on Ian's github."; reference"RFC7227: Guidelines for Creating New DHCPv6 Options"; leaf enable"I-D: draft-ietf-dhc-dhcpv6-yang"; } revision 2017-11-24 {type boolean; mandatory true;description"indicate whether this option will be included in"First version of theoption set";separated relay specific YANG model."; reference "I-D: draft-ietf-dhc-dhcpv6-yang"; }list operator-option-dns-wire{ key operator-option-dns-wire-id;/* * Grouping */ grouping vendor-infor { description"operator dns wire format info";"Vendor information."; container vendor-info { description ""; leafoperator-option-dns-wire-ident-num { typeuint8;uint32; mandatory true; description"operator dns wire format id";"enterprise number"; }leaf operator-option-dns-wire{leaf-list data { typebinary; mandatory true;string; description"operator dns wire format value";"specific vendor info"; } } } /* * Data Nodes */ containers46-dmr-optionrelay { presence "Enables the relay"; description"s46 dmr option"; reference "RFC7598: DHCPv6 Options for Configuration"dhcpv6 relay portion"; container relay-config{ description "configuration tree ofSoftwire Address and Port-Mapped Clients"; leaf enablerelay"; container relay-attributes {type boolean; mandatory true;description"indicate whether this option will be included in"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 optionset"; } list dmr { key dmr-id; description "dmr info";and Subscriber-Id option."; leafdmr-idname { typeuint8; mandatory true;string; description"dmr id";"relay agent name"; } leafdmr-prefix-len { type uint8; mandatory true;description"dmr prefix length"; } leaf dmr-ipv6-prefix{ typeinet:ipv6-prefix; mandatory true; description "dmr ipv6 prefix"; } } } container s46-v4-v6-binding-option {string; description"s46 binding option"; reference "RFC7598: DHCPv6 Options for Configuration"description ofSoftwire Address and Port-Mapped Clients"; leaf enablethe relay agent"; } leaf-list dest-addrs { typeboolean; mandatory true;inet:ipv6-address; description"indicate whether this option will"Each DHCPv6 relay agent may beincluded in the option set";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."; } listcesubscribers { keyce-id;subscriber; description"ce info";"subscribers"; leafce-idsubscriber { type uint8; mandatory true; description"ce id";"subscriber"; } leafipv4-addrsubscriber-id { typeinet:ipv4-address;string; mandatory true; description"ce ipv4 addr";"subscriber id"; } } list remote-host { key ent-num; description "remote host"; leafbind-prefix6-lenent-num { typeuint8;uint32; mandatory true; description"bind ipv6 prefix length";"enterprise number"; } leafbind-ipv6-prefixremote-id { typeinet:ipv6-prefix;string; mandatory true; description"bind ipv6 prefix"; } uses portset-para;"remote id"; } } uses vendor-infor; }//NB - The list ofcontainer rsoo-option-sets { description "DHCPv6 relay agent could provide some information that would be useful to DHCPv6 client. Since relay agent cannot provide optionsneedsdirectly tobe updated with newer options. }the client, RSOO-enabled options are defined to propose options for the server to send to the client. This containernetwork-rangesmodels such RSOO-enabled options."; reference "RFC6422"; list option-set { key id; description "Thismodel supports a hierarchy to achieve dynamic configuration. Thatlist under the 'rsoo-option-sets' container is similar tosay we could configurethe that defined in serveratmodule. It allows the relay to implement several sets of RSOO-enabled options for differentlevels through this model.interfaces. Thetop level is a global level which is defined aslist only include thecontainer 'network-ranges'. The following levels areEAP Re-authentication Protocol (ERP) Local Domain Name DHCPv6 Option definedas sub-containers under it. The 'network-ranges' contains the parameters (e.g. option-sets) that would be allocated to allin RFC6440, since it is theclients servedonly one RSOO-enabled options accepted bythis server.";IANA so far."; leafoption-set-idid { typeuint8;uint32; description"a specific option set";"option sed id"; } uses dhcpv6-options:relay-supplied-option-definitions; } } listnetwork-rangerelay-if { // if - This should reference an entry in ietf-interfaces keynetwork-range-id;if-name; description"Under the 'network-ranges' container,"A relay agent may have several interfaces, we should provide a'network-range'way to configure and manage parameters on the interface-level. A list that describes specific interfaces and their corresponding parameters isdefinedemployed toconfigurefulfil theserver atconfigfuration. Here we use anetwork level which is also consideredstring called 'if-name; as thesecond level. Different network are identified by thekey'network-range-id'. This is because a server may have different configuration parameters (e.g. option sets) for different networks.";of list."; leafnetwork-range-idif-name { typeuint8;string; mandatory true; description"equivalent to subnet id";"interface name"; } leafnetwork-descriptionenable { typestring;boolean; mandatory true; description"description of the subnet";"whether this interface is enabled"; } leafnetwork-prefixipv6-address { typeinet:ipv6-prefix; mandatory true;inet:ipv6-address; description"subnet prefix";"ipv6 address for this interface"; } leafinherit-option-setinterface-id { typeboolean; mandatory true;string; description"indicate whether to inherit the configuration from higher level";"interface id"; } leafoption-set-idrsoo-option-set-id { typeuint8; mandatory true; description "the selected option-set"; } container reserved-addressesleafref { path "/relay/relay-config/rsoo-option-sets/option-set/id"; } description"reserved addresses";"Configured Relay Supplied Option set"; } liststatic-bindingnext-entity { keycli-id;dest-addr; description"static binding"This node defines a list that is used to describe the next hop entity ofreserved addresses";this relay distinguished by their addresses."; leafcli-iddest-addr { typeuint32;inet:ipv6-address; mandatory true; description"client id"; } container duid { description "Sets the DUID"; uses duid; } leaf-list reserv-addr { type inet:ipv6-address; description "reserved"destination addr"; }} leaf-list other-reserv-addrleaf available { typeinet:ipv6-address;boolean; mandatory true; description"other reserved addr"; }"whether the next entity is available or not"; }container reserved-prefixes { description "reserved prefixes"; list static-binding { key cli-id; description "static binding";leafcli-idmulticast { typeuint32;boolean; mandatory true; description"client id"; } container duid { description "Sets"whether theDUID"; uses duid;address is multicast or not"; } leafreserv-prefix-lenserver { typeuint8;boolean; mandatory true; description"reserved prefix length";"whether the next entity is a server"; } } } } container relay-state{ config "false"; description "state tree of relay"; list relay-if{ key if-name; description "..."; leafreserv-prefix {if-name{ typeinet:ipv6-prefix;string; mandatory true; description"reserved prefix"; }"interface name"; } list pd-route { // if - need to look at if/how we model these. If they are // going to be modelled, then they should be ro state // entries (we're not trying to configure routes here) key pd-route-id; description "pd route"; leafexclude-prefix-lenpd-route-id { type uint8; mandatory true; description"exclude prefix length";"pd route id"; } leafexclude-prefixrequesting-router-id { typeinet:ipv6-prefix;uint32; mandatory true; description"exclude prefix";"requesting router id"; }list other-reserv-prefix { key reserv-id; description "other reserved prefix";leafreserv-iddelegating-router-id { typeuint8;uint32; mandatory true; description"reserved prefix"delegating router id"; } leafprefix-lennext-router { typeuint8;inet:ipv6-address; mandatory true; description"prefix length";"next router"; } leafprefixlast-router { typeinet:ipv6-prefix;inet:ipv6-address; mandatory true; description"reserved prefix"; }"previous router"; } }container address-pools { description "A container describes the DHCPv6 server's address pools.";listaddress-pool {next-entity{ keypool-id;dest-addr; description"A DHCPv6 server can be configured with several address pools. This list"This node definessuch address pools whicha list that is used to describe the next hop entity of this relay agent. Different entities aredistinguishdistinguished bythe key called 'pool-name'.";their addresses."; leafpool-id {dest-addr{ typeuint8;inet:ipv6-address; mandatory true; description"pool id";"destination addr"; }leaf pool-prefixcontainer packet-stats {type inet:ipv6-prefix; mandatory true;description"pool prefix"; }"packet statistics"; leafstart-addresssolicit-rvd-count { typeinet:ipv6-address-no-zone;uint32; mandatory true; description"start address";"solicit received counter"; } leafend-addressrequest-rvd-count { typeinet:ipv6-address-no-zone;uint32; mandatory true; description"end address";"request received counter"; } leafrenew-timerenew-rvd-count { typeyang:timeticks;uint32; mandatory true; description "renewtime";received counter"; } leafrebind-timerebind-rvd-count { typeyang:timeticks;uint32; mandatory true; description "rebindtime";recevied counter"; } leafpreferred-lifetimedecline-rvd-count { typeyang:timeticks;uint32; mandatory true; description"preferred lifetime for IA";"decline received counter"; } leafvalid-lifetimerelease-rvd-count { typeyang:timeticks;uint32; mandatory true; description"valid liftime for IA";"release received counter"; } leaftotal-ipv6-countinfo-req-rvd-count { typeuint64; config "false";uint32; mandatory true; description"how many ipv6 addressses are in the pool";"information request counter"; } leafused-ipv6-countrelay-for-rvd-count { typeuint64; config "false";uint32; mandatory true; description"how many are allocated";"relay forward received counter"; } leafutilization-ratiorelay-rep-rvd-count { typethreshold;uint32; mandatory true; description"the utilization ratio";"relay reply received counter"; } leafinherit-option-setpacket-to-cli-count { typeboolean;uint32; mandatory true; description"indicate whether"packet toinherit the configuration from higher level";client counter"; } leafoption-set-idadver-sent-count { typeuint8;uint32; mandatory true; description"the selected option-set"; }"advertisement sent counter"; }list binding-info { key cli-id; config "false"; description "A list records a binding information for each DHCPv6 client that has already been allocated IPv6 addresses.";leafcli-idconfirm-sent-count { type uint32; mandatory true; description"client id"; } container duid { description "Sets the DUID"; uses duid;"confirm sent counter"; }list cli-ia { key iaid; description "client IA";leafia-typereply-sent-count { typestring;uint32; mandatory true; description"IA type";"reply sent counter"; } leafiaidreconfig-sent-count { type uint32; mandatory true; description"IAID";"reconfigure sent counter"; }leaf-list cli-addrleaf relay-for-sent-count { typeinet:ipv6-address;uint32; mandatory true; description"client addr";"relay forward sent counter"; } leafpool-idrelay-rep-sent-count { typeuint8;uint32; mandatory true; description"pool id";"relay reply sent counter"; } } } } containerprefix-pools { description "If a server supports prefix delegation function, this container will be used to define the delegating router's refix pools."; list prefix-poolrelay-stats {key pool-id;config "false"; 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'.";"relay statistics"; leafpool-idcli-packet-rvd-count { typeuint8;uint32; mandatory true; description"pool id";"client packet received counter"; } leafprefixrelay-for-rvd-count { typeinet:ipv6-prefix;uint32; mandatory true; description"ipv6 prefix";"relay forward received counter"; } leafprefix-lengthrelay-rep-rvd-count { typeuint8;uint32; mandatory true; description"prefix length";"relay reply recevied counter"; } leafrenew-timepacket-to-cli-count { typeyang:timeticks;uint32; mandatory true; description"renew time";"packet to client counter"; } leafrebind-timerelay-for-sent-count { typeyang:timeticks;uint32; mandatory true; description"rebind time";"relay forward sent counter"; } leafpreferred-lifetimerelay-rep-sent-count { typeyang:timeticks;uint32; mandatory true; description"preferred lifetime for IA";"relay reply sent counter"; } leafvalid-lifetimediscarded-packet-count { typeyang:timeticks;uint32; mandatory true; description"valid lifetime for IA";"discarded packet counter"; } } } } /* * Notifications */ notification notifications { description "dhcpv6 relay notification module"; container dhcpv6-relay-event { description "dhcpv6 relay event"; container topo-changed { description "raised when the topology of the relay agent is changed."; leafutilization-ratiorelay-if-name { typethreshold;string; mandatory true; description"utilization ratio";"relay interface name"; } leafinherit-option-setfirst-hop { type boolean; mandatory true; description"whether to inherit configuration from higher level";"first hop"; } leafoption-set-idlast-entity-addr { typeuint8;inet:ipv6-address; mandatory true; description"the selected option-set";"last entity address"; } }list binding-info { key cli-id; config "false"; description "A list records a binding information for each} } } <CODE ENDS> 3.3. DHCPv6client that has already been allocated IPv6 addresses."; leaf cli-idClient YANG Model This module imports typedefs from [RFC6991]. <CODE BEGINS> file "ietf-dhcpv6-client@2017-12-22.yang" module ietf-dhcpv6-client {type uint32; mandatory true; description "client id";yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-dhcpv6-client"; prefix "dhcpv6-client"; import ietf-inet-types { prefix inet; revision-date "2013-07-15"; }container duidimport ietf-yang-types {description "Sets the DUID"; uses duid;prefix yang; revision-date "2013-07-15"; }list cli-iapdimport ietf-dhcpv6-options {key iaid;prefix dhcpv6-options; revision-date "2017-12-22"; } organization "DHC WG"; contact "yong@csnet1.cs.tsinghua.edu.cn wangh13@mails.tsinghua.edu.cn lh.sunlinh@gmail.com ian.farrer@telekom.de sladjana.zechlin@telekom.de hezihao9512@gmail.com "; description"client IAPD"; leaf iaid"This model defines a YANG data model that can be used to configure and manage a DHCPv6 client."; revision 2017-12-22 {type uint32; mandatory true;description"IAID";"Resolve most issues on Ian's github."; reference "I-D: draft-ietf-dhc-dhcpv6-yang"; }leaf-list cli-prefixrevision 2017-11-24 {type inet:ipv6-prefix;description"client ipv6 prefix";"First version of the separated client specific YANG model."; reference "I-D: draft-ietf-dhc-dhcpv6-yang"; }leaf-list cli-prefix-len/* * Grouping */ grouping vendor-infor {type uint8;description"client prefix length"; }"Vendor information."; container vendor-info { description ""; leafpool-ident-num { typeuint8;uint32; mandatory true; description"pool id";"enterprise number"; } leaf-list data { type string; description "specific vendor info"; } } }container hosts { description "hosts level"; list hostgrouping duid {key cli-id;description"specific host";"DHCP Unique Identifier"; reference "RFC3315: Section 9"; leafcli-idtype-code { typeuint32; mandatory true;uint16; default 65535; description"client id";"Type code of this DUID"; }container duidchoice duid-type { default duid-invalid; description"Sets"Selects theDUID"; uses duid;format for the DUID."; case duid-llt { description "DUID Based on Link-layer Address Plus Time (Type 1 - DUID-LLT)"; reference "RFC3315 Section 9.2"; leaf duid-llt-hardware-type { type uint16; description "Hardware type as assigned by IANA (RFC826)."; } leafinherit-option-setduid-llt-time { typeboolean; mandatory true;yang:timeticks; description"whether to inherit configuration from higher level";"The time value is the time that the DUID is generated represented in seconds since midnight (UTC), January 1, 2000, modulo 2^32."; } leafoption-set-idduid-llt-link-layer-addr { typeuint8; mandatory true;yang:mac-address; description"the selected option-set";"Link-layer address as described in RFC2464"; } } case duid-en { description "DUID Assigned by Vendor Based on Enterprise Number (Type 2 - DUID-EN)"; reference "RFC3315 Section 9.3"; leafnis-domain-nameduid-en-enterprise-number { typestring;uint32; description"nis domain name";"Vendor's registered Private Enterprise Number as maintained by IANA"; } leafnis-plus-domain-nameduid-en-identifier { type string; description"nisp domain name"; } } }"Indentifier, unique to the device that is using it"; } }container relay-opaque-parascase duid-ll { description"This container contains some opaque values in Relay Agent options that need to be configured"DUID Based onthe server side only for value match. Such Relay Agent options include Interface-Id option, Remote-Id option and Subscriber-Id option."; list relaysLink-layer Address (Type 3 - DUID-LL)"; reference "RFC3315 Section 9.4"; leaf duid-ll-hardware-type {key relay-name;type uint16; description"relay agents";"Hardware type as assigned by IANA (RFC826)."; } leafrelay-nameduid-ll-link-layer-addr { typestring; mandatory true;yang:mac-address; description"relay agent name";"Link-layer address as described in RFC2464"; }list interface-info} case duid-uuid {key if-name;description"interface info";"DUID Based on Universally Unique Identifier (Type 4 - DUID-UUID)"; reference "RFC6335 Defination of the UUID-Based Unique Identifier"; leafif-nameuuid { typestring; mandatory true;yang:uuid; description"interface name";"A Universally Unique IDentifier in the string representation defined in RFC 4122. The canonical representation uses lowercase characters"; } } case duid-invalid { description "DUID based on free raw bytes"; leafinterface-iddata { typestring; mandatory true;binary; description"interface id";"The bits to be used as the identifier"; } }list subscribers} } grouping portset-para {key subscriber;description"subscribers"; leaf subscriber"portset parameters"; container port-parameter {type uint8; mandatory true;description"subscriber"; }"port parameter"; leafsubscriber-idoffset { typestring;uint8; mandatory true; description"subscriber id"; }"offset in a port set"; }list remote-host { key ent-num; description "remote host";leafent-numpsid-len { typeuint32;uint8; mandatory true; description"enterprise number";"length of a psid"; } leafremote-idpsid { typestring;uint16; mandatory true; description"remote id"; }"psid value"; } } }container rsoo-enabled-optionsgrouping iaid { description"rsoo enabled options";"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 listrsoo-enabled-option{is a 4-byte number IAID defined in [RFC3315]."; list identity-association { config "false"; keyoption-code;iaid; description"rsoo enabled option";"IA"; leafoption-codeiaid { typeuint16;uint32; mandatory true; description"option code";"IAID"; } leafdescriptionia-type { type string; mandatory true; description"description of the option";"IA type"; } leaf-list ipv6-addr { type inet:ipv6-address; description "ipv6 address"; } leaf-list ipv6-prefix { type inet:ipv6-prefix; description "ipv6 prefix"; }container packet-statsleaf-list prefix-length {config "false";type uint8; description"A container presents the packet statistics related to the DHCPv6 server.";"ipv6 prefix length"; } leafsolicit-countt1-time { typeuint32;yang:timeticks; mandatory true; description"solicit counter";"t1 time"; } leafrequest-countt2-time { typeuint32;yang:timeticks; mandatory true; description"request counter";"t2 time"; } leafrenew-countpreferred-lifetime { typeuint32;yang:timeticks; mandatory true; description"renew counter";"preferred lifetime"; } leafrebind-countvalid-lifetime { typeuint32;yang:timeticks; mandatory true; description"rebind counter";"valid lifetime"; } } } /* * Data Nodes */ container client { presence "Enables the client"; description "dhcpv6 client portion"; container client-config{ description "configuration tree of client"; container duid { description "Sets the DUID"; uses duid; } list client-if { key if-name; description "A client may have several interfaces, it is more reasonable to configure and manage parameters on the interface-level. The list defines specific client interfaces and their data. Different interfaces are distinguished by the key which is a configurable string value."; leafdecline-countif-name { typeuint32;string; mandatory true; description"decline count";"interface name"; } leafrelease-countcli-id { type uint32; mandatory true; description"release counter";"client id"; } leafinfo-req-countdescription { typeuint32; mandatory true;string; description"information request counter";"description of the client interface"; } leafadvertise-countpd-function { typeuint32;boolean; mandatory true; description"advertise counter";"Whether the client can act as a requesting router to request prefixes using prefix delegation ([RFC3633])."; } leafconfirm-countrapid-commit { typeuint32;boolean; mandatory true; description"confirm counter";"'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."; } 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."; // if - not sure about the intended use here as it seems // to be redfining what will be received in the PIO. Is // the intention to be whether they PIO options will be // obeyed as received or overridden? leafreply-countm-tab { typeuint32;boolean; mandatory true; description"reply counter";"m tab"; } leafreconfigure-counto-tab { typeuint32;boolean; mandatory true; description"reconfigure counter";"o tab"; }leaf relay-forward-count { type uint32; mandatory true; description "relay forward counter";}leaf relay-reply-countcontainer client-configured-options {type uint32; mandatory true;description"relay reply counter";"client configured options"; uses dhcpv6-options:client-option-definitions; } } } containerrelay { presence "Enables relay";client-state{ config "false"; description"dhcpv6 relay portion";"state tree of client"; containerrelay-attributesif-other-paras { description "A client can obtain extra configuration data other than address and prefix information through DHCPv6. This container describessome basic attributes ofsuch data therelay agent including some relay agent specific optionsclient was configured. The potential configuration datathat need to be configured previously. Such optionsmay includeRemote-Id option and Subscriber-Id option."; leaf nameDNS server addresses, SIP server domain names, etc."; uses dhcpv6-options:server-option-definitions; } } } /* * Notifications */ notification notifications {type string;description"relay agent name"; } leaf"dhcpv6 client notification module"; container dhcpv6-client-event { description "dhcpv6 client event"; container ia-lease-event {type string;description"description of"raised when therelay agent"; } leaf-list dest-addrsclient was allocated a new IA from the server or it renew/rebind/release its current IA"; leaf event-type { typeinet:ipv6-address;enumeration{ enum "allocation" { 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.";"allocate"; }list subscribersenum "rebind" {key subscriber;description"subscribers"; leaf subscriber"rebind"; } enum "renew" {type uint8; mandatory true;description"subscriber";"renew"; }leaf subscriber-idenum "release" {type string;description "release"; } } mandatory true; description"subscriber id"; }"event type"; }list remote-hostcontainer duid {key ent-num;description"remote host";"Sets the DUID"; uses duid; } leafent-numiaid { type uint32; mandatory true; description"enterprise number";"IAID"; } leafremote-idserv-name { type string;mandatory true;description"remote id";"server name"; } leaf description { type string; description "description of event"; }uses vendor-infor;} containerrelay-supplied-options-optioninvalid-ia-detected { description"relay supplied options option"; list rsoo-set"raised when the identity association of the client can be proved to be invalid. Possible condition includes duplicated address, illegal address, etc."; container duid {key rsoo-set-id;description"rsoo set";"Sets the DUID"; uses duid; } leafrsoo-set-idcli-duid { typeuint8;uint32; mandatory true; description"rsoo set id";"duid of client"; }container erp-local-domain-name-option { description "erp local domain name option";leafenableiaid { typeboolean;uint32; mandatory true; description"indicate whether this option is included in the rsoo set";"IAID"; }list erp-for-clientleaf serv-name {key cli-id;type string; description"erp for client";"server name"; } leafcli-iddescription { typeuint32; mandatory true;string; description"client id";"description of the event"; } } container retransmission-failed { description "raised when the retransmission mechanism defined in [RFC3315] is failed."; container duid { description "Sets the DUID"; uses duid; } leaferp-namedescription { typestring; mandatory true;enumeration { enum "MRC failed" { description"erp name"; } } } }"MRC failed"; }list relay-ifenum "MRD failed" {key if-name;description"A relay agent may have several interfaces, we should provide a way to configure and manage parameters on the interface-level. A list that describes specific interfaces and their corresponding parameters is employed to fulfil the configfuration. Here we use a string called 'if-name; as the key of list."; leaf if-name { type string;"MRD failed"; } } mandatory true; description"interface name";"description of failure"; }leaf enable} container failed-status-turn-up {type boolean; mandatory true;description"whether this interface is enabled"; } leaf ipv6-address"raised when the client receives a message includes an unsuccessful Status Code option."; container duid {type inet:ipv6-address;description"ipv6 address for this interface";"Sets the DUID"; uses duid; } leafinterface-idstatus-code { typestring; description "interface id"; } leaf-list rsoo-setenumeration {type uint8; description "configured rsoo set"; } list pd-routeenum "1" {key pd-route-id;description"pd route"; leaf pd-route-id"UnspecFail"; } enum "2" {type uint8; mandatory true;description"pd route id";"NoAddrAvail"; }leaf requesting-router-idenum "3" {type uint32; mandatory true;description"requesting router id";"NoBinding"; }leaf delegating-router-idenum "4" {type uint32; mandatory true;description"delegating router id";"NotOnLink"; }leaf next-routerenum "5" {type inet:ipv6-address; mandatory true;description"next router";"UseMulticast"; } }leaf last-router { type inet:ipv6-address;mandatory true; description"previous router";"employed status code"; } }list next-entity} } } <CODE ENDS> 3.4. DHCPv6 Options YANG Model This module imports typedefs from [RFC6991]. <CODE BEGINS> file "ietf-dhcpv6-options@2017-12-22.yang" module ietf-dhcpv6-options {key dest-addr;yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-dhcpv6-options"; prefix "dhcpv6-options"; 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 ian.farrer@telekom.de sladjana.zechlin@telekom.de hezihao9512@gmail.com"; description "Thisnodemodel defines alistYANG data model thatiscan be used todescribe the next hop entityconfigure and manage a DHCPv6 server."; revision 2017-12-22 { description "Resolve most issues on Ian's github."; reference "I-D: draft-ietf-dhc-dhcpv6-yang"; } revision 2017-11-24 { description "First version ofthis relay distinguished by their addresses."; leaf dest-addrthe separated DHCPv6 options YANG model."; reference "I-D:draft-ietf-dhc-dhcpv6-yang"; } /* * Features */ // features for server options feature server-unicast-op { description "Support for Server Unicast option"; } feature sip-server-domain-name-list-op { description "Support for SIP Server Domain Name List option"; } feature sip-server-address-list-op { description "Support for SIP Server Address List option"; } feature dns-config-op {type inet:ipv6-address; mandatory true;description"destination addr";"Support for DNS Recursive Name Server option"; }leaf availablefeature domain-searchlist-op {type boolean; mandatory true;description"whether the next entity is available or not";"Support for Domain Search List Option"; }leaf multicastfeature nis-config-op {type boolean; mandatory true;description"whether the address is multicast or not";"Support for Network Information Service (NIS) Servers option"; }leaf serverfeature nis-plus-config-op {type boolean; mandatory true;description"whether the next entity is a server";"Support for Network Information Service V2 (NIS+) Servers option"; }container packet-statsfeature nis-domain-name-op {config "false";description"packet statistics"; leaf cli-packet-rvd-count"Support for Network Information Service (NIS) Domain Name option"; } feature nis-plus-domain-name-op {type uint32; mandatory true;description"client received packet counter";"Support for Network Information Service V2 (NIS+) Server option"; }leaf solicit-rvd-countfeature sntp-server-op {type uint32; mandatory true;description"solicit received counter";"Support for Simple Network Protocol Configuration (SNTP) Servers option"; }leaf request-rvd-countfeature info-refresh-time-op {type uint32; mandatory true;description"request received counter";"Support for Information Refresh Time option"; }leaf renew-rvd-countfeature client-fqdn-op {type uint32; mandatory true;description"renew received counter";"Support for Client FQDN option"; }leaf rebind-rvd-countfeature posix-timezone-op {type uint32; mandatory true;description"rebind recevied counter";"Support for New POIX Timezone option"; }leaf decline-rvd-countfeature tzdb-timezone-op {type uint32; mandatory true;description"decline received counter";"Support for New TZDB Timezone option"; }leaf release-rvd-countfeature ntp-server-op {type uint32; mandatory true;description"release received counter";"Support for Network Time Protocol (NTP) Server option"; }leaf info-req-rvd-countfeature boot-file-url-op {type uint32; mandatory true;description"information request counter";"Support for Boot File URL option"; }leaf relay-for-rvd-countfeature boot-file-param-op {type uint32; mandatory true;description"relay forward received counter";"Support for Boot File Parameters option"; }leaf relay-rep-rvd-countfeature aftr-name-op {type uint32; mandatory true;description"relay reply received counter";"Support for Address Family Transition Router (AFTR) option"; }leaf packet-to-cli-countfeature kbr-default-name-op { description "Support for Kerberos Default Name Option"; } feature kbr-kdc-op {type uint32; mandatory true;description"packet to client counter";"Support for Kerberos KDC option"; }leaf adver-sent-countfeature sol-max-rt-op {type uint32; mandatory true;description"advertisement sent counter";"Support for SOL_MAX_RT option"; }leaf confirm-sent-countfeature inf-max-rt-op {type uint32; mandatory true;description"confirm sent counter";"Support for INF_MAX_RT option"; }leaf reply-sent-countfeature addr-selection-op {type uint32; mandatory true;description"reply sent counter";"Support for Address Selection opiton"; }leaf reconfig-sent-countfeature pcp-server-op {type uint32; mandatory true;description"reconfigure sent counter";"Support for Port Control Protocol (PCP) option"; }leaf relay-for-sent-countfeature s46-rule-op {type uint32; mandatory true;description"relay forward sent counter";"Support for S46 Rule option"; }leaf relay-rep-sent-countfeature s46-br-op {type uint32; mandatory true;description"relay reply sent counter";"Support for S46 Border Relay (BR) option"; } feature s46-dmr-op { description "Support for S46 Default Mapping Rule (DMR) option"; } feature s46-v4-v6-binding-op { description "Support for S46 IPv4/IPv6 Address Bind option"; } // features for relay-supplied options feature erp-local-domain-name-op { description "Support for ERP Local Domain Name option"; }container relay-stats// features for client options feature option-request-op {config "false";description"relay statistics"; leaf cli-packet-rvd-count"Support for Option Request option"; } feature rapid-commit-op {type uint32; mandatory true;description"client packet received counter";"Support for Rapid Commit option"; }leaf relay-for-rvd-countfeature user-class-op {type uint32; mandatory true;description"relay forward received counter";"Support for User Class option"; }leaf relay-rep-rvd-countfeature vendor-class-op {type uint32; mandatory true;description"relay reply recevied counter";"Support for Vendor Class option"; }leaf packet-to-cli-countfeature client-arch-type-op {type uint32; mandatory true;description"packet to client counter";"Support for Client System Architecture Type option"; }leaf relay-for-sent-countfeature client-network-interface-identifier-op {type uint32; mandatory true;description"relay forward sent counter";"Support for Client Network Interface Identifier option"; }leaf relay-rep-sent-countfeature kbr-principal-name-op {type uint32; mandatory true;description"relay reply sent counter";"Support for Kerberos Principal Name option"; }leaf discarded-packet-countfeature kbr-realm-name-op {type uint32; mandatory true;description"discarded packet counter";"Support Kerberos Realm Name option"; } feature client-link-layer-addr-op { description "Support for Client Link-Layer Address Option"; } // features for custom options feature operator-op-ipv6-address { description "Support for Option with IPv6 Addresses"; }container clientfeature operator-op-single-flag {presence "Enables client";description"dhcpv6 client portion"; container duid"Support for Option with Single Flag"; } feature operator-op-ipv6-prefix { description"Sets the DUID"; uses duid;"Support for Option with IPv6 Prefix"; }list client-iffeature operator-op-int32 {key if-name;description"A client may have several interfaces, it is more reasonable to configure and manage parameters on the interface-level. The list defines specific client interfaces and their data. Different interfaces are distinguished by the key which is a configurable string value."; leaf if-name"Support for Opion with 32-bit Integer Value"; } feature operator-op-int16 {type string; mandatory true;description"interface name";"Support for Opion with 16-bit Integer Value"; }leaf cli-idfeature operator-op-int8 {type uint32; mandatory true;description"client id";"Support for Opion with 8-bit Integer Value"; }leaffeature operator-op-uri { description "Support for Opion with URI"; } feature operator-op-textstring {type string;description"description of the client interface";"Support for Opion with Text String"; }leaf pd-functionfeature operator-op-var-data {type boolean; mandatory true;description"Whether the client can act as a requesting router to request prefixes using prefix delegation ([RFC3633]).";"Support for Opion with Variable-Length Data"; }leaf rapid-commitfeature operator-op-dns-wire {type boolean; mandatory true;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.";"Support for Opion with DNS Wire Format Domain Name List"; } /* * Groupings */ grouping portset-para { description "portset parameters"; containermo-tabport-parameter { 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.";"port parameter"; leafm-taboffset { typeboolean;uint8; mandatory true; description"m tab";"offset in a port set"; } leafo-tabpsid-len { typeboolean;uint8; mandatory true; description"o tab"; }"length of a psid"; }container oro-options { description "oro options"; list oro-option { key option-code; description "oro option";leafoption-codepsid { type uint16; mandatory true; description"option code";"psid value"; }leaf} } grouping duid { description "DHCP Unique Identifier"; reference "RFC3315: Section 9"; leaf type-code { typestring; mandatory true;uint16; default 65535; description"description"Type code oforo options";this DUID"; } choice duid-type { default duid-invalid; description "Selects the format for the DUID."; case duid-llt { description "DUID Based on Link-layer Address Plus Time (Type 1 - DUID-LLT)"; reference "RFC3315 Section 9.2"; leaf duid-llt-hardware-type { type uint16; description "Hardware type as assigned by IANA (RFC826)."; } leaf duid-llt-time { type yang:timeticks; description "The time value is the time that the DUID is generated represented in seconds since midnight (UTC), January 1, 2000, modulo 2^32."; }container client-configured-optionsleaf duid-llt-link-layer-addr { type yang:mac-address; description"client configured options"; list new-or-standard-cli-option"Link-layer address as described in RFC2464"; } } case duid-en {key option-code;description"new or standard client option";"DUID Assigned by Vendor Based on Enterprise Number (Type 2 - DUID-EN)"; reference "RFC3315 Section 9.3"; leafoption-codeduid-en-enterprise-number { typeuint16; mandatory true;uint32; description"option code";"Vendor's registered Private Enterprise Number as maintained by IANA"; } leafoption-nameduid-en-identifier { type string;mandatory true;description"option name";"Indentifier, unique to the device that is using it"; } } case duid-ll { description "DUID Based on Link-layer Address (Type 3 - DUID-LL)"; reference "RFC3315 Section 9.4"; leafoption-descriptionduid-ll-hardware-type { typestring; mandatory true;uint16; description"description of client option";"Hardware type as assigned by IANA (RFC826)."; } leafoption-referenceduid-ll-link-layer-addr { typestring;yang:mac-address; description "Link-layer address as described in RFC2464"; } } case duid-uuid { description"the"DUID Based on Universally Unique Identifier (Type 4 - DUID-UUID)"; reference "RFC6335 Defination ofoption"; }the UUID-Based Unique Identifier"; leafoption-valueuuid { typestring; mandatory true;yang:uuid; description"the option value";"A Universally Unique IDentifier in the string representation defined in RFC 4122. The canonical representation uses lowercase characters"; } }container user-class-optioncase duid-invalid { description"user class option";"DUID based on free raw bytes"; leafenabledata { typeboolean; mandatory true;binary; description"indicate whether this option will"The bits to beconfigured atused as theclient";identifier"; }list user-class} } } grouping server-option-definitions {key user-class-id;description"user class";"Contains definitions for options configured on the DHCPv6 server which will be supplied to clients."; container server-unicast-option { if-feature server-unicast-op; presence "Enable this option"; description "OPTION_UNICAST (12) Server Unicast Option"; reference "RFC3315: Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"; leafuser-class-idserver-address { typeuint8; mandatory true;inet:ipv6-address; description"user class id";"server ipv6 address"; } } container sip-server-domain-name-list-option { if-feature sip-server-domain-name-list-op; presence "Enable this option"; description "OPTION_SIP_SERVER_D (21) SIP Servers Domain Name List"; reference "RFC3319: Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers"; leafuser-class-infosip-serv-domain-name { type string; mandatory true; description"user class info"; }"sip server domain name"; } } containervendor-class-optionsip-server-address-list-option {description "vendor classif-feature sip-server-address-list-op; presence "Enable this option"; description "OPTION_SIP_SERVER_A (22) SIP Servers IPv6 Address List"; reference "RFC3319: Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers"; list sip-server { key sip-serv-id; description "sip server info"; leafenablesip-serv-id { typeboolean;uint8; mandatory true; description"indicate whether this option will be configured at the client";"sip server id"; } leafent-numsip-serv-addr { typeuint32;inet:ipv6-address; mandatory true; description"enterprise number";"sip server addr"; }leaf-list data { type string; description "option data";} } containerclient-fqdn-optiondns-config-option {description "client fqdnif-feature dns-config-op; presence "Enable this option";leaf enable { type boolean; mandatory true;description"indicate whether this option will be configured at the client"; } leaf fqdn"OPTION_DNS_SERVERS (23) DNS recursive Name Server option"; reference "RFC3646: DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"; list dns-server {type string; mandatory true;key dns-serv-id; description"fqdn"; }"dns server info"; leafserver-initiate-updatedns-serv-id { typeboolean;uint8; mandatory true; description"whether"DNS serverinitiate";list entry ID."; } leafclient-initiate-updatedns-serv-addr { typeboolean;inet:ipv6-address; mandatory true; description"whether client initiate";"DNS server address."; } } } containerclient-architecture-type-optiondomain-searchlist-option { if-feature domain-searchlist-op; presence "Enable this option"; description"client architecture"OPTION_DOMAIN_LIST (24) Domain Search List Option"; reference "RFC3646: DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"; list domain-searchlist { key domain-searchlist-id; description "dns server info"; leaf domain-searchlist-id { typeoption";uint8; mandatory true; description "Domain seachlist entry ID."; } leafenabledomain-search-list-entry { typeboolean;string; mandatory true; description"indicate whether this option will be configured at the client";"Domain search list entry."; } } } container nis-config-option { if-feature nis-config-op; presence "Enable this option"; description "OPTION_NIS_SERVERS (27) Network Information Service (NIS) Servers Option."; reference "RFC3898: Network Information Service (NIS) Configuration Options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"; listarchitecture-typesnis-server { keytype-id;nis-serv-id; description"architecture types";"nis server info"; leaftype-idnis-serv-id { typeuint16;uint8; mandatory true; description"type"nis server id"; } leafmost-preferrednis-serv-addr { typeboolean;inet:ipv6-address; mandatory true; description"most preferred flag";"nis server addr"; } } } containerclient-network-interface-optionnis-plus-config-option {description "client network interfaceif-feature nis-plus-config-op; presence "Enable this option";leaf enabledescription "OPTION_NISP_SERVERS (28): Network Information Service V2 (NIS+) Servers Option."; reference "RFC3989: Network Information Service (NIS) Configuration Options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"; list nis-plus-server {type boolean; mandatory true;key nis-plus-serv-id; description"indicate whether this option will be configured at the client"; }"NIS+ server information."; leaftypenis-plus-serv-id { type uint8; mandatory true; description"type";"nisp server id"; } leafmajornis-plus-serv-addr { typeuint8;inet:ipv6-address; mandatory true; description"major";"nisp server addr"; } } } container nis-domain-name-option { if-feature nis-domain-name-op; presence "Enable this option"; description "OPTION_NIS_DOMAIN_NAME (29) Network Information Service (NIS) Domain Name Option"; reference "RFC3989: Network Information Service (NIS) Configuration Options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"; leafminornis-domain-name { typeuint8; mandatory true;string; description"minor";"The Network Information Service (NIS) Domain Name option is used by the server to convey client's NIS Domain Name info to the client."; } } containerkerberos-principal-name-optionnis-plus-domain-name-option {description "kerberos principal nameif-feature nis-plus-domain-name-op; presence "Enable this option";leaf enable { type boolean; mandatory true;description"indicate whether this option will be configured at the client"; }"OPTION_NISP_DOMAIN_NAME (30) Network Information Service V2 (NIS+) Domain Name Option"; reference "RFC3989: Network Information Service (NIS) Configuration Options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"; leafprincipal-namenis-plus-domain-name { type string;mandatory true;description"principal name";"The Network Information Service V2 (NIS+) Domain Name option is used by the server to convey client's NIS+ Domain Name info to the client."; } } containerclient-link-layer-addr-optionsntp-server-option {description "client link layer addressif-feature sntp-server-op; presence "Enable this option"; description "OPTION_SNTP_SERVERS (31) Simple Network Time Protocol (SNTP) Servers Option"; reference "RFC4075: Simple Network Time Protocol (SNTP) Configuration Option for DHCPv6"; list sntp-server { key sntp-serv-id; description "sntp server info"; leafenablesntp-serv-id { typeboolean;uint8; mandatory true; description"indicate whether this option will be configured at the client";"sntp server id"; } leaflink-layer-typesntp-serv-addr { typeuint16;inet:ipv6-address; mandatory true; description"link layer type";"sntp server addr"; } } } container info-refresh-time-option { if-feature info-refresh-time-op; presence "Enable this option"; description "OPTION_INFORMATION_REFRESH_TIME (32) Information Refresh Time option."; reference "RFC4242: Information Refresh Time Option for Dynamic Host Configuration Protocol for IPv6 (DHCPv6"; leaflink-layer-addrinfo-refresh-time { typestring;yang:timeticks; mandatory true; description"link layer address"; }"The refresh time."; } } containeridentity-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-associationclient-fqdn-option {key iaid;if-feature client-fqdn-op; presence "Enable this option"; description"IA";"OPTION_CLIENT_FQDN (39) DHCPv6 Client FQDN Option"; reference "RFC4704: The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Client Fully Qualified Domain Name (FQDN) Option"; leafiaidserver-initiate-update { typeuint32;boolean; mandatory true; description"IAID";"server initiate"; } leafia-typeclient-initiate-update { typestring;boolean; mandatory true; description"IA type";"client initiate"; }leaf-list ipv6-addrleaf modify-name-from-cli { typeinet:ipv6-address;boolean; mandatory true; description"ipv6 address";"modify by client"; }leaf-list ipv6-prefix { type inet:ipv6-prefix; description "ipv6 prefix";}leaf-list prefix-lengthcontainer posix-timezone-option {type uint8;if-feature posix-timezone-op; presence "Enable this option"; description"ipv6 prefix length"; }"OPTION_NEW_POSIX_TIMEZONE (41) Posix Timezone option"; reference "RFC4833: Timezone Options for DHCP"; leaft1-timetz-posix { typeyang:timeticks;string; mandatory true; description"t1 time";"TZ Posix IEEE 1003.1 String"; } } container tzdb-timezone-option { if-feature tzdb-timezone-op; presence "Enable this option"; description "OPTION_NEW_TZDB_TIMEZONE (42) Timezone Database option"; reference "RFC4822: Timezone Options for DHCP"; leaft2-timetz-database { typeyang:timeticks;string; mandatory true; description"t2 time";"Reference to the TZ Database"; } } container ntp-server-option { //This option looks like it needs work to correctly model the //option as defined in the RFC. // Zihao - Re-modelled so it only contains one // time source suboption if-feature ntp-server-op; presence "Enable this option"; description "OPTION_NTP_SERVER (56) NTP Server Option for DHCPv6"; reference "RFC5908: Network Time Protocol (NTP) Server Option for DHCPv6"; list ntp-server { key ntp-serv-id; description "ntp server info"; leafpreferred-lifetimentp-serv-id { typeyang:timeticks;uint8; mandatory true; description"preferred lifetime";"ntp server id"; }leaf valid-lifetimechoice ntp-time-source-suboption { description "Select a NTP time source suboption."; case server-address { leaf-list ntp-serv-addr-suboption { typeyang:timeticks; mandatory true;inet:ipv6-address; description"valid lifetime"; }"ntp server addr"; } }container if-other-parascase server-multicast-address {config "false";leaf-list ntp-serv-mul-addr-suboption { type inet:ipv6-address; 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"ntp serverdomain names, etc.";multicast addr"; } } case server-fqdn { leaf-listuni-dhcpv6-serv-addrntp-serv-fqdn-suboption { typeinet:ipv6-address;string; description"unicast"ntp serveraddress";fqdn"; } } } } } containerdns-paras { description "dns parameters"; leaf domain-search-listboot-file-url-option {type string; mandatory true;if-feature boot-file-url-op; presence "Enable this option"; description"domain search list"; }"OPT_BOOTFILE_URL (59) Boot File URL option"; reference "RFC5970: DHCPv6 Options for Network Boot"; listdns-serversboot-file { keydns-serv-id;boot-file-id; description"dns servers";"boot file info"; leafdns-serv-idboot-file-id { type uint8; mandatory true; description"dns server"boot file id"; } leaf-list suitable-arch-type { type uint16; description "architecture type"; } leaf-list suitable-net-if { type uint32; description "network interface"; } leafdns-serv-addrboot-file-url { typeinet:ipv6-address;string; mandatory true; description"dns server address";"url for boot file"; } } } containersip-parasboot-file-param-option { if-feature boot-file-param-op; presence "Enable this option"; description"sip parameters";"OPT_BOOTFiLE_PARAM (60) Boot File Parameters Option"; reference "RFC5970: DHCPv6 Options for Network Boot"; listsip-serversboot-file-paras { keysip-serv-id;para-id; description"sip server info";"boot file parameters"; leafsip-serv-idpara-id { type uint8; mandatory true; description"sip server"parameter id"; } leafsip-serv-addrparameter { typeinet:ipv6-address;string; mandatory true; description"sip server address";"parameter value"; } } } container aftr-name-option { if-feature aftr-name-op; presence "Enable this option"; description "OPTION_AFTR_NAME (64) AFTR-Name DHCPv6 Option"; reference "RFC6334: Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Option for Dual-Stack Lite"; leafsip-serv-domain-nametunnel-endpoint-name { type string; mandatory true; description"sip server domain"aftr name"; } }}containernis-paraskbr-default-name-option { if-feature kbr-default-name-op; presence "Enable this option"; description"nis parameters";"OPTION_KRB_DEFAULT_REALM_NAME (77) Kerberos Default Realm Name Option"; reference "RFC6784: Kerberos Options for DHCPv6"; leafnis-domain-namedefault-realm-name { type string; mandatory true; description"nis domain"default realm name"; } } container kbr-kdc-option { if-feature kbr-kdc-op; presence "Enable this option"; description "OPTION_KRB_KDC (78) Kerberos KDB Option"; reference "RFC6784: Kerberos Options for DHCPv6"; listnis-serverkdc-info { keynis-serv-id;kdc-id; description"nis server";"kdc info"; leafnis-serv-idkdc-id { type uint8; mandatory true; description"nis server"kdc id"; } leafnis-serv-addrpriority { typeinet:ipv6-address;uint16; mandatory true; description"nis server address"; } }"priority"; }container nis-plus-paras { description "nisp parameters";leafnis-plus-domain-nameweight { typestring;uint16; mandatory true; description"nisp domian name";"weight"; }list nis-plus-server { key nis-plus-serv-id; description "nisp server";leafnis-plus-serv-idtransport-type { type uint8; mandatory true; description"nisp server id"; } leaf nis-plus-serv-addr { type inet:ipv6-address; mandatory true; description "nisp server address"; } } } leaf info-refresh-time { type yang:timeticks; description "info refresh time";"transport type"; }container time-zone-paras { description "time zone parameters";leaftz-posixport-number { typestring;uint16; mandatory true; description"tz posix";"port number"; } leaftz-databasekdc-ipv6-addr { typestring;inet:ipv6-address; mandatory true; description"tz database"; }"kdc ipv6 addr"; } leafcli-fqdnrealm-name { type string; mandatory true; description"client fqdn";"realm name"; } } } containerntp-paras { description "ntp parameters"; list ntp-serversol-max-rt-option {key ntp-serv-id;if-feature sol-max-rt-op; presence "Enable this option"; description"ntp server";"OPTION_SOL_MAX_RT (82) sol max rt option"; reference "RFC7083: Modification to Default Values of SOL_MAX_RT and INF_MAX_RT"; leafntp-serv-idsol-max-rt-value { typeuint8;yang:timeticks; mandatory true; description"ntp server id";"sol max rt value"; } } container inf-max-rt-option { if-feature inf-max-rt-op; presence "Enable this option"; description "OPTION_INF_MAX_RT (83) inf max rt option"; reference "RFC7083: Modification to Default Values of SOL_MAX_RT and INF_MAX_RT"; leafntp-serv-addrinf-max-rt-value { typeinet:ipv6-address;yang:timeticks; mandatory true; description"ntp server address";"inf max rt value"; } } container addr-selection-option { if-feature addr-selection-op; presence "Enable this option"; description "OPTION_ADDRSEL (84) and OPTION_ADDRSEL_TABLE (85)"; reference "RFC7078: Distributing Address Selection Policy Using DHCPv6"; // if - Needs checking to see if this matches the RFC - there // are two options here. // Zihao - I think this matches RFC7078 leafntp-serv-mul-addra-bit-set { typeinet:ipv6-address;boolean; mandatory true; description"ntp server multicast address";"a bit"; } leafntp-serv-fqdnp-bit-set { typestring;boolean; mandatory true; description"ntp server fqdn"; } }"p bit"; }container sntp-paras { description "sntp parameters";listsntp-serverpolicy-table { keysntp-serv-id;policy-id; description"sntp server";"policy table"; leafsntp-serv-idpolicy-id { type uint8; mandatory true; description"sntp server"policy id"; } leafsntp-serv-addrlabel { typeinet:ipv6-address;uint8; mandatory true; description"sntp server address"; } }"label"; }container network-boot-paras { description "network boot parameters"; list boot-file { key boot-file-id; description "boot file";leafboot-file-idprecedence { type uint8; mandatory true; description"boot file id"; } leaf-list suitable-arch-type { type uint16; description "architecture type";"precedence"; }leaf-list suitable-net-ifleaf prefix-len { typeuint32;uint8; mandatory true; description"network interface";"prefix length"; } leafboot-file-urlprefix { typestring;inet:ipv6-prefix; mandatory true; description"boot file url";"prefix"; } } } container pcp-server-option { if-feature pcp-server-op; presence "Enable this option"; description "OPTION_V6_PCP_SERVER (86) pcp server option"; reference "RFC7291: DHCP Options for the Port Control Protocol (PCP)"; listboot-file-paraspcp-server { keypara-id;pcp-serv-id; description"boot file parameters";"pcp server info"; leafpara-idpcp-serv-id { type uint8; mandatory true; description"parameter"pcp server id"; } leafparameterpcp-serv-addr { typestring;inet:ipv6-address; mandatory true; description"parameter value"; }"pcp server addr"; } } } containerkerberos-paras { description "kerberos parameters"; leaf default-realm-names46-rule-option {type string; mandatory true;if-feature s46-rule-op; presence "Enable this option"; description"default realm name"; }"OPTION_S46_RULE (89) S46 rule option"; reference "RFC7598: DHCPv6 Options for Configuration of Softwire Address and Port-Mapped Clients"; listkdc-infos46-rule { keykdc-id;rule-id; description"kdc info";"s46 rule"; leafkdc-idrule-id { type uint8; mandatory true; description"kdc"rule id"; } leafpriorityrule-type { typeuint16; mandatory true;enumeration { enum "BMR" { description"priority";"BMR"; }leaf weightenum "FMR" {type uint16;description "FMR"; } } mandatory true; description"weight";"rule type"; } leaftransport-typeprefix4-len { type uint8; mandatory true; description"transport type";"ipv4 prefix length"; } leafport-numberipv4-prefix { typeuint16;inet:ipv4-prefix; mandatory true; description"port number";"ipv4 prefix"; } leafkdc-ipv6-addrprefix6-len { typeinet:ipv6-address;uint8; mandatory true; description"kdc ipv6 address";"ipv6 prefix length"; } leafrealm-nameipv6-prefix { typestring;inet:ipv6-prefix; mandatory true; description"realm name";"ipv6 prefix"; } uses portset-para; } } containeraddr-selection-parass46-br-option { if-feature s46-br-op; presence "Enable this option"; description"address selection parameters";"OPTION_S46_BR (90) S46 BR Option"; reference "RFC7598: DHCPv6 Options for Configuration of Softwire Address and Port-Mapped Clients"; list br { key br-id; description "br info"; leafautomatic-row-addbr-id { typeboolean;uint8; mandatory true; description"row add";"br id"; } leafprefer-temporary-addrbr-ipv6-addr { typeboolean;inet:ipv6-address; mandatory true; description"prefer temporary";"br ipv6 addr"; } } } container s46-dmr-option { if-feature s46-dmr-op; presence "Enable this option"; description "OPTION_S46_DMR (91) S46 DMR Option"; reference "RFC7598: DHCPv6 Options for Configuration of Softwire Address and Port-Mapped Clients"; listpolicy-tabledmr { keypolicy-id;dmr-id; description"policy table";"dmr info"; leafpolicy-iddmr-id { type uint8; mandatory true; description"policy id ";"dmr id"; } leaflabeldmr-prefix-len { type uint8; mandatory true; description"label";"dmr prefix length"; } leafprecedencedmr-ipv6-prefix { typeuint8;inet:ipv6-prefix; mandatory true; description"precedence";"dmr ipv6 prefix"; } } } container s46-v4-v6-binding-option { if-feature s46-v4-v6-binding-op; presence "Enable this option"; description "OPTION_S46_V4V6BIND (92) S46 IPv4/IPv6 Address Binding option"; reference "RFC7598: DHCPv6 Options for Configuration of Softwire Address and Port-Mapped Clients"; list ce { key ce-id; description "ce info"; leafprefix-lence-id { type uint8; mandatory true; description"prefix length";"ce id"; } leafprefixipv4-addr { typeinet:ipv6-prefix;inet:ipv4-address; mandatory true; description"prefix"; } }"ce ipv4 addr"; } leafsol-max-rtbind-prefix6-len { typeyang:timeticks;uint8; mandatory true; description"sol max rt";"bind ipv6 prefix length"; } leafinf-max-rtbind-ipv6-prefix { typeyang:timeticks;inet:ipv6-prefix; mandatory true; description"inf max rt";"bind ipv6 prefix"; } uses portset-para; } } } //if - NB - The list of options needs to be updated. grouping relay-supplied-option-definitions { // if - The structure here needs to be checked and probably reworked. description "OPTION_RSOO (66) Relay-Supplied Options option"; reference "RFC6422: Relay-Supplied DHCP Options"; containerpcp-server-paraserp-local-domain-name-option { if-feature erp-local-domain-name-op; presence "Enable this option"; description"pcp server parameters";"OPTION_ERP_LOCAL_DOMAIN_NAME (65) DHCPv6 ERP Local Domain Name Option"; reference "RFC6440: The EAP Re-authentication Protocol (ERP) Local Domain Name DHCPv6 Option"; listpcp-servererp-for-client { keypcp-serv-id;cli-id; description"pcp server";"erp for client"; leafpcp-serv-idcli-id { typeuint8;uint32; mandatory true; description"pcp server"client id"; } container duid { description "Sets the DUID"; // uses duid; // if - Maybe DUID definition needs to be moved to this module. uses duid; } leafpcp-serv-addrerp-name { typeinet:ipv6-address;string; mandatory true; description"pcp server address";"erp name"; } } }container s46-rule-paras} grouping client-option-definitions { description"s46 rule parameters";"Contains definitions for options configured on the DHCPv6 client which will be sent to the server."; lists46-rulenew-or-standard-cli-option { keyrule-id;option-code; description"s46 rule";"new or standard client option"; leafrule-idoption-code { typeuint8;uint16; mandatory true; description"rule id";"option code"; } leafrule-typeoption-name { typeenumeration { enum "BMR"{ description "BMR"; } enum "FMR"{ description "FMR"; } }string; mandatory true; description"rule type";"option name"; } leafea-lenoption-description { typeuint8;string; mandatory true; description"EA bits length";"description of client option"; } leafprefix4-lenoption-reference { typeuint8; mandatory true;string; description"ipv4 prefix length";"the reference of option"; } leafipv4-prefixoption-value { typeinet:ipv4-prefix;string; mandatory true; description"ipv4 prefix";"the option value"; } } container option-request-option { if-feature option-request-op; presence "Enable this option"; description "OPTION_ORO (6) Option Request Option"; reference "RFC3315: Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"; list oro-option { key option-code; description "oro option"; leafprefix6-lenoption-code { typeuint8;uint16; mandatory true; description"ipv6 prefix length";"option code"; } leafipv6-prefixdescription { typeinet:ipv6-prefix;string; mandatory true; description"ipv6 prefix";"description of oro options"; }uses portset-para;} } containers46-br-parasuser-class-option {description "s46 br parameters";if-feature user-class-op; presence "Enable this option"; description "OPTION_USER_CLASS (15) User Class Option"; reference "RFC3315: Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"; listbruser-class { keybr-id;user-class-id; description"br";"user class"; leafbr-iduser-class-id { type uint8; mandatory true; description"br"user class id"; } leafbr-ipv6-addruser-class-data { typeinet:ipv6-address;string; mandatory true; description"br ipv6 address";"The information contained in the data area of this option is contained in one or more opaque fields that represent the user class or classes of which the client is a member. "; } } } containers46-dmr-paras { description "s46 dmr parameters"; list dmrvendor-class-option {key dmr-id;if-feature vendor-class-op; presence "Enable this option"; description"dmr";"OPTION_VENDOR_CLASS (16) Vendor Class Option"; reference "RFC3315: Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"; leafdmr-identerprise-number { typeuint8;uint32; mandatory true; description"dmr id";"enterprise number"; } list vendor-class { key vendor-class-id; description "vendor class"; leafdmr-prefix-lenvendor-class-id { type uint8; mandatory true; description"dmr prefix length";"vendor class id"; } leafdmr-ipv6-prefixvendor-class-data { typeinet:ipv6-prefix;string; mandatory true; description"dmr prefix";"The vendor-class-data is composed of a series of separate items, each of which describes some characteristic of the client's hardware configuration. Examples of vendor-class-data instances might include the version of the operating system the client is running or the amount of memory installed on the client."; } } } containers46-v4-v6-binding-parasclient-fqdn-option { if-feature client-fqdn-op; presence "Enable this option"; description"s46 v4 v6 binding parameters";"OPTION_CLIENT_FQDN (39) The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Client Fully Qualified Domain Name (FQDN) Option"; reference "RFC4704: The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Client Fully Qualified Domain Name (FQDN) Option"; leafipv4-addrfqdn { typeinet:ipv4-address;string; mandatory true; description"ipv4 address";"fqdn"; } leafbind-prefix6-lenserver-initiate-update { typeuint8;boolean; mandatory true; description"bind ipv6 prefix";"whether server initiate"; }uses portset-para;leaferp-local-domain-nameclient-initiate-update { typestring;boolean; mandatory true; description"erp local domain name";"whether client initiate"; } } containersupported-optionsclient-arch-type-option { if-feature client-arch-type-op; presence "Enable this option"; description"supported options";"OPTION_CLIENT_ARCH_TYPE (61) Client System Architecture Type Option"; reference "RFC5970: DHCPv6 Options for Network Boot"; listsupported-optionarchitecture-types { keyoption-code;type-id; description"supported option";"architecture types"; leafoption-codetype-id { type uint16; mandatory true; description"option code";"type id"; } leafdescriptionmost-preferred { typestring;boolean; mandatory true; description"description of supported option"; }"most preferred flag"; } } } containerpacket-statsclient-network-interface-identifier-option {config "false";if-feature client-network-interface-identifier-op; presence "Enable this option"; description"A container records all the packet status information of a specific interface.";"OPTION_NII (62) Client Network Interface Identifier Option"; reference "RFC5970: DHCPv6 Options for Network Boot"; leafsolicit-counttype { typeuint32;uint8; mandatory true; description"solicit counter";"type"; } leafrequest-countmajor { typeuint32;uint8; mandatory true; description"request counter";"major"; } leafrenew-countminor { typeuint32;uint8; mandatory true; description"renew counter";"minor"; }leaf rebind-count} container kbr-principal-name-option {type uint32; mandatory true;if-feature kbr-principal-name-op; presence "Enable this option"; description"rebind counter"; } leaf decline-count"OPTION_KRB_PRINCIPAL_NAME (75) Kerberos Principal Name Option"; reference "RFC6784: Kerberos Options for DHCPv6"; list principle-name {type uint32; mandatory true;key principle-name-id; description"decline counter"; }"principle name"; leafrelease-countprinciple-name-id { typeuint32;uint8; mandatory true; description"release counter";"principle name id"; } leafinfo-req-countname-type { typeuint32;int32; mandatory true; description"information request counter";"This field specifies the type of name that follows."; } leafadvertise-countname-string { typeuint32;string; mandatory true; description"advertise counter";"This field encodes a sequence of components that form a name, each component encoded as a KerberoString"; } } } container kbr-realm-name-option { if-feature kbr-realm-name-op; presence "Enable this option"; description "OPTION_KRB_REALM_NAME (76) Kerberos Realm Name Option"; reference "RFC6784: Kerberos Options for DHCPv6"; leafconfirm-countrealm-name { typeuint32;string; mandatory true; description"confirm counter";"realm name"; } } container client-link-layer-addr-option { if-feature client-link-layer-addr-op; presence "Enable this option"; description "OPTION_CLIENT_LINKLAYER_ADDR (79) DHCPv6 Client Link-Layer Address Option"; reference "RFC6939: Client Link-Layer Address Option in DHCPv6"; leafreply-countlink-layer-type { typeuint32;uint16; mandatory true; description"reply counter";"Client link-layer address type. The link-layer type MUST be a valid hardware type assigned by the IANA, as described in [RFC0826]"; } leafreconfigure-countlink-layer-addr { typeuint32;string; mandatory true; description"recofigure counter"; }"Client link-layer address"; } } }/* * Notifications */ notification notificationsgrouping custom-option-definitions { description"dhcpv6 notification module";"operator customized options"; containerdhcpv6-server-eventoperator-option-ipv6-address { if-feature operator-op-ipv6-address; presence "Enable this option"; description"dhcpv6 server event"; container pool-running-out"operator ipv6 address option"; reference "RFC7227: Guidelines for Creating New DHCPv6 Options"; list operator-ipv6-addr { key operator-ipv6-addr-id; description"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";"operator ipv6 address info"; leafutilization-ratiooperator-ipv6-addr-id { typeuint16;uint8; mandatory true; description"utilization ratio";"operator ipv6 address id"; }container duidleaf operator-ipv6-addr { type inet:ipv6-address; mandatory true; description"Sets the DUID"; uses duid;"operator ipv6 address id"; } } } container operator-option-single-flag { if-feature operator-op-single-flag; presence "Enable this option"; description "operator single flag"; reference "RFC7227: Guidelines for Creating New DHCPv6 Options"; list flag { key flag-id; description "operator single flag info"; leafserv-nameflag-id { typestring;uint8; mandatory true; description"server name";"operator single flag id"; } leafpool-name {flag-value{ typestring;boolean; mandatory true; description"pool name";"operator single flag value"; } } } containerinvalid-client-detectedoperator-option-ipv6-prefix { if-feature operator-op-ipv6-prefix; presence "Enable this option"; description"raised when the server has found a client which can be regarded as a potential attacker. Some"operator ipv6 prefix option"; reference "RFC7227: Guidelines for Creating New DHCPv6 Options"; list operator-ipv6-prefix{ key operator-ipv6-prefix-id; descriptioncould also be included."; container duid"operator ipv6 prefix info"; leaf operator-ipv6-prefix-id { type uint8; mandatory true; description"Sets the DUID"; uses duid;"operator ipv6 prefix id"; } leaf operator-ipv6-prefix6-len{ type uint8; mandatory true; description "operator ipv6 prefix length"; } leaf operator-ipv6-prefix { typestring;inet:ipv6-prefix; mandatory true; description"description of the event";"operator ipv6 prefix"; } } } containerdhcpv6-relay-eventoperator-option-int32 { if-feature operator-op-int32; presence "Enable this option"; description"dhcpv6 relay event"; container topo-changed {"operator integer 32 option"; reference "RFC7227: Guidelines for Creating New DHCPv6 Options"; list int32val{ key int32val-id; description"raised when the topology of the relay agent is changed.";"operator integer 32 info"; leafrelay-if-nameint32val-id { typestring;uint8; mandatory true; description"relay interface name";"operator integer 32 id"; } leaf int32val{ type uint32; mandatory true; description "operator integer 32 value"; } } } container operator-option-int16 { if-feature operator-op-int16; presence "Enable this option"; description "operator integer 16 option"; reference "RFC7227: Guidelines for Creating New DHCPv6 Options"; list int16val{ key int16val-id; description "operator integer 16 info"; leaffirst-hopint16val-id { typeboolean;uint8; mandatory true; description"first hop";"operator integer 16 id"; } leaflast-entity-addr {int16val{ typeinet:ipv6-address;uint16; mandatory true; description"last entity address";"operator integer 16 value"; } } } containerdhcpv6-client-eventoperator-option-int8 { if-feature operator-op-int8; presence "Enable this option"; description"dhcpv6 client event"; container ia-lease-event {"operator integer 8 option"; reference "RFC7227: Guidelines for Creating New DHCPv6 Options"; list int8val{ key int8val-id; description"raised when the client was allocated a new IA from the server or it renew/rebind/release its current IA";"operator integer 8 info"; leafevent-typeint8val-id { typeenumeration{ enum "allocation" { description "allocate"; } enum "rebind" { description "rebind"; } enum "renew" { description "renew"; } enum "release" { description "release"; } }uint8; mandatory true; description"event type"; } container duid { description "Sets the DUID"; uses duid;"operator integer 8 id"; } leafiaid {int8val{ typeuint32;uint8; mandatory true; description"IAID"; } leaf serv-name { type string; description "server name";"operator integer 8 value"; }leaf description { type string; description "description of event";} } containerinvalid-ia-detectedoperator-option-uri { if-feature operator-op-uri; presence "Enable this option"; description"raised when the identity association of the client can be proved to be invalid. Possible condition includes duplicated address, illegal address, etc."; container duid {"operator uri option"; reference "RFC7227: Guidelines for Creating New DHCPv6 Options"; list uri{ key uri-id; description"Sets the DUID"; uses duid; }"operator uri info"; leafcli-duiduri-id { typeuint32;uint8; mandatory true; description"duid of client";"operator uri id"; } leafiaid {uri{ typeuint32;string; mandatory true; description"IAID";"operator uri value"; } } } container operator-option-textstring { if-feature operator-op-textstring; presence "Enable this option"; description "operator itext string option"; reference "RFC7227: Guidelines for Creating New DHCPv6 Options"; list textstring{ key textstring-id; description "operator text string info"; leafserv-nametextstring-id { typestring;uint8; mandatory true; description"server name";"operator text string id"; } leafdescription {textstring{ type string; mandatory true; description"description of the event";"operator text string value"; } } } containerretransmission-failedoperator-option-var-data { if-feature operator-op-var-data; presence "Enable this option"; description"raised when the retransmission mechanism defined in [RFC3315] is failed."; container duid {"operator variable length data option"; reference "RFC7227: Guidelines for Creating New DHCPv6 Options"; list int32val{ key var-data-id; description"Sets the DUID"; uses duid; }"operator ivariable length data info"; leafdescriptionvar-data-id { typeenumeration { enum "MRC failed" { description "MRC failed"; } enum "MRD failed" {uint8; mandatory true; description"MRD failed"; }"operator variable length id"; } leaf var-data{ type binary; mandatory true; description"description of failure";"operator variable length value"; } } } containerfailed-status-turn-upoperator-option-dns-wire { if-feature operator-op-dns-wire; presence "Enable this option"; description"raised when the client receives a message includes an unsuccessful Status Code option."; container duid {"operator dns wire format domain name list option"; reference "RFC7227: Guidelines for Creating New DHCPv6 Options"; list operator-option-dns-wire{ key operator-option-dns-wire-id; description"Sets the DUID"; uses duid; }"operator dns wire format info"; leafstatus-codeoperator-option-dns-wire-id { typeenumeration { enum "1" { description "UnspecFail"; } enum "2" { description "NoAddrAvail"; } enum "3" { description "NoBinding"; } enum "4" { description "NotOnLink"; } enum "5" {uint8; mandatory true; description"UseMulticast"; }"operator dns wire format id"; } leaf operator-option-dns-wire{ type binary; mandatory true; description"employed status code";"operator dns wire format value"; } } } } } <CODE ENDS> 4. Security Considerations (TBD) TBD 5. IANA Considerations (TBD) This document registers the following YANG modules in the "YANG Module Names" registry [RFC6020]. name: ietf-dhcpv6 namespace: urn:ietf:params:xml:ns:yang:ietf-dhcpv6 prefix: dhcpv6 reference: TBD 6. Acknowledgements The authors would like to thank Qi Sun, Lishan Li, Sladjana Zoric, Tomek Mrugalski, Marcin Siodelski, Bernie Volz and Bing Liu for their valuable comments and contributions to this work. 7. Contributors The following individuals contributed to this effort: Hao Wang Tsinghua University Beijing 100084 P.R.China Phone: +86-10-6278-5822 Email: wangh13@mails.tsinghua.edu.cn Ted Lemon Nomium, Inc 950 Charter St. Redwood City, CA 94043 USA Email: Ted.Lemon@nomium.com 8. References7.1.8.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-editor.org/info/rfc2119>. [RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July 2003, <https://www.rfc-editor.org/info/rfc3315>. [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6", RFC 3633, DOI 10.17487/RFC3633, December 2003, <https://www.rfc-editor.org/info/rfc3633>. [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, DOI 10.17487/RFC6020, October 2010, <https://www.rfc-editor.org/info/rfc6020>. [RFC6087] Bierman, A., "Guidelines for Authors and Reviewers of YANG Data Model Documents", RFC 6087, DOI 10.17487/RFC6087, January 2011, <https://www.rfc-editor.org/info/rfc6087>. [RFC6355] Narten, T. and J. Johnson, "Definition of the UUID-Based DHCPv6 Unique Identifier (DUID-UUID)", RFC 6355, DOI 10.17487/RFC6355, August 2011, <https://www.rfc-editor.org/info/rfc6355>. [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 6991, DOI 10.17487/RFC6991, July 2013, <https://www.rfc-editor.org/info/rfc6991>.7.2.8.2. Informative References [I-D.ietf-netmod-yang-tree-diagrams] Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft-ietf-netmod-yang-tree-diagrams-02ietf-netmod-yang-tree-diagrams-04 (work in progress),OctoberDecember 2017. [RFC3319] Schulzrinne, H. and B. Volz, "Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers", RFC 3319, DOI 10.17487/RFC3319, July 2003, <https://www.rfc-editor.org/info/rfc3319>. [RFC3646] Droms, R., Ed., "DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3646, DOI 10.17487/RFC3646, December 2003, <https://www.rfc-editor.org/info/rfc3646>. [RFC3898] Kalusivalingam, V., "Network Information Service (NIS) Configuration Options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3898, DOI 10.17487/RFC3898, October 2004, <https://www.rfc-editor.org/info/rfc3898>. [RFC4075] Kalusivalingam, V., "Simple Network Time Protocol (SNTP) Configuration Option for DHCPv6", RFC 4075, DOI 10.17487/RFC4075, May 2005, <https://www.rfc-editor.org/info/rfc4075>. [RFC4242] Venaas, S., Chown, T., and B. Volz, "Information Refresh Time Option for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 4242, DOI 10.17487/RFC4242, November 2005, <https://www.rfc-editor.org/info/rfc4242>. [RFC4704] Volz, B., "The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Client Fully Qualified Domain Name (FQDN) Option", RFC 4704, DOI 10.17487/RFC4704, October 2006, <https://www.rfc-editor.org/info/rfc4704>. [RFC4833] Lear, E. and P. Eggert, "Timezone Options for DHCP", RFC 4833, DOI 10.17487/RFC4833, April 2007, <https://www.rfc-editor.org/info/rfc4833>. [RFC5908] Gayraud, R. and B. Lourdelet, "Network Time Protocol (NTP) Server Option for DHCPv6", RFC 5908, DOI 10.17487/RFC5908, June 2010, <https://www.rfc-editor.org/info/rfc5908>. [RFC5970] Huth, T., Freimann, J., Zimmer, V., and D. Thaler, "DHCPv6 Options for Network Boot", RFC 5970, DOI 10.17487/RFC5970, September 2010, <https://www.rfc-editor.org/info/rfc5970>. [RFC6334] Hankins, D. and T. Mrugalski, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Option for Dual-Stack Lite", RFC 6334, DOI 10.17487/RFC6334, August 2011, <https://www.rfc-editor.org/info/rfc6334>. [RFC6422] Lemon, T. and Q. Wu, "Relay-Supplied DHCP Options", RFC 6422, DOI 10.17487/RFC6422, December 2011, <https://www.rfc-editor.org/info/rfc6422>. [RFC6440] Zorn, G., Wu, Q., and Y. Wang, "The EAP Re-authentication Protocol (ERP) Local Domain Name DHCPv6 Option", RFC 6440, DOI 10.17487/RFC6440, December 2011, <https://www.rfc-editor.org/info/rfc6440>. [RFC6784] Sakane, S. and M. Ishiyama, "Kerberos Options for DHCPv6", RFC 6784, DOI 10.17487/RFC6784, November 2012, <https://www.rfc-editor.org/info/rfc6784>. [RFC6939] Halwasia, G., Bhandari, S., and W. Dec, "Client Link-Layer Address Option in DHCPv6", RFC 6939, DOI 10.17487/RFC6939, May 2013, <https://www.rfc-editor.org/info/rfc6939>. [RFC7078] Matsumoto, A., Fujisaki, T., and T. Chown, "Distributing Address Selection Policy Using DHCPv6", RFC 7078, DOI 10.17487/RFC7078, January 2014, <https://www.rfc-editor.org/info/rfc7078>. [RFC7083] Droms, R., "Modification to Default Values of SOL_MAX_RT and INF_MAX_RT", RFC 7083, DOI 10.17487/RFC7083, November 2013, <https://www.rfc-editor.org/info/rfc7083>. [RFC7227] Hankins, D., Mrugalski, T., Siodelski, M., Jiang, S., and S. Krishnan, "Guidelines for Creating New DHCPv6 Options", BCP 187, RFC 7227, DOI 10.17487/RFC7227, May 2014, <https://www.rfc-editor.org/info/rfc7227>. [RFC7291] Boucadair, M., Penno, R., and D. Wing, "DHCP Options for the Port Control Protocol (PCP)", RFC 7291, DOI 10.17487/RFC7291, July 2014, <https://www.rfc-editor.org/info/rfc7291>. [RFC7598] 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", RFC 7598, DOI 10.17487/RFC7598, July 2015, <https://www.rfc-editor.org/info/rfc7598>. Authors' Addresses Yong Cui Tsinghua University Beijing 100084 P.R.China Phone: +86-10-6260-3059 Email: yong@csnet1.cs.tsinghua.edu.cnHao Wang Tsinghua University Beijing 100084 P.R.China Phone: +86-10-6278-5822 Email: wangh13@mails.tsinghua.edu.cnLinhui Sun Tsinghua University Beijing 100084 P.R.China Phone: +86-10-6278-5822 Email: lh.sunlinh@gmail.com Ian Farrer Deutsche Telekom AG CTO-ATI, Landgrabenweg 151 Bonn, NRW 53227 Germany Email: ian.farrer@telekom.de Sladjana Zechlin Deutsche Telekom AG CTO-IPT, Landgrabenweg 151 Bonn, NRW 53227 Germany Email: sladjana.zechlin@telekom.de Zihao He Tsinghua University Beijing 100084 P.R.China Phone: +86-10-6278-5822 Email: hezihao9512@gmail.com