An Architectural Issue How is the EAP key cache managed on the peer and authenticator? To date, key names and cache architectures have been “link specific” What happens when a host is multi-homed? Example: 802.16, 802.11, 802.20 interfaces Do we now have separate EAP key caches for each media? For each interface? Do we now have distinct key names for the same key, one for each media/interface? How does this impact inter-media handoff, code footprint, and complexity? |