rfc9243v2.txt   rfc9243.txt 
skipping to change at line 529 skipping to change at line 529
sets. These are groups of DHCPv6 options with common sets. These are groups of DHCPv6 options with common
parameters that will be supplied to clients on request. The parameters that will be supplied to clients on request. The
'option-set-id' field is used to reference an option-set 'option-set-id' field is used to reference an option-set
elsewhere in the server's configuration. elsewhere in the server's configuration.
option-set: This holds configuration parameters for DHCPv6 option-set: This holds configuration parameters for DHCPv6
options. The initial set of applicable option definitions are options. The initial set of applicable option definitions are
defined here, and additional options that are also relevant to defined here, and additional options that are also relevant to
the relay and/or client are imported from the 'ietf- the relay and/or client are imported from the 'ietf-
dhcpv6-common' module. Where needed, other DHCPv6 option dhcpv6-common' module. Where needed, other DHCPv6 option
modules can be augmented as they are defined. modules can be augmented as they are defined. The complete
list of DHCPV6 options is located at
[IANA-DHCPV6-OPTION-CODES].
class-selector: This is provided as a location for additional class-selector: This is provided as a location for additional
implementation-specific YANG nodes for vendor-specific class implementation-specific YANG nodes for vendor-specific class
selector nodes to be augmented. See Appendix D for an example selector nodes to be augmented. See Appendix D for an example
of this. of this.
allocation-ranges: A hierarchical model is used for the allocation-ranges: A hierarchical model is used for the
allocation of addresses and prefixes. The top-level allocation of addresses and prefixes. The top-level
'allocation-ranges' container holds global configuration 'allocation-ranges' container holds global configuration
parameters. Under this, the 'allocation-range' list is used parameters. Under this, the 'allocation-range' list is used
skipping to change at line 556 skipping to change at line 558
for defining host reservations. State information about active for defining host reservations. State information about active
leases from each pool is also located here. leases from each pool is also located here.
prefix-pools: This defines pools to be used for prefix delegation prefix-pools: This defines pools to be used for prefix delegation
to clients. Static host reservations can also be configured. to clients. Static host reservations can also be configured.
As prefix delegation is not supported by all DHCPv6 server As prefix delegation is not supported by all DHCPv6 server
implementations, it is enabled by a feature statement. implementations, it is enabled by a feature statement.
Information about RPCs: Information about RPCs:
delete-address-lease: This allows the deletion of a lease for an delete-address-lease: This allows the deletion of a lease for an
individual IPv6 address from the server's lease database. individual IPv6 address from the server's lease database. Per
[BCP18], if available, a language identifier should be included
in the output message.
delete-prefix-lease: This allows the deletion of a lease for an delete-prefix-lease: This allows the deletion of a lease for an
individual IPv6 prefix from the server's lease database. individual IPv6 prefix from the server's lease database. Per
[BCP18], if available, a language identifier should be included
in the output message.
Information about notifications: Information about notifications:
address/prefix-pool-utilization-threshold-exceeded: This is address/prefix-pool-utilization-threshold-exceeded: This is
raised when the number of leased addresses or prefixes in a raised when the number of leased addresses or prefixes in a
pool exceeds the configured usage threshold. pool exceeds the configured usage threshold.
invalid-client-detected: This is raised when the server detects invalid-client-detected: This is raised when the server detects
an invalid client. A description of the error and message type an invalid client. A description of the error and message type
that has generated the notification can be included. that has generated the notification can be included.
decline-received: This is raised when a DHCPv6 Decline message is decline-received: This is raised when a DHCPv6 Decline message is
received from a client. received from a client.
non-success-code-sent: This is raised when there is a status non-success-code-sent: This is raised when there is a status
message for a failure. message for a failure. Status codes are drawn from
[IANA-DHCPV6-STATUS-CODES].
3.2. DHCPv6 Relay Tree Diagram 3.2. DHCPv6 Relay Tree Diagram
The tree diagram in Figure 2 provides an overview of the DHCPv6 relay The tree diagram in Figure 2 provides an overview of the DHCPv6 relay
module. The tree also includes the common functions module defined module. The tree also includes the common functions module defined
in Section 4.1. in Section 4.1.
The RPCs in the module are taken from requirements defined in The RPCs in the module are taken from requirements defined in
[RFC8987]. [RFC8987].
skipping to change at line 717 skipping to change at line 724
DHCPv6 relay implementations, it is enabled by this feature DHCPv6 relay implementations, it is enabled by this feature
statement where required. statement where required.
pd-leases: This contains read-only nodes for holding information pd-leases: This contains read-only nodes for holding information
about active delegated prefix leases. about active delegated prefix leases.
relay-options: This holds configuration parameters for DHCPv6 relay-options: This holds configuration parameters for DHCPv6
options that can be sent by the relay. The initial set of options that can be sent by the relay. The initial set of
applicable option definitions are defined here, and additional applicable option definitions are defined here, and additional
options that are also relevant to the server and/or client are options that are also relevant to the server and/or client are
imported from the 'ietf-dhcpv6-common' module. Where needed, imported from the 'ietf-dhcpv6-common' module. Information for
the Authentication Option (OPTION_AUTH (11)) is drawn from
[IANA-DHCPV6-AUTH-NAMESPACES] and [RFC3118]. Where needed,
other DHCPv6 option modules can be augmented as they are other DHCPv6 option modules can be augmented as they are
defined. defined. The complete list of DHCPV6 options is located at
[IANA-DHCPV6-OPTION-CODES].
Information about RPCs: Information about RPCs:
clear-prefix-entry: This allows the removal of a delegated lease clear-prefix-entry: This allows the removal of a delegated lease
entry from the relay. entry from the relay.
clear-client-prefixes: This allows the removal of all of the clear-client-prefixes: This allows the removal of all of the
delegated lease entries for a single client (referenced by delegated lease entries for a single client (referenced by
client DUID) from the relay. client DUID) from the relay. Per [BCP18], if available, a
language identifier should be included in the output message.
clear-interface-prefixes: This allows the removal of all of the clear-interface-prefixes: This allows the removal of all of the
delegated lease entries from an interface on the relay. delegated lease entries from an interface on the relay. Per
[BCP18], if available, a language identifier should be included
in the output message.
Information about notifications: Information about notifications:
topology-change: This is raised when the topology of the relay topology-change: This is raised when the topology of the relay
agent is changed, e.g., a client-facing interface is agent is changed, e.g., a client-facing interface is
reconfigured. reconfigured.
3.3. DHCPv6 Client Tree Diagram 3.3. DHCPv6 Client Tree Diagram
The tree diagram in Figure 3 provides an overview of the DHCPv6 The tree diagram in Figure 3 provides an overview of the DHCPv6
client module. The tree also includes the common functions module client module. The tree also includes the common functions module
skipping to change at line 912 skipping to change at line 925
be configured per a DHCP-enabled interface using the be configured per a DHCP-enabled interface using the
'interface-duid' leaf; otherwise, there is a global 'client- 'interface-duid' leaf; otherwise, there is a global 'client-
duid' leaf. duid' leaf.
client-configured-options: This holds configuration parameters client-configured-options: This holds configuration parameters
for DHCPv6 options that can be sent by the client. The initial for DHCPv6 options that can be sent by the client. The initial
set of applicable option definitions are defined here, and set of applicable option definitions are defined here, and
additional options that are also relevant to the relay and/or additional options that are also relevant to the relay and/or
server are imported from the 'ietf-dhcpv6-common' module. server are imported from the 'ietf-dhcpv6-common' module.
Where needed, other DHCPv6 option modules can be augmented as Where needed, other DHCPv6 option modules can be augmented as
they are defined. they are defined. The complete list of DHCPV6 options is
located at [IANA-DHCPV6-OPTION-CODES].
ia-na, ia-ta, ia-pd: These contain configuration nodes relevant ia-na, ia-ta, ia-pd: These contain configuration nodes relevant
for requesting one or more of each of the lease types. Read- for requesting one or more of each of the lease types. Read-
only nodes related to the active leases for each type are also only nodes related to the active leases for each type are also
located here. As these lease types may not be supported by all located here, drawing the status codes from
DHCPv6 client implementations, they are enabled via individual [IANA-DHCPV6-STATUS-CODES]. As these lease types may not be
feature statements. Stateless DHCP (Section 6.1 of [RFC8415]) supported by all DHCPv6 client implementations, they are
is configured when all address and prefix features are enabled via individual feature statements. Stateless DHCP
disabled. (Section 6.1 of [RFC8415]) is configured when all address and
prefix features are disabled.
Information about notifications: Information about notifications:
invalid-ia-detected: This is raised when the identity association invalid-ia-detected: This is raised when the identity association
of the client can be proved to be invalid. Possible conditions of the client can be proved to be invalid. Possible conditions
include duplicated address, illegal address, etc. include duplicated address, illegal address, etc.
retransmission-failed: This is raised when the retransmission retransmission-failed: This is raised when the retransmission
mechanism defined in [RFC8415] has failed. mechanism defined in [RFC8415] has failed.
4. DHCPv6 YANG Modules 4. DHCPv6 YANG Modules
skipping to change at line 1413 skipping to change at line 1428
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC 9243 This version of this YANG module is part of RFC 9243
(https://www.rfc-editor.org/info/rfc9243); see the RFC itself (https://www.rfc-editor.org/info/rfc9243); see the RFC itself
for full legal notices."; for full legal notices.";
revision 2022-05-04 { revision 2022-05-04 {
description description
"Initial revision."; "Initial revision.";
reference reference
"9243: A YANG Data Model for DHCPv6 Configuration"; "RFC 9243: A YANG Data Model for DHCPv6 Configuration";
} }
/* /*
* Features * Features
*/ */
feature na-assignment { feature na-assignment {
description description
"Denotes that the server implements DHCPv6 non-temporary "Denotes that the server implements DHCPv6 non-temporary
address assignment."; address assignment.";
skipping to change at line 2410 skipping to change at line 2425
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC 9243 This version of this YANG module is part of RFC 9243
(https://www.rfc-editor.org/info/rfc9243); see the RFC itself (https://www.rfc-editor.org/info/rfc9243); see the RFC itself
for full legal notices."; for full legal notices.";
revision 2022-05-04 { revision 2022-05-04 {
description description
"Initial revision."; "Initial revision.";
reference reference
"9243: A YANG Data Model for DHCPv6 Configuration"; "RFC 9243: A YANG Data Model for DHCPv6 Configuration";
} }
/* /*
* Features * Features
*/ */
feature prefix-delegation { feature prefix-delegation {
description description
"Enable if the relay functions as a delegating router for "Enable if the relay functions as a delegating router for
DHCPv6 prefix delegation."; DHCPv6 prefix delegation.";
skipping to change at line 2902 skipping to change at line 2917
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC 9243 This version of this YANG module is part of RFC 9243
(https://www.rfc-editor.org/info/rfc9243); see the RFC itself (https://www.rfc-editor.org/info/rfc9243); see the RFC itself
for full legal notices."; for full legal notices.";
revision 2022-05-04 { revision 2022-05-04 {
description description
"Initial revision."; "Initial revision.";
reference reference
"9243: A YANG Data Model for DHCPv6 Configuration"; "RFC 9243: A YANG Data Model for DHCPv6 Configuration";
} }
/* /*
* Features * Features
*/ */
feature non-temp-addr { feature non-temp-addr {
description description
"Denotes that the client supports DHCPv6 non-temporary address "Denotes that the client supports DHCPv6 non-temporary address
allocations."; allocations.";
skipping to change at line 3729 skipping to change at line 3744
name: ietf-dhcpv6-common name: ietf-dhcpv6-common
namespace: urn:ietf:params:xml:ns:yang:ietf-dhcpv6-common namespace: urn:ietf:params:xml:ns:yang:ietf-dhcpv6-common
maintained by IANA: N maintained by IANA: N
prefix: dhc6 prefix: dhc6
reference: RFC 9243 reference: RFC 9243
7. References 7. References
7.1. Normative References 7.1. Normative References
[IANA-DHCP-AUTH-NAMESPACES] [BCP18] Alvestrand, H., "IETF Policy on Character Sets and
Languages", BCP 18, RFC 2277, January 1998.
<https://www.rfc-editor.org/info/bcp18>
[IANA-DHCPV6-AUTH-NAMESPACES]
IANA, "Dynamic Host Configuration Protocol (DHCP) IANA, "Dynamic Host Configuration Protocol (DHCP)
Authentication Option Name Spaces", Authentication Option Name Spaces",
<https://www.iana.org/assignments/auth-namespaces>. <https://www.iana.org/assignments/auth-namespaces>.
[IANA-DHCPV6-OPTION-CODES] [IANA-DHCPV6-OPTION-CODES]
IANA, "Option Codes", IANA, "Option Codes",
<https://www.iana.org/assignments/dhcpv6-parameters>. <https://www.iana.org/assignments/dhcpv6-parameters>.
[IANA-DHCPV6-STATUS-CODES] [IANA-DHCPV6-STATUS-CODES]
IANA, "DHCPv6 Status Codes", IANA, "DHCPv6 Status Codes",
skipping to change at line 3754 skipping to change at line 3774
<https://www.iana.org/assignments/arp-parameters>. <https://www.iana.org/assignments/arp-parameters>.
[IANA-PEN] IANA, "Private Enterprise Numbers", [IANA-PEN] IANA, "Private Enterprise Numbers",
<https://www.iana.org/assignments/enterprise-numbers>. <https://www.iana.org/assignments/enterprise-numbers>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC2277] Alvestrand, H., "IETF Policy on Character Sets and
Languages", BCP 18, RFC 2277, DOI 10.17487/RFC2277,
January 1998, <https://www.rfc-editor.org/info/rfc2277>.
[RFC3118] Droms, R., Ed. and W. Arbaugh, Ed., "Authentication for [RFC3118] Droms, R., Ed. and W. Arbaugh, Ed., "Authentication for
DHCP Messages", RFC 3118, DOI 10.17487/RFC3118, June 2001, DHCP Messages", RFC 3118, DOI 10.17487/RFC3118, June 2001,
<https://www.rfc-editor.org/info/rfc3118>. <https://www.rfc-editor.org/info/rfc3118>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
skipping to change at line 4107 skipping to change at line 4123
* enabling the DHCP client function globally and for the relevant * enabling the DHCP client function globally and for the relevant
interface, interface,
* referencing the interface that the client configuration is * referencing the interface that the client configuration is
relevant for via an interface-ref to the ietf-interfaces module, relevant for via an interface-ref to the ietf-interfaces module,
* setting the DUID for the DHCPv6-enabled interface, * setting the DUID for the DHCPv6-enabled interface,
* configuring a list of option codes that will be requested by the * configuring a list of option codes that will be requested by the
client in its Option Request Option (OPTION_ORO (5)), client in its Option Request Option (OPTION_ORO (6)),
* configuring a single instance of the Vendor-specific Information * configuring a single instance of the Vendor-specific Information
Option (OPTION_VENDOR_OPTS (17)) with a single sub-option data Option (OPTION_VENDOR_OPTS (17)) with a single sub-option data
item, item,
* requesting a non-temporary IPv6 address (IA_NA) with an identity * requesting a non-temporary IPv6 address (IA_NA) with an identity
association interface identifier of 1, and association interface identifier of 1, and
* requesting an IPv6 delegated prefix address (IA_PD) with an * requesting an IPv6 delegated prefix address (IA_PD) with an
identity association interface identifier of 2. identity association interface identifier of 2.
skipping to change at line 4254 skipping to change at line 4270
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC 9243 This version of this YANG module is part of RFC 9243
(https://www.rfc-editor.org/info/rfc9243); see the RFC itself (https://www.rfc-editor.org/info/rfc9243); see the RFC itself
for full legal notices."; for full legal notices.";
revision 2022-05-04 { revision 2022-05-04 {
description description
"Initial revision."; "Initial revision.";
reference reference
"9243: A YANG Data Model for DHCPv6 Configuration"; "RFC 9243: A YANG Data Model for DHCPv6 Configuration";
} }
/* /*
* Groupings * Groupings
*/ */
grouping sip-server-domain-name-list-option-group { grouping sip-server-domain-name-list-option-group {
description description
"OPTION_SIP_SERVER_D (21) SIP Servers Domain-Name List."; "OPTION_SIP_SERVER_D (21) SIP Servers Domain-Name List.";
reference "RFC 3319: Dynamic Host Configuration Protocol reference "RFC 3319: Dynamic Host Configuration Protocol
skipping to change at line 4434 skipping to change at line 4450
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC 9243 This version of this YANG module is part of RFC 9243
(https://www.rfc-editor.org/info/rfc9243); see the RFC itself (https://www.rfc-editor.org/info/rfc9243); see the RFC itself
for full legal notices."; for full legal notices.";
revision 2022-05-04 { revision 2022-05-04 {
description description
"Initial revision."; "Initial revision.";
reference reference
"9243: A YANG Data Model for DHCPv6 Configuration"; "RFC 9243: A YANG Data Model for DHCPv6 Configuration";
} }
/* /*
* Groupings * Groupings
*/ */
grouping config { grouping config {
description description
"Parameters necessary for the configuration of a DHCPv6 "Parameters necessary for the configuration of a DHCPv6
server."; server.";
skipping to change at line 4721 skipping to change at line 4737
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC 9243 This version of this YANG module is part of RFC 9243
(https://www.rfc-editor.org/info/rfc9243); see the RFC itself (https://www.rfc-editor.org/info/rfc9243); see the RFC itself
for full legal notices."; for full legal notices.";
revision 2022-05-04 { revision 2022-05-04 {
description description
"Initial revision."; "Initial revision.";
reference reference
"9243: A YANG Data Model for DHCPv6 Configuration"; "RFC 9243: A YANG Data Model for DHCPv6 Configuration";
} }
/* /*
* Groupings * Groupings
*/ */
grouping client-class-id { grouping client-class-id {
description description
"Definitions of client message classification for "Definitions of client message classification for
authorization and assignment purposes."; authorization and assignment purposes.";
 End of changes. 19 change blocks. 
26 lines changed or deleted 42 lines changed or added

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

mirror server hosted at Truenetwork, Russian Federation.