draft-ietf-dhc-dhcpv6-yang-13.txt   draft-ietf-dhc-dhcpv6-yang-14.txt 
DHC Working Group Y. Cui DHC Working Group Y. Cui
Internet-Draft L. Sun Internet-Draft L. Sun
Intended status: Standards Track Tsinghua University Intended status: Standards Track Tsinghua University
Expires: 13 June 2021 I.F. Farrer Expires: 17 June 2021 I.F. Farrer
S.Z. Zechlin S.Z. Zechlin
Deutsche Telekom AG Deutsche Telekom AG
Z. He Z. He
Tsinghua University Tsinghua University
M.N. Nowikowski M.N. Nowikowski
Internet Systems Consortium Internet Systems Consortium
10 December 2020 14 December 2020
YANG Data Model for DHCPv6 Configuration YANG Data Model for DHCPv6 Configuration
draft-ietf-dhc-dhcpv6-yang-13 draft-ietf-dhc-dhcpv6-yang-14
Abstract Abstract
This document describes YANG data modules for the configuration and This document describes YANG data modules for the configuration and
management of DHCPv6 servers, relays, and clients. management of DHCPv6 servers, relays, and clients.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
skipping to change at page 1, line 46 skipping to change at page 1, line 46
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on 13 June 2021. This Internet-Draft will expire on 17 June 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 50, line 26 skipping to change at page 50, line 26
<CODE ENDS> <CODE ENDS>
3.4. RFC8415 Server Options YANG Module 3.4. RFC8415 Server Options YANG Module
This module imports typedefs from [RFC6991]. This module imports typedefs from [RFC6991].
<CODE BEGINS> file "ietf-dhcpv6-options-rfc8415-server.yang" <CODE BEGINS> file "ietf-dhcpv6-options-rfc8415-server.yang"
module ietf-dhcpv6-options-rfc8415-server { module ietf-dhcpv6-options-rfc8415-server {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-dhcpv6-options-rfc8415- namespace "urn:ietf:params:xml:ns:yang:" +
server"; "ietf-dhcpv6-options-rfc8415-server";
prefix "rfc8415-srv"; prefix "rfc8415-srv";
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
reference reference
"RFC 6991: Common YANG Data Types"; "RFC 6991: Common YANG Data Types";
} }
import ietf-dhcpv6-common { import ietf-dhcpv6-common {
prefix dhcpv6-common; prefix dhcpv6-common;
skipping to change at page 57, line 34 skipping to change at page 57, line 34
<CODE ENDS> <CODE ENDS>
3.5. RFC8415 Relay Options YANG Module 3.5. RFC8415 Relay Options YANG Module
This module imports typedefs from [RFC6991]. This module imports typedefs from [RFC6991].
<CODE BEGINS> file "ietf-dhcpv6-options-rfc8415-server.yang" <CODE BEGINS> file "ietf-dhcpv6-options-rfc8415-server.yang"
module ietf-dhcpv6-options-rfc8415-server { module ietf-dhcpv6-options-rfc8415-server {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-dhcpv6-options-rfc8415- namespace "urn:ietf:params:xml:ns:yang:" +
server"; "ietf-dhcpv6-options-rfc8415-server";
prefix "rfc8415-srv"; prefix "rfc8415-srv";
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
reference reference
"RFC 6991: Common YANG Data Types"; "RFC 6991: Common YANG Data Types";
} }
import ietf-dhcpv6-common { import ietf-dhcpv6-common {
prefix dhcpv6-common; prefix dhcpv6-common;
skipping to change at page 64, line 41 skipping to change at page 64, line 41
<CODE ENDS> <CODE ENDS>
3.6. RFC8415 Client Options YANG Module 3.6. RFC8415 Client Options YANG Module
This module imports typedefs from [RFC6991]. This module imports typedefs from [RFC6991].
<CODE BEGINS> file "ietf-dhcpv6-options-rfc8415-client.yang" <CODE BEGINS> file "ietf-dhcpv6-options-rfc8415-client.yang"
module ietf-dhcpv6-options-rfc8415-client { module ietf-dhcpv6-options-rfc8415-client {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-dhcpv6-options-rfc8415- namespace "urn:ietf:params:xml:ns:yang:" +
client"; "ietf-dhcpv6-options-rfc8415-client";
prefix "rfc8415-cli"; prefix "rfc8415-cli";
import ietf-dhcpv6-client { import ietf-dhcpv6-client {
prefix dhcpv6-client; prefix dhcpv6-client;
reference reference
"To be updated on publication"; "To be updated on publication";
} }
organization "DHC WG"; organization "DHC WG";
contact contact
skipping to change at page 80, line 9 skipping to change at page 80, line 9
Below the groupings for option definitions, augment statements are Below the groupings for option definitions, augment statements are
used to add the option definitions for use in the relevant DHCP used to add the option definitions for use in the relevant DHCP
element's module (server, relay and/or client). If an option is element's module (server, relay and/or client). If an option is
relevant to more than one element type, then an augment statement for relevant to more than one element type, then an augment statement for
each element is used. each element is used.
<CODE BEGINS> file "ietf-example-dhcpv6-options-rfc3319-server.yang" <CODE BEGINS> file "ietf-example-dhcpv6-options-rfc3319-server.yang"
module ietf-example-dhcpv6-options-rfc3319-server { module ietf-example-dhcpv6-options-rfc3319-server {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-example-dhcpv6-options- namespace "urn:ietf:params:xml:ns:yang:" +
rfc3319-server"; "ietf-example-dhcpv6-options-rfc3319-server";
prefix "rfc3319-srv"; prefix "rfc3319-srv";
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
} }
import ietf-dhcpv6-server { import ietf-dhcpv6-server {
prefix dhcpv6-server; prefix dhcpv6-server;
} }
skipping to change at page 83, line 34 skipping to change at page 83, line 34
configuration parameters are provided. configuration parameters are provided.
At the end there is an augment statement which adds the vendor At the end there is an augment statement which adds the vendor
specific configuration defined in "dhcpv6-server-config:config" under specific configuration defined in "dhcpv6-server-config:config" under
'/dhcpv6-server:config/dhcpv6-server:vendor-config' mount point. '/dhcpv6-server:config/dhcpv6-server:vendor-config' mount point.
<CODE BEGINS> file "ietf-example-dhcpv6-server-config.yang" <CODE BEGINS> file "ietf-example-dhcpv6-server-config.yang"
module ietf-example-dhcpv6-server-config { module ietf-example-dhcpv6-server-config {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-example-dhcpv6-server-c namespace "urn:ietf:params:xml:ns:yang:" +
onfig"; "ietf-example-dhcpv6-server-config";
prefix "dhcpv6-server-config"; prefix "dhcpv6-server-config";
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
} }
import ietf-interfaces { import ietf-interfaces {
prefix if; prefix if;
} }
skipping to change at page 89, line 46 skipping to change at page 89, line 46
required. required.
The mechanism is as follows: class is associated to client based on The mechanism is as follows: class is associated to client based on
rules and then client is allowed to get address(es)/prefix(es) from rules and then client is allowed to get address(es)/prefix(es) from
given network-range/pool if the class name matches. given network-range/pool if the class name matches.
<CODE BEGINS> file "ietf-example-dhcpv6-class-selector.yang" <CODE BEGINS> file "ietf-example-dhcpv6-class-selector.yang"
module ietf-example-dhcpv6-class-selector { module ietf-example-dhcpv6-class-selector {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-example-dhcpv6-class-se namespace "urn:ietf:params:xml:ns:yang:" +
lector"; "ietf-example-dhcpv6-class-selector";
prefix "dhcpv6-class-selector"; prefix "dhcpv6-class-selector";
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
} }
import ietf-interfaces { import ietf-interfaces {
prefix if; prefix if;
} }
 End of changes. 10 change blocks. 
16 lines changed or deleted 16 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/