IETF Logo Mail Archive

Re: Consensus call was Re: Comments on draft-ietf-kitten-krb5-gssapi-prf-03.txt

Sam Hartman <hartmans-ietf@mit.edu> Fri, 03 June 2005 23:15 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DeLNu-0005it-MJ; Fri, 03 Jun 2005 19:15:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DeLNt-0005eG-3O for kitten@megatron.ietf.org; Fri, 03 Jun 2005 19:15:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA23678 for <kitten@ietf.org>; Fri, 3 Jun 2005 19:15:22 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org ([69.25.196.178] helo=carter-zimmerman.mit.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DeLiC-0004Hm-97 for kitten@ietf.org; Fri, 03 Jun 2005 19:36:25 -0400
Received: by carter-zimmerman.mit.edu (Postfix, from userid 8042) id 911DAE0063; Fri, 3 Jun 2005 19:15:23 -0400 (EDT)
To: Jeffrey Altman <jaltman@columbia.edu>
References: <7210B31550AC934A8637D6619739CE690534F6FB@e2k-sea-xch2.sea-alpha.cisco.com> <429493A6.2040708@columbia.edu> <tslhdgh95wg.fsf@cz.mit.edu> <20050603214112.GV27456@binky.Central.Sun.COM>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Fri, 03 Jun 2005 19:15:23 -0400
In-Reply-To: <20050603214112.GV27456@binky.Central.Sun.COM> (Nicolas Williams's message of "Fri, 3 Jun 2005 16:41:12 -0500")
Message-ID: <tsl64wvnib8.fsf@cz.mit.edu>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: kitten@ietf.org
Subject: Re: Consensus call was Re: Comments on draft-ietf-kitten-krb5-gssapi-prf-03.txt
X-BeenThere: kitten@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/kitten>
List-Post: <mailto:kitten@lists.ietf.org>
List-Help: <mailto:kitten-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@lists.ietf.org?subject=subscribe>
Sender: kitten-bounces@lists.ietf.org
Errors-To: kitten-bounces@lists.ietf.org

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

    Sam> I'm willing to live with this text although it's not great.
    Sam> I don't have improvements to offer.  The spirit behind the
    Sam> text is fine.

    Nicolas> How about pointing out that the lack of useful APIs for
    Nicolas> inquiring about cryptographic QoPs or specification of
    Nicolas> policies on the same means that pplications that need to
    Nicolas> make more than nominal use of GSS_Pseudo_random() should
    Nicolas> take extra care?



I'd actually like to stay away from discussion of APIs. m I honestly
believe that for any mechanism we are likely to standardize and for
any use of PRF we are likely to standardize there isn't that big of a
concern beyond the key lifetime concern we're already discussing
unrealted to PRF.

So mentioning APIs as a way to find out whether what you are doing is
OK is fine but mentioning APIsas a requirement seems unnecessary.


_______________________________________________
Kitten mailing list
Kitten@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/kitten

v2.23.0 | Report a Bug | By Email