Re: [nfsv4] New Version Notification for draft-cel-nfsv4-linux-seclabel-xtensions-00.txt

bfields@fieldses.org (J. Bruce Fields) Thu, 03 May 2018 15:05 UTC

Return-Path: <bfields@fieldses.org>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2901127076 for <nfsv4@ietfa.amsl.com>; Thu, 3 May 2018 08:05:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UKjm6eSd0SCC for <nfsv4@ietfa.amsl.com>; Thu, 3 May 2018 08:05:52 -0700 (PDT)
Received: from fieldses.org (fieldses.org [173.255.197.46]) by ietfa.amsl.com (Postfix) with ESMTP id E25D312778D for <nfsv4@ietf.org>; Thu, 3 May 2018 08:05:52 -0700 (PDT)
Received: by fieldses.org (Postfix, from userid 2815) id AEDD4254F; Thu, 3 May 2018 11:05:22 -0400 (EDT)
Date: Thu, 03 May 2018 11:05:22 -0400
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Tom Haynes <loghyr@gmail.com>, NFSv4 <nfsv4@ietf.org>
Message-ID: <20180503150522.GB14163@fieldses.org>
References: <152337099624.13448.11040477333954216664.idtracker@ietfa.amsl.com> <FB6B8D57-CEF6-46E1-97C7-E43C7E49752F@oracle.com> <2CBB38A6-45FF-46A4-96A5-5D1B431E1365@gmail.com> <70601965-7472-4691-B139-8116F095D200@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <70601965-7472-4691-B139-8116F095D200@oracle.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
From: bfields@fieldses.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/s2s-AOzio2USumnjHffelntTrO4>
Subject: Re: [nfsv4] New Version Notification for draft-cel-nfsv4-linux-seclabel-xtensions-00.txt
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4/>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 May 2018 15:05:59 -0000

On Wed, May 02, 2018 at 07:32:23PM -0400, Chuck Lever wrote:
> In recent standards track documents we have avoided discussion
> of rationale when specifying protocol, thus I excluded that
> discussion here as well.

Let's stop doing that.  Rationale is really important, and putting it in
the RFC is the best way to ensure it's not lost.

--b.