One document matched: draft-ietf-netmod-system-mgmt-16.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt"?>
<!DOCTYPE rfc SYSTEM 'rfc2629.dtd'>
<?rfc toc="yes"?>
<?rfc compact="no"?>
<?rfc subcompact="no"?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc iprnotified="no"?>
<?rfc strict="yes"?>
<rfc ipr="trust200902" category="std"
docName="draft-ietf-netmod-system-mgmt-16" >
<front>
<title abbrev="YANG System Management">A YANG Data Model for System Management</title>
<author initials="A" surname="Bierman" fullname='Andy Bierman' >
<organization>YumaWorks</organization>
<address>
<email>andy@yumaworks.com</email>
</address>
</author>
<author initials="M" surname="Bjorklund" fullname='Martin Bjorklund' >
<organization>Tail-f Systems</organization>
<address>
<email>mbj@tail-f.com</email>
</address>
</author>
<date/>
<abstract>
<t>
This document defines a YANG data model for the configuration
and identification of some common system properties
within a device containing a NETCONF server. This includes
data node definitions for system identification, time-of-day
management, user management, DNS resolver configuration, and some
protocol operations for system management.
</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>
This document defines a YANG <xref target="RFC6020"/> data model for the
configuration and identification of some common properties
within a device containing a NETCONF server.
</t>
<t>
Devices that are managed by NETCONF and perhaps other mechanisms
have common properties that need to be configured and monitored
in a standard way.
</t>
<t>
The "ietf‑system" YANG module defined in this document provides the
following features:
</t>
<t>
<list style="symbols">
<t>
system identification configuration and monitoring
</t>
<t>
system time-of-day configuration and monitoring
</t>
<t>
user authentication configuration
</t>
<t>
local users configuration
</t>
<t>
DNS resolver configuration
</t>
<t>
system control operations (shutdown, restart, setting time)
</t>
</list>
</t>
<section title="Terminology">
<t>
The keywords "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, <xref target="RFC2119"/>.
</t>
<t>
The following terms are defined in <xref target="RFC6241"/> and are not redefined
here:
</t>
<t>
<list style="symbols">
<t>
client
</t>
<t>
configuration data
</t>
<t>
server
</t>
<t>
state data
</t>
</list>
</t>
</section>
<section title="Tree Diagrams">
<t>
A simplified graphical representation of the data model is used in
this document. The meaning of the symbols in these
diagrams is as follows:
</t>
<t>
<list style="symbols">
<t>
Brackets "[" and "]" enclose list keys.
</t>
<t>
Abbreviations before data node names: "rw" means configuration
(read-write) and "ro" state data (read-only).
</t>
<t>
Symbols after data node names: "?" means an optional node, "!" means
a presence container, and "*" denotes a list and leaf-list.
</t>
<t>
Parentheses enclose choice and case nodes, and case nodes are also
marked with a colon (":").
</t>
<t>
Ellipsis ("...") stands for contents of subtrees that are not shown.
</t>
</list>
</t>
</section>
</section>
<section title="Objectives">
<section title="System Identification">
<t>
There are many common properties used to identify devices,
operating systems, software versions, etc. that need to
be supported in the system data module.
These objects are defined
as operational state data and the information returned by the
server is intended to be specific to the
device vendor.
</t>
<t>
Some user-configurable administrative strings are also
provided, such as the system location and description.
</t>
</section>
<section title="System Time Management">
<t>
The management of the date and time used by the system need to be
supported. Use of one or more NTP servers to automatically set the
system date and time need to be possible. Utilization of the Timezone
database <xref target="RFC6557"/> also need to be supported. It should be possible to
configure the system to use NTP.
</t>
</section>
<section title="User Authentication">
<t>
The authentication mechanism needs to support password authentication over
RADIUS, to support deployment scenarios with centralized
authentication servers. Additionally, local users need to be supported,
for scenarios when no centralized authentication server exists, or for
situations where the centralized authentication server cannot be
reached from the device.
</t>
<t>
Since the mandatory transport protocol for NETCONF is SSH
<xref target="RFC6242"/> the authentication model needs to support
SSH's "publickey" and "password" authentication methods <xref target="RFC4252"/>.
</t>
<t>
The model for authentication configuration should be flexible enough
to support authentication methods defined by other standard documents
or by vendors. It should be possible to configure the system
authentication properties.
</t>
</section>
<section title="DNS Resolver">
<t>
The configuration of the DNS resolver within the system containing the
NETCONF server is required in order to control how domain names are
resolved.
</t>
</section>
<section title="System Control">
<t>
A few operations are needed to support common tasks such as
restarting the device or setting the system date and time.
</t>
</section>
</section>
<section title="System Data Model">
<section title="System Identification">
<t>
The data model for system identification has the following
structure:
</t>
<figure>
<artwork><![CDATA[
+--rw system
| +--rw contact? string
| +--rw hostname? inet:domain-name
| +--rw location? string
+--ro system-state
+--ro platform
+--ro os-name? string
+--ro os-release? string
+--ro os-version? string
+--ro machine? string
]]></artwork>
</figure>
</section>
<section title="System Time Management">
<t>
The data model for system time management has the following
structure:
</t>
<figure>
<artwork><![CDATA[
+--rw system
| +--rw clock
| | +--rw (timezone)?
| | +--:(timezone-name)
| | | +--rw timezone-name? timezone-name
| | +--:(timezone-utc-offset)
| | +--rw timezone-utc-offset? int16
| +--rw ntp!
| +--rw enabled? boolean
| +--rw server* [name]
| +--rw name string
| +--rw (transport)
| | +--:(udp)
| | +--rw udp
| | +--rw address inet:host
| | +--rw port? inet:port-number
| +--rw association-type? enumeration
| +--rw iburst? boolean
| +--rw prefer? boolean
+--ro system-state
+--ro clock
+--ro current-datetime? yang:date-and-time
+--ro boot-datetime? yang:date-and-time
]]></artwork>
</figure>
<t>
New "case" statements can be added over time or augmented to the "transport"
choice to support other transport protocols.
</t>
</section>
<section title="DNS Resolver Model">
<t>
The data model for configuration of the DNS resolver has the following
structure:
</t>
<figure>
<artwork><![CDATA[
+--rw system
+--rw dns-resolver
+--rw search* inet:domain-name
+--rw server* [name]
| +--rw name string
| +--rw (transport)
| +--:(udp-and-tcp)
| +--udp-and-tcp
| +--rw address inet:ip-address
| +--rw port? inet:port-number
+--rw options
+--rw timeout? uint8
+--rw attempts? uint8
]]></artwork>
</figure>
<t>
New "case" statements can be added over time or augmented to the "transport"
choice to support other transport protocols.
</t>
</section>
<section title="RADIUS Client Model">
<t>
The data model for configuration of the RADIUS client has the
following structure:
</t>
<figure>
<artwork><![CDATA[
+--rw system
+--rw radius
+--rw server* [name]
| +--rw name string
| +--rw (transport)
| | +--:(udp)
| | +--rw udp
| | +--rw address inet:host
| | +--rw authentication-port? inet:port-number
| | +--rw shared-secret string
| +--rw authentication-type? identityref
+--rw options
+--rw timeout? uint8
+--rw attempts? uint8
]]></artwork>
</figure>
<t>
New "case" statements can be added over time or augmented to the "transport"
choice to support other transport protocols.
</t>
</section>
<section title="User Authentication Model">
<t>
This document defines three authentication methods for use with
NETCONF:
</t>
<t>
<list style="symbols">
<t>
publickey for local users over SSH
</t>
<t>
password for local users over any secure transport
</t>
<t>
password for RADIUS users over any secure transport
</t>
</list>
</t>
<t>
Additional methods can be defined by other standard documents or by
vendors.
</t>
<t>
This document defines two optional YANG features, "local‑users" and
"radius‑authentication", which the server advertises to indicate
support for configuring local users on the device, and support for
using RADIUS for authentication, respectively.
</t>
<t>
The authentication parameters defined in this document are primarily
used to configure authentication of NETCONF users, but MAY also be
used by other interfaces, e.g., a Command Line Interface or a
Web-based User Interface.
</t>
<t>
The data model for user authentication has the following structure:
</t>
<figure>
<artwork><![CDATA[
+--rw system
+--rw authentication
+--rw user-authentication-order* identityref
+--rw user* [name]
+--rw name string
+--rw password? ianach:crypt-hash
+--rw authorized-key* [name]
+--rw name string
+--rw algorithm string
+--rw key-data binary
]]></artwork>
</figure>
<section title="SSH Public Key Authentication">
<t>
If the NETCONF server advertises the "local‑users" feature,
configuration of local users and their SSH public keys is supported in
the /system/authentication/user list.
</t>
<t>
Public key authentication is requested by the SSH client. If the
"local‑users" feature is supported, then when a NETCONF client starts
an SSH session towards the server using the "publickey" authentication
"method name" <xref target="RFC4252"/>, the SSH server looks up the user name given
in the SSH authentication request in the /system/authentication/user
list, and verifies the key as described in <xref target="RFC4253"/>.
</t>
</section>
<section title="Local User Password Authentication">
<t>
If the NETCONF server advertises the "local‑users" feature,
configuration of local users and their passwords is supported in the
/system/authentication/user list.
</t>
<t>
For NETCONF transport protocols that support password authentication,
the leaf-list "user‑authentication‑order" is used to control if local
user password authentication should be used.
</t>
<t>
In SSH, password authentication is requested by the client. Other
NETCONF transport protocols MAY also support password authentication.
</t>
<t>
When local user password authentication is requested, the NETCONF
transport looks up the user name provided by the client in the
/system/authentication/user list, and verifies the password.
</t>
</section>
<section title="RADIUS Password Authentication">
<t>
If the NETCONF server advertises the "radius‑authentication" feature,
the device supports user authentication using RADIUS.
</t>
<t>
For NETCONF transport protocols that support password authentication,
the leaf-list "user‑authentication‑order" is used to control if RADIUS
password authentication should be used.
</t>
<t>
In SSH, password authentication is requested by the client. Other
NETCONF transport protocols MAY also support password authentication.
</t>
</section>
</section>
<section title="System Control">
<t>
The following operations are defined:
</t>
<figure>
<artwork><![CDATA[
set-current-datetime
system-restart
system-shutdown
]]></artwork>
</figure>
<t>
Two protocol operations are included to restart or shutdown
the system. The 'system‑restart' operation can be used to
restart the entire system (not just the NETCONF server).
The 'system‑shutdown' operation can be used to power off
the entire system.
</t>
</section>
</section>
<section title="Relationship to the SNMPv2-MIB">
<t>
If a device implements the SNMPv2-MIB <xref target="RFC3418"/>, there are two objects
that MAY be mapped by the implementation. See the YANG module
definition in <xref target="module"/> for details. The following table lists the
YANG data nodes with corresponding objects in the SNMPv2-MIB.
</t>
<?rfc compact="yes"?>
<texttable title="YANG interface configuration data nodes and related SNMPv2-MIB objects">
<ttcol align='left'>YANG data node</ttcol>
<ttcol align='left'>SNMPv2-MIB object</ttcol>
<c>contact</c>
<c>sysContact</c>
<c>location</c>
<c>sysLocation</c>
</texttable>
<?rfc compact="no"?>
</section>
<section title="IANA Crypt Hash YANG module" anchor="iana-module">
<t>
This YANG module references <xref target="RFC1321"/>, <xref target="IEEE-1003.1-2008"/>, and
<xref target="FIPS.180-3.2008"/>.
</t>
<t>
RFC Ed.: update the date below with the date of RFC publication and
remove this note.
</t>
<t><CODE BEGINS> file "iana-crypt-hash@2014-04-04.yang"</t>
<figure>
<artwork><![CDATA[
module iana-crypt-hash {
namespace "urn:ietf:params:xml:ns:yang:iana-crypt-hash";
prefix ianach;
organization "IANA";
contact
" Internet Assigned Numbers Authority
Postal: ICANN
4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292
Tel: +1 310 823 9358
E-Mail: iana&iana.org";
description
"This YANG module defines a typedef for storing passwords
using a hash function, and features to indicate which hash
functions are supported by an implementation.
The latest revision of this YANG module can be obtained from
the IANA web site.
Requests for new values should be made to IANA via
email (iana&iana.org).
Copyright (c) 2014 IETF Trust and the persons identified as
authors of the code. All rights reserved.
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).
The initial version of this YANG module is part of RFC XXXX;
see the RFC itself for full legal notices.";
// RFC Ed.: replace XXXX with actual RFC number and remove this
// note.
// RFC Ed.: update the date below with the date of RFC publication
// and remove this note.
revision 2014-04-04 {
description
"Initial revision.";
reference
"RFC XXXX: A YANG Data Model for System Management";
}
typedef crypt-hash {
type string {
pattern
'$0$.*'
+ '|$1$[a-zA-Z0-9./]{1,8}$[a-zA-Z0-9./]{22}'
+ '|$5$(rounds=\d+$)?[a-zA-Z0-9./]{1,16}$[a-zA-Z0-9./]{43}'
+ '|$6$(rounds=\d+$)?[a-zA-Z0-9./]{1,16}$[a-zA-Z0-9./]{86}';
}
description
"The crypt-hash type is used to store passwords using
a hash function. The algorithms for applying the hash
function and encoding the result are implemented in
various UNIX systems as the function crypt(3).
A value of this type matches one of the forms:
$0$<clear text password>
$<id>$<salt>$<password hash>
$<id>$<parameter>$<salt>$<password hash>
The '$0$' prefix signals that the value is clear text. When
such a value is received by the server, a hash value is
calculated, and the string '$<id>$<salt>$' or
$<id>$<parameter>$<salt>$ is prepended to the result. This
value is stored in the configuration data store.
If a value starting with '$<id>$', where <id> is not '0', is
received, the server knows that the value already represents a
hashed value, and stores it as is in the data store.
When a server needs to verify a password given by a user, it
finds the stored password hash string for that user, extracts
the salt, and calculates the hash with the salt and given
password as input. If the calculated hash value is the same
as the stored value, the password given by the client is
accepted.
This type defines the following hash functions:
id | hash function | feature
---+---------------+-------------------
1 | MD5 | crypt-hash-md5
5 | SHA-256 | crypt-hash-sha-256
6 | SHA-512 | crypt-hash-sha-512
The server indicates support for the different hash functions
by advertising the corresponding feature.";
reference
"IEEE Std 1003.1-2008 - crypt() function
RFC 1321: The MD5 Message-Digest Algorithm
FIPS.180-3.2008: Secure Hash Standard";
}
feature crypt-hash-md5 {
description
"Indicates that the device supports the MD5
hash function in 'crypt-hash' values";
reference "RFC 1321: The MD5 Message-Digest Algorithm";
}
feature crypt-hash-sha-256 {
description
"Indicates that the device supports the SHA-256
hash function in 'crypt-hash' values";
reference "FIPS.180-3.2008: Secure Hash Standard";
}
feature crypt-hash-sha-512 {
description
"Indicates that the device supports the SHA-512
hash function in 'crypt-hash' values";
reference "FIPS.180-3.2008: Secure Hash Standard";
}
}
]]></artwork>
</figure>
<t><CODE ENDS></t>
</section>
<section title="System YANG module" anchor="module">
<t>
This YANG module imports YANG extensions from
<xref target="RFC6536"/>, and imports YANG types from <xref target="RFC6991"/>.
It also references <xref target="RFC1035"/>, <xref target="RFC2865"/>, <xref target="RFC3418"/>, <xref target="RFC5607"/>,
<xref target="RFC5966"/>, <xref target="RFC6557"/>.
</t>
<t>
RFC Ed.: update the date below with the date of RFC publication and
remove this note.
</t>
<t><CODE BEGINS> file "ietf-system@2014-05-14.yang"</t>
<figure>
<artwork><![CDATA[
module ietf-system {
namespace "urn:ietf:params:xml:ns:yang:ietf-system";
prefix "sys";
import ietf-yang-types {
prefix yang;
}
import ietf-inet-types {
prefix inet;
}
import ietf-netconf-acm {
prefix nacm;
}
import iana-crypt-hash {
prefix ianach;
}
organization
"IETF NETMOD (NETCONF Data Modeling Language) Working Group";
contact
"WG Web: <http://tools.ietf.org/wg/netmod/>
WG List: <mailto:netmod@ietf.org>
WG Chair: Thomas Nadeau
<mailto:tnadeau@lucidvision.com>
WG Chair: Juergen Schoenwaelder
<mailto:j.schoenwaelder@jacobs-university.de>
Editor: Andy Bierman
<mailto:andy@yumaworks.com>
Editor: Martin Bjorklund
<mailto:mbj@tail-f.com>";
description
"This module contains a collection of YANG definitions for the
configuration and identification of some common system
properties within a device containing a NETCONF server. This
includes data node definitions for system identification,
time-of-day management, user management, DNS resolver
configuration, and some protocol operations for system
management.
Copyright (c) 2014 IETF Trust and the persons identified as
authors of the code. All rights reserved.
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.";
// RFC Ed.: replace XXXX with actual RFC number and remove this
// note.
// RFC Ed.: remove this note
// Note: extracted from draft-ietf-netmod-system-mgmt-07.txt
// RFC Ed.: update the date below with the date of RFC publication
// and remove this note.
revision "2014-05-14" {
description
"Initial revision.";
reference
"RFC XXXX: A YANG Data Model for System Management";
}
/*
* Typedefs
*/
typedef timezone-name {
type string;
description
"A timezone name as used by the Time Zone Database, sometimes
referred to as the 'Olson Database'.
The exact set of valid values is an implementation-specific
matter. Client discovery of the exact set of time zone names
for a particular server is out of scope.";
reference
"RFC 6557: Procedures for Maintaining the Time Zone Database";
}
/*
* Features
*/
feature radius {
description
"Indicates that the device can be configured as a RADIUS
client.";
reference
"RFC 2865: Remote Authentication Dial In User Service "
+ "(RADIUS)";
}
feature authentication {
description
"Indicates that the device supports configuration
for user authentication.";
}
feature local-users {
if-feature authentication;
description
"Indicates that the device supports configuration of
local user authentication.";
}
feature radius-authentication {
if-feature radius;
if-feature authentication;
description
"Indicates that the device supports configuration of user
authentication over RADIUS.";
reference
"RFC 2865: Remote Authentication Dial In User Service (RADIUS)
RFC 5607: Remote Authentication Dial-In User Service (RADIUS)
Authorization for Network Access Server (NAS)
Management";
}
feature ntp {
description
"Indicates that the device can be configured
to use one or more NTP servers to set the
system date and time.";
}
feature ntp-udp-port {
if-feature ntp;
description
"Indicates that the device supports the configuration of
the UDP port for NTP servers.
This is a 'feature' since many implementations do not support
any other port than the default port.";
}
feature timezone-name {
description
"Indicates that the local timezone on the device
can be configured to use the TZ database
to set the timezone and manage daylight savings time.";
reference
"RFC 6557: Procedures for Maintaining the Time Zone Database";
}
feature dns-udp-tcp-port {
description
"Indicates that the device supports the configuration of
the UDP and TCP port for DNS servers.
This is a 'feature' since many implementations do not support
any other port than the default port.";
}
/*
* Identities
*/
identity authentication-method {
description
"Base identity for user authentication methods.";
}
identity radius {
base authentication-method;
description
"Indicates user authentication using RADIUS.";
reference
"RFC 2865: Remote Authentication Dial In User Service (RADIUS)
RFC 5607: Remote Authentication Dial-In User Service (RADIUS)
Authorization for Network Access Server (NAS)
Management";
}
identity local-users {
base authentication-method;
description
"Indicates password-based authentication of locally
configured users.";
}
identity radius-authentication-type {
description
"Base identity for RADIUS authentication types.";
}
identity radius-pap {
base radius-authentication-type;
description
"The device requests PAP authentication from the RADIUS
server.";
reference
"RFC 2865: Remote Authentication Dial In User Service";
}
identity radius-chap {
base radius-authentication-type;
description
"The device requests CHAP authentication from the RADIUS
server.";
reference
"RFC 2865: Remote Authentication Dial In User Service";
}
/*
* Configuration data nodes
*/
container system {
description
"System group configuration.";
leaf contact {
type string;
description
"The administrator contact information for the system.
A server implementation MAY map this leaf to the sysContact
MIB object. Such an implementation needs to use some
mechanism to handle the differences in size and characters
allowed between this leaf and sysContact. The definition of
such a mechanism is outside the scope of this document.";
reference
"RFC 3418: Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)
SNMPv2-MIB.sysContact";
}
leaf hostname {
type inet:domain-name;
description
"The name of the host. This name can be a single domain
label, or the fully qualified domain name of the host.";
}
leaf location {
type string;
description
"The system location.
A server implementation MAY map this leaf to the sysLocation
MIB object. Such an implementation needs to use some
mechanism to handle the differences in size and characters
allowed between this leaf and sysLocation. The definition
of such a mechanism is outside the scope of this document.";
reference
"RFC 3418: Management Information Base (MIB) for the
Simple Network Management Protocol (SNMP)
SNMPv2-MIB.sysLocation";
}
container clock {
description
"Configuration of the system date and time properties.";
choice timezone {
description
"The system timezone information.";
case timezone-name {
if-feature timezone-name;
leaf timezone-name {
type timezone-name;
description
"The TZ database name to use for the system, such
as 'Europe/Stockholm'.";
}
}
case timezone-utc-offset {
leaf timezone-utc-offset {
type int16 {
range "-1500 .. 1500";
}
units "minutes";
description
"The number of minutes to add to UTC time to
identify the timezone for this system. For example,
'UTC - 8:00 hours' would be represented as '-480'.
Note that automatic daylight savings time adjustment
is not provided, if this object is used.";
}
}
}
}
container ntp {
if-feature ntp;
presence
"Enables the NTP client unless the 'enabled' leaf
(which defaults to 'true') is set to 'false'";
description
"Configuration of the NTP client.";
leaf enabled {
type boolean;
default true;
description
"Indicates that the system should attempt
to synchronize the system clock with an
NTP server from the 'ntp/server' list.";
}
list server {
key name;
description
"List of NTP servers to use for
system clock synchronization. If '/system/ntp/enabled'
is 'true', then the system will attempt to
contact and utilize the specified NTP servers.";
leaf name {
type string;
description
"An arbitrary name for the NTP server.";
}
choice transport {
mandatory true;
description
"The transport protocol specific parameters for this
server.";
case udp {
container udp {
description
"Contains UDP specific configuration parameters
for NTP.";
leaf address {
type inet:host;
mandatory true;
description
"The address of the NTP server.";
}
leaf port {
if-feature ntp-udp-port;
type inet:port-number;
default 123;
description
"The port number of the NTP server.";
}
}
}
}
leaf association-type {
type enumeration {
enum server {
description
"Use client association mode. This device
will not provide synchronization to the
configured NTP server.";
}
enum peer {
description
"Use symmetric active association mode.
This device may provide synchronization
to the configured NTP server.";
}
enum pool {
description
"Use client association mode with one or
more of the NTP servers found by DNS
resolution of the domain name given by
the 'address' leaf. This device will not
provide synchronization to the servers.";
}
}
default server;
description
"The desired association type for this NTP server.";
}
leaf iburst {
type boolean;
default false;
description
"Indicates whether this server should enable burst
synchronization or not.";
}
leaf prefer {
type boolean;
default false;
description
"Indicates whether this server should be preferred
or not.";
}
}
}
container dns-resolver {
description
"Configuration of the DNS resolver.";
leaf-list search {
type inet:domain-name;
ordered-by user;
description
"An ordered list of domains to search when resolving
a host name.";
}
list server {
key name;
ordered-by user;
description
"List of the DNS servers that the resolver should query.
When the resolver is invoked by a calling application, it
sends the query to the first name server in this list. If
no response has been received within 'timeout' seconds,
the resolver continues with the next server in the list.
If no response is received from any server, the resolver
continues with the first server again. When the resolver
has traversed the list 'attempts' times without receiving
any response, it gives up and returns an error to the
calling application.
Implementations MAY limit the number of entries in this
list.";
leaf name {
type string;
description
"An arbitrary name for the DNS server.";
}
choice transport {
mandatory true;
description
"The transport protocol specific parameters for this
server.";
case udp-and-tcp {
container udp-and-tcp {
description
"Contains UDP and TCP specific configuration
parameters for DNS.";
reference
"RFC 1035: Domain Implementation and Specification
RFC 5966: DNS over TCP";
leaf address {
type inet:ip-address;
mandatory true;
description
"The address of the DNS server.";
}
leaf port {
if-feature dns-udp-tcp-port;
type inet:port-number;
default 53;
description
"The UDP and TCP port number of the DNS server.";
}
}
}
}
}
container options {
description
"Resolver options. The set of available options has been
limited to those that are generally available across
different resolver implementations, and generally
useful.";
leaf timeout {
type uint8 {
range "1..max";
}
units "seconds";
default "5";
description
"The amount of time the resolver will wait for a
response from each remote name server before
retrying the query via a different name server.";
}
leaf attempts {
type uint8 {
range "1..max";
}
default "2";
description
"The number of times the resolver will send a query to
all its name servers before giving up and returning an
error to the calling application.";
}
}
}
container radius {
if-feature radius;
description
"Configuration of the RADIUS client.";
list server {
key name;
ordered-by user;
description
"List of RADIUS servers used by the device.
When the RADIUS client is invoked by a calling
application, it sends the query to the first server in
this list. If no response has been received within
'timeout' seconds, the client continues with the next
server in the list. If no response is received from any
server, the client continues with the first server again.
When the client has traversed the list 'attempts' times
without receiving any response, it gives up and returns an
error to the calling application.";
leaf name {
type string;
description
"An arbitrary name for the RADIUS server.";
}
choice transport {
mandatory true;
description
"The transport protocol specific parameters for this
server.";
case udp {
container udp {
description
"Contains UDP specific configuration parameters
for RADIUS.";
leaf address {
type inet:host;
mandatory true;
description
"The address of the RADIUS server.";
}
leaf authentication-port {
type inet:port-number;
default "1812";
description
"The port number of the RADIUS server.";
}
leaf shared-secret {
type string;
mandatory true;
nacm:default-deny-all;
description
"The shared secret which is known to both the
RADIUS client and server.";
reference
"RFC 2865: Remote Authentication Dial In User
Service";
}
}
}
}
leaf authentication-type {
type identityref {
base radius-authentication-type;
}
default radius-pap;
description
"The authentication type requested from the RADIUS
server.";
}
}
container options {
description
"RADIUS client options.";
leaf timeout {
type uint8 {
range "1..max";
}
units "seconds";
default "5";
description
"The number of seconds the device will wait for a
response from each RADIUS server before trying with a
different server.";
}
leaf attempts {
type uint8 {
range "1..max";
}
default "2";
description
"The number of times the device will send a query to
all its RADIUS servers before giving up.";
}
}
}
container authentication {
nacm:default-deny-write;
if-feature authentication;
description
"The authentication configuration subtree.";
leaf-list user-authentication-order {
type identityref {
base authentication-method;
}
must '(. != "sys:radius" or ../../radius/server)' {
error-message
"When 'radius' is used, a RADIUS server"
+ " must be configured.";
description
"When 'radius' is used as an authentication method,
a RADIUS server must be configured.";
}
ordered-by user;
description
"When the device authenticates a user with a password,
it tries the authentication methods in this leaf-list in
order. If authentication with one method fails, the next
method is used. If no method succeeds, the user is
denied access.
An empty user-authentication-order leaf-list still allows
authentication of users using mechanisms that do not
involve a password.
If the 'radius-authentication' feature is advertised by
the NETCONF server, the 'radius' identity can be added to
this list.
If the 'local-users' feature is advertised by the
NETCONF server, the 'local-users' identity can be
added to this list.";
}
list user {
if-feature local-users;
key name;
description
"The list of local users configured on this device.";
leaf name {
type string;
description
"The user name string identifying this entry.";
}
leaf password {
type ianach:crypt-hash;
description
"The password for this entry.";
}
list authorized-key {
key name;
description
"A list of public SSH keys for this user. These keys
are allowed for SSH authentication, as described in
RFC 4253.";
reference
"RFC 4253: The Secure Shell (SSH) Transport Layer
Protocol";
leaf name {
type string;
description
"An arbitrary name for the SSH key.";
}
leaf algorithm {
type string;
mandatory true;
description
"The public key algorithm name for this SSH key.
Valid values are the values in the IANA Secure Shell
(SSH) Protocol Parameters registry, Public Key
Algorithm Names";
reference
"IANA Secure Shell (SSH) Protocol Parameters registry,
Public Key Algorithm Names";
}
leaf key-data {
type binary;
mandatory true;
description
"The binary public key data for this SSH key, as
specified by RFC 4253, Section 6.6, i.e.,:
string certificate or public key format
identifier
byte[n] key/certificate data
";
reference
"RFC 4253: The Secure Shell (SSH) Transport Layer
Protocol";
}
}
}
}
}
/*
* Operational state data nodes
*/
container system-state {
config false;
description
"System group operational state.";
container platform {
description
"Contains vendor-specific information for
identifying the system platform and operating system.";
reference
"IEEE Std 1003.1-2008 - sys/utsname.h";
leaf os-name {
type string;
description
"The name of the operating system in use,
for example 'Linux'";
reference
"IEEE Std 1003.1-2008 - utsname.sysname";
}
leaf os-release {
type string;
description
"The current release level of the operating
system in use. This string MAY indicate
the OS source code revision.";
reference
"IEEE Std 1003.1-2008 - utsname.release";
}
leaf os-version {
type string;
description
"The current version level of the operating
system in use. This string MAY indicate
the specific OS build date and target variant
information.";
reference
"IEEE Std 1003.1-2008 - utsname.version";
}
leaf machine {
type string;
description
"A vendor-specific identifier string representing
the hardware in use.";
reference
"IEEE Std 1003.1-2008 - utsname.machine";
}
}
container clock {
description
"Monitoring of the system
date and time properties.";
leaf current-datetime {
type yang:date-and-time;
description
"The current system date and time.";
}
leaf boot-datetime {
type yang:date-and-time;
description
"The system date and time when the system last restarted.";
}
}
}
rpc set-current-datetime {
nacm:default-deny-all;
description
"Set the /system-state/clock/current-datetime leaf
to the specified value.
If the system is using NTP (i.e., /system/ntp/enabled
is set to 'true'), then this operation will
fail with error-tag 'operation-failed',
and error-app-tag value of 'ntp-active'";
input {
leaf current-datetime {
type yang:date-and-time;
mandatory true;
description
"The current system date and time.";
}
}
}
rpc system-restart {
nacm:default-deny-all;
description
"Request that the entire system be restarted immediately.
A server SHOULD send an rpc reply to the client before
restarting the system.";
}
rpc system-shutdown {
nacm:default-deny-all;
description
"Request that the entire system be shut down immediately.
A server SHOULD send an rpc reply to the client before
shutting down the system.";
}
}
]]></artwork>
</figure>
<t><CODE ENDS></t>
</section>
<section title="IANA Considerations" anchor="iana">
<t>
IANA is requested to create an IANA-maintained YANG Module called
"iana‑crypt‑hash", based on the contents of <xref target="iana-module"/>, which will
allow for new hash algorithms to be added to the type "crypt‑hash".
The registration procedure will be Expert Review, as defined by
<xref target="RFC5226"/>.
</t>
<t>
This document registers two URIs in the IETF XML registry
<xref target="RFC3688"/>. Following the format in RFC 3688, the following
registrations are requested to be made.
</t>
<figure>
<artwork><![CDATA[
URI: urn:ietf:params:xml:ns:yang:iana-crypt-hash
Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace.
URI: urn:ietf:params:xml:ns:yang:ietf-system
Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace.
]]></artwork>
</figure>
<t>
This document registers two YANG modules in the YANG Module Names
registry <xref target="RFC6020"/>.
</t>
<figure>
<artwork><![CDATA[
name: iana-crypt-hash
namespace: urn:ietf:params:xml:ns:yang:iana-crypt-hash
prefix: ianach
reference: RFC XXXX
name: ietf-system
namespace: urn:ietf:params:xml:ns:yang:ietf-system
prefix: sys
reference: RFC XXXX
]]></artwork>
</figure>
</section>
<section title="Security Considerations">
<t>
The YANG modules defined in this memo are designed to be accessed
via the NETCONF protocol <xref target="RFC6241"/>. The lowest NETCONF layer is
the secure transport layer and the mandatory-to-implement secure
transport is SSH <xref target="RFC6242"/>. Authorization for access to specific
portions of conceptual data and operations within this module
is provided by the NETCONF access control model (NACM) <xref target="RFC6536"/>.
</t>
<t>
There are a number of data nodes defined in the "ietf‑system" YANG
module which are writable/creatable/deletable (i.e., config true,
which is the default). These data nodes may be considered sensitive or
vulnerable in some network environments. Write operations to these
data nodes can have a negative effect on network operations. It is
thus important to control write access (e.g., via edit-config) to
these data nodes. These are the subtrees and data nodes and their
sensitivity/vulnerability:
</t>
<t>
<list style="symbols">
<t>
/system/clock/timezone: This choice contains the objects used to
control the timezone used by the device.
</t>
<t>
/system/ntp: This container contains the objects used to
control the Network Time Protocol servers used by the device.
</t>
<t>
/system/dns-resolver: This container contains the objects used to
control the Domain Name System servers used by the device.
</t>
<t>
/system/radius: This container contains the objects used to
control the Remote Authentication Dial-In User Service
servers used by the device.
</t>
<t>
/system/authentication/user-authentication-order: This leaf
controls how user login attempts are authenticated by the device.
</t>
<t>
/system/authentication/user: This list contains the
local users enabled on the system.
</t>
</list>
</t>
<t>
Some of the readable data nodes in the "ietf‑system" YANG module may
be considered sensitive or vulnerable in some network environments.
It is thus important to control read access (e.g., via get,
get-config, or notification) to these data nodes. These are the
subtrees and data nodes and their sensitivity/vulnerability:
</t>
<t>
<list style="symbols">
<t>
/system/platform: This container has objects which may help
identify the specific NETCONF server and/or operating system
implementation used on the device.
</t>
<t>
/system/authentication/user: This list has objects that
may help identify the specific user names and password information
in use on the device.
</t>
</list>
</t>
<t>
Some of the remote procedure call (RPC) operations in the
"ietf‑system" YANG module may be considered sensitive or vulnerable in
some network environments. It is thus important to control access to
these operations. These are the operations and their
sensitivity/vulnerability:
</t>
<t>
<list style="symbols">
<t>
set-current-datetime: Changes the current date and time on the device.
</t>
<t>
system-restart: Reboots the device.
</t>
<t>
system-shutdown: Shuts down the device.
</t>
</list>
</t>
<t>
Since this document describes the use of RADIUS for purposes of
authentication, it is vulnerable to all of the threats that are
present in other RADIUS applications. For a discussion of such
threats, see <xref target="RFC2865"/> and <xref target="RFC3162"/>, and section 4 of <xref target="RFC3579"/>.
</t>
<t>
This document provides configuration parameters for SSH's "publickey"
and "password" authentication mechanisms. Section 9.4 of <xref target="RFC4251"/>
and section 11 of <xref target="RFC4252"/> discuss security considerations for
these mechanisms.
</t>
<t>
The "iana‑crypt‑hash" YANG module defines a type "crypt‑hash" that can
be used to store MD5 hashes. <xref target="RFC6151"/> discusses security
considerations for MD5. The usage of MD5 is NOT RECOMMENDED.
</t>
</section>
<section title="Change Log">
<figure>
<artwork><![CDATA[
-- RFC Ed.: remove this section before publication.
]]></artwork>
</figure>
<section title="00-01">
<t>
<list style="symbols">
<t>
added configuration-source identities
</t>
<t>
added configuration-source leaf to ntp and dns (via grouping) to
choose configuration source
</t>
<t>
added association-type, iburst, prefer, and true leafs to the
ntp-server list
</t>
<t>
extended the ssh keys for a user to a list of keys. support all
defined key algorithms, not just dsa and rsa
</t>
<t>
clarified timezone-utc-offset description-stmt
</t>
<t>
removed '/system/ntp/server/true' leaf from data model
</t>
</list>
</t>
</section>
<section title="01-02">
<t>
<list style="symbols">
<t>
added default-stmts to ntp-server/iburst and ntp-server/prefer leafs
</t>
<t>
changed timezone-location leaf to use iana-timezone typedef instead
of a string
</t>
</list>
</t>
</section>
<section title="02-03">
<t>
<list style="symbols">
<t>
removed configuration-source identities and leafs
</t>
</list>
</t>
</section>
<section title="03-04">
<t>
<list style="symbols">
<t>
removed ndots dns resolver option
</t>
<t>
added radius-authentication-type identity, and identities for pap
and chap, and a leaf to control which authentication type to use
when communicating with the radius server
</t>
<t>
made 0 an invalid value for timeouts and attempts
</t>
</list>
</t>
</section>
<section title="04-05">
<t>
<list style="symbols">
<t>
updated tree diagram explanation text
</t>
</list>
</t>
</section>
<section title="05-06">
<t>
<list style="symbols">
<t>
changed ntp/use-ntp to ntp/enabled
</t>
<t>
changed ntp/ntp-server to ntp/server
</t>
<t>
removed /system/platform/nodename leaf
</t>
<t>
changed /system/name to /system/hostname
</t>
<t>
simplified must expression in user-authentication-order
</t>
<t>
added optional rounds to sha hash definition
</t>
<t>
clarified the crypt-hash description
</t>
<t>
clarified ntp descriptions
</t>
<t>
clarified YANG module description to indicate that some
system properties are supported, not the entire system
</t>
<t>
clarified that system identification values are vendor
specific, not the data node objects
</t>
<t>
clarified sec. 2.2 and 2.3 to indicate that the server should
also be capable of configuring these properties
</t>
<t>
changed /system/dns/search from inet:host to inet:domain-name
</t>
<t>
changed RFC6021 reference to 6021-bis
</t>
<t>
changed /system/platform/nodename to /system/platform/hostname
</t>
<t>
changed /system/radius/server/{leafs} to be within a choice
and 'udp' case statement so other transport specific parameters can
augment this list or they can be added by the WG to a future
version of this module. {leafs} are authentication-port and
shared-secret.
</t>
<t>
updated YANG tree diagrams for objects added in -05 and -06
</t>
</list>
</t>
</section>
<section title="06-07">
<t>
<list style="symbols">
<t>
updated the Abstract and Introduction
</t>
<t>
updated Tree diagram notation
</t>
<t>
identify all external servers (dns, ntp, radius) by name instead of
address, in order to make the data model extensible for additional
transport protocol.
</t>
<t>
updated the Security Considerations section with a reference to
NACM.
</t>
</list>
</t>
</section>
<section title="07-08">
<t>
<list style="symbols">
<t>
renamed the DNS transport to 'udp‑and‑tcp' and added references.
</t>
<t>
moved the operational state nodes into /system-state.
</t>
</list>
</t>
</section>
<section title="08-09">
<t>
<list style="symbols">
<t>
made "ntp" node a presence container
</t>
<t>
added reference to RFC 6151
</t>
<t>
updated reference from 6021-bis to RFC 6991
</t>
<t>
cleaned up usage of config false in the YANG module
</t>
</list>
</t>
</section>
<section title="09-10">
<t>
<list style="symbols">
<t>
clarified relationship with SNMPv2-MIB
</t>
</list>
</t>
</section>
<section title="11-12">
<t>
<list style="symbols">
<t>
added typedef "timezone‑name", and removed reference to
draft-ietf-netmod-iana-timezones
</t>
</list>
</t>
</section>
<section title="13-14">
<t>
<list style="symbols">
<t>
moved the "crypt‑hash" typedef to an IANA maintained module.
</t>
<t>
updated security considerations to mention RADIUS threats.
</t>
</list>
</t>
</section>
<section title="14-15">
<t>
<list style="symbols">
<t>
updated security considerations to mention SSH authentication
method threats.
</t>
</list>
</t>
</section>
</section>
</middle>
<back>
<references title="Normative References">
<reference anchor="RFC2119">
<front>
<title>Key words for use in RFCs to Indicate Requirement Levels</title>
<author initials="S." surname="Bradner" fullname="S. Bradner">
<organization>Harvard University</organization>
</author>
<date month="March" year="1997"/>
<abstract>
<t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="14"/>
<seriesInfo name="RFC" value="2119"/>
<format type="TXT" octets="4723" target="ftp://ftp.isi.edu/in-notes/rfc2119.txt"/>
</reference>
<reference anchor="RFC4251">
<front>
<title>The Secure Shell (SSH) Protocol Architecture</title>
<author initials="T." surname="Ylonen" fullname="T. Ylonen">
<organization/>
</author>
<author initials="C." surname="Lonvick" fullname="C. Lonvick">
<organization/>
</author>
<date year="2006" month="January"/>
<abstract>
<t>The Secure Shell (SSH) Protocol is a protocol for secure remote login and other secure network services over an insecure network. This document describes the architecture of the SSH protocol, as well as the notation and terminology used in SSH protocol documents. It also discusses the SSH algorithm naming system that allows local extensions. The SSH protocol consists of three major components: The Transport Layer Protocol provides server authentication, confidentiality, and integrity with perfect forward secrecy. The User Authentication Protocol authenticates the client to the server. The Connection Protocol multiplexes the encrypted tunnel into several logical channels. Details of these protocols are described in separate documents. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="4251"/>
<format type="TXT" octets="71750" target="http://www.rfc-editor.org/rfc/rfc4251.txt"/>
</reference>
<reference anchor="RFC4252">
<front>
<title>The Secure Shell (SSH) Authentication Protocol</title>
<author initials="T." surname="Ylonen" fullname="T. Ylonen">
<organization/>
</author>
<author initials="C." surname="Lonvick" fullname="C. Lonvick">
<organization/>
</author>
<date year="2006" month="January"/>
<abstract>
<t>The Secure Shell Protocol (SSH) is a protocol for secure remote login and other secure network services over an insecure network. This document describes the SSH authentication protocol framework and public key, password, and host-based client authentication methods. Additional authentication methods are described in separate documents. The SSH authentication protocol runs on top of the SSH transport layer protocol and provides a single authenticated tunnel for the SSH connection protocol. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="4252"/>
<format type="TXT" octets="34268" target="http://www.rfc-editor.org/rfc/rfc4252.txt"/>
</reference>
<reference anchor="RFC4253">
<front>
<title>The Secure Shell (SSH) Transport Layer Protocol</title>
<author initials="T." surname="Ylonen" fullname="T. Ylonen">
<organization/>
</author>
<author initials="C." surname="Lonvick" fullname="C. Lonvick">
<organization/>
</author>
<date year="2006" month="January"/>
<abstract>
<t>The Secure Shell (SSH) is a protocol for secure remote login and other secure network services over an insecure network.</t><t> This document describes the SSH transport layer protocol, which typically runs on top of TCP/IP. The protocol can be used as a basis for a number of secure network services. It provides strong encryption, server authentication, and integrity protection. It may also provide compression.</t><t> Key exchange method, public key algorithm, symmetric encryption algorithm, message authentication algorithm, and hash algorithm are all negotiated.</t><t> This document also describes the Diffie-Hellman key exchange method and the minimal set of algorithms that are needed to implement the SSH transport layer protocol. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="4253"/>
<format type="TXT" octets="68263" target="http://www.rfc-editor.org/rfc/rfc4253.txt"/>
</reference>
<reference anchor="RFC5226">
<front>
<title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
<author initials="T." surname="Narten" fullname="T. Narten">
<organization/>
</author>
<author initials="H." surname="Alvestrand" fullname="H. Alvestrand">
<organization/>
</author>
<date year="2008" month="May"/>
<abstract>
<t>Many protocols make use of identifiers consisting of constants and other well-known values. Even after a protocol has been defined and deployment has begun, new values may need to be assigned (e.g., for a new option type in DHCP, or a new encryption or authentication transform for IPsec). To ensure that such quantities have consistent values and interpretations across all implementations, their assignment must be administered by a central authority. For IETF protocols, that role is provided by the Internet Assigned Numbers Authority (IANA).</t><t> In order for IANA to manage a given namespace prudently, it needs guidelines describing the conditions under which new values can be assigned or when modifications to existing values can be made. If IANA is expected to play a role in the management of a namespace, IANA must be given clear and concise instructions describing that role. This document discusses issues that should be considered in formulating a policy for assigning values to a namespace and provides guidelines for authors on the specific text that must be included in documents that place demands on IANA.</t><t> This document obsoletes RFC 2434. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="26"/>
<seriesInfo name="RFC" value="5226"/>
<format type="TXT" octets="66160" target="http://www.rfc-editor.org/rfc/rfc5226.txt"/>
</reference>
<reference anchor="RFC6151">
<front>
<title>Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms</title>
<author initials="S." surname="Turner" fullname="S. Turner">
<organization/>
</author>
<author initials="L." surname="Chen" fullname="L. Chen">
<organization/>
</author>
<date year="2011" month="March"/>
<abstract>
<t>This document updates the security considerations for the MD5 message digest algorithm. It also updates the security considerations for HMAC-MD5. This document is not an Internet Standards Track specification; it is published for informational purposes.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="6151"/>
<format type="TXT" octets="14662" target="http://www.rfc-editor.org/rfc/rfc6151.txt"/>
</reference>
<reference anchor='RFC6241'>
<front>
<title>Network Configuration Protocol (NETCONF)</title>
<author initials='R.' surname='Enns' fullname='R. Enns' role="editor">
<organization/>
</author>
<author initials='M.' surname='Bjorklund' fullname='M. Bjorklund' role="editor">
<organization/>
</author>
<author initials='J.' surname='Schoenwaelder' fullname='J. Schoenwaelder' role="editor">
<organization/>
</author>
<author initials='A.' surname='Bierman' fullname='A. Bierman' role="editor">
<organization/>
</author>
<date year='2011' month='June'/>
</front>
<seriesInfo name='RFC' value='6241'/>
</reference>
<reference anchor="RFC6242">
<front>
<title>Using the NETCONF Protocol over Secure Shell (SSH)</title>
<author initials="M." surname="Wasserman" fullname="M. Wasserman">
<organization/>
</author>
<date year="2011" month="June"/>
<abstract>
<t>This document describes a method for invoking and running the Network Configuration Protocol (NETCONF) within a Secure Shell (SSH) session as an SSH subsystem. This document obsoletes RFC 4742. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="6242"/>
<format type="TXT" octets="22704" target="http://www.rfc-editor.org/rfc/rfc6242.txt"/>
</reference>
<reference anchor='RFC6536'>
<front>
<title>Network Configuration Protocol (NETCONF) Access Control Model</title>
<author initials='A.' surname='Bierman' fullname='A. Bierman'>
<organization /></author>
<author initials='M.' surname='Bjorklund' fullname='M. Bjorklund'>
<organization /></author>
<date year='2012' month='March' />
<abstract>
<t>The standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) requires a structured and secure operating environment that promotes human usability and multi-vendor interoperability. There is a need for standard mechanisms to restrict NETCONF protocol access for particular users to a pre-configured subset of all available NETCONF protocol operations and content. This document defines such an access control model. [STANDARDS-TRACK]</t></abstract></front>
<seriesInfo name='RFC' value='6536' />
<format type='TXT' octets='90803' target='http://www.rfc-editor.org/rfc/rfc6536.txt' />
</reference>
<reference anchor="RFC6020">
<front>
<title>YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)</title>
<author initials="M." surname="Bjorklund" fullname="M. Bjorklund">
<organization/>
</author>
<date year="2010" month="October"/>
<abstract>
<t>YANG is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF), NETCONF remote procedure calls, and NETCONF notifications. [STANDARDS TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="6020"/>
<format type="TXT" octets="324178" target="http://www.rfc-editor.org/rfc/rfc6020.txt"/>
</reference>
<reference anchor="RFC1321">
<front>
<title abbrev="MD5 Message-Digest Algorithm">The MD5 Message-Digest Algorithm</title>
<author initials="R." surname="Rivest" fullname="Ronald L. Rivest">
<organization>Massachusetts Institute of Technology, (MIT) Laboratory for Computer Science</organization>
<address>
<postal>
<street>545 Technology Square</street>
<street>NE43-324</street>
<city>Cambridge</city>
<region>MA</region>
<code>02139-1986</code>
<country>US</country>
</postal>
<phone>+1 617 253 5880</phone>
<email>rivest@theory.lcs.mit.edu</email>
</address>
</author>
<date year="1992" month="April"/>
</front>
<seriesInfo name="RFC" value="1321"/>
<format type="TXT" octets="35222" target="http://www.rfc-editor.org/rfc/rfc1321.txt"/>
</reference>
<reference anchor="RFC2865">
<front>
<title>Remote Authentication Dial In User Service (RADIUS)</title>
<author initials="C." surname="Rigney" fullname="C. Rigney">
<organization/>
</author>
<author initials="S." surname="Willens" fullname="S. Willens">
<organization/>
</author>
<author initials="A." surname="Rubens" fullname="A. Rubens">
<organization/>
</author>
<author initials="W." surname="Simpson" fullname="W. Simpson">
<organization/>
</author>
<date year="2000" month="June"/>
<abstract>
<t>This document describes a protocol for carrying authentication, authorization, and configuration information between a Network Access Server which desires to authenticate its links and a shared Authentication Server. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="2865"/>
<format type="TXT" octets="146456" target="http://www.rfc-editor.org/rfc/rfc2865.txt"/>
</reference>
<reference anchor="RFC3162">
<front>
<title>RADIUS and IPv6</title>
<author initials="B." surname="Aboba" fullname="B. Aboba">
<organization/>
</author>
<author initials="G." surname="Zorn" fullname="G. Zorn">
<organization/>
</author>
<author initials="D." surname="Mitton" fullname="D. Mitton">
<organization/>
</author>
<date year="2001" month="August"/>
<abstract>
<t>This document specifies the operation of RADIUS (Remote Authentication Dial In User Service) when run over IPv6 as well as the RADIUS attributes used to support IPv6 network access. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="3162"/>
<format type="TXT" octets="20492" target="http://www.rfc-editor.org/rfc/rfc3162.txt"/>
</reference>
<reference anchor="RFC3418">
<front>
<title>Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)</title>
<author initials="R." surname="Presuhn" fullname="R. Presuhn">
<organization/>
</author>
<date year="2002" month="December"/>
<abstract>
<t>This document defines managed objects which describe the behavior of a Simple Network Management Protocol (SNMP) entity. This document obsoletes RFC 1907, Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2). [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="STD" value="62"/>
<seriesInfo name="RFC" value="3418"/>
<format type="TXT" octets="49096" target="http://www.rfc-editor.org/rfc/rfc3418.txt"/>
</reference>
<reference anchor="RFC5607">
<front>
<title>Remote Authentication Dial-In User Service (RADIUS) Authorization for Network Access Server (NAS) Management</title>
<author initials="D." surname="Nelson" fullname="D. Nelson">
<organization/>
</author>
<author initials="G." surname="Weber" fullname="G. Weber">
<organization/>
</author>
<date year="2009" month="July"/>
<abstract>
<t>This document specifies Remote Authentication Dial-In User Service (RADIUS) attributes for authorizing management access to a Network Access Server (NAS). Both local and remote management are supported, with granular access rights and management privileges. Specific provisions are made for remote management via Framed Management protocols and for management access over a secure transport protocol. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="5607"/>
<format type="TXT" octets="55464" target="http://www.rfc-editor.org/rfc/rfc5607.txt"/>
</reference>
<reference anchor="RFC1035">
<front>
<title abbrev="Domain Implementation and Specification">Domain names - implementation and specification</title>
<author initials="P." surname="Mockapetris" fullname="P. Mockapetris">
<organization>USC/ISI</organization>
<address>
<postal>
<street>4676 Admiralty Way</street>
<city>Marina del Rey</city>
<region>CA</region>
<code>90291</code>
<country>US</country>
</postal>
<phone>+1 213 822 1511</phone>
</address>
</author>
<date year="1987" day="1" month="November"/>
</front>
<seriesInfo name="STD" value="13"/>
<seriesInfo name="RFC" value="1035"/>
<format type="TXT" octets="125626" target="http://www.rfc-editor.org/rfc/rfc1035.txt"/>
</reference>
<reference anchor="RFC5966">
<front>
<title>DNS Transport over TCP - Implementation Requirements</title>
<author initials="R." surname="Bellis" fullname="R. Bellis">
<organization/>
</author>
<date year="2010" month="August"/>
<abstract>
<t>This document updates the requirements for the support of TCP as a transport protocol for DNS implementations. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="5966"/>
<format type="TXT" octets="14970" target="http://www.rfc-editor.org/rfc/rfc5966.txt"/>
</reference>
<reference anchor="FIPS.180-3.2008" target="http://csrc.nist.gov/publications/fips/fips180-3/fips180-3_final.pdf">
<front>
<title>Secure Hash Standard</title>
<author>
<organization>National Institute of Standards and Technology</organization>
</author>
<date month="October" year="2008"/>
</front>
<seriesInfo name="FIPS" value="PUB 180-3"/>
</reference>
<reference anchor="IEEE-1003.1-2008">
<front>
<title>POSIX.1-2008</title>
<author>
<organization>Institute of Electrical and Electronics Engineers</organization>
</author>
<date month="March" year="2008"/>
</front>
<seriesInfo name="IEEE" value="Standard 1003.1"/>
</reference>
<reference anchor="RFC6991">
<front>
<title>Common YANG Data Types</title>
<author initials="J." surname="Schoenwaelder" fullname="J. Schoenwaelder">
<organization/>
</author>
<date year="2013" month="July"/>
<abstract>
<t>This document introduces a collection of common data types to be used with the YANG data modeling language. This document obsoletes RFC 6021.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="6991"/>
<format type="TXT" octets="60242" target="http://www.rfc-editor.org/rfc/rfc6991.txt"/>
</reference>
</references>
<references title="Informative References">
<reference anchor="RFC3579">
<front>
<title>RADIUS (Remote Authentication Dial In User Service) Support For Extensible Authentication Protocol (EAP)</title>
<author initials="B." surname="Aboba" fullname="B. Aboba">
<organization/>
</author>
<author initials="P." surname="Calhoun" fullname="P. Calhoun">
<organization/>
</author>
<date year="2003" month="September"/>
<abstract>
<t>This document defines Remote Authentication Dial In User Service (RADIUS) support for the Extensible Authentication Protocol (EAP), an authentication framework which supports multiple authentication mechanisms. In the proposed scheme, the Network Access Server (NAS) forwards EAP packets to and from the RADIUS server, encapsulated within EAP-Message attributes. This has the advantage of allowing the NAS to support any EAP authentication method, without the need for method- specific code, which resides on the RADIUS server. While EAP was originally developed for use with PPP, it is now also in use with IEEE 802. This memo provides information for the Internet community.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="3579"/>
<format type="TXT" octets="104469" target="http://www.rfc-editor.org/rfc/rfc3579.txt"/>
</reference>
<reference anchor='RFC3688'>
<front>
<title>The IETF XML Registry</title>
<author initials='M.' surname='Mealling' fullname='M. Mealling'>
<organization /></author>
<date year='2004' month='January' />
<abstract>
<t>This document describes an IANA maintained registry for IETF standards which use Extensible Markup Language (XML) related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas.</t></abstract></front>
<seriesInfo name='BCP' value='81' />
<seriesInfo name='RFC' value='3688' />
<format type='TXT' octets='17325' target='http://www.rfc-editor.org/rfc/rfc3688.txt' />
</reference>
<reference anchor='RFC6557'>
<front>
<title>Procedures for Maintaining the Time Zone Database</title>
<author initials='E.' surname='Lear' fullname='E. Lear'>
<organization /></author>
<author initials='P.' surname='Eggert' fullname='P. Eggert'>
<organization /></author>
<date year='2012' month='February' />
<abstract>
<t>Time zone information serves as a basic protocol element in protocols, such as the calendaring suite and DHCP. The Time Zone (TZ) Database specifies the indices used in various protocols, as well as their semantic meanings, for all localities throughout the world. This database has been meticulously maintained and distributed free of charge by a group of volunteers, coordinated by a single volunteer who is now planning to retire. This memo specifies procedures involved with maintenance of the TZ database and associated code, including how to submit proposed updates, how decisions for inclusion of those updates are made, and the selection of a designated expert by and for the time zone community. The intent of this memo is, to the extent possible, to document existing practice and provide a means to ease succession of the database maintainers. This memo documents an Internet Best Current Practice.</t></abstract></front>
<seriesInfo name='BCP' value='175' />
<seriesInfo name='RFC' value='6557' />
<format type='TXT' octets='18469' target='http://www.rfc-editor.org/rfc/rfc6557.txt' />
</reference>
</references>
</back></rfc>
| PAFTECH AB 2003-2026 | 2026-04-22 04:56:26 |