Re: [dhcwg] I-D ACTION:draft-ietf-dhc-agentopt-radius-08.txt

We were told by the AAA experts that the RADIUS model involves keeping state about the remote host regarding some attributes. It would be wrong to attempt to manage this state in both the RADIUS and DHCP servers. The most obvious is the IP address, but they advised us that all but those in the list in agentopt-radius-08 might cause problems for the RADIUS server.

John

At 09:11 AM 9/10/2004, Mayumi Yanagiya wrote:
>I have a question.
>
>>>4. DHCP Relay Agent Behavior
>>
>>
>>When the DHCP relay agent receives a DHCP message from the client, it
>>MAY append a DHCP Relay Agent Information option containing the
>>RADIUS Attributes sub-option, along with any other sub-options it is
>>configured to supply.  The RADIUS Attributes sub-option MUST only
>>contain the attributes provided in the RADIUS Access/Accept message.
>>The DHCP relay agent MUST NOT add more than one RADIUS Attributes
>>sub-option in a message.
>>
>>The relay agent MUST include the User-Name and Framed-Pool attributes
>>in the RADIUS Attributes sub-option if available, and MAY include
>>other attributes.
>>
>>To avoid dependencies between the address allocation and other state
>>information between the RADIUS server and the DHCP server, the DHCP
>>relay agent SHOULD include only the attributes in the table below an
>>instance of the RADIUS Attributes sub-option.  The table, based on
>>the analysis in RFC 3580 [10], lists attributes that MAY be included:
>
>I'm not sure what "other state information" is.
>I can't understand the reason why dependencies between
>the address allocation and other state information should be avoided.
>Will any problem be caused if we define new attribute?
>
>--Mayumi

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg