IETF 93 - Prague - nfsv4 working group
July 22, 2015, 9:00 - 11:30AM

-- Note Well, Blue Sheets

Not e-mail, but organization, on blue sheets. Fix slides.

-- Agenda bashing (beepy)

Multidomain draft add Adamson.

-- Document Editor Update (Haynes) (5 minutes)

Spencer needs to shepherd document.

-- Xattr draft update (Eshel) (30 minutes)

Mark presenting. 

Named attributes doesn't map to Xattrs. Get draft going. 

Adamson asked to add language about maximum size - Haynes said look at 
READDIR discussion. Not maxcount, but max buffer size.

Haynes described how to move to working group document.

-- Block and SCSI layout updates (Hellwig) (30 minutes) FlexFile Layout - (Haynes) (15 minutes)

Block storage addition to pNFS.

Errata found to RFC 5663. Linux proof of concept back in 2011 - struggling
prototype. Only one implementation.

See slides for details on issues found via new prototype. 

Two choices - new SCSI layout document dependent on RFC 5663, should
we supercede that doc with combined doc. Take discussion on doc evolution
to mail list.

Only other objection was non-SCSI block storage. NVME - there is persistent
reservations. Rope someone in to write that document.

Will upload new version of SCSI layout, we will consider RFC 5663 errata
or not to errata.

-- FlexFiles Requirements - (Haynes) (5 minutes)

Be careful about wording of some sections. Fencing is not security.
Clarifying that is big change from version 5 to version 6.

See slides. Linux client delivered upstream. As was wireshark changes.

-- Layout Type Requirements - (Haynes) (5 minutes)

IESG comments need to be addressed.

Martin says we're resetting to be back in the working group. For
review.

-- Multidomain draft (Adamson)

No slides.

Similar to layout types. Clarifying issues in NFS V4.0 and 4.1,
especially with FedFS.

Get status - is it in WG last call. Should it be informational
or standards draft. Draft clarifies how make all this work.

2119 MUSTs, SHOULDs and MAYs can be used in an informational draft
says David Black. Martin thinks its wise to put on standards track.
No errata to speak of - just additional information.