IETF Logo Mail Archive

Re: WG Last Call: draft-ietf-sasl-gs2-14

Simon Josefsson <simon@josefsson.org> Thu, 30 July 2009 11:56 UTC

Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C002328C155 for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Thu, 30 Jul 2009 04:56:02 -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 m3eNk-hAmOWS for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Thu, 30 Jul 2009 04:56:01 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 34DD83A6908 for <sasl-archive-Zoh8yoh9@ietf.org>; Thu, 30 Jul 2009 04:56:00 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n6UBPRi7056781 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 30 Jul 2009 04:25:27 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n6UBPRpf056772; Thu, 30 Jul 2009 04:25:27 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n6UBPO4u055985 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-sasl@imc.org>; Thu, 30 Jul 2009 04:25:26 -0700 (MST) (envelope-from simon@josefsson.org)
Received: from mocca.josefsson.org (dhcp-52e8.meeting.ietf.org [130.129.82.232] (may be forged)) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5) with ESMTP id n6UBPKsm022249 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 30 Jul 2009 13:25:22 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: Nicolas Williams <Nicolas.Williams@sun.com>, ietf-sasl@imc.org
Subject: Re: WG Last Call: draft-ietf-sasl-gs2-14
References: <ldveiskuhya.fsf@cathode-dark-space.mit.edu> <4A6216CC.2050104@isode.com> <87ws5u44xz.fsf@mocca.josefsson.org> <20090729150853.GE1020@Sun.COM> <4A706ADF.5000805@isode.com> <87bpn3wlb5.fsf@mocca.josefsson.org> <20090729205210.GV1020@Sun.COM> <87d47jmbi0.fsf@mocca.josefsson.org> <4A7181DC.6050903@isode.com>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:090730:alexey.melnikov@isode.com::GbKXnjYiVz/8g9+D:JBhU
X-Hashcash: 1:22:090730:ietf-sasl@imc.org::1QfFrp0BfKm/I0yz:R/7Z
X-Hashcash: 1:22:090730:nicolas.williams@sun.com::jFojbnr1g0Gq1/cG:ch3B
Date: Thu, 30 Jul 2009 13:25:20 +0200
In-Reply-To: <4A7181DC.6050903@isode.com> (Alexey Melnikov's message of "Thu, 30 Jul 2009 13:19:56 +0200")
Message-ID: <87k51q8lb3.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.96 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Virus-Scanned: clamav-milter 0.95.2 at yxa-v
X-Virus-Status: Clean
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

Alexey Melnikov <alexey.melnikov@isode.com> writes:

> Simon Josefsson wrote:
>
>>Nicolas Williams <Nicolas.Williams@sun.com> writes:
>>  
>>
>>>Jeff Hutzelman points out that RFC2744 specifically requires that all
>>>gss_buffer_t outputs be released.  That wouldn't bother me at all here
>>>(we'd have to say that draft-ietf-sasl-gs2 updates RFC2744), but,
>>>RFC5587 (draft-ietf-kitten-extended-mech-inquiry, in AUTH48) had a
>>>chance to do that and didn't, so I'd say that these output buffers
>>>should be released by the app.
>>>    
>>>
>>Good catch, I have removed the paragraph.  How memory should be managed
>>by applications (i.e., they have to be released) then follows directly
>>from the normative RFC 2744 and GS2 shouldn't say anything about it.
>>Alexey, I hope this resolves your question.
>>  
>>
> Can we say that informatively in the document, considering that this
> mistake was done before?

Yep, the variable descriptions now follows the style used by RFC 2743 to
document this, e.g.:

   o sasl_mech_name UTF-8 STRING -- SASL name for this
     mechanism; caller must release with
     GSS_Release_buffer()

Is this clear enough?

/Simon

v2.23.0 | Report a Bug | By Email