IETF Logo Mail Archive

Re: [nfsv4] rfc5666bis and rpcrdma-bidirection progress update

David Noveck <davenoveck@gmail.com> Tue, 29 November 2016 09:51 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 B887F12964A for <nfsv4@ietfa.amsl.com>; Tue, 29 Nov 2016 01:51:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.439
X-Spam-Level:
X-Spam-Status: No, score=-2.439 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, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_DNSWL_LOW=-0.7, 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 sxxFtF4OFre5 for <nfsv4@ietfa.amsl.com>; Tue, 29 Nov 2016 01:50:59 -0800 (PST)
Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (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 D9802129643 for <nfsv4@ietf.org>; Tue, 29 Nov 2016 01:50:58 -0800 (PST)
Received: by mail-oi0-x230.google.com with SMTP id y198so183885350oia.1 for <nfsv4@ietf.org>; Tue, 29 Nov 2016 01:50:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=X27f/jDvZ6nmi7UyUnF2x03zZ0u2j26zIaFlyzOg1X4=; b=ZTJlXc/SYT2x9BrpkKzBliWKYZzKPTJzXqY9vuXpq2LH14oe0qgI4snFMNsNI+E079 E1tpAN5t3aIM5lPiXv5nrXC4dQexu5Es9Jd53lVANTphKXJAlzpzslJ6f4JNP9AiLVTd EZXbV/RDLvTdEXXXKfGigbkz4CdqsrRuwCnqkDOtSdB7AXs8h51XDTQivVS1/pc0e85k 4MMaSjYk7pBu56yC+S58DLpYvpXU4F9qcxTBSzYC1OfCpEI6K9dEwq/Egavds216eqIQ 6bcdDqqPPXtUaGcjm5Eokrg0BHLOsSYZDG+e6JHAyMOHVrK4TuwRcht155ClDahKxyhm bg/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=X27f/jDvZ6nmi7UyUnF2x03zZ0u2j26zIaFlyzOg1X4=; b=lUDqeJQMYDc/nZCypWuwa+znZDXPdjLVBo3mybtCuqUMduYji5OP4ZP9PBfSvZYTE6 7RjT5N1Z6JThLkRNCjr/flHZ0rOfDoqU7GPXw+RltKhdfJLYwODQJd4yJ0/8uQeu7TqH SVrP5LUQq6X5ncgE4C0WevNKm3/y5Oxw19jgsJ2Hnt9z8nfXTkjYEwEVLMmz9J3JbeCu NN1GDh7/Pj2ryeldOUm4eQ2uqH3XWKqNt4VOUhp3BvCmtzzs+8M7HFUvkPc2YVDnXqgn fgYY3lDDBuckOJdQef6F/Itnhx00+kwvgBWzE+kWU0Z7A16BhExElDoI+aQCMaOsaBmR aysg==
X-Gm-Message-State: AKaTC02mEVC+DF31QDQrOUouLmfjCcwIC1iMBayH0Nwv4j0R/a6l8LoATV/BAp04XXS02Z41YEYnc0Y5NyxmEQ==
X-Received: by 10.157.11.14 with SMTP id a14mr15973182ota.185.1480413058261; Tue, 29 Nov 2016 01:50:58 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.137.202 with HTTP; Tue, 29 Nov 2016 01:50:57 -0800 (PST)
Received: by 10.182.137.202 with HTTP; Tue, 29 Nov 2016 01:50:57 -0800 (PST)
In-Reply-To: <5f2e984d-54db-5998-f9cd-58bf0ea0a88a@gmail.com>
References: <6ED97840-F1BF-4BBC-9C01-7F0A8943CB78@oracle.com> <MWHPR03MB289336B4D7E04D053D27D225C7A80@MWHPR03MB2893.namprd03.prod.outlook.com> <4958FA14-2C47-4AEA-A72F-1C83F92DB4BE@oracle.com> <a3368e2b-ae35-ddef-80b3-d33646e46d88@gmail.com> <F924E4D7-3E26-4BFA-A82E-3713CDBC560A@oracle.com> <CADaq8jduTgJCsdhVmDV0wiiuhf0fkJXYYbsJ0znibipqFuQOZw@mail.gmail.com> <MWHPR03MB28934787F990928A41E84830C78A0@MWHPR03MB2893.namprd03.prod.outlook.com> <CADaq8jdpMCuq5k+k_Gjj4rC6iOgCt5xjwjorcPakRgsbqOWfMg@mail.gmail.com> <MWHPR03MB2893DA050246297A8E362D92C78A0@MWHPR03MB2893.namprd03.prod.outlook.com> <5C52351B-09D7-4273-85E7-445B642FDDCC@oracle.com> <MWHPR03MB28932EE72AB17813102AC8A3C78A0@MWHPR03MB2893.namprd03.prod.outlook.com> <5f2e984d-54db-5998-f9cd-58bf0ea0a88a@gmail.com>
From: David Noveck <davenoveck@gmail.com>
Date: Tue, 29 Nov 2016 04:50:57 -0500
Message-ID: <CADaq8jeDBuZGmn_O3tLCMTUiJxbane+Hn-6nyDf=HVEfjfd9vA@mail.gmail.com>
To: William Allen Simpson <william.allen.simpson@gmail.com>
Content-Type: multipart/alternative; boundary="001a113db65075667405426d8670"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/1DmH1Kk3NtqLqHPTY2xCQ6Y3cA0>
Cc: nfsv4@ietf.org
Subject: Re: [nfsv4] rfc5666bis and rpcrdma-bidirection progress update
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.17
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, 29 Nov 2016 09:51:01 -0000

It is possible to get around this in gmail by creating a filter. One of the
options, for a defined set of messages, such as messages from a given
address, is to not treat the message as spam. Then it appears in your inbox
normally, except it is preceded by a little note: Why is this message not
in spam? :-)

On Nov 29, 2016 2:23 AM, "William Allen Simpson" <
william.allen.simpson@gmail.com> wrote:

> Why is this message in Spam? It has a from address in microsoft.com but
> has failed microsoft.com's required tests for authentication.
>
> (For all your messages today.  Thank goodness I check spam every so often.)
>
> On 11/28/16 5:33 PM, Spencer Shepler wrote:
>
>>
>> Chuck,
>>
>> You comment:
>> "It would help to get regular status updates on the document pipeline,
>> whether there are any hold-ups, and what the non-executive members of the
>> WG can do about them. IESG review processes are managed off the WG mailing
>> list, thus many of us are not privy to progress on individual I-Ds, nor do
>> we have a sense of what tasks there are remaining to do. The chairs are
>> usually copied on all of this. Perhaps they could monitor and periodically
>> reflect a summary to the WG.[Spencer] "
>>
>> Sure, I can work to push out a summary for those time where documents are
>> hung up on procedural or review comments, etc.
>>
>> For those that are interested to follow along, all document status for
>> the WG can be found here:
>>
>> https://datatracker.ietf.org/group/nfsv4/documents/
>>
>> Current state of the document, next steps, and what they mean are
>> available via these pages.
>>
>> For an individual document that has been or is going through IESG the
>> specific comments and feedback are captured.  For example, the iSCSI layout
>> document comments are listed here: https://datatracker.ietf.org/d
>> oc/draft-ietf-nfsv4-scsi-layout/ballot/
>>
>> Spencer
>>
>>
>>
>> _______________________________________________
>> nfsv4 mailing list
>> nfsv4@ietf.org
>> https://www.ietf.org/mailman/listinfo/nfsv4
>>
>>
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4
>

v2.14.0 | Report a Bug | By Email