IETF 75 - Kitten Working Group Minutes ======================================== Location: Stockholm, Sweden - City Conference Center Time: 7/30/09 at 15:10-16:10 Local time Co-Chairs: Tom Yu Shawn Emery Scribe: Larry Zhu Security Area Director: Tim Polk Action Items: ============= Co-chairs: Write a new set of requirements for the GSS-API and post to the list. Co-chairs: Identify work items that stem from these requirements and find any editors to work on said items. AD: Work with IANA to progress draft-ietf-kitten-gssapi-extensions-iana. AD: Send to draft-lha-gssapi-delegate-policy IETF LC. Leif Johansson: Update draft-ietf-kitten-gssapi-naming-exts based on WG response. Conference Session: =================== Slides for this meeting can be found here: WG Update: http://www.ietf.org/proceedings/75/slides/kitten-0.pdf Charter Status: http://www.ietf.org/proceedings/75/slides/kitten-1.pdf WG Update: [draft-ietf-kitten-gssapi-extensions-iana] Now in expert review, asking feedback from IANA. Michelle Cotton likely contact for review. [draft-ietf-kitten-gssapi-channel-bindings] Channel binding clarifications published as RFC 5554. [draft-ietf-kitten-extended-mech-inquiry] Author has added memory management text and constant type declarations. Currently in RFC-Editor's Queue. [draft-ietf-kitten-gssapi-store-cred] Now published as RFC 5588. [draft-ietf-kitten-rfc2853bis] In RFC-Editor's Queue, responded to questions earlier this week. Author moved to a different company and material was provided before 11/10/08 given that this is a bis document. As a result, editor needs to add section 6.c.iii into the boilerplate. Shawn believes that the author's prior employer qualifies as a contributer and therefore yields a more restricted license. [draft-ietf-kitten-gssapi-naming-exts] Changes based on WG feed-back will be incorporated into the next revision of the draft. Non-WG update: [draft-lha-gssapi-delegate-policy] Currently under AD evaluation. Tim will submit to IETF LC later this week. Non-controversial concepts with a couple of implementations. Going through milestones: Leif's draft, draft-ietf-kitten-gssapi-naming-exts, start WGLC in the first week in September. Review charter items: Shawn: Mapping and c-binding clarification. Alex: How many documents are left to be done. Currently active documents, only one active draft. Rest of AD evaluation and RFC editor queue. Not recharter, but close the working group. Love: GSS-API, many functionalities, it seems that not there. Get implementers. Love: Need to have experience first, to make it useful. Tim: running code and ID should run in parallel. If there are major missing pieces, find editors, contributors, then recharter. Works to be done and people willing to work on, the recharter. Shawn: How many people would like contribute to new drafts in order to improve the APIs? 4, sufficient? Tim: Not for sure, take it to the list. To refine it to see. And ask for reviewers. Shawn: How many are willing to review? 1 Simon: Current charter, thread safety, not done. Shawn: The new work is a super set. Items that would intersect: a. Thread safety b. Name space clarifications. Love: Things that I would like to see added to the GSS-API specifications: 1. initialization/new credentials 2. listing/iterating credentials 3. exporting/importing credentials 4. error message reporting 5. asynchronous calls Tom: How many are not in the charter already? Tom: Useability of the API? Reduction of parameters in the APIs. Alexey: No big deal. Leif: A lot silence. Determine how many current drafts address API questions. Love: Not at all. Thread safety being the closest, other stuff not overlapping. Tom: Get a few new documents, describe the problem space. Leif: Send to list, charter text suggestion? Charter Progress: Slides on remaining work. Store creds: Done, have RFC. Channel binding, done, have RFC. Rest need to work on. Channel conjunction mechanism Mike: NFS channel conjunction mechanism not needed, went with BTNS solution. C# binding, no momentum. No volunteer. Some of these individual submissions. TLS channel binding dependency. Done. Tim: If no working group document and want to go to standards then need to show community support. Volunteers? Tom, Alexey, yes Global grid forum's GSS-API extension document. Something we can generate from IANA extension template? Any one who is familiar with it to comment on it? None. Going through the list Love: Pseudo-mechanism, hard to make it work. Take it off the charter. Proposal: No new document, should close the group. Tim: No promise to close the working group. At least one draft between meetings. Two drafts. Incumbent on the chair, to look for new editors, and produce the draft, or close the group. Open mic: none. ================ Session Over