Subject: Re: [AAA-WG]: Authentication method AVP?

From: David Mitton <[email-masked]>
Date: Mon, 01 Sep 2003 13:29:09 -0400

On 8/12/2003 01:07 PM +0300, Jari Arkko wrote:
>[email-masked] wrote:
>>Authentication method AVP?
>>Submitter name: Pasi Eronen
>>Submitter email address: [email-masked]
>>Date first submitted: August 12, 2003
>>Reference: Document: NASREQ-12/EAP
>>Comment type: T
>>Priority: 2
>>Section: -
>>Rationale/Explanation of issue:
>>Diameter EAP application has Accounting-EAP-Auth-Method AVP that 
>>corresponds to the MS-Acct-EAP-Type RADIUS attribute from RFC 2548.  In 
>>RADIUS, this attribute is used together with MS-Acct-Auth-Type attribute 
>>(which has values for PAP, CHAP, EAP, MS-CHAP-1, etc.).
>>Should NASREQ have a corresponding AVP, named perhaps
>>Accounting-Auth-Method? (Note that this is different from
>
>Yes.
>
>>Acct-Authentic AVP, which has values for local, RADIUS and Diameter)
>>I guess we could define this AVP in Diameter EAP document if adding this 
>>to NASREQ this late would be a problem.
>
>I think we should put it in NASREQ.
>
>--Jari

Okay, can we elaborate more on the intended semantics?

Is this an informational readout for Accounting as to what auth method was 
actually used?

Which end originates it? (if accounting only, then client to Acct server)
Which way does it flow?
Can we enumerate all the desired values?

How does this relate to the RADIUS attributes and MS VSAs at a protocol 
gateway?

We have a day to get this in.

Dave.