From: Noveck, Dave (Dave.Noveck@netapp.com)
Date: 03/07/02-04:03:32 PM Z
Message-ID: <8C610D86AF6CD4119C9800B0D0499E336A8C9E@red.nane.netapp.com>
From: "Noveck, Dave" <Dave.Noveck@netapp.com>
Subject: RE: Draft agenda for NFSv4 meeting in Minneapolis Wed. Mar. 20 13 :00 - 15:00
Date: Thu, 7 Mar 2002 14:03:32 -0800
I just looked at the Goals and Milestones section under
http://www.ietf.org/html.charters/nfsv4-charter.html.
Both "Conduct final Interoperability tests" and
"Conduct full Interoperability tests for all NFSV4
features" are both marked "Done".
What are "final Interoperability tests" and how do
they relate to the "full Interoperability tests"?
I would think that the "final" tests would be
final, i.e. after all of the others, but perhaps
there is some IETF reason why not. What's the
deal?
Unless I missed an amazing burst of creativity by
having to leave Connectathon one day early, there
are lots of features that haven't had full interoperability
testing (with two independently developed implementations).
Nobody has implemented (so no interoperability testing):
SPKM3 support.
LIPKEY support.
Migration support.
Replication support.
Some implementation work but no known interoperability testing:
UTF-8 support.
Some implementation work and limited interoperablity testing
but not extensive enough to meet the criterion:
Delegation.
State recovery.
Implementation and some testing in passing but no sufficiently
focused testing to establish full interoperability (i.e. the stuff
might work if we carefully tested it, but we haven't written the
tests).
UID's and GID's as strings.
Implementation and interoperability testing which might meet
the criterion:
Named attributes.
Features that have had enough testing to establish interoperability.
All the V2/V3 features.
Security negotiation through GSSRPC.
Kerberos support.
Pseudo-fs.
Locking (although note the caveats below)
No mandatory locking.
OPENs have been tested but I only know of one client that
would be issuing opens with anything other than DENY=NONE.
As mentioned above, only limited testing of state recovery.
No testing under adverse network conditions to establish
that the implementations of the seqencing/stateid features
are really interoperable.
Anybody have additions or other changes to this list?
-----Original Message-----
From: Brian Pawlowski [mailto:beepy@netapp.com]
Sent: Thursday, March 07, 2002 2:24 PM
To: nfsv4-wg@sunroof.eng.sun.com
Subject: Draft agenda for NFSv4 meeting in Minneapolis Wed. Mar. 20
13:00 - 15:00
Hello,
I have attached the proposed agenda for the Minneapolis IETF
meeting of the NFSv4 WG. For info about this IETF meeting see:
http://www.ietf.org/meetings/IETF-53.html
Note the pre-registration/pre-payment cutoff of
NOON ET, FRIDAY, 8 MARCH 2002
The working group will focus on closure of the specification
updates with results of testing from Connectathon of the various
implementations and the plan and dates for resubmission and
consideration as an updated Prooposed Standard.
Make sure you review the working group documents before you come.
First two rows of the room seating will be reserved for those
who have read the docs! Document links are available via
the WG web page at
http://www.ietf.org/html.charters/nfsv4-charter.html
Please submit any agenda changes/additions or requests to present to me
(beepy@netapp.com) before 5PM ET March 13, 2002.
beepy
8< --------------------------------------------------------
Network File System Version 4 (nfsv4)
-------------------------------------
Chair(s):
Robert Thurlow <Robert.Thurlow@eng.sun.com>
Brian Pawlowski <beepy@netapp.com>
Document Editor:
Spencer Shepler <shepler@eng.sun.com>
AGENDA: Wednesday March 20th: 13:00pm - 15:00 (2 hours)
Welcome and Introduction (Pawlowski) 5 min
Agenda bash
Connectathon results (Shepler) 5 min
Closure of specification update (Shepler) 25 min
Migration/replication next steps (Thurlow) 25 min
Review of work items (Shepler/Pawlowski) 25 min
- API GSSAPI advancement
- MIB draft
- RPC/XDR/RPCSEC_GSS RFC plans
Open discussion (Pawlowski) 30 m
Wrapup (Pawlowski) 5 m
This archive was generated by hypermail 2.1.2 : 03/04/05-01:49:34 AM Z CST