1. Discussion about App-ID naming convention Group Name: ARC/SEC/PRO Source: FUJITSU Meeting Date: 2015-07-20 Agenda Item: App-ID operation

2. Role of App-ID App-ID can: Identify the application context on M2M Platform (ex. HEMS-A, healthcare-X, bank-33) Indicate the group which treats as same in access control to the resource. App-ID cannot: Provide information to determine the application is not cracked Provide proof of ownership of the App-ID

3. App-ID is not self-contained App-ID should be provided with following info – Proof of ownership: only authorized entity can use – Authority ID: who authorize the ownership – Permission to allow operation: what can do Both M2M Application and IN-CSE must share them

4. Suggestion Those are not required by security, but it ease to operate Compatible with Rel-1 specification Printable string representation Keep separate on ‘ID assignment’ and ‘proof of ownership’.

5. Proposed App-ID convention [N|R.]. N|R : N: Non-registered, R:Registered at The organization domain which contract with App-ID authority, who insures the ownership of the App-ID. Unique name of the application (context), the assignment of the name should be coordinated within the contracted organization Note: when App-ID is used without registration, should be chosen by M2M-SP who hosts the M2M Application.