IETF Logo Mail Archive

[nfsv4] Re: Feedback on user ID for any bis work

"Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de> Thu, 29 August 2024 15:02 UTC

Return-Path: <tigran.mkrtchyan@desy.de>
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 D2F7DC15109A for <nfsv4@ietfa.amsl.com>; Thu, 29 Aug 2024 08:02:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.651
X-Spam-Level:
X-Spam-Status: No, score=-1.651 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, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.455, 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 (1024-bit key) header.d=desy.de
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 5mxF2dA_ubbG for <nfsv4@ietfa.amsl.com>; Thu, 29 Aug 2024 08:02:13 -0700 (PDT)
Received: from smtp-o-2.desy.de (smtp-o-2.desy.de [IPv6:2001:638:700:1038::1:9b]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0ABBC14F697 for <nfsv4@ietf.org>; Thu, 29 Aug 2024 08:02:11 -0700 (PDT)
Received: from smtp-buf-1.desy.de (smtp-buf-1.desy.de [131.169.56.164]) by smtp-o-2.desy.de (Postfix) with ESMTP id 2598513F651 for <nfsv4@ietf.org>; Thu, 29 Aug 2024 17:02:08 +0200 (CEST)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp-o-2.desy.de 2598513F651
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=desy.de; s=default; t=1724943728; bh=1rKwq1NZrT6a9/x2L1Wtq9istZf0hIpuHGmOYsgB8HU=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From; b=r54k+DEZCL1hbIe4QVzfUyp+6qGaHwHPhpfrhkXgHR0IvSCFMigmb1o6qNy58wRXV Trz4/HzYXyEuMqcv8jeCLNmJx14+7ydbaKrmKvM4g9Ix3zL0TOfOMm5CLYpribDCIK wqyI2n486PDe6LhwusiWuL7Vwich7vcdbmngP1C4=
Received: from smtp-m-1.desy.de (smtp-m-1.desy.de [IPv6:2001:638:700:1038::1:81]) by smtp-buf-1.desy.de (Postfix) with ESMTP id 1810120038; Thu, 29 Aug 2024 17:02:08 +0200 (CEST)
Received: from b1722.mx.srv.dfn.de (b1722.mx.srv.dfn.de [194.95.235.47]) by smtp-m-1.desy.de (Postfix) with ESMTP id 0E40340044; Thu, 29 Aug 2024 17:02:08 +0200 (CEST)
Received: from smtp-intra-3.desy.de (smtp-intra-3.desy.de [IPv6:2001:638:700:1038::1:45]) by b1722.mx.srv.dfn.de (Postfix) with ESMTP id E9704220039; Thu, 29 Aug 2024 17:02:06 +0200 (CEST)
Received: from z-mbx-2.desy.de (z-mbx-2.desy.de [131.169.55.140]) by smtp-intra-3.desy.de (Postfix) with ESMTP id 931781A003E; Thu, 29 Aug 2024 17:02:06 +0200 (CEST)
Date: Thu, 29 Aug 2024 17:02:06 +0200
From: "Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de>
To: Chuck Lever III <chuck.lever@oracle.com>
Message-ID: <1086079167.54167075.1724943726342.JavaMail.zimbra@desy.de>
In-Reply-To: <2C377184-60B5-43B3-9FAD-33F682DBAC5D@oracle.com>
References: <EFD2C35A-9FC4-4381-82F2-475957CEE07B@cert.org> <1452890090.47955225.1723888278946.JavaMail.zimbra@z-mbx-2> <2C377184-60B5-43B3-9FAD-33F682DBAC5D@oracle.com>
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="----=_Part_54167076_986906765.1724943726472"
X-Mailer: Zimbra 9.0.0_GA_4612 (ZimbraWebClient - FF129 (Linux)/9.0.0_GA_4612)
Thread-Topic: Feedback on user ID for any bis work
Thread-Index: AQHa8La8an3vR2MFLUKhyJjmaE53blk1uI7e
Message-ID-Hash: JMBID2ITFBTRCOAJ4QVPPHQS4YPWDT4J
X-Message-ID-Hash: JMBID2ITFBTRCOAJ4QVPPHQS4YPWDT4J
X-MailFrom: tigran.mkrtchyan@desy.de
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-nfsv4.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: NFSv4 <nfsv4@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [nfsv4] Re: Feedback on user ID for any bis work
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/LofDYaM-KakziaFuZgmK1t51CRY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Owner: <mailto:nfsv4-owner@ietf.org>
List-Post: <mailto:nfsv4@ietf.org>
List-Subscribe: <mailto:nfsv4-join@ietf.org>
List-Unsubscribe: <mailto:nfsv4-leave@ietf.org>


Hi Chick,

The current state is available at:

https://github.com/kofemann/rpc-sec-oidc/blob/main/draft-tigran-nfsv4-rpcsecoidc.md

It is still quite raw, but indeed, if people comment, this will give me some guidelines and momentum.

Best regards,
   Tigran.

----- Original Message -----
> From: "Chuck Lever III" <chuck.lever@oracle.com>
> To: "Tigran Mkrtchyan" <tigran.mkrtchyan@desy.de>
> Cc: "Chris Inacio" <inacio@cert.org>, "NFSv4" <nfsv4@ietf.org>
> Sent: Saturday, 17 August, 2024 17:04:19
> Subject: Re: [nfsv4] Feedback on user ID for any bis work

>> On Aug 17, 2024, at 5:51 AM, Mkrtchyan, Tigran <tigran.mkrtchyan@desy.de> wrote:
>> 
>> 
>> One option that we are currently exploring is adding OIDC tokens support to RPC.
>> This will play nicely with RPC-over-TLS. It should allow to pass identity tokens
>> to server to map with ldap or a local configuration. I am trying to define
>> the problem statement as an personal draft, but not that active as I wish. So,
>> if general interest is there, then I will try to allocate more time to it.
> 
> Hi Tigran-
> 
> I think this approach is valuable. I recommend you submit an incomplete
> personal draft so others can help flesh out the problem statement. My
> two cents euro.
> 
> 
> --
> Chuck Lever

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