IETF Logo Mail Archive

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

Lars Eggert <lars.eggert@nokia.com> Mon, 11 August 2008 10:05 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 F3BC93A6E2F; Mon, 11 Aug 2008 03:05:52 -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 4C6583A69DF for <nfsv4@core3.amsl.com>; Mon, 11 Aug 2008 03:05:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.573
X-Spam-Level:
X-Spam-Status: No, score=-6.573 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 y1xhgukh2Pyl for <nfsv4@core3.amsl.com>; Mon, 11 Aug 2008 03:05:50 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230]) by core3.amsl.com (Postfix) with ESMTP id 2FCA23A693B for <nfsv4@ietf.org>; Mon, 11 Aug 2008 03:05:49 -0700 (PDT)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id m7BA5fNb010720 for <nfsv4@ietf.org>; Mon, 11 Aug 2008 13:05:49 +0300
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 11 Aug 2008 13:05:46 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 11 Aug 2008 13:05:39 +0300
Received: from net-115.nrpn.net ([10.241.184.208]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Mon, 11 Aug 2008 13:05:39 +0300
Message-Id: <A3E4032C-4853-4BE3-8AD2-1EA999C4DB73@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
To: NFSv4 <nfsv4@ietf.org>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Mon, 11 Aug 2008 13:05:34 +0300
X-Mailer: Apple Mail (2.926)
X-OriginalArrivalTime: 11 Aug 2008 10:05:40.0219 (UTC) FILETIME=[CF0A5CB0:01C8FB99]
X-Nokia-AV: Clean
Subject: [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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: nfsv4-bounces@ietf.org
Errors-To: nfsv4-bounces@ietf.org

Section 1, paragraph 0:
 >    RPCSEC_GSS version 2 (RPCSEC_GSSv2) is the same as RPCSEC_GSS  
version
 >    1 (RPCSEC_GSSv1) except that support for channel bindings has been
 >    added.

   I'd be good to add a citation to [2] for RPCSEC_GSSv1 and RFC5056 for
   "channel bindings." We can do that with an RFC Editor Note - send me
   one.


Section 7., paragraph 1:
 >    The security considerations are the same as [2].

   This document is all about applying a security mechanism (channel
   bindings) to [2]. Surely this raises new security considerations?
   If not, please explain why not - this is surely something the  
security
   directorate will want to know.

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

v2.23.0 | Report a Bug | By Email