--- 1/draft-ietf-dhc-dhcpv6-yang-20.txt 2021-06-14 08:13:45.737952018 -0700 +++ 2/draft-ietf-dhc-dhcpv6-yang-21.txt 2021-06-14 08:13:45.913956422 -0700 @@ -1,18 +1,18 @@ DHC Working Group I. Farrer, Ed. Internet-Draft Deutsche Telekom AG -Intended status: Standards Track 1 June 2021 -Expires: 3 December 2021 +Intended status: Standards Track 14 June 2021 +Expires: 16 December 2021 YANG Data Model for DHCPv6 Configuration - draft-ietf-dhc-dhcpv6-yang-20 + draft-ietf-dhc-dhcpv6-yang-21 Abstract This document describes YANG data modules for the configuration and management of DHCPv6 (Dynamic Host Configuration Protocol for IPv6) servers, relays, and clients. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", @@ -29,21 +29,21 @@ 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 on 3 December 2021. + This Internet-Draft will expire on 16 December 2021. Copyright Notice Copyright (c) 2021 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. @@ -63,26 +63,26 @@ 2. DHCPv6 Tree Diagrams . . . . . . . . . . . . . . . . . . . . 6 2.1. DHCPv6 Server Tree Diagram . . . . . . . . . . . . . . . 6 2.2. DHCPv6 Relay Tree Diagram . . . . . . . . . . . . . . . . 13 2.3. DHCPv6 Client Tree Diagram . . . . . . . . . . . . . . . 16 3. DHCPv6 YANG Modules . . . . . . . . . . . . . . . . . . . . . 19 3.1. DHCPv6 Server YANG Module . . . . . . . . . . . . . . . . 19 3.2. DHCPv6 Relay YANG Module . . . . . . . . . . . . . . . . 39 3.3. DHCPv6 Client YANG Module . . . . . . . . . . . . . . . . 48 3.4. DHCPv6 Common YANG Module . . . . . . . . . . . . . . . . 63 4. Security Considerations . . . . . . . . . . . . . . . . . . . 71 - 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 72 - 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 73 - 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 73 + 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 73 + 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 74 + 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 74 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 74 8.1. Normative References . . . . . . . . . . . . . . . . . . 74 - 8.2. Informative References . . . . . . . . . . . . . . . . . 76 + 8.2. Informative References . . . . . . . . . . . . . . . . . 77 Appendix A. Data Tree Examples . . . . . . . . . . . . . . . . . 77 A.1. DHCPv6 Server Configuration Example . . . . . . . . . . . 77 A.2. DHCPv6 Relay Configuration Example . . . . . . . . . . . 81 A.3. DHCPv6 Client Configuration Examples . . . . . . . . . . 82 Appendix B. Example of Augmenting Additional DHCPv6 Option Definitions . . . . . . . . . . . . . . . . . . . . . . . 85 Appendix C. Example Vendor Specific Server Configuration Module . . . . . . . . . . . . . . . . . . . . . . . . . 88 Appendix D. Example definition of class-selector configuration . . . . . . . . . . . . . . . . . . . . . . 95 @@ -757,21 +757,21 @@ +--rw ia-ta* [ia-id] | +--rw ia-id uint32 | +--rw ia-ta-options | +--ro lease-state | +--ro ia-ta-address? inet:ipv6-address | +--ro preferred-lifetime? dhc6:timer-seconds32 | +--ro valid-lifetime? dhc6:timer-seconds32 | +--ro allocation-time? yang:date-and-time | +--ro last-renew-rebind? yang:date-and-time | +--ro server-duid? dhc6:duid - +--rw ia-pd* [ia-id] + +--rw ia-pd* [ia-id] {prefix-delegation}? | +--rw ia-id uint32 | +--rw ia-pd-options | +--ro lease-state | +--ro ia-pd-prefix? inet:ipv6-prefix | +--ro preferred-lifetime? dhc6:timer-seconds32 | +--ro valid-lifetime? dhc6:timer-seconds32 | +--ro lease-t1? dhc6:timer-seconds32 | +--ro lease-t2? dhc6:timer-seconds32 | +--ro allocation-time? yang:date-and-time | +--ro last-renew-rebind? yang:date-and-time @@ -806,20 +806,21 @@ | +--ro server-duid dhc6:duid +---n server-duid-changed +--ro new-server-duid dhc6:duid +--ro previous-server-duid dhc6:duid +--ro lease-ia-na? | -> /dhcpv6-client/client-if/ia-na/ia-id +--ro lease-ia-ta? | -> /dhcpv6-client/client-if/ia-ta/ia-id +--ro lease-ia-pd? -> /dhcpv6-client/client-if/ia-pd/ia-id + {prefix-delegation}? Figure 3: DHCPv6 Client Data Module Structure Descriptions of important nodes: * enabled: Globally enables/disables all DHCPv6 client functions. * dhcpv6-client: This container holds the client's DHCPv6 specific configuration. @@ -844,38 +845,39 @@ * client-configured-options: Holds configuration parameters for DHCPv6 options which can be sent by the client. The initial set of applicable option definitions are defined here and additional options that are also relevant to the relay and/or server are imported from the 'ietf-dhcpv6-common' module. Where needed, other DHCPv6 option modules can be augmented as they are defined. * ia-na, ia-ta, ia-pd: Contains configuration nodes relevant for requesting one or more of each of the lease types. Read-only nodes related to the active leases for each type are also located - here. + here. As prefix delegation is not supported by all DHCPv6 client + implementations, it is enabled with a feature statement. Information about notifications: * invalid-ia-detected: Raised when the identity association of the client can be proved to be invalid. Possible conditions include: duplicated address, illegal address, etc. * retransmission-failed: Raised when the retransmission mechanism defined in [RFC8415] has failed. 3. DHCPv6 YANG Modules 3.1. DHCPv6 Server YANG Module This module imports typedefs from [RFC6991], [RFC8343]. - file "ietf-dhcpv6-server@2021-06-01.yang" + file "ietf-dhcpv6-server@2021-06-14.yang" module ietf-dhcpv6-server { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-dhcpv6-server"; prefix "dhc6-srv"; import ietf-inet-types { prefix inet; reference "RFC 6991: Common YANG Data Types"; @@ -922,24 +925,25 @@ Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; - revision 2017-11-24 { + revision 2021-06-14 { description - "First version of the separated server specific YANG model."; - reference "I-D: draft-ietf-dhc-dhcpv6-yang"; + "Initial Revision."; + reference + "XXXX: YANG Data Model for DHCPv6 Configuration"; } /* * Features */ feature prefix-delegation { description "Denotes that the server implements DHCPv6 prefix delegation."; @@ -1801,32 +1803,32 @@ description "IPv6 prefix of an active lease that will be deleted from the server."; } } output { leaf return-message { type string; description "Response message from the server."; - } } + } } 3.2. DHCPv6 Relay YANG Module This module imports typedefs from [RFC6991], [RFC8343]. - file "ietf-dhcpv6-relay@2021-06-01.yang" + file "ietf-dhcpv6-relay@2021-06-14.yang" module ietf-dhcpv6-relay { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-dhcpv6-relay"; prefix "dhc6-rly"; import ietf-inet-types { prefix inet; reference "RFC 6991: Common YANG Data Types"; @@ -1879,25 +1881,25 @@ Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; - revision 2017-11-24 { + revision 2021-06-14 { description - "First version of the separated relay specific YANG model."; + "Initial Revision."; reference - "I-D: draft-ietf-dhc-dhcpv6-yang"; + "XXXX: YANG Data Model for DHCPv6 Configuration"; } /* * Features */ feature prefix-delegation { description "Enable if the relay functions as a delegating router for DHCPv6 prefix delegation."; @@ -2280,26 +2284,26 @@ } } } } 3.3. DHCPv6 Client YANG Module This module imports typedefs from [RFC6991], [RFC8343]. - file "ietf-dhcpv6-client@2021-06-01.yang" + file "ietf-dhcpv6-client@2021-06-14.yang" module ietf-dhcpv6-client { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-dhcpv6-client"; - prefix "dhcpv6-clnt"; + prefix "dhc6-clnt"; import ietf-inet-types { prefix inet; reference "RFC 6991: Common YANG Data Types"; } import ietf-yang-types { prefix yang; reference @@ -2348,24 +2352,37 @@ Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; - revision 2017-11-24 { + revision 2021-06-14 { description - "First version of the separated client specific YANG model."; - reference "I-D: draft-ietf-dhc-dhcpv6-yang"; + "Initial Revision."; + reference + "XXXX: YANG Data Model for DHCPv6 Configuration"; + } + + /* + * Features + */ + + feature prefix-delegation { + description + "Denotes that the client implements DHCPv6 prefix + delegation."; + reference "RFC 8415: Dynamic Host Configuration Protocol for + IPv6 (DHCPv6), Section 6.3"; } /* * Groupings */ grouping message-statistics { description "Counters for DHCPv6 messages."; leaf solicit-count { @@ -2710,20 +2728,21 @@ address."; } leaf server-duid { type dhc6:duid; description "DUID of the leasing server."; } } } list ia-pd { + if-feature prefix-delegation; key ia-id; description "Configuration relevant for an IA_PD (Identity Association for Prefix Delegation)."; reference "RFC 8415: Dynamic Host Configuration Protocol for IPv6 (DHCPv6), Section 13.3"; leaf ia-id { type uint32; description "The unique identifier for this IA_PD."; @@ -2960,35 +2981,36 @@ "Reference to the IA_NA lease."; } leaf lease-ia-ta { type leafref { path "/dhcpv6-client/client-if/ia-ta/ia-id"; } description "Reference to the IA_TA lease."; } leaf lease-ia-pd { + if-feature prefix-delegation; type leafref { path "/dhcpv6-client/client-if/ia-pd/ia-id"; } description "Reference to the IA_PD lease."; } } } 3.4. DHCPv6 Common YANG Module This module imports typedefs from [RFC6991]. - file "ietf-dhcpv6-common@2021-06-01.yang" + file "ietf-dhcpv6-common@2021-06-14.yang" module ietf-dhcpv6-common { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-dhcpv6-common"; prefix "dhc6"; organization "IETF DHC (Dynamic Host Configuration) Working Group"; contact @@ -3018,34 +3040,34 @@ Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; - revision 2018-01-30 { + revision 2021-06-14 { description - "Initial revision"; - reference "I-D: draft-ietf-dhc-dhcpv6-yang"; + "Initial Revision."; + reference + "XXXX: YANG Data Model for DHCPv6 Configuration"; } typedef threshold { type uint8 { range 1..100; } description "Threshold value in percent."; } - typedef timer-seconds32 { type uint32; units "seconds"; description "Timer value type, in seconds (32-bit range)."; } typedef duid-base { type string { pattern '([0-9a-fA-F]{2}){3,130}'; @@ -3047,124 +3069,125 @@ } typedef duid-base { type string { pattern '([0-9a-fA-F]{2}){3,130}'; } description "Each DHCP server and client has a DUID (DHCP Unique Identifier). The DUID consists of a two-octet type field and an arbitrary length (1-128 octets) content - field. The duid-base type provides the + field. The duid-base type is used by other duid types with + additional pattern constraints. + Currently, there are four defined types of DUIDs in RFC 8415 and RFC 6355 - DUID-LLT, DUID-EN, DUID-LL and DUID-UUID. DUID-unstructured represents DUIDs which do not follow any of the defined formats."; reference "RFC 8415: Dynamic Host Configuration Protocol for IPv6 (DHCPv6), Section 11 RFC 6355: Definition of the UUID-Based DHCPv6 Unique Identifier (DUID-UUID), Section 4"; } typedef duid-llt { type duid-base { pattern '0001' + '[0-9a-fA-F]{12,}'; } description "DUID type 1, based on Link-Layer Address Plus Time - (DUID-LLT). Constructed with a 2-byte hardware type assigned - by IANA, 4-bytes containing the time the DUID is generated + (DUID-LLT). Constructed with a 2-octet hardware type assigned + by IANA, 4-octet containing the time the DUID is generated (represented in seconds since midnight (UTC), January 1, 2000, modulo 2^32), and a link-layer address. The address is encoded without separator characters. For example: - +------+----+----------+--------------+ - | 0001 | 06 | 28490058 | 00005E005300 | - +------+----+----------+--------------+ + +------+------+----------+--------------+ + | 0001 | 0006 | 28490058 | 00005E005300 | + +------+------+----------+--------------+ - This example includes the 2-octet DUID type of 1 (0001), the - hardware type is 06 (IEEE Hardware Types) the creation - time is 0x284900580 (constructed as described above). Finally, - the link-layer address is 00005E005300 (EUI-48 address + This example includes the 2-octet DUID type of 1 (0x01), the + hardware type is 0x06 (IEEE Hardware Types) the creation + time is 0x028490058 (constructed as described above). Finally, + the link-layer address is 0x5E005300 (EUI-48 address 00-00-5E-00-53-00)"; reference "RFC 8415: Dynamic Host Configuration Protocol for IPv6 (DHCPv6), Section 11.2 IANA 'Hardware Types' registry. "; } typedef duid-en { type duid-base { pattern '0002' + '[0-9a-fA-F]{4,}'; } description "DUID type 2, assigned by vendor based on Enterprise Number (DUID-EN). This DUID consists of the 4-octet vendor's registered Private Enterprise Number as maintained by IANA followed by a unique identifier assigned by the vendor. For example: - +------+------+------------------+ - | 0002 | 0009 | 0CC084D303000912 | - +------+------+------------------+ - - This example includes the 2-octet DUID type of 2 (0002), - 4-octets for the Enterprise Number (0009), followed by 8-octets + +------+----------+------------------+ + | 0002 | 00000009 | 0CC084D303000912 | + +------+----------+------------------+ - of identifier data (0x0CC084D303000912)."; + This example includes the 2-octet DUID type of 2 (0x02), + 4-octets for the Enterprise Number (0x09), followed by + 8-octets of identifier data (0x0CC084D303000912)."; reference "RFC 8415: Dynamic Host Configuration Protocol for IPv6 (DHCPv6), Section 11.3 IANA 'Private Enterprise Numbers' registry. "; } typedef duid-ll { type duid-base { pattern '0003' + '([0-9a-fA-F]){4,}'; } description "DUID type 3, based on Link-Layer Address (DUID-LL). - Constructed with a 2-byte hardware type assigned + Constructed with a 2-octet hardware type assigned by IANA, and a link-layer address. The address is encoded without separator characters. For example: - +------+----+--------------+ - | 0003 | 06 | 00005E005300 | - +------+----+--------------+ + +------+------+--------------+ + | 0003 | 0006 | 00005E005300 | + +------+------+--------------+ + This example includes the 2-octet DUID type of 3 (0x03), the + hardware type is 0x06 (IEEE Hardware Types), and the link-layer - This example includes the 2-octet DUID type of 3 (0003), the - hardware type is 06 (IEEE Hardware Types), and the link-layer - address is 00005E005300 (EUI-48 address 00-00-5E-00-53-00)"; + address is 0x5E005300 (EUI-48 address 00-00-5E-00-53-00)"; reference "RFC 8415: Dynamic Host Configuration Protocol for IPv6 (DHCPv6), Section 11.4 IANA 'Hardware Types' registry. "; } typedef duid-uuid { type duid-base { pattern '0004' + '[0-9a-fA-F]{32}'; } description "DUID type 4, based on Universally Unique Identifier (DUID-UUID). This type of DUID consists of 16 octets containing a 128-bit UUID. For example: +------+----------------------------------+ | 0004 | 9f03b182705747e38a1e422910078642 | +------+----------------------------------+ - This example includes the 2-octet DUID type of 4 (0004), and + This example includes the 2-octet DUID type of 4 (0x04), and the UUID 9f03b182-7057-47e3-8a1e-422910078642."; reference "RFC 8415: Dynamic Host Configuration Protocol for IPv6 (DHCPv6), Section 11.5 RFC 6355: Definition of the UUID-Based DHCPv6 Unique Identifier (DUID-UUID)"; } typedef duid-unstructured { type duid-base { @@ -3174,21 +3197,21 @@ } description "Used for DUIDs following any other formats than DUID types 1-4. For example: +----------------------------------+ | 7b6a164d325946539dc540fb539bc430 | +----------------------------------+ Here, an arbitrary 16-octet value is used. The only constraint - placed on this is that the first 2-octects are not 0001-0004 + placed on this is that the first 2-octects are not 0x01-0x04 to avoid collision with the other defined DUID types (duid-llt, duid-en, duid-ll, or duid-uuid)."; reference "RFC 8415: Dynamic Host Configuration Protocol for IPv6 (DHCPv6), Section 11"; } typedef duid { type union { type duid-llt; type duid-en; @@ -3438,36 +3461,36 @@ URI: urn:ietf:params:xml:ns:yang:ietf-dhcpv6-common Registrant Contact: The IESG. XML: N/A; the requested URI is an XML namespace. This document registers the following YANG modules in the "YANG Module Names" registry [RFC6020]. name: ietf-dhcpv6-server namespace: urn:ietf:params:xml:ns:yang:ietf-dhcpv6-server - prefix: dhcpv6-server + prefix: dhc6-srv reference: RFC XXXX YANG Data Model for DHCPv6 Configuration name: ietf-dhcpv6-relay namespace: urn:ietf:params:xml:ns:yang:ietf-dhcpv6-relay - prefix: dhcpv6-client + prefix: dhc6-rly reference: RFC XXXX YANG Data Model for DHCPv6 Configuration name: ietf-dhcpv6-client namespace: urn:ietf:params:xml:ns:yang:ietf-dhcpv6-client - prefix: dhcpv6-relay + prefix: dhc6-clnt reference: RFC XXXX YANG Data Model for DHCPv6 Configuration name: ietf-dhcpv6-common namespace: urn:ietf:params:xml:ns:yang:ietf-dhcpv6-common - prefix: dhcpv6-common + prefix: dhc6 reference: RFC XXXX YANG Data Model for DHCPv6 Configuration 6. Acknowledgments The authors would like to thank Qi Sun, Lishan Li, Hao Wang, Tomek Mrugalski, Marcin Siodelski, Bernie Volz, Ted Lemon, Bing Liu, Tom Petch, and Acee Lindem for their valuable comments and contributions to this work. 7. Contributors @@ -3702,21 +3725,22 @@ Figure 5: Host Reservation Configuration Example XML The following example shows configuration for a network range and pool to be used for delegating prefixes to clients. In this example, each client will receive a /56 prefix. The 'max-pd-space-utiliation' is set to 80 so that a 'prefix-pool- - utilization-threshold-exceeded' notification will be raised. + utilization-threshold-exceeded' notification will be raised if the + number of prefix allocations exceeds this. 1 prefix-pool-example 2001:db8::/32 54000 7200 32400 @@ -3844,24 +3868,24 @@ * Sets the client's DUID. * Configures a list of option codes that will be requested by the client in its Option Request Option (OPTION_ORO (5)). * Configures a single instance of the Vendor-specific Information Option (OPTION_VENDOR_OPTS (17)) with a single sub-option data item. * Requests a non-temporary IPv6 address (IA_NA) with an identity - association interface identifier of 00000001. + association interface identifier of 1. * Requests an IPv6 delegated prefix address (IA_PD) with an identity - association interface identifier of 00000002. + association interface identifier of 2. eth0 ianaift:ethernetCsmacd DHCPv6 Relay Interface true @@ -3876,31 +3900,31 @@ 17 23 24 82 9 - 01 + 1 abcd1234 - 00000001 + 1 - 00000002 + 2 Figure 9: Basic Server Configuration Example XML Appendix B. Example of Augmenting Additional DHCPv6 Option Definitions The following section provides a example of how the DHCPv6 option definitions can be extended to include additional options. It is @@ -3974,24 +3998,25 @@ Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; - revision 2019-10-18 { + revision 2021-06-14 { description - "Initial version."; - reference "I-D: draft-ietf-dhc-dhcpv6-yang"; + "Initial Revision."; + reference + "XXXX: YANG Data Model for DHCPv6 Configuration"; } /* * Groupings */ grouping sip-server-domain-name-list-option-group { description "OPTION_SIP_SERVER_D (21) SIP Servers Domain-Name List"; reference "RFC 3319: Dynamic Host Configuration Protocol @@ -4036,24 +4061,24 @@ leaf sip-serv-id { type uint8; description "SIP server list entry identifier."; } leaf sip-serv-addr { type inet:ipv6-address; description "SIP server IPv6 address."; } - } } } + } /* * Augmentations */ augment "/dhc6-srv:dhcpv6-server/dhc6-srv:option-sets/" + "dhc6-srv:option-set" { description "Augment the option definition groupings to the server module."; @@ -4143,24 +4168,25 @@ Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; - revision 2019-06-04 { + revision 2021-06-14 { description - "Initial revision."; - reference "I-D: draft-ietf-dhc-dhcpv6-yang"; + "Initial Revision."; + reference + "XXXX: YANG Data Model for DHCPv6 Configuration"; } /* * Groupings */ grouping config { description "Parameters necessary for the configuration of a DHCPv6 server"; @@ -4466,24 +4492,25 @@ Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; - revision 2019-06-13 { + revision 2021-06-14 { description - "Initial version."; - reference "I-D: draft-ietf-dhc-dhcpv6-yang"; + "Initial Revision."; + reference + "XXXX: YANG Data Model for DHCPv6 Configuration"; } /* * Groupings */ grouping client-class-id { description "Definitions of client message classification for authorization and assignment purposes."; @@ -4658,23 +4684,23 @@ case client-duid-id { description "Client class selection based on the value of the received client DUID."; leaf duid { type dhc6:duid; description "Client DUID."; } } - } } + } /* * Augmentations */ augment "/dhc6-srv:dhcpv6-server/dhc6-srv:class-selector" { description "Augment class selector functions to the DHCPv6 server module."; container client-classes {