Return-Path: 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 5596F3A09D3 for ; Sun, 24 May 2020 04:25:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 qC7-y1SdTsaV for ; Sun, 24 May 2020 04:25:28 -0700 (PDT) Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) (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 CDE933A09D2 for ; Sun, 24 May 2020 04:25:27 -0700 (PDT) Received: by mail-ej1-x636.google.com with SMTP id e2so17744072eje.13 for ; Sun, 24 May 2020 04:25:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=bocE7RrfAePdYKgj/mKFFUUqbf6oYc18AlDXYiDreT8=; b=IkpeeLNR371d8agm1mKH80igHAjj0HibsCnmbjqWyxtHYuDZApm4hgAwog5hkfV3xF FUR3WXdCL1vDSCHkKEvF1GsI44MeDcooTmhNNdVKzWwKQkjOCzpXD2YuOcDMn2f9j4rb 6ZZo+mTn4qbsULOXJY6DrP965wLcmHlV1mJW3Czsx4A6HjUKZfv9fjTvD/rsBsGhW3+y +mNUExTIr/tsQSJbB23GNO+aXpybx8DuGWJS9wC8vmVB6O7hOEQp6CAH79S/VGGjQRR2 sjYVz2aVU5TDWIgY5vX0a7KEl7fyMI/GtiReramM3CABzVRI8SrxSEIjQBamJR1b21c3 Ivag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=bocE7RrfAePdYKgj/mKFFUUqbf6oYc18AlDXYiDreT8=; b=o2Xul0to6fM/6nF8EHuQpKa+pD5SEdqL1oXksddTLhPYORMdOVR2UaEBa6zhMczWQM InBvJZb2FEJlUgLHtq3fOfTDuO5QI/3TFLOzlJtdMuyqlEVqFMl87qwJg1ht++cePnMT YfZxArz9x+aCuNCh7RbSpsexPN2uUmXwOySq/cF5hp98GkFYn+/Xf/3sJksDyTXMc9Z8 4hTIvP7mRcxfRxd9E5X9RaUdmgP7iUWgyHBxQxY66lHB1tlvxkeV2ks6uwtw+L9pVd7N QkoJQ0Iwj8fcQfxdFJmPhSWgV3mKuridk3P+FYLvM+45peEBhWQPxuubhPTQErwF3ayx ep7g== X-Gm-Message-State: AOAM533Czy30I94WmlQtJL4atCTw9FFolTpg7XVpCVXE0j/t/mmQ3eHv vPQAbNWapQMfUAGd027UXk1yWERl2UvsyhNAq9402g== X-Google-Smtp-Source: ABdhPJzghiWTdWGLZ4XOyijPIodCrJyfMuN5Ns9I/hFE4Yz6qEZeOPl/Xx3TL8401dE5GiX2hfS7U+QEYgl8YHkM4JY= X-Received: by 2002:a17:906:934e:: with SMTP id p14mr14938253ejw.498.1590319526152; Sun, 24 May 2020 04:25:26 -0700 (PDT) MIME-Version: 1.0 From: David Noveck Date: Sun, 24 May 2020 07:25:15 -0400 Message-ID: To: Magnus Westerlund Cc: Talpey Thomas , NFSv4 Content-Type: multipart/alternative; boundary="0000000000006f8ddf05a6631eff" Archived-At: Subject: [nfsv4] Proposed charter changes (with updates) X-BeenThere: nfsv4@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: NFSv4 Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 May 2020 11:25:29 -0000 --0000000000006f8ddf05a6631eff Content-Type: text/plain; charset="UTF-8" First of all, thanks to Daniel and Tom for corrections/suggestions. I am proposing replacing the second paragraph of the extensions section which now reads: Similarly, associated ONC protocol components that have a versioning/ extension framework can be incrementally extended, when necessary. By the following two-paragraph replacement: In dealing with needed extensions to areas that underlay NFSv4, the working group's role will depend on the specific area needing extension. In the case of associated ONC protocol components, those that have a versioning/extension framework can be incrementally extended, when necessary. In the case of lower-layer facilities of particular importance to NFSv4, the working group will work with the responsible working group to make sure needed extensions are available. In cases in which there is no assigned working group, it can help develop the necessary extension itself. --0000000000006f8ddf05a6631eff Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
First=C2=A0of all, thanks to Daniel and Tom for correction= s/suggestions.

I am propos= ing replacing the second paragraph of the extensions section which now read= s:

Similarly, associated ONC protocol components that have a versioning= /


=
By the following two-paragraph replacement:

In dealing with nee= ded extensions to areas that underlay NFSv4, the working group's role w= ill depend on the specific area needing extension.=C2=A0 In the case of ass= ociated ONC protocol components, those that=C2=A0have a versioning/extensio= n framework can be incrementally extended, when necessary.

In the case of lower-layer facilit= ies of particular importance to NFSv4, the working group will work with the= responsible=C2=A0working group=C2=A0to make sure needed extensions are ava= ilable.=C2=A0 In cases in which there is no assigned working group, it can = help develop the necessary extension itself.
=

--0000000000006f8ddf05a6631eff--