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

spencer shepler <spencer.shepler@gmail.com> Mon, 20 May 2019 16:38 UTC

Return-Path: <spencer.shepler@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 DE6051201D0 for <nfsv4@ietfa.amsl.com>; Mon, 20 May 2019 09:38:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 JdigWGpm73EA for <nfsv4@ietfa.amsl.com>; Mon, 20 May 2019 09:37:59 -0700 (PDT)
Received: from mail-lf1-x12d.google.com (mail-lf1-x12d.google.com [IPv6:2a00:1450:4864:20::12d]) (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 B0BFE1201D6 for <nfsv4@ietf.org>; Mon, 20 May 2019 09:37:58 -0700 (PDT)
Received: by mail-lf1-x12d.google.com with SMTP id d8so10813196lfb.8 for <nfsv4@ietf.org>; Mon, 20 May 2019 09:37:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=QNG9bmsxblfAUOPhmlniA9kxat+KUR4zn8KKmZT5iEk=; b=IU2WaPtOIAh471qGaxMcNVgIVA6ol1dAtXues5/JlqBflr5NYpC7UV52hNajI4nyr5 2k6uyePbHB9ovO8FBYeOC8zoDBkEgFtb8MdIt77FowrOHueDpLx17DEVCyp3sw9XRxeV 4wqETrRX46pnXF8MzshfuSoUynSCUIOu8S1Vzl3NqFNF3jWqjQetulqItevfgcdr2u22 LOU1C/Ot1IvEZOxEHoUUJQQAvTZ03aOCLhI3j1sn+6e1sgzhxi0ogw3Jmx3nDBFcCcCb 9FeFN38ssZMKEJ2TR3fccYQWpYOehLBkF31IkMCkIEC9bMb7bNf5mxoYpoL4ZspCfvCq MyNw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=QNG9bmsxblfAUOPhmlniA9kxat+KUR4zn8KKmZT5iEk=; b=jIOgFxI0IYsa4almE8xtVfLzhA18gGfY2k1D0KkxcB0xMRqMZvjbL//LDW8FKVDSOW ixFRrTImOnUXYYbFwIL4UOZ6QoG6iPGLqAMHb+8CD36Q15kSTCBsZVJXcvOYm3ndgTwK s3MCkjBPcswM4zJx94rKzFhcjLdgVPLZnv5EwM7MmHSBkb9E8s96V6rc7VQ7NXxFjb0C JYPd+2nXMf4h8XHIfDnGE+FKX3fxoBj60E83IUI44yk3dFW/H3XwvNx2zIOm7Sw7DatH gQVZANxOdWXiRY1vU2TjjzI8Ij9ezYGPlgs88T0kOlbqjWUox+lXKvJtFbWyJeSYw+1B FHdQ==
X-Gm-Message-State: APjAAAVH58tBFgOhfgGiEw1Es4Hski/QZoWOQ4r9v7YBvX0B8rPazjK7 6rG0IeQsqo7Z0BgsFMFXt+fN2iiV2gKQkgGeNVM=
X-Google-Smtp-Source: APXvYqznuDYjRSvlFkfLFXx4i7sXtjZXAmVXexacupRBiLfv9D+IQ5d4fXJaUxBS/kiXlhRuI2NSlfhlZKICr1cd11o=
X-Received: by 2002:a19:ae14:: with SMTP id f20mr36012575lfc.49.1558370276998; Mon, 20 May 2019 09:37:56 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <05F68A95-DC80-4202-83B6-50AB6BE143F4@oracle.com>
From: spencer shepler <spencer.shepler@gmail.com>
Date: Mon, 20 May 2019 09:37:45 -0700
Message-ID: <CAFt6Ba=aPN+Y2mUdn7PQyZvCiHXXDRDviOgV8wiXJQw+Pi1GVA@mail.gmail.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Benjamin Coddington <bcodding@redhat.com>, NFSv4 <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ca035d0589545a16"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/eSshZ2FNzhJCwDhXmYDnfh-ACsE>
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 16:38:01 -0000

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> wrote:

>
>
> > On May 20, 2019, at 12:01 PM, Benjamin Coddington <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>
> >>> 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
>
>
>
>