Re: [nfsv4] Potential charter update - removal of "use of NVMe in accessing a pNFS SCSI Layout" work item

"faibish, sorin" <Faibish.Sorin@dell.com> Mon, 20 May 2019 18:20 UTC

Return-Path: <Faibish.Sorin@dell.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 B9460120044 for <nfsv4@ietfa.amsl.com>; Mon, 20 May 2019 11:20:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.709
X-Spam-Level:
X-Spam-Status: No, score=-2.709 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dell.com header.b=dCQyB3gd; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=emc.com header.b=vpf1K2Qc
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 NW4sW8Um2IQs for <nfsv4@ietfa.amsl.com>; Mon, 20 May 2019 11:20:50 -0700 (PDT)
Received: from mx0b-00154904.pphosted.com (mx0b-00154904.pphosted.com [148.163.137.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43EDA120026 for <nfsv4@ietf.org>; Mon, 20 May 2019 11:20:50 -0700 (PDT)
Received: from pps.filterd (m0170397.ppops.net [127.0.0.1]) by mx0b-00154904.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x4KIAWHA018294; Mon, 20 May 2019 14:20:47 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dell.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=smtpout1; bh=0flG6Ww57+GJ/eaqoJPLhrUOim6P9h7m11BCj7F3cAM=; b=dCQyB3gdTApcTIjjv6bBGsLidUJJlPMoB9OEv3MPQm4MGn+6ZIEvhZhk4axElZUy5nWc qdzeIjhQXhm9qhGgwV+IerwKYNE3pC6wUx0ZZbuieDiTEHeop7Zh2/SHHpA1AAWaG7B/ UwDcA6SxEAoOxlij7xwaQUdZSTNTcN+pVNg0vsWH10sMPZl3v9OV5J3ybsqVOewX1BR6 7F3EjgAqt9tGMSpGWaLARnweajtJc2aPr4crxZ0vunzThIuRX6V+W9tLNfrW20xXPF5P f6hCfVJj1VH2EvPMUaDuCc4tstbNPOInNw8VBpIhL6U+Ty1877TLQEqc23JCzOat6BAS JQ==
Received: from mx0a-00154901.pphosted.com (mx0a-00154901.pphosted.com [67.231.149.39]) by mx0b-00154904.pphosted.com with ESMTP id 2sjb4s5ern-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 20 May 2019 14:20:47 -0400
Received: from pps.filterd (m0134746.ppops.net [127.0.0.1]) by mx0a-00154901.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x4KI81RL070725; Mon, 20 May 2019 14:20:46 -0400
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by mx0a-00154901.pphosted.com with ESMTP id 2skysrskxc-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Mon, 20 May 2019 14:20:45 -0400
Received: from maildlpprd54.lss.emc.com (maildlpprd54.lss.emc.com [10.106.48.158]) by mailuogwprd52.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id x4KIKb2E030094 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 20 May 2019 14:20:44 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com x4KIKb2E030094
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1558376444; bh=un9WLleci1lIB68YYv4pZD1eeNE=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=vpf1K2QcQFlLMBenTA6LIWi7ezl5D//NWLTUbA12pHxtw6Ysx65pJlMFgPK+rxsXe B5vrZxAaY6Ug3LhOx/wld4CXUyRsVmZZY89MKe4FiimjEQrRY9eatXC2Qwzs+rqcr8 R03QqUvSwVRpTBg7nZjA2bSBlSBcRNagzviQdWWw=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com x4KIKb2E030094
Received: from mailusrhubprd54.lss.emc.com (mailusrhubprd54.lss.emc.com [10.106.48.19]) by maildlpprd54.lss.emc.com (RSA Interceptor); Mon, 20 May 2019 14:20:10 -0400
Received: from MXHUB315.corp.emc.com (MXHUB315.corp.emc.com [10.146.3.93]) by mailusrhubprd54.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id x4KIK9wm012520 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Mon, 20 May 2019 14:20:09 -0400
Received: from MX304CL01.corp.emc.com ([fe80::2d21:ebf8:dc15:2b07]) by MXHUB315.corp.emc.com ([10.146.3.93]) with mapi id 14.03.0439.000; Mon, 20 May 2019 14:20:09 -0400
From: "faibish, sorin" <Faibish.Sorin@dell.com>
To: spencer shepler <spencer.shepler@gmail.com>, Chuck Lever <chuck.lever@oracle.com>
CC: NFSv4 <nfsv4@ietf.org>
Thread-Topic: [nfsv4] Potential charter update - removal of "use of NVMe in accessing a pNFS SCSI Layout" work item
Thread-Index: AQHVDyJjjzGEcrOc60CV+bvXczDXhaZ0ajEAgAABGoCAAAIYAIAAAdgAgAAAiACAAAm6gP//2L/g
Date: Mon, 20 May 2019 18:20:08 +0000
Message-ID: <2313358402DBCC4DB2F2DC03CB08BBFE01A71832@MX304CL01.corp.emc.com>
References: <CAFt6Ba=t6dPX2kky-1h+dFo7zr75AqpsDF0ypoMzunKM8RMkQA@mail.gmail.com> <0604B063-3A9B-4B6E-BAF2-53568D4C5CC1@oracle.com> <CAFt6BakJOOOCjxFH9NMdhWqQWSiV7FayLcp8JMOOB97_=JkF_A@mail.gmail.com> <64D9C067-BFF8-4896-AF39-46416BB523F0@oracle.com> <37FC4CCF-97DC-4DFF-8497-D3597D88CF91@redhat.com> <05F68A95-DC80-4202-83B6-50AB6BE143F4@oracle.com> <CAFt6Ba=aPN+Y2mUdn7PQyZvCiHXXDRDviOgV8wiXJQw+Pi1GVA@mail.gmail.com>
In-Reply-To: <CAFt6Ba=aPN+Y2mUdn7PQyZvCiHXXDRDviOgV8wiXJQw+Pi1GVA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.238.78.133]
Content-Type: multipart/alternative; boundary="_000_2313358402DBCC4DB2F2DC03CB08BBFE01A71832MX304CL01corpem_"
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd54.lss.emc.com
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-05-20_07:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1905200114
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1905200114
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/yU48v9zx4Ad9wUmz_dcOZoQEAbA>
Subject: Re: [nfsv4] Potential charter update - removal of "use of NVMe in accessing a pNFS SCSI Layout" work item
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.29
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, 20 May 2019 18:20:53 -0000

Spencer,

If the agenda is not closed yet I would like 10 minutes to discuss new attributes for data reduction. Just slides presenting the problem and few ways to address it. It could bridge into the pNFS SCSI but only indirectly as the purpose of the new attributes are referring to NVMe. Please let me know if I can get 10 min. thanks

./Sorin

From: nfsv4 <nfsv4-bounces@ietf.org> On Behalf Of spencer shepler
Sent: Monday, May 20, 2019 12:38 PM
To: Chuck Lever
Cc: NFSv4
Subject: Re: [nfsv4] Potential charter update - removal of "use of NVMe in accessing a pNFS SCSI Layout" work item


[EXTERNAL EMAIL]

Since it has been 18 months the expiration, etc., I just want to be realistic about keeping it as a WG milestone.

The work can certainly continue and we can readapt the milestones - just doing some housecleaning.

Spencer


On Mon, May 20, 2019 at 9:03 AM Chuck Lever <chuck.lever@oracle.com<mailto:chuck.lever@oracle.com>> wrote:


> On May 20, 2019, at 12:01 PM, Benjamin Coddington <bcodding@redhat.com<mailto:bcodding@redhat.com>> wrote:
>
> On 20 May 2019, at 11:54, Chuck Lever wrote:
>
>>> On May 20, 2019, at 11:46 AM, spencer shepler <spencer.shepler@gmail.com<mailto:spencer.shepler@gmail.com>>
>>> wrote:
>>>
>>>
>>> I would prefer that we discuss and close on as many of the outstanding
>>> discussions via the alias - prior to the face to face meeting.
>>
>> My understanding is that the author intends to revive the document when he
>> has the resources to complete it. There has been no movement here recently
>> and the author has allowed the document to expire.
>>
>> However we have discussed the topic at every IETF meeting for the past few
>> years because there is still plenty of interest in seeing it completed. We
>> agreed to leave the item on the charter as a placeholder.
>>
>> Perhaps it is a topic that is not appropriate as a milestone. Somehow we
>> should document the WG's continued interest in this area. Any suggestions?
>
> I'm interested in picking up work on NVMe access for pNFS SCSI Layouts.
>
> What would be the practical result of removing this work item from the
> milestone list?

For a prototype implementation, probably nothing. You can still communicate
any interesting findings to the document author or the Working Group.


--
Chuck Lever