Internet Engineering Task Force

Diameter Maintenance and Extensions (dime)

Last Modified: 2009-07-07

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

Chair(s):

Operations and Management Area Director(s):

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 Maintenance and Extensions WG will focus on maintenance
and extensions to the Diameter protocol required to enable its use for
authentication, authorization, accounting and provisioning in network
access as well as for other applications environments
(e.g., IP telephony, mobility).

The IETF has completed work on the Diameter Base protocol and is
working on revising the base protocol specification. There is on-going
work on defining RADIUS extensions and the DIME WG will ensure
that work done in RADEXT is also available for Diameter.

The DIME working group plains to address the following items:

- Maintaining and/or progressing, along the standards track, the
Diameter Base protocol and Diameter Applications. This includes
extensions to Diameter Base protocol that can be considered as enhanced
features or bug fixes, such NAI routing or capability update extensions.

- Diameter application design guideline. This document will provide
guidelines for design of Diameter extensions. It will detail when to
consider reusing an existing application and when to develop a new
application.

- Diameter QoS extensions. This work focuses on extensions to
Diameter to support QoS information to be authorized and provisioned
in AAA deployments.

- Protocol extensions for the management of Diameter entities. This work

focuses on the standardization of Management Information Bases (MIBs)
to configure Diameter entities (such as the Diameter Base protocol or
Diameter Credit Control nodes). The usage of other management protocols
for configuring Diameter entities may be future work within the group.

- Diameter extensions for mobility protocols, such as Mobile IPv6 and
Proxy Mobile IPv6. Diameter extensions to support handover keying
developed in the HOKEY WG are part of this effort.

- New Diameter applications, such as the Diameter NAT control
application.
This group will also conduct work on new Diameter applications with
a Diameter application for configuring NATs as the first item.

Additionally, AAA systems require interoperability in order to work.
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.
Done		Submit 'Diameter QoS Application' to the IESG for consideration as a Proposed Standard
Done		Submit 'Diameter Support for EAP Re-authentication Protocol' as DIME working group item
Done		Submit 'Diameter User-Name and Realm Based Request Routing Clarifications' as DIME working group item
Done		Submit 'Diameter Proxy Mobile IPv6' as DIME working group item
Done		Submit 'Quality of Service Attributes for Diameter' to the IESG for consideration as a Proposed Standard
Done		Submit 'Diameter Proxy Mobile IPv6' to the IESG for consideration as a Proposed Standard
Done		Submit 'Diameter User-Name and Realm Based Request Routing Clarifications' to the IESG for consideration as a Proposed Standard
Jun 2009		Submit new DIME charter to the IESG
Jun 2009		Submit 'Updated IANA Considerations for Diameter Command Code Allocations' as DIME working group item
Jul 2009		Submit 'Updated IANA Considerations for Diameter Command Code Allocations' to the IESG for consideration as a Proposed Standard
Jul 2009		Submit 'Diameter NAT Control Application' as DIME working group item
Jul 2009		Submit 'Diameter Capabilities Update' as DIME working group item
Aug 2009		Submit 'Diameter Application Design Guidelines' to the IESG for consideration as a BCP document
Nov 2009		Submit Revision of 'Diameter Base Protocol' to the IESG for consideration as a Proposed Standard
Nov 2009		Submit ' Diameter Credit Control Application MIB' to the IESG for consideration as an Informational RFC
Nov 2009		Submit 'Diameter Base Protocol MIB' to the IESG for consideration as an Informational RFC
Nov 2009		Submit 'Diameter Capabilities Update' to the IESG for consideration as a Proposed Standard
Jan 2010		Submit 'Diameter Support for EAP Re-authentication Protocol' to the IESG for consideration as a Proposed Standard
Jan 2010		Submit 'Diameter NAT Control Application' to the IESG for consideration as a Proposed Standard

Internet-Drafts:

Diameter Base Protocol (340954 bytes)
Diameter Quality of Service Application (120184 bytes)
Diameter Support for EAP Re-authentication Protocol (ERP) (37952 bytes)
Diameter Proxy Mobile IPv6: Mobile Access Gateway and Local Mobility Anchor Interaction with Diameter Server (45118 bytes)
Diameter Credit Control Application MIB (39300 bytes)
Diameter Base Protocol MIB (101579 bytes)
The Diameter Capabilities Update Application (13196 bytes)
Realm-Based Redirection In Diameter (10658 bytes)
Diameter NAT Control Application (91829 bytes)
Diameter Extended NAPTR (13841 bytes)
Diameter IKEv2: Support for Interaction between IKEv2 Server and Diameter Server (28045 bytes)
Diameter Attribute-Value Pairs for Cryptographic Key Transport (12181 bytes)
Diameter Support for Proxy Mobile IPv6 Localized Routing (27652 bytes)

Request For Comments:

Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction (RFC 5447) (38656 bytes)
Quality of Service Parameters for Usage with Diameter (RFC 5624) (23326 bytes)
Clarifications on the Routing of Diameter Requests Based on the Username and the Realm (RFC 5729) (23482 bytes) updates RFC 3588
Updated IANA Considerations for Diameter Command Code Allocations (RFC 5719) (11268 bytes) updates RFC 3588
Traffic Classification and Quality of Service (QoS) Attributes for Diameter (RFC 5777) (91305 bytes)
Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction (RFC 5778) (75444 bytes)