Subject: [Netconf] Summary of action items, decisions, etc. from the NETCONF session

From: "Bert Wijnen \(IETF\)" <[email-masked]>
Date: Thu, 26 Mar 2009 17:33:52 -0700

AIs, decisions, etc. from the NETCONF sessionWG participants,

Here is a summary of actions, decisions and directions we took at our meeting 
at IETF74.

Partial Lock: 
-  Balazs to prepare the text for the two clarifications 
   (lock-ID, Primary use case is for writable-running) to be used in 
   RFC editor's note.  (to be done no later than next week;
   has been posted already)

Monitoring: 
- We need to ask Mark Scott whether he is able to continue to act
  as editor. If not we can ask Martin to pick up the pen.
- Washam to bring his concern on missing monitoring of non-netconf
   locks to the maillist.  
- Possible need for a string indicating which system or protocol is
  holding the lock. 
- Martin to send the results of the counter discussion to the maillist 

With-defaults: 
- Balazs to simplify with-default values as proposed in the session 4741bis: 
- Decision on the validate operation handling: 
     Alternative 1: + 10, - 0   
     Alternative 2: + 0 
     Alternative 2+ test option: + 7 
   Martin to bring it to maillist for confirmation and to bring text proposals 
   for the discussed issues to the maillist. 

rfc4741bis:
- Martin will bring other 4741bis issues for discussion to the maillist.  
  in the coming weeks in april.

Other activities:
- Bob Cole to update his draft to use the NETCONF terminology.
   Also to address all comments already raised during the presentation
 
- The discussion on "Generic solution on message integrity" showed
   that there are two favored options:
     a) extending the security considerations section of SSH,
     b) introducing escaping mechanism for all transports using streaming.
   Interested parties to trigger a discussion on the maillist based on 
   a written draft. 

- There was a sense in the room for enabling YANG to define XML 
   attributes based on YANG extensions and using YANG for the
   definition of NETCONF base module. 
   Additional discussion in the NETMOD session the day after 
   lead to a consensus in this direction. 
   Andy Bierman will bring the consensus in the NETMOD session 
   to the NETCONF maillist for confirmation. 

Bert and Mehmet