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

Slides:

Advertisements

Similar presentations

SEC Clarification Group Name: WG4 (SEC-2014-xxxx) Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information  Contact:

Advertisements

Is a Node or not Node? ARC Node_resolution Group Name: ARC Source: Barbara Pareglio, NEC, Meeting Date: ARC#9.1 Agenda.

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

Problem of non-Blocking Synchronous mode Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 15.0 Agenda Item: TBD.

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

Discussion on oneM2M HTTP Binding Interoperability Test Spec.

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

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

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

Announcement Resources ARC Announcement_Issues Group Name: WG2 Source: Barbara Pareglio, NEC Meeting Date: Agenda Item: Input Contribution.

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

End-to-End security definition Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm, Meeting Date:

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

Answer the Questions Regarding Pending Issues on Access Control Group Name: WG4 SEC Source: LG Electronics Meeting Date: Agenda Item: SEC#11.4.

Management of CMDH Policies Group Name: WG5-MAS Source: Wolfgang Granzow, Qualcomm, Meeting Date: Agenda Item: Management.

Considerations on M2M URIs Group Name: WG2(ARC) Source: Yong-Suk Park, Sung-Chan Choi, Jaeho Kim, KETI, Meeting Date:

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.

Fuctional Procedure for oiC interworking

Supporting long polling Group Name: ARC WG Source: SeungMyeong, LG Electronics, Meeting Date: x-xx Agenda Item: TBD.

Ontology Architectural Support Options Group Name: MAS WG Source: Catalina Mladin, Lijun Dong, InterDigital Meeting Date: Agenda Item: TBD.

Step by step approach Group Name: WG2 Source: Michael hs. Yang, LG uplus, Jaeseung Song, NEC Europe, Meeting.

OneM2M Challenges of M2M Security and Privacy

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

Ontology Architectural Support Options Group Name: MAS WG Source: Catalina Mladin, Lijun Dong, InterDigital Meeting Date: Agenda Item: TBD.

Interworking with an External Dynamic Authorization System Group Name: SEC WG Source: Qualcomm Inc., Wolfgang Granzow & Phil Hawkes Meeting Date: SEC#20.2,

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:

OIC INTERWORKING OPERATIONAL PROCEDURE (ADDRESSING AND DISCOVERY) Group Name: Architecture WG Source: Kiran Vedula, Samsung Electronics,

Routing Problem of the Current Architecture Group Name: ARC Source: Hongbeom Ahn, LG Electronics, Meeting Date: Agenda.

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:

OIC INTERWORKING Resource mapping

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

Protocol Issues related to Plugtest Group Name: TST Source: Wolfgang Granzow, Qualcomm Inc., Meeting Date: Agenda.

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

Streaming Session Support in oneM2M Framework Group Name: WG2 Source: George Foti, Ericsson Meeting Date: Work Item :WI GPP_Rel13_IWK.

LWM2M Interworking Proxy Procedures ARC Considerations

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

Attribute-level access control Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 16 Agenda Item: TBD.

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

Issues of Current Access Control Rule and New Proposal Introduction Group Name: ARC 21 Source: Wei Zhou, Datang, Meeting Date:

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

Protocol Issues related to Plugtest Group Name: TST Source: Wolfgang Granzow, Qualcomm Inc., Meeting Date: Agenda.

CMDH and Policies Contribution: oneM2M-ARC-0603

FUCTIONAL ARCHITECTURE FOR OIC INTERWORKING Group Name: Architecture WG Source: Jieun Keum, Samsung Electronics,

Issues about management Group Name: MAS9.2 Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item:

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

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

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

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

[authenticationProfile] <mgmtObj> specialization

App-ID Ad-Hoc Technical Issues TP AppID R02

oneM2M interop 3 issues and optimizations

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

CSE Retargeting to AE, IPE, and NoDN Hosted Resources

Group multicast fanOut Procedure

2nd Interoperability testing issues

Discussion about Use Case and Architecture in Developer Guide

Proposed design principles for modelling interworked devices

oneM2M Service Layer Protocol Version Handling

MAF&MEF Interface Specification discussion of the next steps

Proximal IoT Interworking solution discussion

oneM2M Versioning Next Steps

Considering issues regarding handling token

CMDH Refinement Contribution: oneM2M-ARC-0397R01

Service Layer Dynamic Authorization [SLDA]

Development Guideline for oneM2M Products and Services

3GPP V2X Interworking Potential Impact

Summary of the MAF and MEF Interface Specification TS-0032

Presentation transcript:

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

Problem statements – AE-ID and CSE-ID must be globally unique without the need for a central coordination point – Need to ensure oneM2M architecture supports the needs of multi- user applications – AE-ID and CSE-ID Identifiers lenghth could become an issue, in particular for constrained networks/devices – Need to shorten the length of URIs / identifiers in particular for constrained devices – Specification allows for hierarchical and non hierachical URIs, but the use of both formats brakes the ACP (no means to go from one format to another)

Solution principles – For a given request, use relative identifiers of AE-ID and CSE-ID: – The relative identifier is defined as the part of the ID that allows the receiving entity (CSE) to derive the globally unique identifier (from the context in which the request is received) – Use only hierarchical URIs for AE or CSE resources – Hierarchial and Non hierarchival URIs can be used for other resources – Multi user applications are supported by means of multiple registrations

CSE-ID M2M-SP-ID CSEBase Provided by SP during provisioning (see section ) Relative CSE-ID – Relative CSE-ID used within M2M SP domain Requests – except for the to parameter when the target resource resides in a different M2M SP domain – except for the from parameter when the request is originated in another M2M SP domain – M2M-SP-ID is mapped in the current version of the TS to a FQDN (guaranteeing global uniqueness for identifiers) – The following are valid identifiers for a CSE: – /CSEBase1/ - relative CSE identifier – FQDN M2M SP1/CSEBase1

AE-ID M2M-SP-ID CSEBase Provided by a CSE (ASN-CSE, MN-CSE or IN-CSE) at application registration – Instance is assigned by a CSE at application registration time. – Regardless of the App-ID, regardless of the ADN – AE-ID: FQDN M2M SP1/CSEBase1/App-ID1_Instance1 – Relative AE-ID could be: – App-ID1_Instance1 – CSEBase1/App-ID1_Instance1 – See table on the use of AE-ID (relative, global unique) App-ID_Instance

ACP – Originator in an ACP (CSE-ID or AE-ID ) – shall always store global unique identifiers when the originator is belonging to a domain that is different from the domain where the ACP resides: – FQDN M2M SP1/CSEBase1/App-ID1_Instance1 – FQDN M2M SP1/CSEBase 1 – Shall always store the following relative identifiers when the orginator is belonging to the same domain where the ACP resides – /CSEBase1/App-ID1_Instance1 – /CSEBase 1

Multi user applications – An application shall perform an application registration, one for each user.

Example1 MN- CSE AE (ADN ) IN- CSE Create rt=remoteCSE (from: /MN-CSEBASE1/ to: /IN-CSEBASE1/) OK Create rt=application (from: App-ID* to: /MN-CSEBASE1/) FQDN M2M SP1/MN-CSEBase1/App-ID_Intance1 Create rt=container, «meter1234» (from: App-ID_Instance1 to: /App-ID_Instance1/) URI (Hierarchical URI): App-ID_Intance1/meter1234 Resource representaion contains Non hierarchical URI: /12Uyzag MN-CSEBase1IN-CSEBase1 …

Example1 cntd. MN- CSE AE (ADN ) IN- CSE Create rt=container «meter1234» (from: App-ID_Instance1 to: /IN-CSEBASE1/App-ID_Instance12345/) URI (Hierarchical URI): /IN-CSEBASE1/App-ID_Instance12345/meter1234 Resource representation - Non hierarchical URI: /IN-CSEBASE1/212Uyzag Create rt=container «meter1234» (from: MN-CSEBase1/App-ID_Instance1 to: /IN-CSEBASE1/App-ID_Instance12345/) URI (Hierarchical URI): /IN-CSEBASE1/App-ID_Instance12345/meter1234 Resource representaion - Non hierarchical URI: /IN-CSEBASE1/212Uyzag MN-CSEBASE1IN-CSEBASE1

Example2 MN- CSE AE (ADN ) IN- CSE MN-CSEBASE1IN-CSEBASE1 IN- CSE IN-CSEBASE2 Mcc’ Retrieve (from: App-ID_Instance1 to: M2M SP2 FQDN/IN-CSEBASE2/App-ID_Instance543/meter654) Retrieve (from: /MN-CASEBASE1/App-ID_Instance1 to: M2M SP2 FQDN/IN-CSEBASE2/App-ID_Instance543/meter654) Retrieve (from: IN-CASEBASE1/MN-CASEBASE1/App-ID_Instance1 to: M2M SP2 FQDN/IN-CSEBASE2/App-ID_Instance543/ meter654)