# Draft Minutes for the NetMod 111 WG Session (as of Aug 16, 2021)

Please help capture the discussion in-line below.
No need to cover what is on the slides, just the discussion.
Please also (optionally) add you name here:

### Note takers:

Joel Jaeggli

-------------------------------------------------------
# Agenda for the NETMOD 111 WG Session
-------------------------------------------------------
Agenda: https://datatracker.ietf.org/meeting/111/materials/agenda-111-netmod
WG Documents: https://datatracker.ietf.org/wg/netmod/documents/

## Session:
   Tuesday, July 27, 2021
   Session II (21:30-22:30 UTC, 14:30-15:30 PDT)

## WG Chairs:
   Lou Berger    (lberger at labs dot net)
   Kent Watsen (kent plus ietf at watsen dot net)
   Joel Jaeggli    (joelja at bogus dot com)

## Available During Session:
   WG ICS: https://datatracker.ietf.org/meeting/111/sessions/netmod.ics
   ICS: https://datatracker.ietf.org/meeting/111/session/28884.ics
   MeetEcho: https://meetings.conf.meetecho.com/ietf111/?group=netmod
   Jabber:          xmpp:netmod@jabber.ietf.org?join

## Available During / After Session:
   CodiMD:        https://codimd.ietf.org/notes-ietf-111-netmod
   Slides: https://datatracker.ietf.org/meeting/111/session/netmod
   Drafts (TGZ): https://datatracker.ietf.org/meeting/111/agenda/netmod-drafts.tgz
   Drafts (PDF): https://datatracker.ietf.org/meeting/111/agenda/netmod-drafts.pdf

## Available After Session:
   Recording:     http://www.meetecho.com/ietf111/recordings#NETMOD
   Jabber Logs:   https://www.ietf.org/jabber/logs/netmod

# Introduction

commenced at 21:30 utc 

## Chairs (10 minutes)

note well

## Session Intro & WG Status

syslog model 26 needs updates to align with referenced documents so it's back in the working group.

nmda diff  draft version 11 is published. is in post-IESG review

Rob - post last call documents
waiting on ieee feedback on vlan interface model

geo-location doc - has a discuss IESG ben will suggest text, perhaps helpful for Chris, Ben and Rob to meet to resolve.


# Chartered items:

##   YANG Versioning Update (30 min)
   https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-module-versioning/
   https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-semver/
   https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-packages/
   https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-ver-selection/
   https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-schema-comparison/


### 21:39 Overview jason sterne presenting

Kent Watsen: What happens if the imported version breaks backwards compatibility?
Jason Sterne: In the end, keep is simple, and don't need a derived-or-compatible version label.
Kent: Okay, will take it offline, it sounds like it has been discussed.
Jason: Yes, it has definitely been discussed, and we believe that it is right compromise.

### 21:55  YANG Module Versioning Draft - Jason Sterne

Raised by Carsten on chat: Are you sure you want a non-URI- and non-shell-compatible character in your filenames?


###  22:03 YANG Semver Draft - Joe Clarke

questions?

kent - we should come back to the point.

jason - is this part of yang 1.1 or do we need to reserve it for yang next 

    the versioning group supports it
    
lou - we would like to (particularly) hear from people who oppose advanving this as part of yang 1.1

Reshad - Can't make out what he is saying.

mahesh - supports the wya that gets this standardized fastest. if that's 1.1 then that's fine

Jason - Vendors are already moving ahead with this, and so is OpenConfig.

balazas - 3gpp is updating their modules in an nbc way so they need this yesterday.

 rob - do we last call these one a time and then hold them until the set is complete or how do we take them forward 

lou / kent - we can last call the ones that are ready (the first 3 of 5), and then the others later, progressing all 5 as a set to the IESG.


# Non-Chartered items:

##  22:19 System Configuration Data Handling Behavior (15 min)
https://datatracker.ietf.org/doc/draft-ma-netconf-with-system
###    Discussion Leader: Qiufang Ma

jason sterne - in option 3 are you proposing that all of you system configuration is visible


jason recognize the difference between running being valid when template expansion is occuring (doesn't that mean running is not valid?)


rob - think this work is useful. running being valid was trying to avoid changing the  defintion in 7950  running is valid if intended is valid

option 2 is the best answer here

prefer that running is only updated by a clieent

balazas - option 2 is very strange

jason - option 2 breaks offline validation

...

jason - suggest a mini interim for this proposal

kent - 22:30 closing the sesstion