eap Mailing List: RE: Strawman -10/EMSK deletion requirement?

[Narayanan, Vidya (vidyan]

Joe, 
I can see the problem with transporting the EMSK to other entities -
however, what really is the concern with caching the EMSK as long as it
is never exported? Is it just the concern of having to maintain state or
is there a security concern here? 

Vidya 

> -----Original Message-----
> From: Salowey, Joe [mailto:jsalowey [at] cisco.com] 
> Sent: Monday, March 06, 2006 2:04 PM
> To: Avi Lior; Jari Arkko
> Cc: eap [at] frascone.com
> Subject: RE: [eap] Strawman -10/EMSK deletion requirement?
> 
> Hi Avi,  
> 
> > 
> > Perhaps you missed my poorly stated point :-)
> > 
> > What if the user is requesting access to a new application? 
> > which could
> > also involve the modification of the user's profile. 
> > If EMSK is not there, then what do I do? Restart the session? No.
> > 
> > At anyrate I belive that there could be other use cases... 
> I gave two 
> > reason why:
> > 
> > Just-in-time;
> > Dynamic-Application provisioning.
> 
> [Joe] Would you agree with the following:
> 
> "For any specific application once the AMSK is generated for 
> that application there is no requirement to cache the EMSK 
> for that application, however there may be a need to cache 
> the EMSK if the system requires other Masks to be generated. "  
> 
> This makes the caching more of a system issue than an issue for one
> particular application.   
> 
> _________________________________________________________________
> To unsubscribe or modify your subscription options, please visit:
> http://lists.frascone.com/mailman/listinfo/eap
> 
> Arhives: http://lists.frascone.com/pipermail/eap
>