Re: [nfsv4] RFC 8178 on Rules for NFSv4 Extensions and Minor Versions
David Noveck <davenoveck@gmail.com> Mon, 17 July 2017 05:00 UTC
Return-Path: <davenoveck@gmail.com>
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 C2D89127369 for <nfsv4@ietfa.amsl.com>; Sun, 16 Jul 2017 22:00:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 imxmC5LtuYXB for <nfsv4@ietfa.amsl.com>; Sun, 16 Jul 2017 22:00:29 -0700 (PDT)
Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0690A12785F for <nfsv4@ietf.org>; Sun, 16 Jul 2017 22:00:29 -0700 (PDT)
Received: by mail-it0-x22a.google.com with SMTP id h199so12590589ith.1 for <nfsv4@ietf.org>; Sun, 16 Jul 2017 22:00:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=vWoxmwSPG3bUbW3TcXD4KlZFvLv5P8ryDonE4QmOKRU=; b=aRHh26rD37b810mxz1KiMTvi4OC85RnvPinBuXJO6v9XbdyK23swxCUWi9OzKPRnBE 0SM9HUr73vLD5fC1170G6cf42jTgRso8vPzdYKvDgf2C8BlHf5AiAn8gfnBi5C8qtkQB Qylj9T/+9FKsC5TcybT1Exb0l3y0n370d1XY5qoe57Ctttvy2QG/4k+1MAZZRxRD6ott YyEd/0gYRT9xaQpa9gIiFFr64Ekav8nMgEnfdPWyAVpYnKdwImelG9UMLZQ2vQ70oIDy jJsh75mboXemWFFCZ+5qOAYNkyesYfs00b3yJIIj9uH/BLbFzrTU7JU9NoMROeDRzr08 kxjw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=vWoxmwSPG3bUbW3TcXD4KlZFvLv5P8ryDonE4QmOKRU=; b=FaQ67B4TZX6H3dgpsYZ4Y+x/stFxNYZ/x6nb3HE9G/VZiq4pzxIWkLqAamOpv4W+Ja o0azIkG3HW5RIvhgq9A/FU+XniR/d2WUKQ0KK2HeZqCIaRIKpqaWJlaKhanj9pJUij31 9gFAFwbQynA5RE2XGKV1eZ/X7prPpCDTcFtfpTyJkCG0HHdHWbFYmgLPA7TZ/c2xTq1y 1J9H43cn8PGsmBJ0236hdnu/ZPqWWO8/mIqhwDwEeim8yRwKUYusR08TRha24dpNVFWR si04nDuV/m4QoRC5bOFGOwQhorAE1K9Rt45dmug6MepZoCoHNeKqCND3UcdPF9dXG1Ll O3rw==
X-Gm-Message-State: AIVw111cMnJDyxqQLDEw/uPJ4Nz7GiOn3CUp3c4ZUDWjEgXqbaw8tbgK z+R2USORJDPHQjMzf+Yei5roHDgymg==
X-Received: by 10.36.208.139 with SMTP id m133mr4036496itg.48.1500267628303; Sun, 16 Jul 2017 22:00:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.57.86 with HTTP; Sun, 16 Jul 2017 22:00:27 -0700 (PDT)
In-Reply-To: <CAFt6Bam6E2qAqZKogheGkx+NGs94XG+omb+nGrTjLTNYTV7m5A@mail.gmail.com>
References: <20170714002733.A4A23B8105F@rfc-editor.org> <CAFt6Bam6E2qAqZKogheGkx+NGs94XG+omb+nGrTjLTNYTV7m5A@mail.gmail.com>
From: David Noveck <davenoveck@gmail.com>
Date: Mon, 17 Jul 2017 01:00:27 -0400
Message-ID: <CADaq8jc=+sVVZjNTLv19Z+HAXhJt_gGWGm_0t4_fKmfR0=nMvw@mail.gmail.com>
To: spencer shepler <spencer.shepler@gmail.com>
Cc: "nfsv4@ietf.org" <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="001a114997780d9d8405547c4730"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/N1bWeXrmbMBIHPock-vaVNgqYMA>
Subject: Re: [nfsv4] RFC 8178 on Rules for NFSv4 Extensions and Minor Versions
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: Mon, 17 Jul 2017 05:00:31 -0000
Thanks, Spencer. This has been a productive year for the working group. During the year since we last met (at IETF96 in Berlin), we have gotten nine RFCs published: 7861-3, 7931, 8000, 8154, 8166-7, and 8178. Three others have completed WGLC but are stuck at various points in the IETF labyrinth: 5667bis, xattrs, umask. On Thu, Jul 13, 2017 at 8:46 PM, spencer shepler <spencer.shepler@gmail.com> wrote: > > Congratulations, Dave (and the working group), for moving this work into > an RFC. Timely publication with the upcoming meeting. > > Spencer > > On Thu, Jul 13, 2017 at 5:27 PM, <rfc-editor@rfc-editor.org> wrote: > >> A new Request for Comments is now available in online RFC libraries. >> >> >> RFC 8178 >> >> Title: Rules for NFSv4 Extensions and >> Minor Versions >> Author: D. Noveck >> Status: Standards Track >> Stream: IETF >> Date: July 2017 >> Mailbox: davenoveck@gmail.com >> Pages: 26 >> Characters: 61627 >> Updates: RFC 5661, RFC 7862 >> >> I-D Tag: draft-ietf-nfsv4-versioning-11.txt >> >> URL: https://www.rfc-editor.org/info/rfc8178 >> >> DOI: 10.17487/RFC8178 >> >> This document describes the rules relating to the extension of the >> NFSv4 family of protocols. It covers the creation of minor versions, >> the addition of optional features to existing minor versions, and the >> correction of flaws in features already published as Proposed >> Standards. The rules relating to the construction of minor versions >> and the interaction of minor version implementations that appear in >> this document supersede the minor versioning rules in RFC 5661 and >> other RFCs defining minor versions. >> >> This document is a product of the Network File System Version 4 Working >> Group of the IETF. >> >> This is now a Proposed Standard. >> >> STANDARDS TRACK: This document specifies an Internet Standards Track >> protocol for the Internet community, and requests discussion and >> suggestions >> for improvements. Please refer to the current edition of the Official >> Internet Protocol Standards (https://www.rfc-editor.org/standards) for >> the >> standardization state and status of this protocol. Distribution of this >> memo is unlimited. >> >> This announcement is sent to the IETF-Announce and rfc-dist lists. >> To subscribe or unsubscribe, see >> https://www.ietf.org/mailman/listinfo/ietf-announce >> https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist >> >> For searching the RFC series, see https://www.rfc-editor.org/search >> For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk >> >> Requests for special distribution should be addressed to either the >> author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless >> specifically noted otherwise on the RFC itself, all RFCs are for >> unlimited distribution. >> >> >> The RFC Editor Team >> Association Management Solutions, LLC >> >> >> > > _______________________________________________ > nfsv4 mailing list > nfsv4@ietf.org > https://www.ietf.org/mailman/listinfo/nfsv4 > >
- [nfsv4] RFC 8178 on Rules for NFSv4 Extensions an… rfc-editor
- Re: [nfsv4] RFC 8178 on Rules for NFSv4 Extension… spencer shepler
- Re: [nfsv4] RFC 8178 on Rules for NFSv4 Extension… David Noveck