Release Timeline Discussion R2 and beyond Group Name: WPM Source: Roland Hechwartner, WPM Convenor, roland.hechwartner@t-mobile.at Meeting Date: 2016-03-15 Agenda Item: 5.3

Timeline for Release 2 & beyond Source: TP-2015-0876R01-Release_Timeline_Discussion Timeline for Release 2 & beyond Release 2 timeline as discussed and agreed (see slide 4) oneM2M Release 2 Features As discussed in interim TP and WPM session during TP#20 meeting week Final assessment based on R2 content at TP#22 i.e. after stage 2 freeze (TP#21) Timing considerations for R2 => R3* (see slide 3) Based on MoW guideline for workflow amongst releases oneM2M Method_of_Work-V-1.3.2 (see Backup) Initiate discussion on duration of Release 3* (see slide 5) Proposal for discussion Initial brief discussion in WPM Further assessment of timeline (scope - duration) of R3* at Stage 3 freeze of release 2 (TP#23) * Release beyond Release 2

oneM2M release 2 features source: TP-2016-0019-Release_2_feature_review oneM2M release 2 features Home domain enablement (at least 1 normative feature) Home appliance information models Industrial domain enablement (at least 1 normative feature) Time series, etc. In conjunction with the TR oneM2M Beyond initial release oneM2M Application Identification Registry established Semantic interoperability base ontology semantic discovery semantic descriptions oneM2M interworking framework Generic interworking AllJoyn/AllSeen and/or OIC and/or OMA LightWeight M2M (OMA LWM2M) and/or 3GPP Rel.13 Interworking Advanced protocol binding WebSocket Efficient content representations (?) Security Enhancement for authorization (?) privacy support e2e security

Release Timeline R2 R3 2015 2016 Color Code Review of R3 timeline Source: TP-2015-0876R01-Release_Timeline_Discussion Release Timeline R2 normative work Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Stage 1 R3 non-normative work R3 normative work Stage1 Freeze Stage 2 R3 non normative work Stage 3 Stage3 Freeze 2015 2016 TP24 R3 start norm work TP25 Stage2 Freeze TP18 TP19 TP20 TP21 TP22 TP23 R2 approval R2 ratification TP26 ARC 19.4 Release 2 Release 3 Color Code Review of R3 timeline R2 R3 Review of R2 timeline

Release Timeline cont´d Source: TP-2015-0876R01-Release_Timeline_Discussion Release Timeline cont´d Release 2 Release 3 Color Code Release 4 2015 2016 2017 2018 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 TP meeting # TP18 TP21 TP23 TP24 TP27 TP30 TP33 TP35 TP31 TP34 Stage 1 Stage1 Freeze R3 start norm work R2 normative work R3 non-normative work R3 Stage 1 freeze R3 normative work R2 R3 R4 Stage 2 Stage2 Freeze R2 normative work R3 non normative work R3 Stage 2 freeze R3 normative work Stage 3 Stage3 Freeze R2 normative work R3 Stage 3 freeze R3 normative work R2 approval R3 approval R2 ratification R3 ratification R4 - Start Normative Work

Release Timeline Proposal Source: TP-2015-0876R01-Release_Timeline_Discussion Release Timeline Proposal It is proposed to review this contribution in order to agree on the timeline for Release 2 Including review and final assessment at TP#22 agree on an initial working assumption for the release beyond R2 (Release 3) Further review and assessment at TP#23 * Release beyond Release 2

Backup

Method of Work See also TP-2015-0809-Method_of_Work-v1_3_2 The following guidelines are therefore given to govern the workflow among subsequent releases development (Release x+1 respect to Release x): Release x+1 stage 1 normative work cannot be initiated before the freezing of Release x stage 3 Release x+1 stage 2 normative work cannot be initiated before the ratification of Release-x Non normative work on stage 1 of Release x+1 can be performed at any time of Release x Non normative work on stage 2 Rel x+1 can be performed after the freezing of stage 3 Release x Testing is seen as an independent process not directly linked to the 3 stages model. these guidelines are general principles for all the Releases, the TP may decide different timelines for a specific release based on identified needs/opportunities.

oneM2M planned Release2 Features - Stage2 Industrial domain enablement (at least 1 normative feature) Time series, etc. In conjunction with the TR APP Developer guideline Home domain enablement (at least 1 normative feature) Home appliance information models oneM2M Beyond initial release Semantic interoperability base ontology semantic discovery semantic descriptions oneM2M interworking framework Generic interworking AllJoyn/AllSeen and/or OIC and/or OMA LightWeight M2M (OMA LWM2M) and/or 3GPP Rel.13 Interworking APP identifiers and registry services Security Enhancement for authorization privacy support e2e security (basic)