Re: [SPKM] RE: Comments on draft-zhu-pku2u-01.txt

Jeffrey Hutzelman <jhutz@cmu.edu> Tue, 20 March 2007 13:33 UTC

Return-path: <spkm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTeTH-00030N-DC; Tue, 20 Mar 2007 09:33:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTeTG-0002yB-Nm for spkm@ietf.org; Tue, 20 Mar 2007 09:33:50 -0400
Received: from minbar.fac.cs.cmu.edu ([128.2.185.161]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HTeSv-0001nE-5t for spkm@ietf.org; Tue, 20 Mar 2007 09:33:50 -0400
Received: from minbar.fac.cs.cmu.edu ([127.0.0.1]) by minbar.fac.cs.cmu.edu id aa16164; 20 Mar 2007 7:37 EDT
Date: Tue, 20 Mar 2007 07:37:57 -0400
From: Jeffrey Hutzelman <jhutz@cmu.edu>
X-X-Sender: <jhutz@minbar.fac.cs.cmu.edu>
To: Martin Rex <martin.rex@sap.com>
Subject: Re: [SPKM] RE: Comments on draft-zhu-pku2u-01.txt
In-Reply-To: <200703191731.SAA07246@uw1048.wdf.sap.corp>
Message-ID: <Pine.LNX.4.33L.0703200735210.15335-100000@minbar.fac.cs.cmu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: Michael.Eisler@netapp.com, kitten@lists.ietf.org, spkm@ietf.org, andros@citi.umich.edu
X-BeenThere: spkm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Low Infrastructure Public Key GSS mechanism <spkm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/spkm>, <mailto:spkm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/spkm>
List-Post: <mailto:spkm@ietf.org>
List-Help: <mailto:spkm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/spkm>, <mailto:spkm-request@ietf.org?subject=subscribe>
Errors-To: spkm-bounces@ietf.org

On Mon, 19 Mar 2007, Martin Rex wrote:

> Whether and how much a client can do for trouble-shooting may
> be application specific!  When helpdesk is called, the only
> information that is reliably available/accessible is that
> logged centrally on backends/servers.

That is true only if the helpdesk is associated with the people operating
the servers, rather than the people supporting the user.  OFten these are
not the same organization, and the only information available is that
recorded on the client.

If one of my users reports a problem talking to some remote site, I can,
if necessary, examine error logs, attach a debugger to their client,
and/or observe the traffic on the wire.  Actually getting error data from
the server can be essential to making this work.

That said, applications should be designed to correctly carry error tokens
without requiring that they be returned with GSS_S_CONTINUE_NEEDED,
because no mechanism should be doing that.

-- Jeff


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