Subject: [AAA-WG]: Wrapping up NASREQ Re-auth

From: Avi Lior <[email-masked]>
Date: Tue, 20 Apr 2004 12:30:03 -0400

A couple of things:

If the RAR properly identifies an active session, the NAS will
   initiate a new local reauthentication or authorization sequence as
   indicated by the Re-Auth-Request-Type value. This will cause the NAS
   to send a new AAR message using the existing Session-Id. The server
   will respond with an AAA message to specify the new service
   parameters.

Shouldn't we state that the AUTH-REQUEST-TYPE AVP of the AAR message be set
to the same value Received in RAR Re-Auth-Request-Type AVP?  And what
happens if its not?

I am still having an issue with the following paragraph:

 If accounting is active, every change of authentication or
   authorization MUST generate an accounting message.  Either an
   Accounting-Record-Type of INTERIM_RECORD indicating the new session
   attributes and cumulative status (preferred) or two messages of the
   types STOP_RECORD, and START_RECORD.  The later would be for service
   specific compatibility with some RADIUS services.

Why is the Interim preferred?
Preferred seems to be an editorial comment.  Should we not specify when this
is to be used? Also, would not Diameter suffer from the same issue that a
RADIUS server would suffer? Would a backend process know why the Interim
record is generated.  Would it always know what has changed? Would it be
able to do the calculation to generate an appropriate bill?

Also, if new attributes are received, this is a new session right? Don't we
have to use something other then Interim records to deliniate a new session
in diameter?
Also, how would you (in a scalable way) specify which method is to be used:
Interim or Stop/Start records?

> -----Original Message-----
> From: Bernard Aboba [mailto:[email-masked]]
> Sent: Monday, April 19, 2004 3:34 PM
> To: [email-masked]
> Subject: [AAA-WG]: Wrapping up NASREQ...
> 
> 
> David Mitton has put up a strawman version of the NASREQ-15 here for
> examination:
> 
> http://www.circularnetworks.com/draft-ietf-aaa-diameter-nasreq-15.txt
> 
> This version is designed to close all open issues (see below).
> 
> Since NASREQ has already gone through WG last call, IETF last
> call, IESG review and approval for publication as a Proposed 
> Standard, this represents the very last opportunity to 
> comment on it before it is done.
> 
> So... speak now or forever (until NASREQbis) hold your piece.
> 
> 
> --------------------------------------------------------------
> ---------
> Generic Edits in D15:
> - Update document dates & version
> - Update David Spence info
> - Fix Acct-Session-ID in ABNFs
> - Remove table entry for Termination-Action
> - Add reference to Base Termination-Cause
> - Re-add missing code points for NAS-Port-Type
> - correct header levels for LAT services
> 
> - Tunnel-Client-Auth-ID, Tunnel-Server-Auth-ID defined as UTF8Strings
> 	(Was Unsigned32 in table, OctetString in description)
> 
> - Pg 60, Sect 9.1, Session-Timeout: Remove phrase "I guess
> the safest bet is to"
> 
> 
> ----------
> Issues:
> 
> Issue 431 - Identities in RADIUS Translation, Pasi Eronen
> 
> 1&2) State attribute should contain:
> "Diameter/"<Origin-Host>"/"<Origin-Realm>"/"<Session-Id>
> 
> 3) State content building should be consistent
> 4) Fix section 9.3 for Origin-Host to identify NAS source, not gateway
> 5) Corrected.
> 6) Origin-Realm & Origin-Host AVP should contain best
> verified info on NAS identity (not the gateway)
> 
> Issue 451 - Interim vs. STOP Record, Avi Lior
> 	a) Compromise - add text to allow Stop/Start as service specific
> 	b) Editorial correction Accepted
> 
> 
> Issue 452 - Accounting Session-Id in ACA Command, Avi Lior
> 	Accepted: Corrected AVP name
> 
> Issue 453 - Problem with Accounting Session-Id and
> Session-Id, Avi Lior
> 	Accepted: Acct-Session-Id cannot be put in Diam Session-Id
> 			Acct-Session-Id is an accepted Diameter AVP.
> 			A RADIUS/Diameter gateway will have to assign &
> track
> 			Diameter Session-Ids.
> 
> Issue 454 - Diameter NASREQ conflict with Base, Bernard Aboba
> 	Close: Text already changed in draft 14
> 
> Issue 457 - Editorial NIT in NASREQ-14, Johan Hermans
> 	Accepted: Updated Service-Type list
> 
> Issue 462 - Typo in NASREQ-14, Ignacio Goyret
> 	Accepted: Tunnel-Client-Auth-Id type bug
> 
> 
>