Diameter Maintenance and Extensions (dime)
------------------------------------------
Charter
Last Modified: 2009-07-07
Current Status: Active Working Group
Chair(s):
Hannes Tschofenig <
[email protected]>
Victor Fajardo <
[email protected]>
Operations and Management Area Director(s):
Dan Romascanu <
[email protected]>
Ronald Bonica <
[email protected]>
Operations and Management Area Advisor:
Dan Romascanu <
[email protected]>
Mailing Lists:
General Discussion:
[email protected]
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:
Posted Revised I-D Title <Filename>
------ ------- --------------------------------------------
Feb 2007 Mar 2010 <draft-ietf-dime-diameter-qos-15.txt>
Diameter Quality of Service Application
May 2007 Mar 2010 <draft-ietf-dime-app-design-guide-11.txt>
Diameter Applications Design Guidelines
Jan 2009 Mar 2010 <draft-ietf-dime-erp-03.txt>
Diameter support for the EAP Re-authentication Protocol (ERP)
May 2009 Jan 2010 <draft-ietf-dime-diameter-cc-appl-mib-03.txt>
Diameter Credit Control Application MIB
May 2009 Jan 2010 <draft-ietf-dime-diameter-base-protocol-mib-04.txt>
Diameter Base Protocol MIB
Jul 2009 Feb 2010 <draft-ietf-dime-capablities-update-03.txt>
The Diameter Capabilities Update Application
Jul 2009 Oct 2009 <draft-ietf-dime-realm-based-redirect-02.txt>
Realm-Based Redirection In Diameter
Aug 2009 Mar 2010 <draft-ietf-dime-nat-control-02.txt>
Diameter Network Address and Port Translation Control
Application
Jan 2010 Dec 2009 <draft-ietf-dime-extended-naptr-00.txt>
Diameter Extended NAPTR
Jan 2010 Jan 2010 <draft-ietf-dime-ikev2-psk-diameter-00.txt>
Diameter IKEv2: Support for Interaction between IKEv2 Server
and Diameter Server
Jan 2010 Mar 2010 <draft-ietf-dime-local-keytran-02.txt>
Diameter Attribute-Value Pairs for Cryptographic Key Transport
Feb 2010 Feb 2010 <draft-ietf-dime-pmip6-lr-00.txt>
Diameter Support for Proxy Mobile IPv6 Localized Routing
Feb 2010 Feb 2010 <draft-ietf-dime-priority-avps-00.txt>
Diameter Priority Attribute Value Pairs
Request For Comments:
RFC Stat Published Title
------- -- ----------- ------------------------------------
RFC5447 PS Feb 2009 Diameter Mobile IPv6: Support for Network Access Server
to Diameter Server Interaction
RFC5624 PS Aug 2009 Quality of Service Parameters for Usage with Diameter
RFC5729 PS Dec 2009 Clarifications on the Routing of Diameter Requests Based
on the Username and the Realm
RFC5719 PS Jan 2010 Updated IANA Considerations for Diameter Command Code
Allocations
RFC5777 PS Feb 2010 Traffic Classification and Quality of Service (QoS)
Attributes for Diameter
RFC5778 PS Feb 2010 Diameter Mobile IPv6: Support for Home Agent to Diameter
Server Interaction
RFC5779 PS Feb 2010 Diameter Proxy Mobile IPv6: Mobile Access Gateway and
Local Mobility Anchor Interaction with Diameter Server