Re: [nfsv4] more on gss authentication for callback

Trond Myklebust <trond.myklebust@fys.uio.no> Thu, 30 October 2003 23:26 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20243 for <nfsv4-archive@odin.ietf.org>; Thu, 30 Oct 2003 18:26:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFMB1-0000Nx-Oc for nfsv4-archive@odin.ietf.org; Thu, 30 Oct 2003 18:26:04 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9UNQ33G001470 for nfsv4-archive@odin.ietf.org; Thu, 30 Oct 2003 18:26:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFMB0-0000N8-FL for nfsv4-web-archive@optimus.ietf.org; Thu, 30 Oct 2003 18:26:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20228 for <nfsv4-web-archive@ietf.org>; Thu, 30 Oct 2003 18:25:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFMAx-0004ax-00 for nfsv4-web-archive@ietf.org; Thu, 30 Oct 2003 18:25:59 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AFMAw-0004at-00 for nfsv4-web-archive@ietf.org; Thu, 30 Oct 2003 18:25:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFMAz-0000MS-9O; Thu, 30 Oct 2003 18:26:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AFMAr-0000Lz-AK for nfsv4@optimus.ietf.org; Thu, 30 Oct 2003 18:25:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20210 for <nfsv4@ietf.org>; Thu, 30 Oct 2003 18:25:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AFMAo-0004aa-00 for nfsv4@ietf.org; Thu, 30 Oct 2003 18:25:50 -0500
Received: from pat.uio.no ([129.240.130.16] ident=7411) by ietf-mx with esmtp (Exim 4.12) id 1AFMAn-0004aQ-00 for nfsv4@ietf.org; Thu, 30 Oct 2003 18:25:49 -0500
Received: from mail-mx2.uio.no ([129.240.10.30]) by pat.uio.no with esmtp (Exim 4.20) id 1AFMAj-0000N7-OM; Fri, 31 Oct 2003 00:25:45 +0100
Received: from charged.uio.no ([129.240.86.49]) by mail-mx2.uio.no with esmtp (Exim 4.14) id 1AFMAc-00060m-VX; Fri, 31 Oct 2003 00:25:38 +0100
Received: from trondmy by charged.uio.no with local (Exim 2.12 #1) id 1AFMAc-00069d-00; Thu, 30 Oct 2003 18:25:38 -0500
To: Nicolas Williams <Nicolas.Williams@sun.com>
Cc: Mike Eisler <mike@eisler.com>, nfsv4@ietf.org
Subject: Re: [nfsv4] more on gss authentication for callback
References: <3FA193EB.4020307@eisler.com> <20031030230143.GA26891@binky.central.sun.com>
From: Trond Myklebust <trond.myklebust@fys.uio.no>
In-Reply-To: <20031030230143.GA26891@binky.central.sun.com>
Message-ID: <shsism6i9zi.fsf@charged.uio.no>
Lines: 14
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Honest Recruiter)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning.
X-UiO-MailScanner: No virus found
Sender: nfsv4-admin@ietf.org
Errors-To: nfsv4-admin@ietf.org
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/mail-archive/working-groups/nfsv4/>
X-Original-Date: 30 Oct 2003 18:25:37 -0500
Date: Thu, 30 Oct 2003 18:25:37 -0500

>>>>> " " == Nicolas Williams <Nicolas.Williams@sun.com> writes:

     > That's why we must purse the CCM-MIC approach.  And that means
     > we need a CB op for servers to ask clients to establish a
     > GSS-API context in the v4 channel for use with CCM-MIC in the
     > CB channel.

Which is totally irrelevant for solving the problem on v4 since it is
not a mandated protocol...

CCM-MIC is 4.1. Let's deal with 4.0 *first*...

Cheers,
  Trond

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