1. Diameter Maintenance and Extensions (dime) IETF 68, March 2007, Prague David Frascone, Hannes Tschofenig

2. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to:  the IETF plenary session,  any IETF working group or portion thereof,  the IESG, or any member thereof on behalf of the IESG,  the IAB or any member thereof on behalf of the IAB,  any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices,  the RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 3978 (updated by RFC 4878) and RFC 3979. Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 3978 (updated by RFC 4878) for details.

3. Agenda 1.WG Update & Interop Report 2.Diameter Base Protocol 3.Diameter Mobility  Diameter Mobile IPv6: HA-to-AAAH support  Diameter Mobile IPv6: NAS HAAA Support 4.Diameter QoS 5.Diameter Application Design Guidelines 6.Diameter Auditing (+Liaison Request from ETSI TISPAN) 7.Liaison Request from ITU-T 8.Diameter Explicit Routing

4. Milestones Update Proposal (Feb 2007)  Mar 2007 Submit "Diameter API" to the IESG for consideration as an Informational RFC  Mar 2007 Submit "Diameter Application Design Guidelines" as a working group item  Aug 2007 Submit Revision of "Diameter Base Protocol" to the IESG for consideration as a Proposed Standard  Aug 2007 Submit the following two Diameter Mobility documents to the IESG for consideration as a Proposed Standard:  "Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction“  "Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction"  Sep 2007 Submit "Diameter QoS Application" to the IESG for consideration as a Proposed Standard  Sep 2007 Submit "Diameter Application Design Guidelines" to the IESG for consideration as an Informational RFC

5. Diameter Interop Report (1)  Date: Jan 29 - Feb 1, 2007 (Orlando)  Host: Intellinet Technologies  Participants: 14 companies  Report: http://www.tschofenig.com/twiki/bin/view/Dime/Diam eterInterop2007 http://www.tschofenig.com/twiki/bin/view/Dime/Diam eterInterop2007  Test Cases: http://www.ietf.org/internet-drafts/draft-fajardo-dime- interop-test-suite-04.txt  A summary of issues raised by the participants can be found in: http://www.tschofenig.com:8080/diameter-interop http://www.tschofenig.com:8080/diameter-interop

6. Diameter Interop Report (2)  Only a few new bugs found in RFC 3588.  Diameter with SCTP support works fine and a number of companies implement SCTP support (7 out of 14 at this interop event).  TLS over TCP support is available but RFC 3588 lacks more details about the security checks that have to be performed. Certificate configuration turns out to be difficult and time consuming.  TLS over SCTP support was only implemented (as a prototype) by a single company.  Election tests are very difficult to perform due to the timing problems.  Dynamic peer discovery is rarely implemented and people don’t see deployment need for them.  A few Diameter EAP and Diameter NASREQ implementations are available.  We do not see a lot of Diameter Mobile IP (only 2) and the Diameter SIP application (zero!) implementations at the interop.  Significant interest in testing Diameter Credit Control.

7. Diameter QoS  Involving a group of experienced people to get some feedback:  Elwyn Davies (IAB member, background in IETF QoS work)  Martin Stiemerling (NSIS working group chair)  Jouni Korhonen (3GPP background)  Michael Montemurro (IEEE background)  Avi Lior (Wimax, 3GPP2 background)  Potentially going to schedule phone conferences and Jabber chats