Re: [Dime] re-chartering

[Glen Zorn <[e-mail]>]

On 1/2/2012 5:40 PM, jouni korhonen wrote:

> Just to make a clean post to the list. The below is the revision submitted for the next IESG meeting regarding DIME rechartering.
> 
> - Jouni
> 
> 
> -----------------
> 
> Diameter Maintenance and Extensions (dime)
> -----------------------------------------
> 
> Current Status: Active
> 
> Last Modified: 2011-12-27
> 
>  Chairs:
>      Lionel Morand <[e-mail]>
>      Jouni Korhonen <[e-mail]>
> 
>  Operations and Management Area Directors:
>      Dan Romascanu <[e-mail]>
>      Ronald Bonica <[e-mail]>
> 
>  Operations and Management Area Advisor:
>      Dan Romascanu <[e-mail]>
> 
>  Mailing Lists:
>      General Discussion: [e-mail]
>      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, charging in network access,
>   provisioning of configuration information within the network, and for
>   new 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. 

s/guideline/guidelines

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

About a month ago there was a brief thread about this draft, in part
containing a promise from one of the authors to "initiate a mail with at
least the points that I would like to see clarified with this document.
And we can use it to set-up after that a confcall. Is it OK?".
Apparently this _was_ OK, but a month has passed and nothing has
happened.  In addition, it has now been nine months since anybody
considered this draft important enough to change the rev number and
resubmit it w/o any other changes (a 2 minute task at worst).  Since
there is clearly zero interest in this work, why is it still in the charter?

> 
>   - 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 extension for bulk and group session management. The aim of
>   this work is to study and standardize a solution for handling groups of
>   sessions within the Diameter base protocol context. The solution would
>   define how to identify and handle grouped 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. Coordination with other IETF working groups and
>   other SDOs will be 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
>   Done     - Submit 'Diameter NAT Control Application' as DIME working group item
>   Done     - Submit 'Diameter Capabilities Update' as DIME working group item
>   Done     - Submit 'Diameter Credit Control Application MIB' to the IESG for consideration as an Informational RFC
>   Done     - Submit 'Diameter Base Protocol MIB' to the IESG for consideration as an Informational RFC
>   Done     - Submit 'Diameter Capabilities Update' to the IESG for consideration as a Proposed Standard
>   Done     - Submit 'Diameter Extended NAPTR' as DIME working group item
>   Done     - Submit 'Realm-Based Redirection In Diameter' as DIME working group item
>   Done     - Submit 'Diameter Support for Proxy Mobile IPv6 Localized Routing' as DIME working group item
>   Done     - Submit 'Diameter Attribute-Value Pairs for Cryptographic Key Transport' as DIME working group item
>   Done     - Submit 'Diameter Priority Attribute Value Pairs' as DIME working group item
>   Done     - Submit 'Diameter IKEv2 PSK' as DIME working group item
>   Done     - Submit Revision of 'Diameter Base Protocol' to the IESG for consideration as a Proposed Standard
>   Done     - Submit 'Diameter Attribute-Value Pairs for Cryptographic Key Transport' to the IESG for consideration as a Proposed Standard
>   Done     - Submit 'Diameter Priority Attribute Value Pairs' to the IESG for consideration as a Proposed Standard
>   Done     - Submit Revision of 'Diameter Network Access Server Application - RFC 4005bis' as DIME working group item
>   Done     - Submit 'Diameter NAT Control Application' to the IESG for consideration as a Proposed Standard
>   Done     - Submit 'Diameter IKEv2 PSK' to the IESG for consideration as a Proposed Standard
>   Done     - Submit 'Diameter Extended NAPTR' to the IESG for consideration as a Proposed Standard
>   Done     - Submit 'Diameter Support for Proxy Mobile IPv6 Localized Routing' to the IESG for consideration as a Proposed 
>   Mar 2012 - Submit 'Realm-Based Redirection In Diameter' to the IESG for consideration as a Proposed Standard
>   Mar 2012 - Submit Revision of 'Diameter Network Access Server Application - RFC 4005bis' to the IESG for consideration as a Proposed Standard
>   May 2012 - Submit 'Diameter Application Design Guidelines' to the IESG for consideration as a BCP document Standard
>   Jul 2012 - Submit 'Diameter Support for EAP Re-authentication Protocol' to the IESG for consideration as a Proposed Standard
>   Aug 2012 - Submit a document on 'Protocol extension for bulk and group signaling' as a working group item
>   Aug 2013 - Submit a document on 'Protocol extension for bulk and group signaling' to the IESG for consideration as a Proposed Standard
> 
> 
> _______________________________________________
> DiME mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/dime