[nfsv4] Future of del-stid stuff

David Noveck <davenoveck@gmail.com> Tue, 21 May 2019 10:58 UTC

Return-Path: <davenoveck@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 5BBB71200D7 for <nfsv4@ietfa.amsl.com>; Tue, 21 May 2019 03:58:22 -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 R19B1_OiSVMf for <nfsv4@ietfa.amsl.com>; Tue, 21 May 2019 03:58:21 -0700 (PDT)
Received: from mail-ot1-x334.google.com (mail-ot1-x334.google.com [IPv6:2607:f8b0:4864:20::334]) (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 DBAEA120048 for <nfsv4@ietf.org>; Tue, 21 May 2019 03:58:20 -0700 (PDT)
Received: by mail-ot1-x334.google.com with SMTP id 66so15952809otq.0 for <nfsv4@ietf.org>; Tue, 21 May 2019 03:58:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=MCOuePqvR09IXA0sA+3riR4nt2D22ovhdPZvy8jyoaA=; b=ZsgIwtiQBx719VuvKWHLpgamodAx2oGBA6zjyE1EjogrqK8N8M5bGSfiD3lTsRprC9 1GDWjpVj+hjjKT68dYqXssnzSa4vabdwfjX659BDrkGfjbVlOxwTNs87a7AzLp4Egtp7 9o1kWeOZSNPcmID6s17S8hL/VB1iyS9eB/Qb51pSxNDb8j8u2KBVfyl3BciODxL7sgdh Q5tIDud8DeOdgVkbrqJ8Rb/1kvPmLk3vKQrkLO9Bu5DSjQ9/bRNNPs5tFcTX4t/8nzmY 9Vzyj6eXzX7+KMXnzDmVg/ZOp7ZixBk06bPo9oCiYlPtw05nR0Eyx1GHnNw5fRuHEEu+ 28Pg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=MCOuePqvR09IXA0sA+3riR4nt2D22ovhdPZvy8jyoaA=; b=oNkQZ2dT4pg/ZUJZO9Sv1/FGEBN42LMKf8TJKIfGQd7uqAiOIzOH8bBhasSXOS5Ws1 b4XLP//H6sF11c66T5wP6jt4qKivaHKuMWM7Mp24OaepShNcz4dwAhdE2wkKBpFnB3nS xxBf4B9d/O2NEHuQsQgQkkomhETcP43TeIlcAotkrLLmkWNxqgtymqwqVy62Ue2ydVno xP7RMW9VdqT/s9MQJfuceN6d0IE9fAqXghCXAyD1SjkAcOc46VJXp32MU3C3OWSbfMPD OUnZrvexKzQkmE78PuSLD4oCmUyrwpWBiq59WY/KFBnCzBCIeSELRl4vlj4EoD8tYDT/ HKDA==
X-Gm-Message-State: APjAAAWWM9aZKoBOWRLhZ6neE8xm/wu4FotGb+cCWOlFo0yMPHlfEz07 OQlYqDEfs4eQ5rqWVJNwGctG+td1e51/U8ziELo=
X-Google-Smtp-Source: APXvYqx5MZ0HDqcWDdVdhiYzp6izRx+zElM3nV9nRnnKoGA0JofC5CLYZHv0s0QfuyBDH5ZrIJEccx264QxzmGMYANQ=
X-Received: by 2002:a9d:4809:: with SMTP id c9mr457972otf.208.1558436300108; Tue, 21 May 2019 03:58:20 -0700 (PDT)
MIME-Version: 1.0
From: David Noveck <davenoveck@gmail.com>
Date: Tue, 21 May 2019 06:58:09 -0400
Message-ID: <CADaq8jdMq+cXisqsftAL9skxJ1+yTw3e+xdSFciZnTchvwGwGw@mail.gmail.com>
To: Thomas Haynes <loghyr@gmail.com>
Cc: NFSv4 <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000012b663058963bada"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/dNJGSbtBZbnMDLMe4qfSGzV60VE>
Subject: [nfsv4] Future of del-stid stuff
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, 21 May 2019 10:58:22 -0000

Do you have any plans to continue the work you started in your del-stid
draft?   It looks like there will be some time available at IETF105 even
adfter the high-priority items mentioned by Chuck and me are dealt with.
If there are travel issues, you could consider participting remotely.   If
a presentation for IETF105 doesn't work for you, it would help if you could
send a message letting the working group know about the future of this
work, if any.