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

Slides:

Advertisements

Similar presentations

Aircraft Fractional Ownership in Aruba From a financing perspective.

Advertisements

Access Control Mechanism for User Group Name: SEC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: Agenda Item:

© Copyright 2006 Efficient Forms, LLC ECS: Agent Workflow.

Service Layer Session Management Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP16 Agenda Item:

App-ID Ad-Hoc Technical Issues TP AppID R02 Group Name: App-ID Ad-Hoc Group Source: Darold Hemphill, iconectiv,

 Receive an Approval Letter from DIDD Provider Enrollment Coordinator.  Contact per letter’s instructions, Julia Jinnette by phone, or letter.

1 System for Administration, Training, and Educational Resources for NASA Managing Access.

1st MODINIS workshop Identity management in eGovernment Frank Robben General manager Crossroads Bank for Social Security Strategic advisor Federal Public.

On Persistent AE Identifiers Group Name: SEC#12.2 Source: Phil Hawkes, Qualcomm Inc (TIA), Francois Ennesser,

Proposal for App Id and Service Provider Id registration Group Name: Shelby Kiewel Source: Shelby Kiewel, iconectiv / Ericsson,

2-levels Access control for HTTP binding Group Name: WG4 (& WG2/WG3 for information) Source: Shingo Fujimoto, FUJITSU, Meeting.

App-ID Use Cases, Syntax and Attributes SEC App-ID_Use_Cases,_Syntax_and_Attributes Group Name: Architecture Source: Darold Hemphill, iconectiv,

Electronic identity management for eGovernment Conceptual framework and objectives Frank Robben General manager Crossroads Bank for Social Security Strategic.

Introduction of PRO WG activities Group Name: TP Source: Shingo Fujimoto, FUJITSU, Meeting Date: Agenda Item:

Tommie Curtis SAIC January 17, 2000 Open Forum on Metadata Registries Santa Fe, NM SDC JE-2023.

PRO R01-URI_mapping_discussion Discussion on URI mapping in protocol context Group Name: PRO and ARC Source: Shingo Fujimoto, FUJITSU,

TS0001 Identifiers way forward Group Name: WG2 Source: Elloumi, Foti, Scarrone, Lu (tbc), Jeong (tbc) Meeting Date: Agenda Item: ARC11/PRO11.

Some identification needs related to workers’ mobility eGovernment – eIDM ad hoc group meeting 4-5 May 2006 CBSS Crossroads Bank for Social Security Frank.

App-ID Discussion Group Name: ARC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: 31 July 2014 Agenda Item: TBD.

SEC Identity_of_registrar_CSE Identity of Registrar CSE Group Name: SEC, ARC and PRO Source:FUJITSU Meeting Date: Agenda Item: Authentication.

Normalization Exercise. First Normal Form Second Normal Form.

By Rashid Khan Lesson 6-Building a Directory Service.

Access Control Status Report Group Name: ARC/SEC Source: Dragan Vujcic, Oberthur Technologies, Meeting Date: 09/12/2013 Agenda Item:

Status Report on Access TP8 Group Name: WG2 Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information  Contact:

Inventory & Monitoring Program SharePoint Permissions Who has access? What can they do with the access? What is the easiest way to manage the permissions?

Establishing a company in Russia Latvia Latvia.

Meeting Savvy By Michael A. Sand

BTS430 Systems Analysis and Design using UML Domain Model—Part 2A: Attributes.

Introducing concept of M2M-application data modeling Group Name: MAS Source: FUJITSU Meeting Date: Agenda Item: Semantics and Device Configuration.

ICOM 6005 – Database Management Systems Design Dr. Manuel Rodríguez Martínez Electrical and Computer Engineering Department Lecture 5 – September 4 th,

App-ID Use Cases, Syntax and Attributes ARC R01-App-ID_Use_Cases,_Syntax_and_Attributes Group Name: Architecture Source: Darold Hemphill, iconectiv,

Core Cluster IM Products & Humanitarian Datasets IMWG Meeting 21 December 2015.

Access Control Status Report Group Name: ARC/SEC Source: Dragan Vujcic, Oberthur Technologies, Meeting Date: 09/12/2013 Agenda Item:

Proposed App-ID Format Group Name: Architecture, Security Source: Darold Hemphill, iconectiv, Meeting Date: Agenda Item:

Credential Identifiers Group Name: SEC#14.2 Source: Phil Hawkes, Qualcomm Inc, Meeting Date:

WG-2 - ARC TP #18 Status Report Group Name: oneM2M TP #18 Source: WG2 Chair (Nicolas Damour – Meeting Date: Agenda.

M2M Service Subscription Profile Discussion Group Name: oneM2M TP #19.2 Source: LG Electronics Meeting Date: Agenda Item:

Introducing Event handler Group Name: SEC & ARC Source: FUJITSU Meeting Date: Agenda Item: Device Configuration.

Discussion about RESTful Admin API Group Name: SEC & ARC Source: FUJITSU Meeting Date: Agenda Item: Device Configuration.

Security API discussion Group Name: SEC Source: Shingo Fujimoto, FUJITSU Meeting Date: Agenda Item: Security API.

Issue regarding authentication at MN-CSE Group Name: ARC & SEC Source: FUJITSU Meeting Date: Agenda Item: Security Admin API.

M2M Service Session Management (SSM) CSF Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP8 Agenda Item:

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

Authorization Architecture Discussion Group Name: SEC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: 28 MAY, 2014 Agenda.

Consideration Security Issues on Registration Group Name: WG4 (SEC) Source: Shingo Fujimoto, FUJITSU, Meeting Date:

Introducing concept of M2M-application data modeling Group Name: MAS Source: FUJITSU Meeting Date: Agenda Item: Semantics and Device Configuration.

DM Collaboration – OMA & BBF: Deployment Scenarios Group Name: WG5 - MAS Source: Tim Carey, ALU, Meeting Date:

Directions for Release 3 Group Name: SEC Source: NEC Europe Ltd. Meeting Date: SEC22, Agenda Item: Discuss directions.

The reading is 7.38 mm. The reading is 7.72 mm.

Introducing User’s Role concept Group Name: WG2(ARC) and WG4(SEC) Source: Shingo Fujimoto, FUJITSU, Meeting Date:

Specifying the Address of Management Client of Managed Entity Group Name: ARC Source: Hongbeom Ahn, SK Telecom, Meeting Date: TP#21 Agenda.

Introducing User’s Role concept Group Name: WG2(ARC) and WG4(SEC) Source: Shingo Fujimoto, FUJITSU, Meeting Date:

Adding Role to ACPs Group Name: SEC Source: OBERTHUR Technologies, Dragan Vujcic Meeting Date: Agenda Item: RBAC.

Container Freight Station, Utilities and Drainage at Bayport Container Terminal (RFQ-148) Brenda Trevino, P.E. Project Manager October 11, 2016.

Ian Deakin, iconectiv 3rd July 2017

App-ID Ad-Hoc Technical Issues TP AppID R02

Domain Model: Visualizing concepts

Proposed design principles for modelling interworked devices

Discussions on Heterogeneous Identification Service

Logarithmic Functions

Management of Placement Area at Bayport Container Terminal (RFQ-147)

Considering issues regarding handling token

3rd week souvenir Task 1: In case of hosting your e-B or e-C system, what are your considerations? Explore in more detail!

Object Oriented Analysis and Design

Agenda OAuth Concepts Programming OAuth.

ECS: Agent Workflow.

IEEE MEDIA INDEPENDENT HANDOVER DCN:

Hosted by Financial Statistics February 28, 2019

Entity Relation Model Tingting Zhang.

Business Organization & Business Entities

Presentation transcript:

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

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

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

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’.

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.