: The Diameter Maintanence and Extentions WG proposed charter

Hi all,

We've been discussing the next steps for the AAA working group. The plan
is to close the WG after the Diameter SIP application is sent to the
IESG.

Here is my initial take at what a Diameter Extensions WG could look 
like. I'd actually like feedback from folks if there are additional 
topics to be considered.

Send comments, and if there is willingness, I can see about creating a 
mailing list to discuss this.

thanks,
John

Diameter Maintanence and Extentions (DiME) WG

Description of Working Group:

The Diameter Maintanence and Extentions WG will focus on 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 DiamExt WG will ensure that work done in RADext is also 
available for Diameter.

The immediate goals of the DiamExt working group are to address the 
following issues:

- Progressing Diameter Base to Draft Standard.

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

- MIPv6 bootstrapping, using Diameter.

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.

Drafts

http://www.ietf.org/internet-drafts/draft-ietf-aaa-diameter-api-04.txt
http://www.ietf.org/internet-drafts/draft-alfano-aaa-qosprot-03.txt
http://tools.ietf.org/wg/aaa/draft-ietf-aaa-uri/draft-ietf-aaa-uri-01.tx
t 
http://www.tschofenig.com/drafts/draft-tschofenig-mip6-aaa-ha-diameter-0
0.txt
http://www.watersprings.org/pub/id/draft-le-aaa-diameter-mobileipv6-04.t
xt


Milestones

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
            information RFC.
Jan 07	Submit Diameter Base to IESG as a Draft Standard