Subject: [Netconf] Result of 4742bis WGLC

From: "Ersue, Mehmet (NSN - DE/Munich)" <[email-masked]>
Date: Wed, 12 Jan 2011 21:20:04 +0100

Hi All,

please find below the list of changes I collected so far during WGLC. 
After some discussion in a small group with the co-chairs, Margaret, 
Martin, Andy and Juergen, we think this is now the result of the WG 
last call.

- It came out that less experienced implementer find it as helpful to
see 
the "invisible LineFeed" in the examples. We concluded that "\n" is the 
most common character for this purpose.
- We also concluded that we should stick to "base:1.1" and extend it 
with a new version, which most likely will introduce other changes. 

Margaret is going to prepare a new version by Friday. As planned we 
will use the update for AD review and ask Dan to start the necessary 
process.

Mehmet

------------------------------------------------------------------------
--

Section 4.1
-----------

OLD:
   The previous version of this document defined the character sequence
   "]]<]]>" as a message separator,

NEW:
   The previous version of this document defined the character sequence
   "]]>]]>" as a message separator,

OLD:
(see Section 4.1.1)

NEW:
(see Section 4.2)

OLD:
(see Section 4.1.2)

NEW:
(see Section 4.3)

Section 4.2
------------

OLD:
  could be encoded as:

  #4
  <rpc
  #18
   message-id="102"

  #79
       xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
    <close-session/>
  </rpc>
  ##

NEW:
  could be encoded as (using "\n" as a visible representation of the
LineFeed
  character):

   C:   \n#4\n
   C:   <rpc
   C:   \n#18\n
   C:    message-id="102"\n
   C:   \n#79\n
   C:        xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">\n
   C:     <close-session/>\n
   C:   </rpc>
   C:   \n##\n

OLD:
   Note that there is no newline character after the 'rpc' end tag, so
   there is no blank line generated before the '##' line.

NEW:
  In the second and third chunks quoted above, each line is terminated
by a
  LineFeed.  For all the XML lines (except the last one), this example 
  treats the LineFeed as part of the chunk-data and so contributing to
the 
  chunk-size.
  Note that there is no LineFeed character after the 'rpc' end-tag
  in this message. The LineFeed required by the start of the
end-of-chunks
  block immediately follows the last '>' character in the message.

Section 4.3
------------

OLD:
   To continue the example given above, a NETCONF over SSH session to
   retrieve a set of configuration information might look like this:
NEW:
  A NETCONF over SSH session, using the backwards-compatible
  end-of-message framing, to retrieve a set of configuration
  information might look like this:

OLD:
   C:
   C: #271
   C: <?xml version="1.0" encoding="UTF-8"?>
   C: <rpc message-id="105"
   C:      xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
   C:   <get-config>
   C:     <source><running/></source>
   C:     <config xmlns="http://example.com/schema/1.2/config">
   C:      <users/>
   C:     </config>
   C:   </get-config>
   C: </rpc>
   C:
   C: ##

   S:
   S: #404
   S: <?xml version="1.0" encoding="UTF-8"?>
   S: <rpc-reply message-id="105"
   S:            xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
   S:   <config xmlns="http://example.com/schema/1.2/config">
   S:     <users>
   S:       <user><name>root</name><type>superuser</type></user>
   S:       <user><name>fred</name><type>admin</type></user>
   S:       <user><name>barney</name><type>admin</type></user>
   S:     </users>
   S:   </config>
   S: </rpc-reply>
   S:
   S: ##

NEW:
   C: <?xml version="1.0" encoding="UTF-8"?>
   C: <rpc message-id="105"
   C: xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
   C:   <get-config>
   C:     <source><running/></source>
   C:     <config xmlns="http://example.com/schema/1.2/config">
   C:      <users/>
   C:     </config>
   C:   </get-config>
   C: </rpc>
   C: ]]>]]>

   S: <?xml version="1.0" encoding="UTF-8"?>
   S: <rpc-reply message-id="105"
   S: xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
   S:   <config xmlns="http://example.com/schema/1.2/config">
   S:     <users>
   S:       <user><name>root</name><type>superuser</type></user>
   S:       <user><name>fred</name><type>admin</type></user>
   S:       <user><name>barney</name><type>admin</type></user>
   S:     </users>
   S:   </config>
   S: </rpc-reply>
   S: ]]>]]>

Section 5
----------

OLD:
  To continue the example used in previous sections, an existing	
  NETCONF subsystem session could be closed as follows:

NEW:
  To continue the example used in section 4.2, an existing	
  NETCONF subsystem session could be closed as follows:

OLD:
   C:
   C: #141
   C: <?xml version="1.0" encoding="UTF-8"?>
   C: <rpc message-id="106"
   C:      xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
   C:   <close-session/>
   C: </rpc>
   C: ##

   S:
   S: #140
   S: <?xml version="1.0" encoding="UTF-8"?>
   S: <rpc-reply id="106"
   S:            xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
   S:   <ok/>
   S: </rpc-reply>
   S: ##

NEW:

   C: \n#140\n
   C: <?xml version="1.0" encoding="UTF-8"?>\n
   C: <rpc message-id="106"\n
   C:      xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">\n
   C:   <close-session/>\n
   C: </rpc>
   C: \n##\n

   S: \n#139\n
   S: <?xml version="1.0" encoding="UTF-8"?>\n
   S: <rpc-reply id="106"\n
   S:            xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">\n
   S:   <ok/>\n
   S: </rpc-reply>
   S: \n##\n