IETF Logo Mail Archive

Re: [nfsv4] New wording of Security Section for Flex Files

Olga Kornievskaia <aglo@citi.umich.edu> Mon, 07 August 2017 16:35 UTC

Return-Path: <olga.kornievskaia@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 62DAC132699 for <nfsv4@ietfa.amsl.com>; Mon, 7 Aug 2017 09:35:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_PASS=-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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GJSDHbWqS7N9 for <nfsv4@ietfa.amsl.com>; Mon, 7 Aug 2017 09:35:11 -0700 (PDT)
Received: from mail-qk0-x241.google.com (mail-qk0-x241.google.com [IPv6:2607:f8b0:400d:c09::241]) (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 57401132466 for <nfsv4@ietf.org>; Mon, 7 Aug 2017 09:35:11 -0700 (PDT)
Received: by mail-qk0-x241.google.com with SMTP id a77so925426qkb.2 for <nfsv4@ietf.org>; Mon, 07 Aug 2017 09:35:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=O1eRedJK9IdPWwKpKvDm93aGr2UmEEHPs+NTNinredU=; b=Qvz64K0kDfsfv4hbUazTJ9UCSTR5vuWUtuMH4xlo7IrWUB1OVROcdtQC18ve/N9g4o Fy8OdoJtatPhknCDLz5VtJBcnw7tKlkEj+EsJAxL8sdrq7mA2yyrPxqceuv99XlwYwYt Qcvyu2EnE3HAaJxKxgGnzBCqUC88hUAZzl4KDDnp550FiJ9eeKq9SoxEYkxtLFtAoNBu AU5R6QjYWFREcxpKPIG2jPU7BoxgKPlamtbZSRJB0kt3Gtls7Cz6vdNLN7cMsvPQmQhT L9UaLss7FTExyfWqIpyEHna7qRaP3JsdY1AALPZjYI+mot8CyNlc8osKy8mrsnwM6z1z DA4A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-transfer-encoding; bh=O1eRedJK9IdPWwKpKvDm93aGr2UmEEHPs+NTNinredU=; b=ll39BtgkpunSIOMwWl90qKTAGuDszvGp/2Wn2LayGKH3IF2A3DHMVB97L9K+41jnOZ /XyvJNnLFarprAqjb90xmQc+fqcGdxVyKQN+5dqo1iYFrkYKtgMQa6dgZGC9bqvV+jEz rYa/OnV4D48Xza6AIAIAdw4RNiSPDMFbJvs+tOPxQoPnzzUrNaWoQ5zhgNU06uVw8w/q CVkbxQY8fHcSBBhHxOwfQ5e5x+rZGLQeJlhgqJ32ykhNiOrauFjyjv7AZ2Y38TvDfreW HXazZeSxXXbs3RJ9T8dFq2uzxPQQoaNgsydx32ZQ0Lv59nDvgiVhDA84huzXtUxwjVWy GiYw==
X-Gm-Message-State: AHYfb5hCTHVu+/RMJ/GvCGnu/U/mGGQhjYWDDbJos0ax8oszj/7+7Lua xxmFRt1BoMarettYcoeRwSA82lolZw==
X-Received: by 10.55.138.67 with SMTP id m64mr1498445qkd.6.1502123710564; Mon, 07 Aug 2017 09:35:10 -0700 (PDT)
MIME-Version: 1.0
Sender: olga.kornievskaia@gmail.com
Received: by 10.12.186.148 with HTTP; Mon, 7 Aug 2017 09:35:09 -0700 (PDT)
In-Reply-To: <DA0CDD40-EE28-441A-9DF9-2253B2ED0675@primarydata.com>
References: <9E3B8A6F-E27C-4A65-A0F7-6E0275B0616A@primarydata.com> <20170728022333.GI58771@kduck.kaduk.org> <CAN-5tyG9cE9JhccW7Fnho10jVE-5YnpoArZ=3DZuz79dFFD9sQ@mail.gmail.com> <CADaq8jc=K5f4cia-jFKjDMAtNhZntFE+Xa0=Lb=LSXOy+sc7Ww@mail.gmail.com> <37BF354D-CF56-4A1C-B391-8565F0E38E72@primarydata.com> <CAN-5tyH-j937PPA=nRSA5iEHOTKynryQjwfKui9dgVdZa3oQrQ@mail.gmail.com> <CAFAFD9C-DF89-4867-8880-1EA43FD4095F@primarydata.com> <CAN-5tyEKO1WVFXZAmW-bxX7bLXUtt2NM97rQi0QsrFpK70M9hw@mail.gmail.com> <DA0CDD40-EE28-441A-9DF9-2253B2ED0675@primarydata.com>
From: Olga Kornievskaia <aglo@citi.umich.edu>
Date: Mon, 07 Aug 2017 12:35:09 -0400
X-Google-Sender-Auth: W_EJodwb48o-JfiFXxm0eaQCkqo
Message-ID: <CAN-5tyG=wSE7y1uJwk5RcbPS2ZU1vXbb8L+otwFAPRovzLYQ2g@mail.gmail.com>
To: Thomas Haynes <loghyr@primarydata.com>
Cc: Dave Noveck <davenoveck@gmail.com>, Benjamin Kaduk <kaduk@mit.edu>, "nfsv4@ietf.org" <nfsv4@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/J0DpjTMVlKzLqNVGczpsAk5PpiM>
Subject: Re: [nfsv4] New wording of Security Section for Flex Files
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, 07 Aug 2017 16:35:12 -0000

On Mon, Aug 7, 2017 at 12:22 PM, Thomas Haynes <loghyr@primarydata.com> wrote:
>
>> On Aug 7, 2017, at 9:06 AM, Olga Kornievskaia <aglo@citi.umich.edu> wrote:
>>
>>
>> Sorry might be a stupid question but why do you need to wait for another version to add back "opaque_auth/or something" that carries the security information?
>
>
> Not a stupid question, I’m just so used to dealing with it that I don’t explain it all of the time:
>
> We’ve had flex files in the Linux client for over 2 years and it understands the ff_data_server4 structure
> to be a given byte format.  So an older client implementation would not be able to work with
> a server which added the security field to the data structure.

Thanks! Makes sense now.

v2.27.8 | Report a Bug | By Email | System Status