[Dime] Protocol Action: 'Diameter Network Access Server Application' to Proposed Standard (draft-ietf-dime-rfc4005bis-14.txt)

The IESG <iesg-secretary@ietf.org> Mon, 23 December 2013 17:28 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 249521AE1DE; Mon, 23 Dec 2013 09:28:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id scRPZ0x_w5Yz; Mon, 23 Dec 2013 09:28:12 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 216D01AE1F5; Mon, 23 Dec 2013 09:28:10 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.90
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131223172810.8627.34400.idtracker@ietfa.amsl.com>
Date: Mon, 23 Dec 2013 09:28:10 -0800
Cc: dime mailing list <dime@ietf.org>, dime chair <dime-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Dime] Protocol Action: 'Diameter Network Access Server Application' to Proposed Standard (draft-ietf-dime-rfc4005bis-14.txt)
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dime/>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Dec 2013 17:28:14 -0000

The IESG has approved the following document:
- 'Diameter Network Access Server Application'
  (draft-ietf-dime-rfc4005bis-14.txt) as Proposed Standard

This document is the product of the Diameter Maintenance and Extensions
Working Group.

The IESG contact persons are Benoit Claise and Joel Jaeggli.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-dime-rfc4005bis/




Technical Summary

    This document obsoletes RFC 4005 and is not backward compatible with
    that document. The main change compared to the RFC 4005 is the removal
    of all of the material related to RADIUS/Diameter protocol interactions,
    which was underspecified and misleading. Moreover, the Command Code Format
    (CCF) for the Accounting-Request and Accounting-Answer messages has been
    changed to explicitly require the inclusion of the Acct-Application-Id AVP and
    exclude the Vendor-Specific-Application-Id AVP. The accounting model to be
    used with this application is also specified.

Working Group Summary

   The document spent almost two years as WG document and the
   proposed changes from RFC 4005 were straightforward and roughly
   endorsed by the Working Group. There was no controversy on its
   final content.

Document Quality

   A number of vendors have indicated interest on implementing
  the specification due it correcting several known flaws.
  There has been no MIB Doctor or Media Type reviews as those
  were not seen relevant for the bis version of the specification.
  There has not been explicitly requested expert reviews outside
  the WG as we believe most if not all important technical experts
  are already represented in the WG and its mailing list. The
  document has received multiple reviews while in WGLC.

Personnel

 Lionel Morand (lionel.morand@orange.com) is the Document Shepherd, as Dime WG co-chair. 
 Benoit Claise (bclaise@cisco.com) is the Responsible Area Director.

RFC Editor Note

  Please add RFC 4005 as an informative reference