Diameter Maintenance and Extensions (dime)

Last Modified: 2009-06-10

Additional information is available at tools.ietf.org/wg/dime

Chair(s):

  • Hannes Tschofenig <Hannes.Tschofenig@gmx.net>

  • Victor Fajardo <vfajardo@tari.toshiba.com>

    Operations and Management Area Director(s):

  • Dan Romascanu <dromasca@avaya.com>
  • Ronald Bonica <rbonica@juniper.net>

    Operations and Management Area Advisor:

  • Dan Romascanu <dromasca@avaya.com>

    Mailing Lists:

    General Discussion: dime@ietf.org
    To Subscribe: https://www.ietf.org/mailman/listinfo/dime
    Archive: http://www.ietf.org/mail-archive/web/dime/current/maillist.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:

    Done  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'
    Done  Submit 'Diameter API' to the IESG for consideration as an Informational RFC
    Done  Submit 'Quality of Service Parameters for Usage with Diameter' to the IESG for consideration as a Proposed Standard.
    Jan 2009  Submit Revision of 'Diameter Base Protocol' to the IESG for consideration as a Proposed Standard
    Jan 2009  Submit 'Diameter QoS Application' to the IESG for consideration as a Proposed Standard
    Jan 2009  Submit 'Diameter Support for EAP Re-authentication Protocol' as DIME working group item
    Jan 2009  Submit 'Diameter User-Name and Realm Based Request Routing Clarifications' as DIME working group item
    Jan 2009  Submit 'Diameter Proxy Mobile IPv6' as DIME working group item
    Jan 2009  Submit 'Quality of Service Attributes for Diameter' to the IESG for consideration as a Proposed Standard
    Mar 2009  Submit 'Diameter Application Design Guidelines' to the IESG for consideration as a BCP document
    Apr 2009  Submit 'Diameter Proxy Mobile IPv6' to the IESG for consideration as a Proposed Standard
    Apr 2009  Submit 'Diameter User-Name and Realm Based Request Routing Clarifications' to the IESG for consideration as a Proposed Standard
    May 2009  Submit 'Diameter Support for EAP Re-authentication Protocol' to the IESG for consideration as a Proposed Standard

    Internet-Drafts:

    The Diameter API (71678 bytes)
    Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction (77462 bytes)
    Diameter Base Protocol (342211 bytes)
    Diameter Quality of Service Application (122068 bytes)
    Quality of Service Parameters for Usage with Diameter (21500 bytes)
    Quality of Service Attributes for Diameter (87497 bytes)
    Diameter User-Name and Realm Based Request Routing Clarifications (19856 bytes)
    Diameter Proxy Mobile IPv6: Mobile Access Gateway and Local Mobility Anchor Interaction with Diameter Server (41007 bytes)
    Diameter Support for EAP Re-authentication Protocol (16034 bytes)
    Diameter Credit Control Application MIB (37993 bytes)
    Diameter Base Protocol MIB (103349 bytes)
    Updated IANA Considerations for Diameter Command Code Allocations (12056 bytes)

    Request For Comments:

    Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction (RFC 5447) (38656 bytes)
    IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.

    Return to working group directory.

    Return to IETF home page.