WG Review: Diameter Maintenance and Extensions (dime)

The IESG <iesg-secretary@ietf.org> Wed, 21 December 2005 13:37 UTC

Received: from localhost.cnri.reston.va.us ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ep49Y-0008Ud-VQ; Wed, 21 Dec 2005 08:37:13 -0500
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ep49W-0008UP-J4; Wed, 21 Dec 2005 08:37:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12515; Wed, 21 Dec 2005 08:36:06 -0500 (EST)
Received: from [] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ep4C9-0004kh-Sf; Wed, 21 Dec 2005 08:39:54 -0500
Received: from apache by newodin.ietf.org with local (Exim 4.43) id 1Ep49W-0007pe-0L; Wed, 21 Dec 2005 08:37:10 -0500
Content-Type: text/plain
Mime-Version: 1.0
To: IETF-Announce@ietf.org
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1Ep49W-0007pe-0L@newodin.ietf.org>
Date: Wed, 21 Dec 2005 08:37:10 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Subject: WG Review: Diameter Maintenance and Extensions (dime)
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iesg@ietf.org
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

A new IETF working group has been proposed in the Operations and Management
Area.  The IESG has not made any determination as yet. The following draft
charter was submitted, and is provided for informational purposes only. 
Please send your comments to the IESG mailing list (iesg@ietf.org) by 
December 28th.


Diameter Maintenance and Extensions (dime)

Current Status: Proposed Working Group

WG Chair(s): TBD

Operations and Management Area Director(s):
Bert Wijnen <bwijnen@lucent.com>
David Kessens <david.kessens@nokia.com>

Operations and Management Area Advisor:
Bert Wijnen <bwijnen@lucent.com>

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

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

- 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 know problems. A
document revising the AAA URI as a specific Diameter URI will be developed.

- Diameter extentions 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.




Mar 06 Submit Diameter API to IESG as an information RFC.
May 06 Submit Diameter URI to IESG as an information RFC.
Sep 06 Submit Diameter QoS Application to IESG as a Proposed Standard.
Sep 06 Submit Diameter Application Design Guidelines to IESG as an informational
Jan 07 Submit Diameter Base to IESG as a Draft Standard

IETF-Announce mailing list