[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RE : AAAEXT charter, Take 1
MORAND Lionel FTRD/DAC/ISS wrote:
There is something unclear in the Jari's proposal. The first part of the charter states that Diameter AND RADIUS extensions will be investigated. The rest of the text is based on the previous proposal in which only RADIUS extensions were considered as well as Diameter/Radius compatibility.
Ok. Let me try to clarify. Hope this helps:
Here's the list of proposed work items. I have
marked the general ones with "GEN", RADIUS-only
ones with "RAD", and RADIUS extensions with some
kind of compatibility need for Diameter with "RAD-COMPAT".
- RADIUS design guidelines [RAD]
- RADIUS/Diameter translation [GEN -- though perhaps best
treated per application]
- Revised NAI specification [GEN]
- Pre-paid support [RAD-COMPAT]
- SIP support [RAD-COMPAT]
- LAN attributes [GEN]
- MIB update [RAD]
So thats a total of seven work items, three out of
which are generic, two are pure RADIUS, and two are
RADIUS with some compatibility requirements for
If there is a proposal for enhancing the current NASREQ application for LAN/WLAN (with a new command or new madatory AVP for instance), would it be now considered as possible work item? I know that the goal is to narrow as much as possible the scope of this working group on RADIUS extensions but reading the first part of charter, I would not understand why such proposal would not be accepted.
There is a proposal for adding better support for LANs and WLANs,
see Farid Adrangi's draft. Its been written for RADIUS only, though
it should presumably work through the usual Diameter NASREQ
translation. Certainly the final RFC, when we get there, should
ensure this. I'd hope that we don't need to duplicate the work
for Diameter NASREQ, and one document would be sufficient. It
certainly seems so at this moment.
to unsubscribe send a message to firstname.lastname@example.org with
the word 'unsubscribe' in a single line as the message text body.