Re: [nfsv4] High-priority items for discussion at IETF 105, take 2

<Faibish.Sorin@dell.com> Tue, 16 July 2019 11:52 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 2E9BE12004D; Tue, 16 Jul 2019 04:52:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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
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 kqxjtM-kh8t5; Tue, 16 Jul 2019 04:52:32 -0700 (PDT)
Received: from mx0a-00154904.pphosted.com (mx0a-00154904.pphosted.com [148.163.133.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 266CF12001B; Tue, 16 Jul 2019 04:52:32 -0700 (PDT)
Received: from pps.filterd (m0170390.ppops.net [127.0.0.1]) by mx0a-00154904.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x6GBnoHf014155; Tue, 16 Jul 2019 07:52:31 -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=bKoJPMukZFO4XLNun9CK7N6H9uuoXkXwVjfpR5Oj0dY=; b=iCYH/l//HFWqtFUqj56VUCT3HiPBSpAeZeEBDJG6JKrpkkNdZru4J1aFGhfdcuo3V8uW Nn2TJaxzZJsLvYsvO5jqnd40OJFllKQtIF12M81sTwq6q9QOIYnqSlMjQKFdcnAvgvLr v18er3fdLgtVtTLS286K57/46W75ruE/Mc/v6I6rTyO8o7wllLOCVctEVFP9saIrX/gG 5cOxAg93RRxl+7Xs0DXj9qZggZdsJ6KPoKt6PvgFnshzMr4PY7qKbcRV4LqwtyrpsQog icjhsC+07QHpUOHKoPHmaoxg1kQNJZly0/RbbCDmm5KLFgSRg4BnzNKtMB3uj5F6Amwd Jw==
Received: from mx0b-00154901.pphosted.com (mx0b-00154901.pphosted.com [67.231.157.37]) by mx0a-00154904.pphosted.com with ESMTP id 2tsa4a9xvc-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 16 Jul 2019 07:52:31 -0400
Received: from pps.filterd (m0144104.ppops.net [127.0.0.1]) by mx0b-00154901.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x6GBmLXD192996; Tue, 16 Jul 2019 07:52:30 -0400
Received: from ausxipps306.us.dell.com (AUSXIPPS306.us.dell.com [143.166.148.156]) by mx0b-00154901.pphosted.com with ESMTP id 2tsc5c9mtr-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 16 Jul 2019 07:52:30 -0400
X-LoopCount0: from 10.166.135.95
X-PREM-Routing: D-Outbound
X-IronPort-AV: E=Sophos;i="5.60,349,1549951200"; d="scan'208,217";a="347412632"
From: <Faibish.Sorin@dell.com>
To: <davenoveck@gmail.com>
CC: <spencer.shepler@gmail.com>, <nfsv4@ietf.org>, <nfsv4-chairs@ietf.org>
Thread-Topic: [nfsv4] High-priority items for discussion at IETF 105, take 2
Thread-Index: AQHVMEKfo7+piHxqRkuzYAnBk6DSH6a3xjuAgAASHYCAFZZegP//xnKt
Date: Tue, 16 Jul 2019 11:37:25 +0000
Message-ID: <31461E66-0F32-49DB-AF77-0E31F67A7CF4@dell.com>
References: <CADaq8jdjRyMD_im_3T7VPPX8T3FzCfL+bXsso8Bnz01aks88Nw@mail.gmail.com> <A8575F78-4307-48FB-BE7D-222FE4A9CC8F@gmail.com> <CAFt6Ba=4BjMF5Fr0dce5E7fDXOq4u9T1S-AKcubx_rwqM5oaww@mail.gmail.com>, <CADaq8jfFvp9mroqxV6z+ti8RL4Of=y7-Sr6Xpgw85=9kSGm8vA@mail.gmail.com>
In-Reply-To: <CADaq8jfFvp9mroqxV6z+ti8RL4Of=y7-Sr6Xpgw85=9kSGm8vA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_31461E660F3249DBAF770E31F67A7CF4dellcom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-07-16_03:, , 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-1907160148
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 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-1907160148
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/FvUhtJw_EJGhYDaSvFux0N6InIQ>
Subject: Re: [nfsv4] High-priority items for discussion at IETF 105, take 2
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: Tue, 16 Jul 2019 11:52:36 -0000

Thank you Dave for the consideration.

./Sorin

Sent from my iPad

On Jul 16, 2019, at 7:04 AM, David Noveck <davenoveck@gmail.com<mailto:davenoveck@gmail.com>> wrote:


[EXTERNAL EMAIL]

I didn't see an agenda for the working group meeting on the web.   Also, the deadline for wg agenda submission has already passed (it was 7/15).   This leaves Sorin and Tom uncertain about whether they will be able to present in Montreal (or remotely if necessary).

In order to address this impasse, I'd like to propose that we base the meeting (probably without a formal agenda) on the high-priority items that Chuck and I came up with and sent out on July 1.  Since those only amount to 95 minutes total, there should be time to allocate both Tom and Sorin 10 minutes each for their presentations.   In order for this to work, all presenters, and whoever winds up chairing the meeting, will have to be mindful of time constraints so that Sorin and Tom each get their time to present.

On Tue, Jul 2, 2019 at 1:24 PM spencer shepler <spencer.shepler@gmail.com<mailto:spencer.shepler@gmail.com>> wrote:

Thanks everyone. I am vacation this week but will pull things together once I am back.

Spencer


On Tue, Jul 2, 2019 at 12:19 PM Tom Haynes <loghyr@gmail.com<mailto:loghyr@gmail.com>> wrote:
Hmm, I also asked for presentation time….



On Jul 1, 2019, at 12:23 PM, David Noveck <davenoveck@gmail.com<mailto:davenoveck@gmail.com>> wrote:

Although we have decided to meet in Montreal, have a (two-hour) session scheduled, and Chuck and I have sent lists of proposed topics to the group, we need to get an agenda together for the meeting.   Chuck and I have discussed what we feel are the high-priority topics for discusion at the meeting.   I previously sent out an incomplete preliminary agenda.   Since then, there have been a few updates, so I'm sending the updated list of items.   In any case, we still need to hear from:

  *   Anyone who knows of additional high-priority items to be added the list.
  *   Anyone who feels that we should not be talking about any of the items currently on the list

It looks like there will be additional time available.   If people have worthwhile items to discuss that are not high-priority, they should send messages to the list and assess interest.   If there are too many to fit, the working group can express its priorities.  If we still wind up with available time when IETF105 rolls around, we can open up the meeting for whatever people would like to bring up.

--------------------------------------------------------------------------------------------------------

Agenda Bashing -- All -- 5 min..

Current updates to NFSv4 spec -- D. Noveck -- 20 min.

This will cover the following documents

  *   RFC8587 (NFS Version 4.0 Trunking Update): It makes sense to discuss this together with the document below since the trunking-related updates for both NFSv4.0 and NFSv4.1 are pretty much the same, even though one is cuurrently an RFC, while the other will probably not be when we meet.
  *   draft-ietf-nfsv4-rfc5661sesqui-msns (Network File System (NFS) Version 4 Minor Version 1 Protocol): This provides updates to NFSv4.1 dealing with trunking and transparent state migration.  There will be a discussion regarding the state of the approval/publication process.

Review of Current Working group Milestones -- D. Noveck -- 20 min.

This will cover all of our current miilestones.   In two cases, the milestones gave already been achieved.

There are six items that have not yet been achieved that still need to be discussed:

  *   Submit final document describing use of NVMe in accessing a pNFS SCSI Layout (as Proposed Standard)

No current document but still has working group interest. Probably should not be a milestone. Need a plan to go forward with this.

  *   Submit Final documents descibing NFSv4.1 trunking discovery and NFSv4.1 Transpaent state migration (two milestones neing addressed by one document)

This is now addressed in the working group document, draft-ietf-nfsv4-rfc5661sesqui-msns (Network File System (NFS) Version 4 Minor Version 1 Protocol):. Discussed in detail in another talk.

  *   Submit final document describing CM private data convention for RPC-over-RDMA version 1 (Informational)

This is now a working group document draft-ietf-nfsv4-rpcrdma-cm-pvt-data (RDMA Connection Manager Private Data For RPC-Over-RDMA Version 1).  It is on its way to IESG consideration.

  *   Submit final document describing RDMA Layout for pNFS.

No current document but still has working group interest. Possibly  should not be a milestone. Need a plan to go forward with this.

  *   Submit final document defining RPC-over-RDMA Version 2 (as Proposed Standard)

This is now an I-D, draft-cel-nfsv4-rpcrdma-version-two (RPC-over-RMA Version Two Protocol). This will be discussed in one of the additional talks.

RPC-TLS and related security work -- C.Lever -- 15 min.

This will be primarily focused on draft-etf-nfsv4-rpc-tls (Remote Procedure Call Encryption by Deafault) but we also want to discuss the potential need for other documents such as an NFSv4-focused document and documents relating to QUIC.

Moving Forward on Integrity Measurement Draft -- C. Lever -- 10 min.

Time for discussion of the future of  draft-ietf-nfsv4-integrity-measurement (Integrity Measurement for Network File System version 4) and possible objection/issues with that draft.

RPC-over-RDMA Version 2 -- C. Lever -- 10 min.

Discussion of current atatus and what is necessary to go forward with this document.

Proposed Plans for rfc5661bis -- D. Noveck -- 15 min.

Will discuss updates that need to be done to provide a reasonably current description of NFSv4.1.   The assumption is that the bis RFC document will be based  on draft-ietf-nfsv4-rfc5661-msns-update (NFS Version 4.1 Update for Multi-Server Namespace) coverted, as the IESG appears to want, into a bis-like format but that the following additional changes would need to be added:

  *   Updates to reflect the changes Tom made to pNFS mapping type requirements in RFC8434.
  *   Changes to avoid the NFSv4.1 specification contradicting RFC8178.
  *   A new internationalization section modeled on that in RFC7530
  *   A new Security Considerations section that meets the requirements of RFC3552 and reflect the changes/advances made my the security work now underway.
  *   Current erratta.
  *   Anything else people think needs to be fixed in the NFSv4.1 specification.

We can also consider alternate plans to provide more current NFSv4.1 specification documents.
_____________________________________________________________________________

I'd like to mention that, for those unable to be in Montreal on the week of 7/20, remote participation will be available, even for people who want to present a talk.   Time zones can be a drag, but it is well worth considering remote presentation if you have something you think the working group needs to  hear.
_______________________________________________
nfsv4 mailing list
nfsv4@ietf.org<mailto:nfsv4@ietf.org>
https://www.ietf.org/mailman/listinfo/nfsv4

_______________________________________________
nfsv4 mailing list
nfsv4@ietf.org<mailto:nfsv4@ietf.org>
https://www.ietf.org/mailman/listinfo/nfsv4
_______________________________________________
nfsv4 mailing list
nfsv4@ietf.org<mailto:nfsv4@ietf.org>
https://www.ietf.org/mailman/listinfo/nfsv4
Dell Corporation Limited is registered in England and Wales. Company Registration Number: 2081369
Registered address: Dell House, The Boulevard, Cain Road, Bracknell,  Berkshire, RG12 1LF, UK.
Company details for other Dell UK entities can be found on  www.dell.co.uk.