These are the draft minutes from todays session. they are still editable on
Etherpad: https://etherpad.ietf.org/p/notes-ietf-107-netmod > Available Post Session: > Recording: WebEx recording be made available after the meeting. > Jabber Logs: https://www.ietf.org/jabber/logs/netmod > Etherpad: https://etherpad.ietf.org/p/notes-ietf-107-netmod > Slides: https://datatracker.ietf.org/meeting/interim-2020-netmod-01/session/netmod > > > Introduction > > TITLE: Session Intro & WG Status > PRESENTER: Chairs > introduction Design team acknowledgements document status. since last meeting > > Adopted items: > > TITLE: Recently Adopted YANG Module Versioning Drafts > PRESENTER: Authors > DRAFT(s) > https://tools.ietf.org/html/draft-ietf-netmod-yang-module-versioning-00 > https://tools.ietf.org/html/draft-ietf-netmod-yang-packages-00 > https://tools.ietf.org/html/draft-ietf-netmod-yang-schema-comparison-00 > https://tools.ietf.org/html/draft-ietf-netmod-yang-semver-00 > https://tools.ietf.org/html/draft-ietf-netmod-yang-solutions-00 > https://tools.ietf.org/html/draft-ietf-netmod-yang-ver-selection-00 > https://tools.ietf.org/html/draft-ietf-netmod-yang-versioning-reqs-02 --- Robert Wilton presenting the yang version history overview Kent - we likely need to get the sense of the room to take to the list Robert - requirements doucment can be held until we are ready to progress the solution since the other documents will reference it normally Joe clarke - requirements document is stable, wglc it now and wait on the solution overview Itallo busi - is the solution already supported by YANG tools? Can other WG use this solution in the YANG modules they develop? Robert - the schema solution may be already supported by pyang while packages and versioning is not yet supported Robert - design team is officially complete authors will continue to meet regularly to work on these documents, those meetings will be open to all prioritize the delivery of versioning semver packages Lou - so long as the base set of drafts doesn't change the other two drafts completely but staging them --- Reshad presenting yang module versioning Kent - currently this is aimed at proposed standard it could be experiemental we will need to come to consesnsus on this Joe clarke - I think you're concerned about semver not module versioning. main issues from the adoption call Robert - one option is allow multiple versioning schemes, one problem with a single YANG statement is how to define the separate version schemes. Perhaps each version scheme defines its own extension label. Lou - reminder that we asked the question when the documents were split,that at some point we have to decide if need to allow for more than one [versioning format] Jason Stern - it is useful to have a prefered scheme you don't want to have to gues that the 1.2.3 pattern means something specific Reshad - further dicussion needed Martin - Discussion on whether revision 1.2.3 is somewhat dependent on whether YANG semver ends up being experimental rather than proposed standard. Lou - The decision as to whether a doc should be experimental or standards track can often be revisited at WG LC time. Tim Carey - It is much easier for tooling if they can easily understand what scheme is being used. Balazs - We should explicitly state the used schema for revision label. Reshad - presenting again slide 6/7 issues Balazs: status-description is good for the same reason a seperate reference, contact, organization statement is used. We could put all that into description too, but it would make it messier. --- Joe Clarke presenting yang semver Carsten Bormann - maybe not a good Idea to use lower and upper case m and use a different latter to differentiate Joe - worth dicussing on list to get a record given I don't think it has been dicussed before Sue Hares - I'm not sure we're going to get modules for some bgp features that won't have non-backward compatible features. Joe - if you need to a do a bgp2.0 semver would do that Lou - introduicing this may make non-backwards-changes more likely, and we already have examples of non-backwards-compatible changes in IETF Balazas - some other orgzations don't take backwards compatibility so seriously Italo - even if all the updates are linear and BC, there is still the possibility to have a 1.0.0 version in IESG process and a 1.1.0 version in WG process Joe - use use the lineage of the module and bc nbc tags, Charles Eckel - would make an nbc change but then bump the major version Jason Sterne - strong attempt to not use the m in ietf modules. at least this modified semver gives us a machanism to show that happen. Robert - semver allows the addition of descriptions after major revisions, this could be used for bis documents that haven't been republished as new RFCs Martin Mjorklund - module versioning draft makes this possible Joe - moving on to github issues #48 --- Bo wu - presenting versioned yang schema Jason Sterne design team has already taken an hour we should abreviate or push to the end the remaining two dt docs Lou - wouldlike feedback from the working group comments to the list. Jason - yang schema selection Kent - a similar dicussion will take place in the netconf meeting on monday Lou - chairs will talk on how best to coordinate between groups. --- Reshad - presenting yang schema comparison > > Not-Yet-Adopted items: > > TITLE: A YANG Data model for ECA Policy Management > PRESENTER: Authors > DRAFT(s) > https://tools.ietf.org/html/draft-wwx-netmod-event-yang-06 --- Qin Wu presenting a yang policy model for eca policy management. Joel - 06 working group adaption revealed some issues that we should address before considering adoption again igor / andy issues. > TITLE: YANG Data Node Self Explanation Tags > PRESENTER: Tao,Ran > DRAFT(s) > https://tools.ietf.org/html/draft-tao-netmod-yang-node-tags-01 --- Qin Wu presenting Lou - this is the normal point where we would ask for a hum will do it on the list > > TITLE: 3GPP's UML to YANG Object Module Mapping > PRESENTER: Balazs Lengyel > DRAFT(s) > <none> --- Balazas presenting > TITLE: CORECONF > PRESENTER: Carsten Bormann > DRAFT(s) > https://tools.ietf.org/html/draft-ietf-core-yang-cbor-12 > https://tools.ietf.org/html/draft-ietf-core-sid-11 > https://tools.ietf.org/html/draft-ietf-core-comi-09 > https://tools.ietf.org/html/draft-ietf-core-yang-library-01 --- Carsten Bormann presenting Virtual Bluesheet -- please add your name and affiliation NAME AFFILIATION Warren Kumari Google Kent Watsen Watsen Networks Lou Berger LabN Consulting, LLC Rob Wilton Cisco Jason Sterne Nokia Carsten Bormann, TZI Guangying zheng Huawei Martin Björklund Bo Wu Huawei Dhruv Dhody Huawei-India Ivaylo Petrov Acklio Jan Lindblad Cisco Arunprabhu Kandasamy Acklio Sergio Belotti NOKIA Balazs Lengyel Ericsson Yoshifumi Atarashi Alaxala Tim Carey, Nokia Joe Clarke Cisco Charles Eckel, Cisco Ray Atarashi IIJ-II William Lupton Broadband Forum Joel Jaeggli Fastly Yuji Tochio Fujitsu Susan Hares Huawei Reshad Rahman Cisco Italo Busi Huawei Xufeng Liu Volta Networks David Sinicrope Ericsson Qin Wu Huawei Gabriele Galimberti Cisco Peng Liu China Mobile
pEpkey.asc
Description: application/pgp-keys
_______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod