[Netconf] FW: AUTH48 [MF]: RFC 6022 <draft-ietf-netconf-monitoring-15.txt> NOW AVAILABLE

["Ersue, Mehmet (NSN - DE/Munich)" <[e-mail]>]

Dear NETCONF WG,

the NETCONF Monitoring draft is in the AUTH48 phase and the 
editors proposed the changes below as last minute editorial
changes. 

The change on "p 4. list datastore" vs. "list configuration"
has not been posted to the ML before, which solves an 
inconcistency between the sections 2.1.2 and 5. 

We put AUTH48 on hold to get your approval on this. Please 
speak up if you have any strong concerns with this particular 
change by September 27, 2010, 11am EDT.

Mehmet


-----Original Message-----
From: Martin Bjorklund [mailto:[e-mail]] 
Sent: September-23-10 9:08 AM
To: [e-mail]
Cc: Mark Scott; [e-mail];
[e-mail]
Subject: Re: AUTH48 [MF]: RFC 6022
<draft-ietf-netconf-monitoring-15.txt> NOW AVAILABLE

Hi,

I have reviewed the document and the changes made so far.  I'm
including new changes in OLD/NEW format below.

RFC Editor <[e-mail]> wrote:
> 2) Section 2: Data Model to Monitor NETCONF
> 
>    A server that implements the data model defined in this document
>    MUST advertise the capability URI
>    "urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring", as described
>    in [RFC6020].
> 
> <!-- [rfced] The above sounds as though 
> "urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring" was registered
in RFC
> 6020.  Perhaps this could be rephrased as:
> 
>         A server that implements the data model defined in this
>         document
("urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring") 
>         MUST advertise the capability URI as described in <xref
>         target="RFC6020"/>.
> -->

I see the point.  Actually, the entire paragraph is redundant, since
YANG defines what MUST be advertised.  But if we want to make as few
changes as possible, the proposed text is fine.


p. 4  (the list is called "list datatore", not "list configuration"
       in the data model)
OLD:

   The /netconf-state/datastores subtree contains the list of available
   datastores for the NETCONF server and includes information on their
   lock state.

   configuration
       /name
       /locks

NEW:

   The /netconf-state/datastores subtree contains the list of available
   datastores for the NETCONF server and includes information on their
   lock state.

   datastore
       /name
       /locks


p. 6
OLD:

      Identifies transport for each session.  The transport is

NEW:

      Identifies the transport for each session.  The transport is


p. 6 (make terminology consitent)
OLD:

   in-rpcs (yang:zero-based-counter32)
      Number of correct <rpc> requests received.

NEW:

   in-rpcs (yang:zero-based-counter32)
      Number of correct <rpc> messages received.


p. 7
OLD:

   in-rpcs (yang:zero-based-counter32)
      Number of correct <rpc> requests received.

NEW:

   in-rpcs (yang:zero-based-counter32)
      Number of correct <rpc> messages received.


p. 13
OLD:

  revision 2010-06-22 {

NEW:

  revision 2010-09-23 {

(or maybe the date the RFC is published.  The important thing is that
it is not 2010-06-22)


p. 18
OLD:

   list partial-locks {

NEW:

   list partial-lock {


p. 19
OLD:

   leaf-list locked-nodes {

NEW:

   leaf-list locked-node {



/martin