March 19, 2003AAA WG, IETF 561 AAA WG Meeting IETF 56 San Francisco, CA March 19, 2003

AAA WG, IETF 562 Agenda Preliminaries (10 minutes) –Bluesheets –Minute Takers –Agenda Bashing –Document Status Diameter NASREQ, David Mitton (10 minutes) – Diameter Credit Control Application, John Loughney (10 minutes) – 06.txthttp:// 06.txt Credit Control and Prepaid Applications, Avi Lior (10 minutes) – 00.txthttp:// 00.txt Diameter Multimedia Application, Miguel Garcia (10 minutes) – 00.txthttp:// 00.txt Diameter Session Mobility, Dan Forsberg (10 minutes) – mobility-00.txthttp:// mobility-00.txt

March 19, 2003AAA WG, IETF 563 Agenda (cont’d) Diameter APIs, Yoshihiro Obha and David Frascone (10 minutes) – – Diameter Mobile IPv4, Tony Johansson (10 minutes) – Diameter CMS, Stephen Farrell (10 minutes) – Issues in AAA Key Distribution (20 minutes), Russ Housley – AAA WG roadmap (AAA WG Chairs & Randy Bush)

March 19, 2003AAA WG, IETF 564 Document Status Charter: In RFC Editor Queue –Diameter Base-17 –Transport-12 IESG Review completed –Diameter MIPv4-13 Passed AAA WG Last Call –NASREQ-11 Work in progress –Diameter EAP: Due June 2003 –Diameter CMS: Due December 2003 New WG work items –Diameter Key wrap –Diameter Credit Control –Diameter Multimedia

March 19, 2003AAA WG, IETF 565 Some Sobering Facts… No AAA protocol document specifying key distribution has ever been approved as an IETF Proposed Standard –RFC 2548 is Informational (and vendor-specific) –Diameter MIPv4 is blocked on security –No progress on Diameter EAP or CMS What does AAA WG need to do in order to make progress? –What aspects of the problem have we missed? –What criteria do we need to meet?

March 19, 2003AAA WG, IETF 566 Where Do We Go From Here? Need a fresh start on Diameter Mobile IPv4 –WG: Address IESG concerns on clarity of system description –IESG: Provide more detailed feedback on how draft needs to be changed to conform the principles Need a key framework document –Describe the protocols and how they interact system (EAP, AAA, TSK derivation) –Analyze the security properties of the system –Enumerate the security requirements –Address key naming and binding issues (including examples) –EAP WG: draft-aboba-pppext-key-problem-06.txt Split out Diameter Key Wrap into a separate document –Create a design team to focus on this. Take a fresh look at Diameter CMS –Can we remove deployment barriers? –Can we decrease the complexity of the specification? –Any implementation plans?