1. Clarification of Access Control Mechanism on Rel-1 & Rel-2 Group Name: SEC ( ARC & PRO for information) Source: FUJITSU Meeting Date: 2015-12-03 Agenda Item: Rel-1 MNT & Rel-2 STE

2. Issues MNT for Rel-1 – defined unimplemetable features which is subject to remove for easing testing specification. STE for Rel-2 – SEC group planning to extending security framework from Rel-1 specification, but backward compatibility issue was not discussed. – Possible impacts on transition from Rel-1 to Rel-2 should be discussed by SEC group 2

3. Relationship between definitions / concepts Originator: AE or CSE which requests operation. Credential: the information shared between Originator and registrar CSE to authenticate Originator. App-ID: identifier for application logic to assign privileged operation Role-ID: identifier for role of application to assign privileged operation 3

4. Authorization procedure (describe in clause 7) Access control is performed referring ACPs Request message carries security parameters – to, from, op: copied from primitive parameters – fc: (how this affect to access control ?) – role: (where this can be retrieved ?) Context parameters are also evaluated – rq_time: the timereceived time is used – rq_loc: (how this can be retrieved ?) – rq_ip: (how this can be retrieved ?) 4

5. Proposal Removing following parameters from TS – rq_ip, rq_loc: the procedure to retrieve required parameter is not specified in TS – When the solution is provided, it can be backed. Adding clarification texts for following params – App-id: specified by AE, and used to figure out associated role-id – Role-id: remove from primitive parameter, but valid in ACP rule 5

6. Access Authorization for role-base access control AE RegistrarPDPPEP Association of AE-ID & App-ID is shared during enrollment procedure Send req. with App-ID forward req. with App-ID Inquiry Role-ID for App-ID List of Role-IDs Check validity of App-ID Access granted Forward response Send response 6