YANG Module for NETCONF Monitoring
draft-ietf-netconf-monitoring-15

netconf-state
    /capabilities
    /datastores
    /schemas
    /sessions
    /statistics

configuration
    /name
    /locks

schema
    /identifier   (key)
    /version      (key)
    /format       (key)
    /namespace
    /location

session
    /session-id (key)
    /transport
    /username
    /source-host
    /login-time
    /in-rpcs
    /in-bad-rpcs
    /out-rpc-errors
    /out-notifications

statistics
    /netconf-start-time
    /in-bad-hellos
    /in-sessions
    /dropped-sessions
    /in-rpcs
    /in-bad-rpcs
    /out-rpc-errors
    /out-notifications

<rpc message-id="101"
     xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <get>
    <filter type="subtree">
      <netconf-state xmlns=
      "urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring">
        <schemas/>
      </netconf-state>
    </filter>
  </get>
</rpc>


The NETCONF server returns a list of schema available for
retrieval.


<rpc-reply message-id="101"
           xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <data>
    <netconf-state
    xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring">
      <schemas>
        <schema>
          <identifier>foo</identifier>
          <version>1.0</version>
          <format>xsd</format>
          <namespace>http://example.com/foo</namespace>
          <location>ftp://ftp.example.com/schemas/foo_1.0.xsd</location>
          <location>http://www.example.com/schema/foo_1.0.xsd</location>
          <location>NETCONF</location>
        </schema>
        <schema>
          <identifier>foo</identifier>
          <version>1.1</version>
          <format>xsd</format>
          <namespace>http://example.com/foo</namespace>
          <location>ftp://ftp.example.com/schemas/foo_1.1.xsd</location>
          <location>http://www.example.com/schema/foo_1.1.xsd</location>
          <location>NETCONF</location>
        </schema>
        <schema>
          <identifier>bar</identifier>
          <version>2008-06-01</version>
          <format>yang</format>
          <namespace>http://example.com/bar</namespace>
          <location>
            http://example.com/schema/bar@2008-06-01.yang
          </location>
          <location>NETCONF</location>
        </schema>
        <schema>
          <identifier>bar-types</identifier>
          <version>2008-06-01</version>
          <format>yang</format>
          <namespace>http://example.com/bar</namespace>
          <location>
            http://example.com/schema/bar-types@2008-06-01.yang
          </location>
          <location>NETCONF</location>
        </schema>
      </schemas>
    </netconf-state>
  </data>
</rpc-reply>

  1.  foo,  version 1.0 in xsd format:

    a.  Via FTP using location
        ftp://ftp.example.com/schemas/foo_1.0.xsd

    b.  Via HTTP using location
        http://www.example.com/schema/foo_1.0.xsd

    c.  Via <get-schema> using identifier, version, and
    format parameters.


    <rpc message-id="101"
      xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
      <get-schema
      xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring">
        <identifier>foo</identifier>
        <version>1.0</version>
        <format>xsd</format>
      </get-schema>
    </rpc>

    <rpc-reply message-id="101"
      xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
      <data
      xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring">
        <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
          <!-- foo 1.0 xsd schema contents here -->
        </xs:schema>
      </data>
    </rpc-reply>

  2. bar, version 2008-06-01 in YANG format:

    a.  Via HTTP using location
        http://example.com/schema/bar@2008-06-01.yang

    b.  Via <get-schema> using identifer and version
        parameters:

      <rpc message-id="102"
        xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
        <get-schema
        xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring">
          <identifer>bar</identifer>
          <version>2008-06-01</version>
        </get-schema>
      </rpc>

      <rpc-reply message-id="102"
        xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
        <data
        xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring">
          module bar {
            //default format (yang) returned
            //bar version 2008-06-01 yang module
            //contents here ...
          }
        </data>
      </rpc-reply>


  3. bar-types, version 2008-06-01 in default YANG format:

    a. Via <get-schema> using identifer parameter:

    <rpc message-id="103"
      xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
      <get-schema
      xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring">
        <identifer>bar-types</identifer>
      </get-schema>
    </rpc>

    <rpc-reply message-id="103"
      xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
      <data
      xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring">
        module bar-types {
          //default format (yang) returned
          //latest revision returned
          //is version 2008-06-01 yang module
          //contents here ...
        }
      </data>
    </rpc-reply>

<CODE BEGINS>

module ietf-netconf-monitoring {

  namespace "urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring";
  prefix "ncm";

  import ietf-yang-types { prefix yang; }
  import ietf-inet-types { prefix inet; }

  organization
    "IETF NETCONF (Network Configuration) Working Group";

  contact
    "WG Web:   <http://tools.ietf.org/wg/netconf/>
     WG List:  <mailto:netconf@ietf.org>

     WG Chair: Mehmet Ersue
               <mailto:mehmet.ersue@nsn.com>

     WG Chair: Bert Wijnen
               <mailto:bertietf@bwijnen.net>

     Editor:   Mark Scott
               <mailto:mark.scott@ericsson.com>

     Editor:   Martin Bjorklund
               <mailto:mbj@tail-f.com>";

  description
    "NETCONF Monitoring Module.
     All elements in this module are read-only.

     Copyright (c) 2010 IETF Trust and the persons identified as
     the document authors.  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

  revision 2010-06-22 {
    description
      "Initial revision.";
    reference
      "RFC XXXX: YANG Module for NETCONF Monitoring";
  // RFC Ed.: replace XXXX with actual RFC number and remove this note
  }

  typedef netconf-datastore-type {
    type enumeration {
      enum running;
      enum candidate;
      enum startup;
    }
    description
      "Enumeration of possible NETCONF datastore types.";
    reference
      "RFC 4741: NETCONF Configuration Protocol";
  }

  identity transport {
    description
      "Base identity for NETCONF transport types.";
  }

  identity netconf-ssh {
    base transport;
    description
      "NETCONF over Secure Shell (SSH).";
    reference
      "RFC 4742: Using the NETCONF Configuration Protocol
                 over Secure SHell (SSH)";
  }

  identity netconf-soap-over-beep {
    base transport;
    description
      "NETCONF over Simple Object Access Protocol (SOAP) over
       Blocks Extensible Exchange Protocol (BEEP).";
    reference
      "RFC 4743: Using NETCONF over the Simple Object
                 Access Protocol (SOAP)";
  }

  identity netconf-soap-over-https {
    base transport;
    description
      "NETCONF over Simple Object Access Protocol (SOAP)
      over Hypertext Transfer Protocol Secure (HTTPS).";
    reference
      "RFC 4743: Using NETCONF over the Simple Object
                 Access Protocol (SOAP)";
  }

  identity netconf-beep {
    base transport;
    description
      "NETCONF over Blocks Extensible Exchange Protocol (BEEP).";
    reference
      "RFC 4744: Using the NETCONF Protocol over the
                 Blocks Extensible Exchange Protocol (BEEP)";
  }

  identity netconf-tls {
    base transport;
    description
      "NETCONF over Transport Layer Security (TLS).";
    reference
      "RFC 5539: NETCONF over Transport Layer Security (TLS)";
  }

  identity schema-format {
    description
      "Base identity for data model schema languages.";
  }

  identity xsd {
    base schema-format;
    description
      "W3C XML Schema Definition.";
    reference
      "W3C REC REC-xmlschema-1-20041028:
         XML Schema Part 1: Structures";
  }

  identity yang {
    base schema-format;
    description
      "The YANG data modeling language for NETCONF.";
    reference
      "RFC YYYY:  YANG - A data modeling language for NETCONF";
   // RFC Ed.: replace YYYY with actual RFC number and remove this note
  }

  identity yin {
    base schema-format;
    description
      "The YIN syntax for YANG.";
    reference
      "RFC YYYY:  YANG - A data modeling language for NETCONF";
   // RFC Ed.: replace YYYY with actual RFC number and remove this note
  }

  identity rng {
    base schema-format;
    description
      "Regular Language for XML Next Generation (RELAX NG).";
    reference
      "ISO/IEC 19757-2:2008: RELAX NG";
  }

  identity rnc {
    base schema-format;
    description
      "Relax NG Compact Syntax";
    reference
      "ISO/IEC 19757-2:2008: RELAX NG";
  }

  grouping common-counters {
    description
      "Counters that exist both per session, and also globally,
       accumulated from all sessions.";

    leaf in-rpcs {
      type yang:zero-based-counter32;
      description
        "Number of correct <rpc> messages received.";
    }
    leaf in-bad-rpcs {
      type yang:zero-based-counter32;
      description
        "Number of messages received when a <rpc> message was expected,
         that were not correct <rpc> messages.  This includes XML parse
         errors and errors on the rpc layer.";
    }
    leaf out-rpc-errors {
      type yang:zero-based-counter32;
      description
        "Number of <rpc-reply> messages sent which contained an
         <rpc-error> element.";
    }
    leaf out-notifications {
      type yang:zero-based-counter32;
      description
        "Number of <notification> messages sent.";
    }
  }

  container netconf-state {
    config false;
    description
      "The netconf-state container is the root of the monitoring
       data model.";

    container capabilities {
      description
        "Contains the list of NETCONF capabilities supported by the
         server.";

      leaf-list capability {
        type inet:uri;
        description
          "List of NETCONF capabilities supported by the server.";
      }
    }

    container datastores {
      description
        "Contains the list of NETCONF configuration datastores.";

      list datastore {
        key name;
        description
          "List of NETCONF configuration datastores supported by
           the NETCONF server and related information.";

        leaf name {
          type netconf-datastore-type;
          description
            "Name of the datastore associated with this list entry.";
        }
        container locks {
          presence
            "This container is present only if the datastore
             is locked.";
          description
            "The NETCONF <lock> and <partial-lock> operations allow
             a client to lock specific resources in a datastore.  The
             NETCONF server will prevent changes to the locked
             resources by all sessions except the one which acquired
             the lock(s).

             Monitoring information is provided for each datastore
             entry including details such as the session which acquired
             the lock, the type of lock (global or partial) and the
             list of locked resources.  Multiple locks per datastore
             are supported.";

          grouping lock-info {
            description
              "Lock related parameters, common to both global and
               partial locks.";

            leaf locked-by-session {
              type uint32;
              mandatory true;
              description
                "The session ID of the session that has locked
                 this resource.  Both a global lock and a partial
                 lock MUST contain the NETCONF session-id.

                 If the lock is held by a session which is not managed
                 by the NETCONF server (e.g., a CLI session), a session
                 id of 0 (zero) is reported.";
              reference
                "RFC 4741: NETCONF Configuration Protocol";
            }
            leaf locked-time {
              type yang:date-and-time;
              mandatory true;
              description
                "The date and time of when the resource was
                 locked.";
            }
          }

          choice lock-type {
            description
              "Indicates if a global lock or a set of partial locks
               are set.";

            container global-lock {
              description
                "Present if the global lock is set.";
              uses lock-info;
            }

            list partial-locks {
              key lock-id;
              description
                "List of partial locks.";
              reference
                "RFC 5717: Partial Lock Remote Procedure Call (RPC) for
                           NETCONF";

              leaf lock-id {
                type uint32;
                description
                  "This is the lock id returned in the <partial-lock>
                   response.";
              }
              uses lock-info;
              leaf-list select {
                type string;
                min-elements 1;
                description
                  "The xpath expression which was used to request
                   the lock.  The select expression indicates the
                   original intended scope of the lock.";
              }
              leaf-list locked-nodes {
                type instance-identifier;
                description
                  "The list of instance-identifiers (i.e., the
                   locked nodes).

                   The scope of the partial lock is defined by the list
                   of locked nodes.";
              }
            }
          }
        }
      }
    }

    container schemas {
      description
        "Contains the list of data model schemas supported by the
         server.";

      list schema {
        key "identifier version format";

        description
          "List of data model schemas supported by the server.";

        leaf identifier {
          type string;
          description
            "Identifier to uniquely reference the schema.  The
             identifier is used in the <get-schema> operation and may
             be used for other purposes such as file retrieval.

             For modeling languages which support or require a data
             model name (e.g., YANG module name) the identifier MUST
             match that name.  For YANG data models, the identifier is
             the name of the module or submodule.  In other cases an
             identifier such as a filename MAY be used instead.";
        }
        leaf version {
          type string;
          description
            "Version of the schema supported.  Multiple versions MAY be
             supported simultaneously by a NETCONF server.  Each
             version MUST be reported individually in the schema list,
             i.e., with same identifier, possibly different location,
             but different version.

             For YANG data models, version is the value of the most
             recent YANG 'revision' statement in the module or
             submodule, or the empty string if no revision statement
             is present.";
        }
        leaf format {
          type identityref {
            base schema-format;
          }
          description
            "The data modeling language the schema is written
             in (currently xsd, yang, yin, rng or rnc).

             For YANG data models, 'yang' format MUST be supported and
             'yin' format MAY also be provided.";
        }
        leaf namespace {
          type inet:uri;
          mandatory true;
          description
            "The XML namespace defined by the data model.

             For YANG data models, this is the module's namespace.
             If the list entry describes a submodule, this field
             contains the namespace of the module to which the
             submodule belongs.";
        }
        leaf-list location {
          type union {
            type enumeration {
              enum "NETCONF";
            }
            type inet:uri;
          }
          description
            "One or more locations from which the schema can be
             retrieved. This list SHOULD contain at least one
             entry per schema.

             A schema entry may be located on a remote file system
             (e.g., reference to file system for ftp retrieval) or
             retrieved directly from a server supporting the
             <get-schema> operation (denoted by the value 'NETCONF').";
        }
      }
    }

    container sessions {
      description
        "The sessions container includes session specific data for
         NETCONF management sessions.  The session list MUST include
         all currently active NETCONF sessions.";

      list session {
        key session-id;
        description
          "All NETCONF sessions managed by the NETCONF server
           MUST be reported in this list.";

        leaf session-id {
          type uint32 {
            range "1..max";
          }
          description
            "Unique identifier for the session.  This value is the
             NETCONF session identifier, as defined in RFC4741.";
          reference
            "RFC 4741: NETCONF Configuration Protocol";
        }
        leaf transport {
          type identityref {
            base transport;
          }
          mandatory true;
          description
            "Identifies the transport for each session, e.g.,
            'netconf-ssh', 'netconf-soap', etc.";
        }
        leaf username  {
          type string;
          mandatory true;
          description
            "The username is the client identity that was authenticated
            by the NETCONF transport protocol. The algorithm used to
            derive the username is NETCONF transport protocol specific
            and in addition specific to the authentication mechanism
            used by the NETCONF transport protocol.";
        }
        leaf source-host {
          type inet:host;
          description
            "Host identifier of the NETCONF client.  The value
             returned is implementation specific (e.g., hostname,
             IPv4 address, IPv6 address)";
        }
        leaf login-time {
          type yang:date-and-time;
          mandatory true;
          description
            "Time at the server at which the session was established.";
        }
        uses common-counters {
          description
            "Per-session counters.  Zero based with following reset
             behaviour:
               - at start of a session
               - when max value is reached";
        }
      }
    }

    container statistics {
      description
        "Statistical data pertaining to the NETCONF server.";

      leaf netconf-start-time {
        type yang:date-and-time;
        description
          "Date and time at which the management subsystem was
           started.";
      }
      leaf in-bad-hellos {
        type yang:zero-based-counter32;
        description
          "Number of sessions silently dropped because an
          invalid <hello> message was received.  This includes hello
          messages with a 'session-id' attribute, bad namespace, and
          bad capability declarations.";
      }
      leaf in-sessions {
        type yang:zero-based-counter32;
        description
          "Number of sessions started.  This counter is incremented
           when a <hello> message with a <session-id> is sent.

          'in-sessions' - 'in-bad-hellos' =
              'number of correctly started netconf sessions'";
      }
      leaf dropped-sessions {
        type yang:zero-based-counter32;
        description
          "Number of sessions that were abnormally terminated, e.g.,
           due to idle timeout or transport close.  This counter is not
           incremented when a session is properly closed by a
           <close-session> operation, or killed by a <kill-session>
           operation.";
      }
      uses common-counters {
        description
          "Global counters, accumulated from all sessions.
           Zero based with following reset behaviour:
             - re-initialization of NETCONF server
             - when max value is reached";
      }
    }
  }

  rpc get-schema {
    description
      "This operation is used to retrieve a schema from the
       NETCONF server.

       Positive Response:
         The NETCONF server returns the requested schema.

       Negative Response:
         If requested schema does not exist, the <error-tag> is
         'invalid-value'.

         If more than one schema matches the requested parameters, the
         <error-tag> is 'operation-failed', and <error-app-tag> is
         'data-not-unique'.";

    input {
      leaf identifier {
        type string;
        mandatory true;
        description
          "Identifier for the schema list entry.";
      }
      leaf version {
        type string;
        description
          "Version of the schema requested.  If this parameter is not
           present, and more than one version of the schema exists on
           the server, a 'data-not-unique' error is returned, as
           described above.";
      }
      leaf format {
        type identityref {
          base schema-format;
        }
        description
           "The data modeling language of the schema.  If this
            parameter is not present, and more than one formats of
            the schema exists on the server, a 'data-not-unique' error
            is returned, as described above.";
      }
    }
    output {
        anyxml data {
          description
            "Contains the schema content.";
      }
    }
  }
}

<CODE ENDS>

  URI: urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring
  Registrant Contact: The IESG.
  XML: N/A, the requested URI is an XML namespace.

  name: ietf-netconf-monitoring
  namespace: urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring
  prefix: ncm
  reference: RFCXXXX

- removed the session-id and session-id-or-zero typedefs from the
  YANG module

- updated after AD and Gen-Art reviews
- Sec 6:  new security text template (rev4) used
- updated IANA considerations to reference Yang Module Names registry
- updated references to latest versions
- removed unused informative reference to rfc5277
- updated username description to specify SSH algorithm
- updated <get-schema> negative response
- Yang Module changes:
  - added Martin to list of contacts
  - prefix changed to 'ncm' (netconf monitoring)
  - grouping netconf-datastore-type is now an enumeration
  - netconf-over-soap-over-beep description update
  - netconf-over-soap-over-https description update
  - yang identity description update
  - yin identity description update
  - fixed reference statement in yin identity
  - capabilities leaf-list description update
  - added presence statement to locks container
  - name changed from container to leaf node
  - name key added for datastores list
  - added typedef sessionid-or-zero
  - locked-time now mandatory
  - lock-type description added
  - schemas description added
  - schema description added
  - namespace now mandatory

- updated for AD review

- updated URI and YANG module revision
- updated sec 5 title to align with other text
- updated Acknowledgements
- added Description statements to identityrefs in the YANG module
- updated document expiry
- updated document title to v11
- sec 1.1:  removed 'schema' definition;  it will be placed in one of
the base NETCONF documents instead (i.e. 4741bis)
- sec 2:  reworded 'The NETCONF monitoring data defined' to 'The NETCONF
monitoring data model defined'
- sec 2.1:  reworded 'The /netcong-state subtree...' to
'The netconf-state container...'
- sec 2.1:  reworded 'List of NETCONF datastores...' to
'Includes all supported datastore types...'
- sec 2.1:  removed '(Container)' for consistency
- sec 2.1.3:  reworded format to remove file/module with schema
- sec 2.1.3 reworded 'The data modeling language of the file/module...'
to 'The data modeling language the schema is written in...' removing
references to files/modules.
- sec 2.1.3: reworded 'defined by the data model' to 'defined by the
schema'
- sec 2.1.3: reworded namespace from 'by the data model' to 'by the
schema'
- sec 2.1.4 changed '[NETCONF Configuration Protocol]' to '[RFC4741]'
- sec 4.1 simplified wording in this section.  Specifically removed the
SHOULD and MUST statements which are already qualified in sec 2.1.3 and
in YANG the module
- sec 4.1 to address comment about lack of standardized sftp definition
changed 'sftp' to 'ftp' and updated examples to use standardized ftp URI
- sec 4.1 reworded 'data models' to 'schema'
- sec 4.1 updated YANG example URI to use '@' instead of '-'
- sec 4.2 updated YANG example URI to use '@' instead of '-'
- YANG module, revision statement: changed RFC title to match draft name
- YANG module, container netconf-state: updated description to match
sec 2.1
- YANG module, container datastores: updated description
- YANG module, list partial-locks:  added reference to RFC5717
- YANG module,leaf-list locked-nodes:  removed text which was
inconsistent with partial lock RFC
- YANG module, leaf format:  updated description to match sec 2.1.3
- YANG module, container sessions:  updated description to match
sec 4.1
- YANG module, leaf source-host:  updated description to clarify
that identifier is likely to be implementation specific per sec 2
- References:  moved YANG, Common Yang Data Types and XML from
informative to normative
- References:  updated partial lock details to RFC5717

- sec 1.1, updated schema definition, removed YANG definition (it is
  in references instead)
- reworded text in Intro about NETCONF clients adjusting 'capabilities',
  per agreement that capacbilities can not change in a session (per
  4741bis)
- introduction, removed description of NETCONF behaviour for schema
  changes on active sesssions.  Has been moved to 4741bis
- updated namespace from '*:ns:netconf::state' to
  '*:yang:ns:ietf-netconf-monitoring:DRAFT-10'
  For details see ML archive:
  'http://www.ietf.org/mail-archive/web/netconf/current/msg05296.html'
- moved majority of sec 2 into the yang module (making module self
  describing), leaving only overview text in the RFC body.
  For details see ML archive:
  'http://www.ietf.org/mail-archive/web/netconf/current/msg05209.html'
- reworded definition of 'schema'
- removed residual references to XSD types (i.e. xs:string)
- reworded text that schema may not always be retrievable
- will add additional text that yang format is both the default
  and mandatory;  yin is optional
- updated text per Juergen's WGLC comments on v09.
  For details see ML arhive:
  'http://www.ietf.org/mail-archive/web/netconf/current/msg05306.html'
- updated reference in sec 1.1 for RFC2119
- title change to 'YANG Module for NETCONF Monitoring'

- reversion of 'session-type' to 'transport'
- element naming consistency.  All lowerCamelCase names have been
  converted to 'hyphen-delimited' or 'netconf-style-naming' as it is
  sometimes referred to on the ML.  E.g.  'sessionType' ->
  'session-type'.  This change impacts both the draft text and yang
  module.
- <get-schema> operation updated:
        - now has only one mandatory parameter, 'identifier'
        - updated negative responses, including the rpc operation
        description in yang module
- comments added to the yang module indicating that the definition of
  'session-id' is consistent with 4741bis 'session-id-type' and could
  be imported from that pending RFC.  Similar for
  'netconf-datastore-type'. This was in favour of adding further
  dependencies and delays by waiting for 4741bis to complete.

- Addresses action items from IETF75 and mailing list comments
- Most significant is the decision to adopt YANG as normative
  As a result the publication of this draft depends on:
    o WGLC updates (if required)
    o updates to the normative model as result of netmod YANG
      changes (if required)
    o data organization changes if WG adopts a new data
      hierarchy for netmod (this draft uses "/netconf-state/")
- XML Schema of model and IP host definition have been removed

- updates the examples in sec 4.2 per ML discussion

- replaced references to 'schema-retrieval capability' with
'<get-schema> operation'
- upper/lowercase alignment on references to 'format'
- changed negative response for <get-schema> to 'data-missing'
- ML comments on v05 which required changes in the draft:
  o 2.1.2:  reworded to avoid suggestion that configurable data was
    contained in the sub-tree (per Balazs' request)
  o 2.1.2:  reworded paragraph partial lock and select statements
    (per Balazs' suggested text)
  o Fixed examples in 3.1 and added negative response (per Balazs'
    comment)
  o YANG:  location changed to leaf-list (per Balazs' comment)
  o added non-normative references to yang and yang-types (per Balazs'
    comment)
  o 2.1.3:  added YIN and RNC to format 'enums' text and models

This version addresses action items from IETF74 and comments on v4.
- updated statistics (and counter definitions) per offline discussion:
- updated counter definitions
- updated data types  (addition of ZeroBasedCounter32)
- per session counters;  see section 2.1.4
- global counters;  see section 2.1.5
- unique sessionId handling and WG consensus:
  o expected handling of NETCONF and non-NETCONF sessions defined
  o explicit exclusion of sessionId=0 added
  o see section 2.1.4
- removal of subscriptions subtree;  was sec 2.1.5 in v4
- revised XSD and YANG models

- New RPC operation defined <get-schema<, replacing
  <list-schema>.
- Updated Abstract and Introduction:  new text, removed NETCONF
  protocol diagram.
- Changed /netconfstate/ to /netconf-state
- Added netconf-state/datastores
- Changed /netconf-state/schema to /netconf-state/schemas
- Added /netconf-state/statistics
- Added /schema/format (and added to key)
- Added /schema/namespace (and added to key)
- Updated examples.
- More detailed monitored data descriptions per ML comments.

- incorporates ML list comments on v-02.

- Merged content from 'draft-scott-netconf-schema-query' into this draft
- this draft now covers both schema retrievel and monitoring

- WG first draft, 'draft-ietf-netconf-monitoring-01'.
- Related draft 'draft-scott-netconf-schema-query-00' also presented
  covering schema retrieval.  Query draft proposes new NETCONF
  operations to retrieve schema defined in this draft.

- Initial draft, 'draft-scott-monitoring-00'
- based on 'draft-netconf-chisholm-monitoring-02'
- adopted as working group document at IETF69.