IETF 76 - Kitten Working Group Minutes ====================================== Location: Hiroshima, Japan - ANA Crowne Plaza Hiroshima Hotel Time: 11/11/09 at 9:00 - 10:15 Local Time Co-Chairs: Tom Yu Shawn Emery Scribe: Jim Schaad Security Area Director: Tim Polk Action Items: ============= AD: To review draft-ietf-kitten-gssapi-extensions-iana with Michelle Cotton (IANA) AD: Send to draft-lha-gssapi-delegate-policy IETF LC. Co-chairs: Bring requested features (based on draft-yu-kitten-api-wishlist) to the list and have members prioritize which features that they would like in a I-D and implement. Leif Johansson: Update draft-ietf-kitten-gssapi-naming-exts based on implementation feed-back. WGLC will be issued on 3/10. Conference Session: =================== Slides for this meeting can be found here: WG Update: http://tools.ietf.org/agenda/76/slides/kitten-0.pdf Review of active items: [draft-ietf-kitten-gssapi-extensions-iana] Tim Polk - IANA review - it has started now, there as some delays. [draft-ietf-kitten-gssapi-naming-exts] Lief Johansson - additional input from an MIT implementer - give some additional feedback on impleenation w/o knowledge of the draft. No current indications that this will be large impact. [draft-lha-gssapi-delegate-policy] Tim Polk - just requested went to IETF last call. Future WG items: ---------------- Still waiting for volenteers to look at the new work items. Last IETF Tim asked for 2 drafts - currently have one Tim Polk - if the chair wants something - push - if the requestors want something and aren't pushing - then [let it go] Shawn Emery - as working - error reporting is priority. Sam Hartman - question - how important is it really - things have been hacked together for it. Shawn - good point. Sam - no comments from users - this is a problem and the current fixes aren't good enough because... Wants to fix real-world problems. Nicolas Williams - playing w/version 3 of the api - extensions could be v2 upates or v3 - anything that is really new should be delayed - i.e. initial creditionals. Nico - better error - easier to do in new api - along w/async, programmer friendly. Can do now - listing/iteration, exporting. Nico - can sketch new api - but if people are not going to implement - not worth doing. Like to know who is going to implement. Doing off schedule - and slowing on sketching out the new v3 api. Shawn - Take priority on the WG list. Nico - could produce a description of current state of v3 - but some of the new items require new API. Looked at trying to force on v2 - but had problems (w/ support from Love). Can clean up w/removing output parameters that can be got else where (help friendliness). If nobody wants to implement should look at v2. Shawn - Which are v2 - listing, exporting, strength are v2 - everything else is v3. Sam - how much can be prototyped in a couple of hours that wraps the v2 to see if it makes life easier? Ok if somebody wants to do whole API - should potentially check out first. Nico - make doc for simplified GSS-API profile - would help Sam - maybe not a worry - things that we originally thought that was not going to be used is now - multi-year lead time. Nico - in the past did document - then implement and some of the implenation was never done. Now looking at reverse process. Things like memory management cause me to think that v3 is much more important - can document the current state. Tom Yu - get the application developers on board early and get input on what they want. Nico - I am also an application developer - too many output args is a very frustating part. Jeff Hutzelman - get a document out so that we can get feedback on what it currently looks like. Shawn - need to use the list to develop these priorities Charter Items: Milestones: Leif Johansson will update draft-ietf-kitten-gssapi-naming-exts based on implementation feed-back and should be ready for WGLC by 3/10. Open Mic: No open mic questions/comments. Session Over ===========