[nfsv4] Opsdir last call review of draft-ietf-nfsv4-xattrs-05

Jürgen Schönwälder <j.schoenwaelder@jacobs-university.de> Sun, 14 May 2017 08:46 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Jürgen Schönwälder <j.schoenwaelder@jacobs-university.de>
To: ops-dir@ietf.org
Cc: ietf@ietf.org, draft-ietf-nfsv4-xattrs.all@ietf.org, nfsv4@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149475155989.2899.8921343359746045233@ietfa.amsl.com>
Date: Sun, 14 May 2017 01:45:59 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/Uxn_WXEaWV67ez2A2C1FD_Bi2tA>
Subject: [nfsv4] Opsdir last call review of draft-ietf-nfsv4-xattrs-05

Reviewer: Jürgen Schönwälder
Review result: Ready

This was a nice read, a very well written document. I do not see any
operational issues for the Internet resulting from this
specification.
The functionality provided seems to be desirable.

I was a bit surprised to see that numeric values for NFSv4 protocol
extensions etc appear to be somewhat magically managed (section 8.6)
instead of using IANA but this likely has its own history and
reasons.

[nfsv4] Opsdir last call review of draft-ietf-nfs… Jürgen Schönwälder