Re: [kitten] Fwd: [Editorial Errata Reported] RFC2743 (3797)

mrex@sap.com (Martin Rex) Tue, 12 November 2013 23:52 UTC

Return-Path: <mrex@sap.com>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F96C21E80D5 for <kitten@ietfa.amsl.com>; Tue, 12 Nov 2013 15:52:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.183
X-Spam-Level:
X-Spam-Status: No, score=-10.183 tagged_above=-999 required=5 tests=[AWL=0.066, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XEuC-FfQP9Bs for <kitten@ietfa.amsl.com>; Tue, 12 Nov 2013 15:51:58 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 8807321E8089 for <kitten@ietf.org>; Tue, 12 Nov 2013 15:51:58 -0800 (PST)
Received: from mail06.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id rACNprli002348 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 13 Nov 2013 00:51:53 +0100 (MET)
In-Reply-To: <5282AC0E.80606@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Date: Wed, 13 Nov 2013 00:51:53 +0100
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20131112235153.73B531AA82@ld9781.wdf.sap.corp>
From: mrex@sap.com
X-SAP: out
Cc: "kitten@ietf.org" <kitten@ietf.org>
Subject: Re: [kitten] Fwd: [Editorial Errata Reported] RFC2743 (3797)
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/kitten>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Nov 2013 23:52:03 -0000

Stephen Farrell wrote:
> 
> FYI, comments welcome, if any. I assume this should
> be approved.
 
> http://www.rfc-editor.org/errata_search.php?rfc=2743&eid=3797
> Type: Editorial
> Reported by: Benjamin Kaduk <kaduk@mit.edu>
> 
> Section: 2.4.5  GSS_Import_name
>
>  [compressed summary of the change]
>
> -    o  GSS_S_COMPLETE indicates that a valid name representation is
> -    output in output_name and described by the type value in
> -    output_name_type.
>
> +    o  GSS_S_COMPLETE indicates that a valid name representation is
> +    output in output_name.

I agree that the reference to the non-existing parameter output_name_type
is a defect in the description for the GSS_S_COMPLETE result of
GSS_Import_name.


I'm slighlty confused by the expression "valid name representation is output".
Admittedly, the descriptions of GSS_S_COMPLETE for the two calls
GSS_Inquire_cred and GSS_Inquire_cred_by_mech also employ "represents":
"the output cred_name .. represents .. the credentials's associated principal
name"
whereas other calls (GSS_Accept_sec_context, GSS_Inquire_context,
GSS_Canonicalize_name, GSS_Duplicate_name) use expressions like
"returns src_name", "src_name is valid" or
"returns another reference (dest_name)" 

How about:

   o  GSS_S_COMPLETE indicates that input_name_string was converted
   to an internal name and returned as output_name


-Martin