Diameter Maintenance and Extensions (dime)


In addition to this official charter maintained by the IETF Secretariat, there is additional information about this working group on the Web at:

       Additional DIME Web Page

Last Modified: 2007-05-21

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

Chair(s):

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

  • David Frascone <dave@frascone.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>

    Secretary(ies):

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

    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:

    Mar 2006  Submit Diameter API to IESG as an information RFC
    May 2006  Submit Diameter URI to IESG as an information RFC
    Sep 2006  Submit Diameter QoS Application to IESG as a Proposed Standard
    Sep 2006  Submit Diameter Application Design Guidelines to IESG as an informational RFC
    Jan 2007  Submit Diameter Base to IESG as a Draft Standard

    Internet-Drafts:

    The Diameter API (72991 bytes)
    Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction (62712 bytes)
    Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction (42613 bytes)
    Diameter Base Protocol (340379 bytes)
    Diameter Quality of Service Application (107948 bytes)
    Diameter Applications Design Guidelines (47566 bytes)
    Quality of Service Parameters for Usage with the AAA Framework (44697 bytes)
    Quality of Service Attributes for Diameter (48377 bytes)

    No Request For Comments


    IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.

    Return to working group directory.

    Return to IETF home page.