Subject: [AAA-WG]: Diameter Base Update details

From: <[email-masked]>
Date: Tue, 28 Jan 2003 21:26:05 +0200

Hi all,

I've tried to summarize the major changes in the Diameter base spec from
16 to 17.

thanks,
John

Diameter 17 Updates

1) "Accounting-RADIUS-Session-Id" (44) changed to "Accounting-Session-Id" 

2) Section 1.2.4, 3rd paragraph, Page 14 changed to:

	"Every Diameter implementation MUST support accounting.
	Basic accounting support is sufficient to handle any application
	that uses the ACR/ACA commands defined in this document, as long
	as no new mandatory AVPs are added. A mandatory AVP is defined as
	one which has the "M" bit set when sent within an accounting
	command, regardless of whether it is required or optional
	within the ABNF for the accounting application."

3) Sections 2.4 & 11.3, 2nd paragraph changed to:

	Diameter Base Accounting      0
	NASREQ                        1 [NASREQ]
	Mobile-IP                     4 [DIAMMIP]	
	Relay                         0xffffffff

4) General cleanup on  "SHOULD be placed as close to the Diameter header as possible."

5) Added reference to 2194

6) added to 4.6

	E2E-Sequence AVP 300  6.15    Grouped    | M  |  P  |    |  V  | Y  |

7) User defined.

8) End-to-end security definition improved

9) IPAddress changed to Address & format now includes a 16 bit address type,
   to discriminate IPv4, IPv6, etc. addresses

10) Error-Message changed to UTF8String 

11) Host-IP-Address AVP (AVP Code 257) type changed to Address (from IPAddress)

12) Text for section "11.1.1  AVP Codes" updated.

13) Fixed allocation range for Application IDs, Section 11.3

	IANA [IANA] will assign the range 0x00000001 to 0x00ffffff for 
	standards-track applications; and 0x01000000 - 0xfffffffe for 
	vendor specific applications, on a first-come, first-served basis. 
	The following values are allocated.