Re: [nfsv4] Fwd: New Version Notification for draft-ietf-nfsv4-layout-types-12.txt

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Thu, 19 April 2018 19:32 UTC

Return-Path: <spencerdawkins.ietf@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 2558512DA54 for <nfsv4@ietfa.amsl.com>; Thu, 19 Apr 2018 12:32:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 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_LOW=-0.7, 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=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 EpzXKj18dDPG for <nfsv4@ietfa.amsl.com>; Thu, 19 Apr 2018 12:32:39 -0700 (PDT)
Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::22c]) (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 9CBBB120454 for <nfsv4@ietf.org>; Thu, 19 Apr 2018 12:32:39 -0700 (PDT)
Received: by mail-yw0-x22c.google.com with SMTP id e63-v6so2028160ywh.6 for <nfsv4@ietf.org>; Thu, 19 Apr 2018 12:32:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=25wP3RNqUud6bDEVy7GogMqhpZCqtbkwSrSuxr0+F3c=; b=fEkiMWCf6EZ3H5a8Kt2kvt66AHJGuEZ/hbJWzgiTPMZkGEsBIMBrkpALDvBpqBURsy 36l6zdIOBYuNZU5L1ErZK+AkrjHN6RqbgNFXcPC73OBDaPv0w1+MBy6Pjq+osgHnc6g5 im32lDRN0SWAESPJlA3EscMHInWyx9RPG71DHnxEv2biqDV2rq/fptDsraiHzI5MiSwQ vpF663HNLJ16G3jT9kzfo1zmw/iyLH9Td6PeUxZ7hRdcEB/Ad8oZ4/R2XTnp4rLUXwGV fUHZoxiI7syqUI3VEHrLBYfeUKdOWpvx1EDZGXs6bRZalfQHqcIhKnVjj1j0XwbRzpfP CDmg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=25wP3RNqUud6bDEVy7GogMqhpZCqtbkwSrSuxr0+F3c=; b=frTGukkaGqHrdVsWxpeiTjCS7AH/QfbW9TiRM4CxYfWtjXIVOq9SC08iNKlrR8odHm rYeXMgwXok4wZpXR06XmrjpF3Xicq1kaWn1qaCr+F+90FS4j/7HDJhCcU3t3bSBiD+fL y3x8vXVCaJ9ZYb7jFvEHI9ftfH12zddwrDf7t/MYOhJc651UbcWfsOa7uP336nRCokWO xOtbfhYp8oURSTO+XCK0TlVKg2l/EA1diTC6op28Y4u1rbiOWm/+YMJJmsMPClJWLZXE ePDmldEy2KQ3UPtM+dDbQRpfT1jLbL0dYNyL42abYjeY8z4mGnHWHEmgVLomzC1pIJ9Q PsBQ==
X-Gm-Message-State: ALQs6tDYYzgtipvLSM1/nphxivk/mTyjXs44aq2V1czES9Vg9JmxWLys MC+WBfiTa2IboMxXh5tv/O+/ar8mUaA0dKa+XS3cVw==
X-Google-Smtp-Source: AIpwx482Nj6lM6qP1Ek+ExpezX5LqWnj7jRLM7EvA7kxkOxW9Te6LVCmNXhYnHqmcVo2uZQcQv3muG2zhTkLzYLZey0=
X-Received: by 2002:a81:ec14:: with SMTP id j20-v6mr4310572ywm.311.1524166358624; Thu, 19 Apr 2018 12:32:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a5b:192:0:0:0:0:0 with HTTP; Thu, 19 Apr 2018 12:32:37 -0700 (PDT)
In-Reply-To: <F27833FB-0667-4085-AD86-C46BBD2C0C73@gmail.com>
References: <152416107200.28684.15531571510439665324.idtracker@ietfa.amsl.com> <F27833FB-0667-4085-AD86-C46BBD2C0C73@gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 19 Apr 2018 14:32:37 -0500
Message-ID: <CAKKJt-c9ZtAgVd=qOudN6oLrPpZOu=8HE2hR2MaUhq4gH6Qixw@mail.gmail.com>
To: Tom Haynes <loghyr@gmail.com>
Cc: NFSv4 <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000626ebe056a38a2ed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/k3sfz_u0RPNeLER3fC-0nc4zAZQ>
Subject: Re: [nfsv4] Fwd: New Version Notification for draft-ietf-nfsv4-layout-types-12.txt
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 19 Apr 2018 19:32:42 -0000

Hi, Tom,

On Thu, Apr 19, 2018 at 1:05 PM, Tom Haynes <loghyr@gmail.com> wrote:

> This has the changes per the IESG review process.
>

This is looking good. I have one last question - did you see Mirja's
question about possible use of RFC 8174 boilerplate, since the draft uses
both uppercase and lowercase RFC 2119 language (and that's what RFC 8174 is
supposed to help with)?

Mirja's review ended up in the mailing list archive at
https://www.ietf.org/mail-archive/web/nfsv4/current/msg16137.html.

Thanks,

Spencer (D)


> Begin forwarded message:
>
> *From: *internet-drafts@ietf.org
> *Subject: **New Version Notification for
> draft-ietf-nfsv4-layout-types-12.txt*
> *Date: *April 19, 2018 at 11:04:32 AM PDT
> *To: *"Thomas Haynes" <loghyr@gmail.com>
>
>
> A new version of I-D, draft-ietf-nfsv4-layout-types-12.txt
> has been successfully submitted by Thomas Haynes and posted to the
> IETF repository.
>
> Name: draft-ietf-nfsv4-layout-types
> Revision: 12
> Title: Requirements for pNFS Layout Types
> Document date: 2018-04-19
> Group: nfsv4
> Pages: 16
> URL:            https://www.ietf.org/internet-drafts/draft-
> ietf-nfsv4-layout-types-12.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-nfsv4-
> layout-types/
> Htmlized:       https://tools.ietf.org/html/draft-ietf-nfsv4-layout-
> types-12
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-
> nfsv4-layout-types
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-
> nfsv4-layout-types-12
>
> Abstract:
>   This document defines the requirements which individual pNFS layout
>   types need to meet in order to work within the parallel NFS (pNFS)
>   framework as defined in RFC5661.  In so doing, it aims to clearly
>   distinguish between requirements for pNFS as a whole and those
>   specifically directed to the pNFS File Layout.  The lack of a clear
>   separation between the two set of requirements has been troublesome
>   for those specifying and evaluating new Layout Types.  In this
>   regard, this document updates RFC5661.
>
>
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>
>
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4
>
>