Diameter Maintenance and Extensions (dime)Last Modified: 2011-12-09 Additional information is available at tools.ietf.org/wg/dime
Chair(s):Operations and Management Area Director(s):
Operations and Management Area Advisor:Mailing Lists:General Discussion: dime@ietf.orgTo 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 andextensions to the Diameter protocol required to enable its use for authentication, authorization, accounting, charging in network access, provisioning of configuration information within the network, and for new AAA session management uses within the extensibility rules of the Diameter base protocol. The DIME working group plans 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. - 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. - 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. - Protocol extensions for bulk and grouped AAA session management. The aim of this work is to study and standardize a solution for handling groups of AAA sessions within the Diameter base protocol context. The solution would define how to identify and handle grouped AAA sessions in commands and operations. Additionally, Diameter-based 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, and is within the extensibility rules of Diameter and AAA scope. Coordination with other IETF working groups and other SDOs (e.g. 3GPP) will be used to ensure this. Goals and Milestones:
Internet-Drafts:Diameter Base Protocol (338331 bytes)Diameter Applications Design Guidelines (38790 bytes) Diameter support for EAP Re-authentication Protocol (ERP) (33356 bytes) Diameter Credit Control Application MIB (39300 bytes) Diameter Base Protocol MIB (98529 bytes) The Diameter Capabilities Update Application (13325 bytes) Realm-Based Redirection In Diameter (12821 bytes) Diameter Network Address and Port Translation Control Application (135338 bytes) Diameter IKEv2 SK: Shared Key-based Support for IKEv2 Server to Diameter Server Interaction (37595 bytes) Diameter Attribute-Value Pairs for Cryptographic Key Transport (13653 bytes) Diameter Support for Proxy Mobile IPv6 Localized Routing (36014 bytes) Diameter Priority Attribute Value Pairs (17335 bytes) Diameter Network Access Server Application (154283 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) Diameter Proxy Mobile IPv6: Mobile Access Gateway and Local Mobility Anchor Interaction with Diameter Server (RFC 5779) (44709 bytes) Diameter Quality of Service Application (RFC 5866) (122639 bytes) Diameter Straightforward-Naming Authority Pointer (S-NAPTR) Usage (RFC 6408) (32490 bytes) updates RFC 3588 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||