2.4.3 Diameter Maintenance and Extensions (dime)

NOTE: This charter is a snapshot of the 70th IETF Meeting in Vancouver, BC Canada. It may now be out-of-date.

Last Modified: 2007-05-21


David Frascone <dave@frascone.com>
Hannes Tschofenig <Hannes.Tschofenig@gmx.net>

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>


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

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


  • draft-ietf-dime-diameter-api-02.txt
  • draft-ietf-dime-mip6-split-04.txt
  • draft-ietf-dime-mip6-integrated-05.txt
  • draft-ietf-dime-rfc3588bis-05.txt
  • draft-ietf-dime-diameter-qos-01.txt
  • draft-ietf-dime-app-design-guide-01.txt
  • draft-ietf-dime-qos-parameters-00.txt
  • draft-ietf-dime-qos-attributes-01.txt

    No Request For Comments

    Meeting Minutes


    Diameter Base Protocol (Victor)
    Mobile IPv6 Split (Jouni)
    Mobile IPv6 Integrated (Jouni)
    QOS Attributes (Jouni)
    Applications Design Guideline (Victor)
    Proxy MIPv6 (Jouni)
    Diameter Prefix Delegation (Behcet Sarikaya)
    Diameter ERP
    Alternative Diameter Mobile IPv4 (Ahmad Muhanna)
    QoS Parameters
    Diameter Classifier (Avi / Mark)
    Explicit Routing (Tina)
    draft-asveren-dime-cong-02 (Tolga / Jouni)