Diameter Maintenance and Extensions (dime) Internet Drafts
| The Diameter API | |||||||||||||||||
|
The Diameter authentication, authorization, and accounting (AAA) protocol provides support for peering AAA transactions across the Internet. This document describes an API for the Diameter protocol. The API is defined for the C language. The intent of the API is to foster source code portability across multiple programming platforms. | ||||||||||||||||
| Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction | |||||||||||||||||
|
Mobile IPv6 deployments may want to bootstrap their operations dynamically based on an interaction between the Home Agent and the Diameter server of the Mobile Service Provider (MSP). This document specifies the interaction between a Mobile IP Home Agent and that Diameter server. Several different mechanisms for authenticating a Mobile Node are supported. The usage of the Internet Key Exchange v2 (IKEv2) protocol allows different mechanisms, such as the Extensible Authentication Protocol (EAP), certificates and pre-shared secrets to be used. Furthermore, another method makes use of the Mobile IPv6 Authentication Protocol. In addition to authentication and authorization, the configuration of Mobile IPv6 specific parameters and accounting is specified in this document. | ||||||||||||||||
| Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction | |||||||||||||||||
|
A Mobile IPv6 node requires a home agent address, a home address, and a security association with its home agent before it can start utilizing Mobile IPv6. RFC 3775 requires that some or all of these parameters are statically configured. Mobile IPv6 bootstrapping work aims to make this information dynamically available to the Mobile Node. An important aspect of the Mobile IPv6 bootstrapping solution is to support interworking with existing authentication, authorization and accounting infrastructure. This document describes MIPv6 bootstrapping using the Diameter Network Access Server (NAS) to home Authentication, Authorization and Accounting server (HAAA) interface. | ||||||||||||||||
| Diameter Base Protocol | |||||||||||||||||
|
The Diameter base protocol is intended to provide an Authentication, Authorization and Accounting (AAA) framework for applications such as network access or IP mobility. Diameter is also intended to work in both local Authentication, Authorization & Accounting and roaming situations. This document specifies the message format, transport, error reporting, accounting and security services to be used by all Diameter applications. The Diameter base application needs to be supported by all Diameter implementations. | ||||||||||||||||
| Diameter Quality of Service Application | |||||||||||||||||
|
This document describes the framework, messages and procedures for the Diameter Quality of Service (QoS) application. The Diameter QoS application allows network elements to interact with Diameter servers when allocating QoS resources in the network. In particular, two modes of operation -- Pull and Push -- are defined. | ||||||||||||||||
| Diameter Applications Design Guidelines | |||||||||||||||||
|
The Diameter Base protocol provides updated rules on how to extend Diameter by modifying and/or deriving from existing applications or creating entirely new applications. This is a companion document to the Diameter Base protocol that further explains and clarifies these rules. It is meant as a guidelines document and therefore it does not add, remove or change existing rules. | ||||||||||||||||
| Quality of Service Parameters for Usage with the AAA Framework | |||||||||||||||||
|
This document defines a number of Quality of Service (QoS) parameters that can be reused for conveying QoS information within RADIUS and Diameter. The payloads used to carry these QoS parameters are opaque for the AAA client and the AAA server itself and interpreted by the respective Resource Management Function. | ||||||||||||||||
| Quality of Service Attributes for Diameter | |||||||||||||||||
|
This document extends the IPFilterRule AVP functionality of the Diameter Base protocol and the functionality of the QoS-Filter-Rule AVP defined in RFC 4005. The ability to convey Quality of Service information using the AVPs defined in this document is available to existing and future Diameter applications where permitted by the command ABNF. | ||||||||||||||||
 |
 |
 |
 |
|
 |
|
 |
|
 |
|
 |
Diameter Maintenance and Extensions (dime)
Last Modified: 2008-08-21
Additional information is available at tools.ietf.org/wg/dime
Chair(s):
Operations and Management Area Director(s):
Operations and Management Area Advisor:
Secretary(ies):
Mailing Lists:
General Discussion: dime@ietf.orgTo 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 maintenanceand 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:
| Nov 2007 | 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' | |
| Nov 2007 | Submit "Diameter API" to the IESG for consideration as an Informational RFC | |
| Dec 2007 | Submit Revision of "Diameter Base Protocol" to the IESG for consideration as a Proposed Standard | |
| Dec 2007 | Submit 'Diameter Application Design Guidelines' to the IESG for consideration as an Informational RFC | |
| Jan 2008 | Submit 'Diameter QoS Application' to the IESG for consideration as a Proposed Standard |
Internet-Drafts:
The Diameter API (71981 bytes)Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction (84866 bytes)
Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction (38513 bytes)
Diameter Base Protocol (341657 bytes)
Diameter Quality of Service Application (120998 bytes)
Diameter Applications Design Guidelines (35757 bytes)
Quality of Service Parameters for Usage with the AAA Framework (47349 bytes)
Quality of Service Attributes for Diameter (68992 bytes)
No Request For Comments
IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.
Return to working group directory. 
