1. Access Bind Issues August 10, 2001 London

2. Some Issues 1.Accessor concept seems very DataPath oriented – does it work with other access application like wireless Lans 2.Does trigger for access and selection of what a “session” is need to be differentiated 3.PEP carries authoritative session info – does it need to have authorization object 4.How does an accessor actually initiate a conversation with client?

3. Accessor / DataPath Accessor is a datapath construct How does it get extended to deal with out of band signals Need to add use cases to the document –Wireless? –VOIP? –Tunnels?

4. Trigger/ Session creator distinction The AccessorSessionScope defines what causes a access request trigger and what is in a session. Seems possible that what triggers a session (e.g. out of band signal from telco) will be different from what is included in a session (e.g. source/destination IP address combination)

5. Authorization Object PEP must have all info about a session to be able to restart it on alternative PDP Current Model does not have info about how the session was authorized Authorization come is from PDP via some authentication with client May need to have Authorization info for auditing/ logging

6. SessionBinding The SessionBinding attribute is used to indicate that a session is a “daughter” of another session. –How does PEP know which sessions are parent/daughter (do we need to provision this) –Does Daughter get removed when parent terminates? If so, who initiates it (PDP or PEP) Should there be other ways to tie sessions together