Re: [nfsv4] AD review: draft-ietf-nfsv4-rpcsec-gss-v2-03

"Mike Eisler" <mre-ietf@eisler.com> Mon, 18 August 2008 21:51 UTC

Return-Path: <nfsv4-bounces@ietf.org>
X-Original-To: nfsv4-archive@megatron.ietf.org
Delivered-To: ietfarch-nfsv4-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1013A3A6B82; Mon, 18 Aug 2008 14:51:08 -0700 (PDT)
X-Original-To: nfsv4@core3.amsl.com
Delivered-To: nfsv4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D0DD33A68BD for <nfsv4@core3.amsl.com>; Mon, 18 Aug 2008 14:51:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mWDBld9vOAsM for <nfsv4@core3.amsl.com>; Mon, 18 Aug 2008 14:51:05 -0700 (PDT)
Received: from webmail2.sd.dreamhost.com (sd-green-dreamhost-133.dreamhost.com [208.97.187.133]) by core3.amsl.com (Postfix) with ESMTP id EB6AB3A6C41 for <nfsv4@ietf.org>; Mon, 18 Aug 2008 14:51:05 -0700 (PDT)
Received: from webmail.eisler.com (localhost [127.0.0.1]) by webmail2.sd.dreamhost.com (Postfix) with ESMTP id 8F430DC719; Mon, 18 Aug 2008 14:51:25 -0700 (PDT)
Received: from 198.95.226.230 (SquirrelMail authenticated user mre-ietf@eisler.com) by webmail.eisler.com with HTTP; Mon, 18 Aug 2008 14:51:25 -0700 (PDT)
Message-ID: <21564.198.95.226.230.1219096285.squirrel@webmail.eisler.com>
In-Reply-To: <6A3C6C08-6A9D-4CF1-91EB-2BCAEB4A1A55@nokia.com>
References: <13364.198.95.226.230.1219088407.squirrel@webmail.eisler.com> <6A3C6C08-6A9D-4CF1-91EB-2BCAEB4A1A55@nokia.com>
Date: Mon, 18 Aug 2008 14:51:25 -0700
From: Mike Eisler <mre-ietf@eisler.com>
To: nfsv4@ietf.org, ars.eggert@nokia.com
User-Agent: SquirrelMail/1.4.10a
MIME-Version: 1.0
Subject: Re: [nfsv4] AD review: draft-ietf-nfsv4-rpcsec-gss-v2-03
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: nfsv4-bounces@ietf.org
Errors-To: nfsv4-bounces@ietf.org

On Mon, August 18, 2008 1:59 pm, Lars Eggert wrote:
>
> Sorry I was unclear - I was talking about the first sentence in the
> introduction, not the abstract.
>
> (And you could just add the references as raw text - e.g. "[RFC5056]"
> - instead of using xref or having the RFC Editor do this.)
>
> If you agree, I'll add an RFC Editor Note to the datatracker that adds
> these two references to the introduction, and then start the IETF last
> call?

It is less error prone to just push a -05 (which I just did now)
especially since I found some other typos.

So -05 is ready for IETF last call, assuming you like the
Security Considerations.

Thanks.


-- 
Mike Eisler, Senior Technical Director, NetApp, 719 599 9026,
http://blogs.netapp.com/eislers_nfs_blog/



_______________________________________________
nfsv4 mailing list
nfsv4@ietf.org
https://www.ietf.org/mailman/listinfo/nfsv4