Diameter Maintenance and Extensions (dime)
------------------------------------------
Charter
Last Modified: 2009-01-07
Current Status: Active Working Group
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:
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:
Posted Revised I-D Title <Filename>
------ ------- --------------------------------------------
Mar 2006 Jul 2008 <draft-ietf-dime-diameter-api-07.txt>
The Diameter API
Jun 2006 Dec 2008 <draft-ietf-dime-mip6-split-16.txt>
Diameter Mobile IPv6: Support for Home Agent to Diameter Server
Interaction
Jun 2006 Jan 2009 <draft-ietf-dime-mip6-integrated-12.txt>
Diameter Mobile IPv6: Support for Network Access Server to
Diameter Server Interaction
Dec 2006 Dec 2008 <draft-ietf-dime-rfc3588bis-15.txt>
Diameter Base Protocol
Feb 2007 Dec 2008 <draft-ietf-dime-diameter-qos-07.txt>
Diameter Quality of Service Application
May 2007 Nov 2008 <draft-ietf-dime-app-design-guide-08.txt>
Diameter Applications Design Guidelines
Jun 2007 Dec 2008 <draft-ietf-dime-qos-parameters-08.txt>
Quality of Service Parameters for Usage with Diameter
Jul 2007 Dec 2008 <draft-ietf-dime-qos-attributes-09.txt>
Quality of Service Attributes for Diameter
Jan 2009 Jan 2009 <draft-ietf-dime-pmip6-00.txt>
Diameter Proxy Mobile IPv6: Support For Mobile Access Gateway
and Local Mobility Anchor to Diameter Server Interaction
Jan 2009 Jan 2009 <draft-ietf-dime-nai-routing-00.txt>
Diameter User-Name and Realm Based Request Routing
Clarifications
Request For Comments:
None to date.