[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

questions on draft-mariblanca-aaa-eap-lla-00.txt

Hi David and others,

I am going through the draft that have slots for San Diego meeting, so I am sorry if there has been discussions regarding this draft and I have missed those threads.

My question regarding the EAP lower layer attributes is:

I can understand that one may want to signal the info on the kind of L2 that is carrying the EAP messages over the link from end device to Access node, so PPP and 802.1x make sense. But what is the purpose of IKEv2 and PANA? Are we saying we expanded the L2 concept to L3 and EAP is carried over IKEv2 for protection over the single hop? If yes, then why nothing on IKEv1? Would you care to explain?

I also have a general question: RFC 3579 defines an EAP-message attribute for RADIUS with an IANA type of 79. So far I have not understood how grouping of attributes works for RADIUS, but it feels like the EAP-message attribute and L2 info attribute should be grouped together somehow, especially if the attribute space is tight. Anybody cares to explain?

Thanks,

Madjid

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>