* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Netmod Status Pages

Network Modeling (Active WG)
Ops Area: Robert Wilton, Warren Kumari | 2008-Apr-29 —  
Chairs
 
 
 


IETF-108 netmod agenda

Session 2020-07-30 1410-1550: Room 4 - Audio stream - netmod chatroom

Agenda

 changed a few seconds ago 7 views
 owned this note

NetMod 108 Draft Minutes

Session:
Thursday July 28th
UTC: 14:10-15:50

Meeting Materials

https://datatracker.ietf.org/meeting/108/session/netmod
https://meetings.conf.meetecho.com/ietf108/?group=netmod

Video recording: https://www.youtube.com/watch?v=2CN1jB3OuOY

Session Intro & WG Status

Chairs (10 minutes)

Introduction - Lou Berger presenting
Please see the note well.
bluesheets are handled automatically by meetecho.

Liasons
discussion to be had around whether to reach out to the IEEE

Working remotely chairs are here to support virtual interims and side meetings.

Update on: (14:20 - 5 min)

Sub-interface VLAN YANG Data Models

https://tools.ietf.org/html/draft-ietf-netmod-sub-intf-vlan-model-07

Common Interface Extension YANG Data Models

https://tools.ietf.org/html/draft-ietf-netmod-intf-ext-yang-09
Rob Wilton

14:15utc

proposal to not include in-disards-overflow
no objections in meeting

concerns with the subinterface vlan model changes?
no objections

Lou Berger - are we ready for publication?
will confirm on list for resolved comments

do we need to send a liason over the vlan terms
          

Rob Wilton - will hand ad responsibility for these drafts to warren
don’t think formal liason is required. they have been involved.
use the ieee-ietf coordination mailing list
also use the ieee yangsters review since they have done it.

Lou Berger - I can send those if you prefer

Warren Kumar - sounds good to me, prefer that the mail not come from me.

Rob Wilton - I’ll send it

Lou Berger - Please cc at least netmod-chairs

General Update on the YANG Versioning Solution (14:25 - 5 min)

Reshad Rahman

Lou Berger - believe that we previously agreed to hold the documents until all are ready to go.

Reshad Rahman - authors plan to get modver and semver to wg lc first and then focus on progressing the other documents

Updated YANG Module Revision Handling (14:30 - 20 min)

https://tools.ietf.org/html/draft-ietf-netmod-yang-module-versioning-01
Reshad Rahman

interpreting revision labels in semver
no questions

use of revision labels by submodules
review section 3.3 update

revision label in filename
lada - having a symbolic link is an issue due to the changing filename
these is even worse then date

Reshad Rahman - downside is without it you have to look at the contents of the file.

Rob Wilton - git is to not have the revision date or label in the git repo itself but publish it somehwere else

Kent Watsen - agree with rob

revision label uniquely identifies a module version.

Ladislav Lhotka - this also includes changes in whitespace?

NBC changes can break imports

Kent Watsen - the break in backwards compatibility may not be in the area the matters.

Rob Wilton - not using the revision label to make decision, rather the revision history is used.

Kent Watsen - python packages declare compatibility with current / past versions but not future versions.

Kent Watsen - it does sound confusing the purpose of this effort is to address this problem

Lou Berger - would be really helpful if you (rob / reshad) would send your example to the list.

impact of changing import statement

Reshad Rahman - consider rough consensus to be option b (not sure now)

Rob Wilton - is the example sufficiently clear

Kent Watsen - are you speaking as contributor?

Lou Berger - do send the email I thought I understood it until your last statement

should we import yang revision identifier?

insignificant whitespace changes

Ladislav Lhotka’s earlier question.

Reshad Rahman - should result in a new change e.g. editorial.

Charles Eckel - don’t userstand the usecase for whitespace but nothing else

Reshad Rahman - don’t have an answer for you

via jabber - Jan Lindblad
There is probably no reason to publish with only whitespace changes. The point is that there should be a version number for every different checksum

Ladislav Lhotka - we still have this alternative syntax which raises the case of two syntaxes of the same version.

Kent Watsen - the yin files have a different suffix

Joe Clarke - if I decide to publish something and all I change is whitespace I still want to note that.

Ladislav Lhotka - starting from a YIN module and using different tools for translating it to YANG, one can easily end up with modules differing in whitespace.

YANG Semantic Versioning (14:50 - 15 min)

https://tools.ietf.org/html/draft-ietf-netmod-yang-semver-01
Joe Clarke
+1:15

No comments - please send other comments/questions to the list.

Common YANG Data Types (15:05 - 15 min)

https://tools.ietf.org/html/draft-ietf-netmod-rfc6991-bis-04
Juergen Schoenwaelder
+1:28

Kent Watsen - will take questions to the list.

Telemetry Data Self Explanation Tags (15:20 - 10 min)

https://tools.ietf.org/html/draft-tao-netmod-yang-node-tags-03
Qin Wu

+1:40

Lou Berger - we will need check IPR
Qin Wu - okay

Kent Watsen - similar work in NETCONF, need to ensure importance of work.
Qin Wu - Not a strong a dependency.




Generated from PyHt script /wg/netmod/agenda.pyht Latest update: 24 Oct 2012 16:51 GMT -