[AAA-WG]: Diameter NASreq draft 17
David Mitton <david@mitton.com> Mon, 19 July 2004 22:49 UTC
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27500 for <aaa-archive@lists.ietf.org>; Mon, 19 Jul 2004 18:49:34 -0400 (EDT)
Received: by trapdoor.merit.edu (Postfix) id DBCEB9123B; Mon, 19 Jul 2004 18:49:22 -0400 (EDT)
Delivered-To: aaa-wg-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56) id A567B9123D; Mon, 19 Jul 2004 18:49:21 -0400 (EDT)
Delivered-To: aaa-wg@trapdoor.merit.edu
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by trapdoor.merit.edu (Postfix) with ESMTP id 1E2B89123B for <aaa-wg@trapdoor.merit.edu>; Mon, 19 Jul 2004 18:49:20 -0400 (EDT)
Received: by segue.merit.edu (Postfix) id 0A62E59F1F; Mon, 19 Jul 2004 18:49:20 -0400 (EDT)
Delivered-To: aaa-wg@merit.edu
Received: from c000.snv.cp.net (h013.c000.snv.cp.net [209.228.32.77]) by segue.merit.edu (Postfix) with SMTP id 9F5EA59E5B for <aaa-wg@merit.edu>; Mon, 19 Jul 2004 18:49:19 -0400 (EDT)
Received: (cpmta 5570 invoked from network); 19 Jul 2004 15:49:18 -0700
Received: from 66.30.125.93 (HELO h000094929690.mitton.com) by smtp.mitton.com (209.228.32.77) with SMTP; 19 Jul 2004 15:49:18 -0700
X-Sent: 19 Jul 2004 22:49:18 GMT
Message-Id: <5.2.1.1.2.20040719184841.03279620@mail.comcast.net>
X-Sender: david@mitton.com@getmail.mitton.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Mon, 19 Jul 2004 18:48:47 -0400
To: aaa-wg@merit.edu
From: David Mitton <david@mitton.com>
Subject: [AAA-WG]: Diameter NASreq draft 17
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: owner-aaa-wg@merit.edu
Precedence: bulk
I've submitted a new version to ietf-drafts A copy is availible at: http://www.circularnetworks.com/draft-ietf-aaa-diameter-nasreq-17.txt Changes are: 18-July-2004 Document Editor: David Mitton --- Issue # 468 Summary Description: Missing "[Failed AVP]" in AAA ABNF Document review found several inconsistencies in error reporting AVPs in the message ABNFs and occurance tables. a) Inserted in AAA, and ACA ABNF * [ Failed-AVP ] b) Inserted missing in ACA ABNF [Error-Message] c) Removed redundant from RAA ABNF [Error-Message] [Error-Reporting-Host] d) Inserted Error-Message and Failed-AVP in Accounting occurence tables. Section 10.2. e) Corrected occurance of Error-Reporting-Host in Non-Framed ACA table from 0+ to 0-1 Question: Why is Failed-AVP 0+ in Request messages? (Table 10.1, page 75) Can a Failed AVP be forwarded in a non-Answer message? ----- Issue # 466 Description: Missing QoSFilterRule AVP Inserted proposed text as section 6.9 (old 6.9++) Assigned AVP code 407 Section renumbering and reference fixups. Added the new AVP to the ABNF for AAA, ACR Added the new AVP to table of Section 6. Added the new AVP to the AVP occurance tables in Section 10. Changed occurance of NAS-Filter rule to 0+ in ACR Added DIFFSERV, DIFFSERVAF, and DIFFSERVEF as Informative references ---- Issue # 464 Application-Id usage Section 1.3, Advertising Application Support, now says: Diameter applications conforming to this specification MUST advertise support by including the value of one (1) in the Auth-Application-Id of Capabilities-Exchange-Request (CER), AA-Request (AAR) and AA-Answer (AAA) messages. All other messages are defined by [Base] and use the Base application id value. ---- Updated dates, Realigned tables, page breaks
- [AAA-WG]: Diameter NASreq draft 17 David Mitton