Internet DRAFT - draft-zhang-dns-resolver-yang
draft-zhang-dns-resolver-yang
Internet Engineering Task Force QF. Zhang
Internet Draft Ericsson
Intended status: Standards Track September 30, 2016
Expires: April 2017
Yang Data Model for DNS Resolver Protocol
draft-zhang-dns-resolver-yang-00.txt
Abstract
This document defines a YANG data model that can be used to
configure and manage DNS Resolver.
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), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
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."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
This Internet-Draft will expire on February 30, 2009.
Copyright Notice
Copyright (c) 2016 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
ZHANG Expires April 30, 2017 [Page 1]
Internet-Draft DNS Resolver Yang Data Model September 2016
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction...................................................2
1.1. Terminology...............................................2
1.2. Tree Diagrams.............................................3
2. Design of Data Model...........................................3
2.1. Overview..................................................3
2.2. Resource Record...........................................4
3. DNS Resolver YANG Module.......................................4
4. Security Considerations........................................6
5. IANA Considerations............................................6
6. Normative References...........................................6
1. Introduction
This document defines a YANG [RFC6020] data model for the management
of DNS protocol.
This data model includes configuration data and state data (status
information and counters for the collection of statistics).
1.1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119].
The following terms are used within this document:
The following terms are defined in [RFC6241] and are not redefined
here:
o client
o configuration data
Zhang Expires March 30, 2017 [Page 2]
Internet-Draft DNS Resolver Yang Data Model September 2016
o server
o state data
The following terms are defined in [RFC6020] and are not redefined
here:
o augment
o data model
o data node
o presence container
1.2. Tree Diagrams
A simplified graphical representation of the data model is used in
this document. The meaning of the symbols in these diagrams is as
follows:
o Brackets "[" and "]" enclose list keys.
o Abbreviations before data node names: "rw" means configuration
(read-write), and "ro" means state data (read-only).
o Symbols after data node names: "?" means an optional node, "!"
means a presence container, and "*" denotes a list and leaf-list.
o Parentheses enclose choice and case nodes, and case nodes are also
marked with a colon (":").
o Ellipsis ("...") stands for contents of subtrees that are not
shown.
2. Design of Data Model
The goal of this document is to define a data model that provides a
common user interface to the DNS Resolver protocol. There is very
information that is designated as "mandatory", providing freedom for
vendors to adapt this data model to their respective product
implementations.
2.1. Overview
The DNS Resolver YANG module defined in this document is augmented to
the DNS resolver, which is defined in RFC7317.
Zhang Expires March 30, 2017 [Page 3]
Internet-Draft DNS Resolver Yang Data Model September 2016
2.2. Resource Record
In general, we expect a resolver to cache all static hostname-to-
IpAddress mapping data. Each static mapping data is one resource
record, it contains the hostname and the corresponding IP address.
module: ietf-system-dns-resolver
augment /sys:system/sys:dns-resolver:
+--rw resource-record* [name]
+--rw name string
+--rw address inet:ip-address
3. DNS Resolver YANG Module
<CODE BEGINS> file "ietf-dns-resolver@2016-09-23.yang"
module ietf-system-dns-resolver {
yang-version "1";
namespace "urn:ietf:params:xml:ns:yang:ietf-system:dns-resolver";
prefix "dnsres";
import ietf-inet-types {
prefix inet;
}
import ietf-system {
prefix sys;
}
organization
"IETF NETMOD (NETCONF Data Modeling Language) Working Group";
contact
"Qifeng Zhang
Ericsson (China) Communication Co.,Ltd
ET2, No.5 Lize East street, Chaoyang District
100102
China
Phone: +86 13911502387
EMail: qifeng.zhang@ericsson.com";
description
"This YANG module defines a data model for the configuration of
DNS Resolver defined in RFC1035";
Zhang Expires March 30, 2017 [Page 4]
Internet-Draft DNS Resolver Yang Data Model September 2016
revision 2016-09-23 {
description
"Initial revision.";
reference
"RFC 1035: DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION";
}
/* Configuration data */
augment "/sys:system/sys:dns-resolver" {
description
"Augment dns-resolver to include resource record.";
list resource-record {
key "name";
description
"List of Resource Record entry.";
leaf name {
type string;
description
"An arbitrary name for the host.";
}
leaf address {
type inet:ip-address;
mandatory true;
description
"The address of the host.";
}
}
}
}
<CODE ENDS>
Zhang Expires March 30, 2017 [Page 5]
Internet-Draft DNS Resolver Yang Data Model September 2016
4. Security Considerations
The data model defined does not create any security implications.
5. IANA Considerations
This draft does not request any IANA action.
6. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC1034] P. Mockapetris, "DOMAIN NAMES - CONCEPTS AND FACILITIES",
DOI 10.17487/RFC1034, RFC 1034, November 1987,
<http://www.rfc-editor.org/info/rfc1034>.
[RFC1035] P. Mockapetris, "DOMAIN NAMES - IMPLEMENTATION AND
SPECIFICATION", DOI 10.17487/RFC1035, RFC 1035, November
1987, <http://www.rfc-editor.org/info/rfc1035>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, <http://www.rfc-
editor.org/info/rfc6020>.
[RFC6021] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 6021,
DOI 10.17487/RFC6021, October 2010, <http://www.rfc-
editor.org/info/rfc6021>.
Authors' Addresses
Qifeng Zhang
Ericsson (China) Communications Company Ltd.
Ericsson Tower, No. 5 Lize East Street,
Chaoyang District Beijing 100102, P.R. China
Email: qifeng.zhang@ericsson.com
Zhang Expires March 30, 2017 [Page 6]
