Subject: [Netconf] NETCONF WG Session Summary and AIs from IETF #97

From: "Ersue, Mehmet (Nokia - DE/Munich)" <[email-masked]>
Date: Fri, 18 Nov 2016 08:37:37 +0000

Dear Benoit, NETCONF WG,

below is the NETCONF WG session summary and AIs from IETF #97.

=> This mail is at the same time to verify and validate the discussion result and agreements from the IETF 97 NETCONF session.
=> If there is no strong objection we will execute as agreed in the IETF 97 NETCONF session.

The NETCONF session took place on Thursday, November 17, 2016, from 15:20-17:50 KDT, Seoul, Korea.

- We had approx. 90+ participants in the 2.5 hour NETCONF session,
- We reviewed the status of the WG,
- We had a discussion on chartered documents.

The rough notes from the Etherpad are available at:
http://etherpad.tools.ietf.org:9000/p/notes-ietf-97-netconf?useMonospaceFont=true

- All: Please review the notes on the Etherpad page above and state on the maillist if anything needs to be corrected.

- As part of the WG status discussion the new milestones have been presented. There was a discussion on the schedule of the Restconf Collection draft.
It has been agreed to put it on hold for now. Kent wants to work on it too.
AI: Co-chairs to start a discussion on open issues and clarify how and in which time frame the draft could be addressed.
Though it has been stated that based on dependencies the keystore draft has a much higher priority for the WG.

Chartered items:
    1. Zero Touch Provisioning for NETCONF Call Home (ZeroTouch) - K. Watsen (30 min.)
       https://tools.ietf.org/html/draft-ietf-netconf-zerotouch-11

- The draft seems to be ready to go to WGLC after the next update.
Different people are implementing the draft. Other than Kent people spoke on mic are Rick Taylor, Radek, Andy.
The WG would like to have the review of a DNS expert to clarify whether it works with DHCPv4.
AI Kent: Reach out to DNSOP maillist.
Mehmet asked whether people see any other issue which should be solved before starting WGLC.
The WG supports to go to LC.

Server Model Drafts: K. Watsen (5 min)
-----------------------------
    2. Keystore Model
       https://tools.ietf.org/html/draft-ietf-netconf-keystore-00
    3. SSH Client Server Models
       https://tools.ietf.org/html/draft-ietf-netconf-ssh-client-server-01
    4. TLS Client Server Models
       https://tools.ietf.org/html/draft-ietf-netconf-tls-client-server-01
    5. NETCONF Client Server Models
       https://tools.ietf.org/html/draft-ietf-netconf-netconf-client-server-01
    6. RESTCONF Client Server Models
       https://tools.ietf.org/html/draft-ietf-netconf-restconf-client-server-01

- Based on the module dependencies the Keystore draft has the highest priority.
After having completed Zerotouch these drafts will be progressed.

    NETCONF Notification Drafts:
    -----------------------------------
    7. Subscribing to YANG datastore push updates - Eric Voit (15 min)
       https://tools.ietf.org/html/draft-ietf-netconf-yang-push-04
    8. Subscribing for Event Notifications (RFC 5277bis) - Eric Voit (10 min)
       https://tools.ietf.org/html/draft-ietf-netconf-rfc5277bis-01
    9. NETCONF Support for Event Notifications - Eric Voit (5 min)
       https://tools.ietf.org/html/draft-ietf-netconf-netconf-event-notifications-01
   10. RESTCONF & HTTP Transport for Event Notifications - Eric Voit (5 min)
       https://tools.ietf.org/html/draft-ietf-netconf-restconf-notif-01

- The co-chairs clarified that the team discussing and working on the notification draft is an informal team open to anyone. It is not a closed design team in IETF terms nominated by chairs/AD. People who want to be involved please approach Eric Voit.
- Different issues have been discussed.
- AI: Eric to bring remaining issues to the maillist.
- Eric requested help in aligning the protocol with gRPC. He will approach gRPC experts he know.
- The notification team had indeed a good progress on the notification drafts. Co-chairs asked the WG to comment on the drafts and clarified that if there is no further comments or issues raised on the maillist the developed solution is going to be seen as stable.
- The drafts being prepared are still subject to review in the WG.

   11. NETCONF Access Control Model - A. Bierman (10 min)
       https://tools.ietf.org/html/draft-bierman-netconf-rfc6536bis-00

- It needs to be clarified whether the schema-mount related text can be put into schema-mount or the NACM draft.
There are different issues which need to be addressed, some related to I2RS. One issue is assigning priorities to clients, second issue is related to access control on the dynamic datastores (e.g. I2RS). Another issue is from RFC 6536 with parent/child relationships which is important for RESTCONF.
Sue Harris will review the draft from I2RS point view and send the issues she sees to NETCONF maillist.
- Mahesh asked to define the format for accounting records. There was support in the room. Remote attendees Martin B., Juergen and Balazs were against having accounting in the same draft. A new draft can be developed.
- Mehmet clarified that we need to understand the open issues and provide initial sections in the draft update. Based on the new version we can discuss the adoption as WG item.

Non-Chartered items:

    1. Voucher and Voucher Revocation Profiles for Bootstrapping Protocols - K. Watsen (15 min)
       https://tools.ietf.org/html/draft-kwatsen-netconf-voucher-00

- Kent stated the draft is mostly done. WG members should comment on the maillist.
- Three WGs could potentially adopt the draft; NETCONF, ANIMA, 6tisch.
- Kent stated that the Zerotouch has use cases for and a normative reference to the voucher draft.
- Benoit wanted to see from the Security ADs if anything (use cases or work) has been done on vouchers.
- There was interest in the room to do the voucher work in NETCONF WG.
- Benoit and the co-chairs agreed to write an email to SEC ADs, ANIMA, 6tisch WG co-chairs and their supporting ADs to figure out which WG should be the home for the voucher draft.

    2. Datastore DT Discussion - Phil Shafer, et.al. (45 min)
       A Revised Conceptual Model for YANG Datastores
       https://tools.ietf.org/html/draft-nmdsdt-netmod-revised-datastores-00

- NETCONF WG supports the DT draft. There are different issues related to the required NETCONF and RESTCONF extensions which need to be discussed and clarified.
- The DT document got the support of NETMOD WG already before the NETCONF session.
- As the datastore concept specified in the current NETCONF RFC is being changed we need to ask for consensus in NETCONF WG too.
After getting the consensus on NETCONF maillist the required charter update and the necessary work for NETCONF and RESTCONF bis-drafts can be started.
- It is already clear that the DT draft will be adopted by NETMOD WG. NETMOD WG itself requires a charter update to start the subsequent work.
- There was some discussion on how to achieve consensus in both WGs in parallel.
It was agreed that NETMOD co-chairs will send a consensus call directed to both WGs to NETCONF and NETMOD ML with one email. The mail will also state that based on the consensus the DT draft will be adopted by NETMOD WG.

Mehmet & Mahesh