IETF Logo Mail Archive

Re: [nfsv4] Fwd: New Version Notification for draft-dnoveck-nfsv4-security-08.txt

Brian Pawlowski <beepee@gmail.com> Sun, 03 March 2024 17:14 UTC

Return-Path: <beepee@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 E9AB0C14F61D for <nfsv4@ietfa.amsl.com>; Sun, 3 Mar 2024 09:14:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.212
X-Spam-Level:
X-Spam-Status: No, score=-1.212 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, MIME_HTML_ONLY=0.1, MIME_HTML_ONLY_MULTI=0.001, MIME_QP_LONG_LINE=0.001, MPART_ALT_DIFF=0.79, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WedaZcGq2L95 for <nfsv4@ietfa.amsl.com>; Sun, 3 Mar 2024 09:14:34 -0800 (PST)
Received: from mail-pl1-x635.google.com (mail-pl1-x635.google.com [IPv6:2607:f8b0:4864:20::635]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CE61C14F685 for <nfsv4@ietf.org>; Sun, 3 Mar 2024 09:14:29 -0800 (PST)
Received: by mail-pl1-x635.google.com with SMTP id d9443c01a7336-1dc49b00bdbso33836925ad.3 for <nfsv4@ietf.org>; Sun, 03 Mar 2024 09:14:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1709486067; x=1710090867; darn=ietf.org; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:content-transfer-encoding:from:to:cc:subject:date :message-id:reply-to; bh=mXDSHVGXEEEJ/rUKsdkYEbNonH7DJs6Gptl2ksct6/8=; b=mquJvoweyOf3tzOtlBvjgCnrIiQu2ozyZIKCVmLArcNaiFzdWoeJfY13IDfgt5BeP6 lyhRDQxgAKxLHROH0zV5OfXhE7qqqF3Wdfgh0XpFXJ77QFfFiaWBKScJ0eFo6/h9d/BL oQBi35UyT/9od3KWY65ydXDUGh9tKgGFJcnxUGQLkhs+O24orc6OY/kea5pWNkCz58eq 56kVTmqlcqaYOZSSGVk+PnDj519vlx+JCP9oiqykH2WlkHNxKu3GRTCadxPpCt3yuUrl mre3TPnofqUXw36Kow1ugymmfhJxLz8yT75t0zzoGN7/Sg2RFBZeysfWTkl+Zh0ptFp2 KmZA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709486067; x=1710090867; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:content-transfer-encoding:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=mXDSHVGXEEEJ/rUKsdkYEbNonH7DJs6Gptl2ksct6/8=; b=LJ+nG91m2mTQnTvrWem6r9sIaeF4GWdu7Ulx7rojIq84BsI01KyaKKQM3ILQU2cOqo VwZeiZviEeazBUFSaBtxeCI1gLLPomkBrzEjwuWw3PRU2klwX41T5xD9R99RZOgeNlug FaiTxeLy0qEKbB78bVHZeAOqYPz7LAjaeIpKYv5Ur8leXmHlaFdbRIodRAjHCvgM1t5S vDJt2H7HR1OvelKRwmjSTeHTa4ndvf5BPCwFkcpj5Y1LEVUn9PCl71Ihw2hZK6UAGtHI YcaOYgIeQksdec7zS1olJ6buaBREz0If7Jsjo9ntYPrJVDIc3qoyqDAEUExNzUif+5gH WgMQ==
X-Gm-Message-State: AOJu0YyNvMaRiwP82xc8qWa0cttRd4udUWd47WIVJ90QsE6ik8z0ZrQ2 OAgX7L1Y+IZCK2JlPtAsDibQY3QWXzYqgv9XryXhNDmUqiNdC1vSpKT/ZOqC
X-Google-Smtp-Source: AGHT+IHaNhoPk1GJEpU54j7jT6Te1NQMNjpy+F27PBnyxDPDyfpQOqNS79752UBdEqHgiXdcuWURYg==
X-Received: by 2002:a17:903:25d3:b0:1dc:418f:890b with SMTP id jc19-20020a17090325d300b001dc418f890bmr5609891plb.40.1709486067449; Sun, 03 Mar 2024 09:14:27 -0800 (PST)
Received: from smtpclient.apple ([2601:647:6680:23e6:6cc9:38b4:47b0:f0d7]) by smtp.gmail.com with ESMTPSA id e12-20020a170902d38c00b001dc05535632sm6863103pld.170.2024.03.03.09.14.26 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 03 Mar 2024 09:14:26 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail-B070F538-BC17-46C6-B8D3-57D0840E3FE6"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
From: Brian Pawlowski <beepee@gmail.com>
In-Reply-To: <CADaq8jeHa0PPye1xtUyHipFa60tuCOufW_7uXmY3UV9RwuySqg@mail.gmail.com>
Date: Sun, 03 Mar 2024 09:14:15 -0800
Cc: NFSv4 <nfsv4@ietf.org>
Message-Id: <392A934B-CCAF-472B-990D-470175C578A6@gmail.com>
References: <CADaq8jeHa0PPye1xtUyHipFa60tuCOufW_7uXmY3UV9RwuySqg@mail.gmail.com>
To: David Noveck <davenoveck@gmail.com>
X-Mailer: iPhone Mail (21D61)
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/QEXGW_GTwDz6zfZdurtmOmC0Awg>
Subject: Re: [nfsv4] Fwd: New Version Notification for draft-dnoveck-nfsv4-security-08.txt
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.39
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: Sun, 03 Mar 2024 17:14:39 -0000

Thanks Dave!

On Mar 3, 2024, at 06:53, David Noveck <davenoveck@gmail.com> wrote:


Got this in by the deadline.  Will discuss at IETF119.

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Sun, Mar 3, 2024 at 9:50 AM
Subject: New Version Notification for draft-dnoveck-nfsv4-security-08.txt
To: David Noveck <davenoveck@gmail.com>


A new version of Internet-Draft draft-dnoveck-nfsv4-security-08.txt has been
successfully submitted by David Noveck and posted to the
IETF repository.

Name:     draft-dnoveck-nfsv4-security
Revision: 08
Title:    Security for the NFSv4 Protocols
Date:     2024-03-03
Group:    Individual Submission
Pages:    113
URL:      https://www.ietf.org/archive/id/draft-dnoveck-nfsv4-security-08.txt" rel="noreferrer nofollow" target="_blank">https://www.ietf.org/archive/id/draft-dnoveck-nfsv4-security-08.txt
Status:   https://datatracker.ietf.org/doc/draft-dnoveck-nfsv4-security/" rel="noreferrer nofollow" target="_blank">https://datatracker.ietf.org/doc/draft-dnoveck-nfsv4-security/
HTML:     https://www.ietf.org/archive/id/draft-dnoveck-nfsv4-security-08.html" rel="noreferrer nofollow" target="_blank">https://www.ietf.org/archive/id/draft-dnoveck-nfsv4-security-08.html
HTMLized: https://datatracker.ietf.org/doc/html/draft-dnoveck-nfsv4-security" rel="noreferrer nofollow" target="_blank">https://datatracker.ietf.org/doc/html/draft-dnoveck-nfsv4-security
Diff:     https://author-tools.ietf.org/iddiff?url2=draft-dnoveck-nfsv4-security-08" rel="noreferrer nofollow" target="_blank">https://author-tools.ietf.org/iddiff?url2=draft-dnoveck-nfsv4-security-08

Abstract:

   This document describes the core security features of the NFSv4
   family of protocols, applying to all minor versions.  The discussion
   includes the use of security features provided by RPC on a per-
   connection basis.  Important aspects of the authorization model,
   related to the ACL feature, will be specified in a separate document.

   The current version of the document is intended, in large part, to
   result in working group discussion regarding existing NFSv4 security
   issues and to provide a framework for addressing these issues and
   obtaining working group consensus regarding necessary changes.

   When the resulting documents (i.e. this document and one derived from
   the separate ACL specification) are eventually published as RFCs,
   they will, by updating these documents, supersede the description of
   security appearing in existing minor version specification documents
   such as RFC 7530 and RFC 8881,



The IETF Secretariat


_______________________________________________
nfsv4 mailing list
nfsv4@ietf.org
https://www.ietf.org/mailman/listinfo/nfsv4

v2.23.0 | Report a Bug | By Email