CIFS and the krb5 PRF

[Jeffrey Altman]

Nicolas Williams wrote:

> On Thu, Apr 21, 2005 at 01:37:37PM -0500, Nicolas Williams wrote:
> 
>>On Thu, Apr 21, 2005 at 12:32:20PM -0600, Matt Peterson wrote:
>>
>>>Hi,
>>>
>>>
>>>>>Jeffrey Altman wrote:
>>>>> I have started a discussion with you on the krbdev at mit.edu mailing
>>>>> list. Let's take this discussion there. I am sure that we can work
>>>>> with you to get the functionality you need into a future release
>>>>> without muddying the GSS standards track.
>>>
>>>So can someone explain why this is a krbdev at mit.edu discussion and not 
>>>something suited to the kitten list?  I don't think it is mudding the waters 
>>>at all.  It seems to me like a legitmate request for generic API 
>>>functionality.
>>
>>KITTEN is not charatered to design a raw krb5 mechanism and associated
>>mechanism-specific GSS extensions.  Generic GSS extensions, OTOH, do
>>fall under its charter.
>>
>>There's no need to burden the KITTEN list subscribers with talk of a
>>GSS-based API for raw krb5, at least not yet.
>>
>>None of which means that a raw krb5 API based on the GSS-API couldn't be
>>documented in IETF RFCs.  All we need is a forum with the right
>>participants, and I do believe that this is pretty close to being the
>>right forum.
> 
> 
> this == krbdev

Nico:

Thank you for pressing send on your e-mail before I had a chance to
press send on mine.

Nico is correct on all counts.  When the preliminary work on a raw krb5
mechanism and associated GSS extensions get to the point where a
proposal can be made for standards action, those participating can do
one of the following:

* request that the Kerberos working group be re-chartered to do the work

* request that a new working group be chartered

* submit one or more individual drafts

The important part is that the conversation take place in an open forum
with the necessary participants.   krbdev at mit.edu is targeted at the
development of the MIT Kerberos implementation and is also frequented by
developers looking to implement or utilize the MIT APIs.

Jeffrey Altman