IETF 78 - kitten Working Group Minutes ======================================== Location: Maastricht, The Netherlands - MECC Time: 7/26/10 at 17:40-19:40 Local time Co-Chairs: Tom Yu Shawn Emery Scribe (Jabber): Jim Schaad Security Area Director: Tim Polk Action Items: ============= Co-chairs: Will poll the WG list again to see which registry type specified for draft-ietf-kitten-gssapi-extensions-iana: single GSS-API name-space registry registry per programming language Co-chairs: Start WG LC on draft-ietf-kitten-digest-to-historic. Co-chairs: Will poll WG for consensus on whether we should recharter to include the following drafts as work items: draft-cantor-ietf-sasl-saml-ec draft-mills-kitten-sasl-oauth Co-chairs: Find volunteers to take on work items outlined in draft-yu-kitten-api-wishlist. Nico Williams: Will update draft-williams-tls-app-sasl-opt and present the problem statement to the TLS WG. Both WGs will perform LC when ready. Eliot Lear and Klaas Wierenga: Will work with Alexey Melnikov to clarify their respective drafts: draft-lear-ietf-sasl-openid draft-wierenga-ietf-sasl-saml Sam Hartman: Will update the gssapi-naming-exts draft and submit a new draft discusing the various mechanism implementations for naming extensions. Conference Session: =================== Slides for this meeting can be found here: WG Update: http://www.ietf.org/proceedings/78/slides/kitten-0.pdf Naming Extensions - Lessons Learned: http://www.ietf.org/proceedings/78/slides/kitten-1.pdf WG Update: [draft-ietf-kitten-gssapi-extensions-iana] IANA wants the WG to pick a registry type: single GSS-API name-space registry registry per programming language Rough consensus given in the room was that there should be a registry per programming language, but the co-chairs will take this again to the list. Yuri ??? had also mentioned work with Globus that has a single registry that different bindings could use. This option will also be analyzed as a solution. [draft-ietf-kitten-gssapi-naming-exts] Sam Hartman presented lessons learned from naming extensions based on implementation experience. Sam will work in updating the current draft and submitting any additional drafts to discuss the various mechanism instances. Cancel the IETF LC and rip out section 6 and put them into separate documents. We still need consensus from the list on how the new draft will be updated. [Non-WG update] draft-lha-gssapi-delegate-policy is now RFC 5896. [draft-ietf-kitten-digest-to-historic] Start WG LC on draft-ietf-kitten-digest-to-historic. The WG LC was last made a few years ago. [draft-yu-kitten-api-wishlist] We are still looking for volunteers/editors for the various GSS-API work items from draft-yu-kitten-api-wishlist, which are: initialization/new credentials listing/iterating credentials exporting/importing credentials error message reporting asynchronous calls security strength reporting programmer friendliness [draft-lear-ietf-sasl-openid] [draft-wierenga-ietf-sasl-saml] Simon Joffeson has reworked both drafts to include the GSS-API bridge. Alexey Melnikov has also requested clarifying text in the drafts to help understand the use cases. Sam had asked why the saml-ec draft was not considered by the WG? Shawn mentioned that the SASL mechanism list was very specific in the charter. Will poll WG for consensus on whether we should recharter to include the following drafts as work items: draft-cantor-ietf-sasl-saml-ec draft-mills-kitten-sasl-oauth [Milestone Review] WG will develop milestones for: draft-lear-ietf-sasl-openid draft-wierenga-ietf-sasl-saml once Alexey/editors have made clarifying updates and more reviews by the WG. Open mic: none. ================ Session Over