Diameter Maintenance and Extensions (dime) ------------------------------------------ Charter Last Modified: 2007-11-12 Current Status: Active Working Group Chair(s): Hannes Tschofenig David Frascone Operations and Management Area Director(s): Dan Romascanu Ronald Bonica Operations and Management Area Advisor: Dan Romascanu Secretary(ies): Victor Fajardo Mailing Lists: General Discussion:dime@ietf.org To Subscribe: https://www1.ietf.org/mailman/listinfo/dime Archive: http://www.ietf.org/mail-archive/web/dime/index.html Description of Working Group: The Diameter Maintanence and Extensions WG will focus on maintenance and extensions to the Diameter protocol required to enable its use in applications such as IP telephony and Local Area Network authentication, authorization and accounting. The IETF has recently completed work on the Diameter Base protocol. There is on-going work on defining RADIUS extensions. The work done in the DiME WG will ensure that work done in RADext is also available for Diameter. The immediate goals of the DiME working group are to address the following issues: - Maintaining and/or progressing, along the standards track, the Diameter procotol and Diameter Applications. Every revised document to be "maintained" requires explicit approval before it will be accepted as a WG document. - An informational RFC on a Diameter API. - Diameter Application design guidelines. This document will provide guidelines for design of new Diameter Applications. It will detail when to consider reusing an existing application and when to develop a new application. Interaction between vendor & SDO specific extensions and applications will be covered. - Diameter QoS application. This document will develop a new Diameter application for supporting QoS in AAA deployments. The NSIS WG will be consulted on proper design of QoS attributes. - Diameter URI. RFC 3588 defines an AAA URI which has some known problems. A document revising the AAA URI as a specific Diameter URI will be developed. - Diameter extensions for MIPv6. This may include support for Mobile IP extensions, like FMIP; as well as support for MIP bootstrapping. Additionally, AAA systems require interoperability in order to work. Uncontrolled extensibility is not a mechanism for interoperability. Therefore, the working group, along with the AD, will need to evaluate any potential extensions and require verification that the proposed extension is needed. Coordination with other IETF working groups and other SDOs will used to ensure this. Goals and Milestones: Nov 2007 Submit the following two Diameter Mobility documents to the IESG for consideration as a Proposed Standards:* 'Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction' * 'Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction' Nov 2007 Submit "Diameter API" to the IESG for consideration as an Informational RFC Dec 2007 Submit Revision of "Diameter Base Protocol" to the IESG for consideration as a Proposed Standard Dec 2007 Submit 'Diameter Application Design Guidelines' to the IESG for consideration as an Informational RFC Jan 2008 Submit 'Diameter QoS Application' to the IESG for consideration as a Proposed Standard Internet-Drafts: Posted Revised I-D Title ------ ------- -------------------------------------------- Mar 2006 Sep 2007 The Diameter API Jun 2006 Sep 2007 Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction Jun 2006 Nov 2007 Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction Dec 2006 Oct 2007 Diameter Base Protocol Feb 2007 Jul 2007 Diameter Quality of Service Application May 2007 Nov 2007 Diameter Applications Design Guidelines Jun 2007 Sep 2007 Quality of Service Parameters for Usage with the AAA Framework Jul 2007 Sep 2007 Quality of Service Attributes for Diameter Request For Comments: None to date.