Minutes interim-2023-nfsv4-01: Tue 19:00
minutes-interim-2023-nfsv4-01-202307111900-00
Meeting Minutes | Network File System Version 4 (nfsv4) WG | |
---|---|---|
Date and time | 2023-07-11 19:00 | |
Title | Minutes interim-2023-nfsv4-01: Tue 19:00 | |
State | Active | |
Other versions | plain text | |
Last updated | 2023-07-20 |
minutes-interim-2023-nfsv4-01-202307111900-00
NFSv4 Interim Meeting via Meetecho 20230711 Participants: Brian Pawlowski NFSV4 Chair Christopher Inacio NFSV4 CHAIR David Black PARTICIPANT David Noveck NFSV4 CHAIR John Klensin PARTICIPANT [A couple of us were having some technical difficulty with Meetecho with either displaying slides or audio issue being able to unmute to talk. The latter problem was fixed by exiting and rejoining] Minutes were taken offline after the last Meetecho notepad lost IETF group meeting minutes in Yokohama. Agenda: Agenda bash call - ? Document status / chairs - 5m rfc5661-bis - ~45m 117 meeting planning - 10m agenda topics Link to Interim Meeting Recording and Transcript: https://www.youtube.com/watch?v=9odmoDuyiZY Notes: [Document status / chairs - 5m] beepy and Chris gave an update on specs in Last Call and WG Adoption - see slide. But: 1. Internationalization - needs follow up at IETF meeting, more work, need directional feedback from expert review. 2. draft-ietf-nfsv4-layoutwcc - no comments on mail list for WGLC, discuss at next IETF WG meeting 3. delstid - revision made and submitted addressing WGLC comments, needs another WGLC (but expect approval) 4. draft-ietf-nfsv4-scsi-layout-nvme - APPROVED during WGLC, advance to IETF 5. draft-talpey-rdma-commit - WG Adoption Call Approved [Security draft discussion - chairs] Security document status was in WG last call/adoption before (long ago)? What is the status? Looks like we needs a reset. We will take to next IETF for discussion. Security document review needed in light of Threat analysis for pNFS - define expectations for different modes. [rfc5661-bis - Dave] Dave gave motivation for -bis document to create common base for all minor versions. And he gave a summary of docs related to this work )described in slides). Dave is flagging a group of issues related to the quality of the document. Dave flagged that we were not conformant with RFC 2119 key word use to indicate requirement levels. Dave wants to sharpen up use of REQUIRED or MUST, RECOMMENDED → SHOULD, and then lower case recommended - David Black. Make sure docs capitalize key words when used in accordance with IETF 2119. There is a collision of similar terms in doc describing NFS roles such as "client owner" that need to be standardized (and likely clearly defined). David Black asked if changes describe on slide 9 will impact the NVME pNFS document. The suggested terminology fixes. Noveck said he will make sure we align terminology. On security. Chris brought up the need for a threat analysis of the new draft (and related documents). Chris suggests copout out work and starting ~1 month after the 117 meeting in SF. David Black commented on slide 11 regarding RECOMMENDED being removed from mode bits description. Some things need to be REQUIRED. Need to change SHOULD to REQUIRED for some of the ode bits to ensure interoperability (there is a minimum set required. Dave explained in several slides how to navigate the new draft. Changes (diffs) in shift from rfc8881 can ,mostly be ignored, representing reorganization of material and typo style issues. Appendices A, B and C of rfc561-bis are really your friend. They will help you navigate the -bis document more quickly: A : Nature of changes B: Status of changes C: Issues Requiring Discussion See interim meeting slides (https://datatracker.ietf.org/doc/slides-interim-2023-nfsv4-01-sessa-rfc5661-bis/) for summary of these appendices. There are things remaining to be done in the -01 draft: - Directory delegation - Persistence issues [117 meeting planning and future interims] Proposed agenda for 117 meeting in SF: • Document status updates • LAYOUT_WCC • Delstid • pNFS SCSI layout for NVME • RDMA extensions • Security game planning • Internationalization efforts → Internationalization move forward plans • Rfc5661-bis • Future interim meeting planning We have to publish an interim meeting report (these minutes and slides?). THE END