Release Timeline Discussion R2 and beyond Group Name: TP_WPM Source: Roland Hechwartner, WPM Convenor, Meeting Date: 2015-11-12.

Slides:

Advertisements

Similar presentations

Technical Plenary From: oneM2M TP leadership Source: Meeting Date: Agenda Item:

Advertisements

Release 2: Work Items best practices Group Name: TP15 Source: Scarrone Enrico, Telecom Italia Meeting Date:

Methods Of Work Ad hoc Report TP#11 Source: Enrico Scarrone, Telecom Italia, Meeting Date:

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.

3G.IP/ R1 3G.IP 2002 Charter. 3G.IP/ R1 2 3G.IP Mission Statement u Actively promote a common IP based wireless system for third generation.

Progressing the Work on the MAS TR-0006, TR-0007 Group Name: Management Abstraction and Semantics Source: Tim Carey, ALU,

Requirements Overview Group Name: Technical Plenary (TP19) Source: Shelby Kiewel, iconectiv, Meeting Date: Agenda Item:

OneM2M-ARC Enhancement_on_resources Some thoughts on oneM2M resources Group Name: WG2 Source: Norio Uchida, NEC, Barbara.

Report of co-conveners WG1/WG2 meetings between TP1 and TP2 Group Name: Technical Plenary #2 Source: Omar Elloumi, Alcatel-Lucent,

Proposed Co-convened WG1/2 Objectives, Schedule, and Activities Group Name: TP#1 Source: Omar Elloumi (Alcatel-Lucent), Laurent Laporte (Sprint) Meeting.

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

Work Programme Management Ad hoc Group Report Group Name: one M2M TP9 Source: Convenor WPM Joachim Koss, Gemalto M2M,

Timeline for the oneM2M Partnership Project Timeline and Milestones [Joachim Koss, ETSI] Contribution to oneM2M plenary, 05 Mar 2012 Doc: Source: ETSI.

An operator’s perspective on support for different M2M deployment scenarios AT&T Group Name: TP Source: Farooq Bari, Jianrong Wang; AT&T;

MoW&M&P Report Group Name: TP19 Source: MoW Convenor, Enrico Scarrone, Telecom Italia, Meeting Date:

Setting oneM2M’s Market direction

Guidelines for: Release Maintenance, Small Enhancement and Feature Work Items Group Name: TP15 Source: Mow Convenor, (Scarrone Enrico, Telecom Italia)

Work Programme Management Ad hoc Group Report Group Name: one M2M TP12 Source: Convenor WPM Joachim Koss, Gemalto M2M,

Response Status Codes Concepts for oneM2M Group Name: WG3 Source: Philip Jacobs, Cisco, Meeting Date: Agenda Item: TS-0004.

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

Discussion on the problem of non- Blocking Synchronous mode Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 15.2.

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

WG 3 Progress Report at TP #7 Group Name: oneM2M TP #7 Source: Raymond Forbes, LM Ericsson, Meeting Date: /18 Agenda.

Report of the oneM2M Legal Subcommittee Group Name: oneM2M Steering Committee Source: Thomas Goode, ATIS, Meeting Date:

WPM ad-hoc group report TP#17 closing Group Name: WPM (TP adhoc) Source: convener WPM Roland Hechwartner, Meeting Date:

Matching Resources with CSFs Group Name: WG2 (ARC) Source: Hongbeom Ahn, LG Electronics, Meeting Date:

Timeline for the oneM2M Partnership Project Timeline and Milestones [Steve Barclay, ATIS] [Joachim Koss, ETSI] Contribution to oneM2M-Cons#4, 28 Mar 2012.

WG 2 Progress Report at TP#9 Group Name: oneM2M TP #9 Source: WG2 leadership Meeting Date: /21 Agenda Item: WG Reports.

SEC Conference calls following TP#11 Group Name: WG4 (SEC ) Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information.

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

Supporting Time Series Data Group Name: WG2 Source: Qi Yu, Mitch Tseng- Huawei Technologies, Co. LTD. Meeting Date: Work Item :WI-0033.

MoW&M&P Report Group Name: TP18 Source: MoW Convenor, Enrico Scarrone, Telecom Italia, Meeting Date:

3GPP Rel-13 Interworking discussions

Work Programme Management Ad hoc Group Report Group Name: one M2M TP7 Source: Convenor WPM Joachim Koss, Gemalto M2M,

ARC ordinary F2F meeting Seoul, June 2013 WG2 MEETING NOTES.

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

Release Timeline Discussion R2 and beyond Group Name: TP_WPM Source: Roland Hechwartner, WPM Convenor, Meeting Date:

Timeline for the oneM2M Partnership Project Timeline and Milestones [Joachim Koss, ETSI] Contribution to oneM2M plenary, 14 Mar 2012 Doc: Source: [ETSI]

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

TST WG Progress Report at TP #20 Group Name: TP Source: TST WG Chair, JaeSeung Song (KETI) Meeting Date: to Agenda Item: TP20, Item.

SEC #11 WG4 Status & Release 1 Outlook Group Name: Source:,, Meeting Date: Agenda Item:

WG1 status report to TP#21 Group Name: oneM2M TP21 Source: Shelby Kiewel (iconectiv) Meeting Date: to Agenda Item: TP#21, Item 10.4,

WG5 – MAS#21 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:

Status of Active Work Items Level of Completeness Group Name: WPM Source: Roland Hechwartner, WPM Convenor Updated:

A discussion on Release duration TP #14 Source: JaeSeung Song, KETI (TTA), Meeting Date: TP Discussion_on_Release_duration.

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

MoW Report Group Name: TP21 Source: MoW Convenor, Enrico Scarrone, Telecom Italia, Meeting Date:

WG1 status report to TP#20 Group Name: oneM2M TP20 Source: Joerg Swetina (NEC) Meeting Date: to Agenda Item: TP#19, Item 10.4, Reports.

TP WG1 - REQ Progress Report at TP #14 Group Name: WG1 REQ (Requirements) Source: WG1 Vice Chair (Joerg Swetina, NEC), Secretary Changho RYOO,

Technical Plenary Terms for the collaboration with P2413 From: oneM2M TP Chair Source: Meeting Date: Agenda Item:

WG5 – MAS#22 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Tim Carey(Alcatel-Lucent, WG5 Vice Chair) Meeting Date:

WPM ad-hoc group report TP#20 Group Name: WPM (TP adhoc) Source: convener WPM Roland Hechwartner, Meeting Date:

Discussion on Certification Group Name: TST WG Source: JaeSeung Song, WG6 Chair, Meeting Date: TST #21.

Reasons for CSF Clean-up (Issues & Next Steps) Group Name: WG2 Source: Syed Husain – NTT DOCOMO Meeting Date: (ARC_9.3) Agenda Item: 6 DOC#:

WG1 - REQ Progress Report at TP #11 Group Name: WG1 REQ (Requirements) Source: WG1 Vice Chairs Meeting Date: to Agenda Item: TP#11,

Proposed Process for Forming the oneM2M Baseline  Group name: TP#1  Source: Laurent Laporte, Sprint,

BUDGET 4Distribution of budget per phases of the project; 4Itemization of budget; 4Division of budget per source of contribution; 4Division of budget between:

Methods of Work Report Group Name: TP#10 Source: Enrico Scarrone, Telecom Italia, Meeting.

WG5 – MAS#23 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:

MoW&M&P Report Group Name: TP19 Source: MoW Convenor, Enrico Scarrone, Telecom Italia, Meeting Date:

Better Regulation and the Future Challenges in Transport

Non-Assurance Services

WPM ad-hoc group report TP#24

Release Timeline Discussion R2 and beyond

DSC Change Governance Review Group

WPM ad-hoc group report TP#25

Agenda item number 1 Agenda item number 2 Agenda item number 3 Agenda item number 4 Agenda item number 5.

GISFI #5 Meeting Report: FRN (Future Radio Networks)

Fees Initiative Chishala Kateka, Working Group Chair IESBA Meeting

Restructured Code – Effective Date

Presentation transcript:

Release Timeline Discussion R2 and beyond Group Name: TP_WPM Source: Roland Hechwartner, WPM Convenor, Meeting Date: Agenda Item: Release Timing Consideration

Release Timeline For Discussion (Assumed) timeline for Release 2 and beyond – Release 2 timeline as discussed and agreed (see slide 3) 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 in oneM2M_Method_of_Work-V (see Backup) and initial discussions in WPM – Initiate discussion on duration of Release 3* (see slide 4) Proposal for discussion – Initial brief discussion on WPM call Further assessment of timeline (scope - duration) of R3* at Stage 3 freeze of release 2 (TP#23) * Release beyond Release 2 © 2015 oneM2M Partners TP WPM R02 2

Release Timeline R2 normative work JulAugSepOctNovDecJanFebMarAprMayJunJulAugSep Stage 1 R3 non-normative work R3 normative work Stage1 Freeze R2 normative work Stage 2 R3 non normative work R3 normative work R2 normative work Stage 3 R3 normative work Stage3 Freeze TP24 R3 start norm work OctNov TP25 Stage2 Freeze TP18TP19TP20TP21TP22TP23 R2 approval R2 ratification TP26 ARC 19.4 © 2015 oneM2M Partners TP WPM R02 3 Release 2 Release 3 Color Code R2 R3 Review of R2 timeline Review of R3 timeline

Release Timeline cont´d © 2015 oneM2M Partners TP WPM R02 4 R2 normative work Q3Q4Q1Q2Q3Q4Q1 Stage 1 R3 non-normative work R3 normative work R2 normative work Stage 2 R3 non normative work R3 normative work R2 normative work Stage 3 R3 normative work Stage3 Freeze 2015 TP24 R3 start norm work Q2Q3 Stage2 Freeze TP18TP21 R2 approval R2 ratification TP30 Q1Q2Q3Q TP meeting # Stage1 Freeze TP23 TP27 TP31 TP33 R3 Stage 1 freeze R3 Stage 2 freeze R3 Stage 3 freeze TP34 TP35 R2 approval R2 ratification Release 2 Release 3 Color Code Release 4 R4 - Start Normative Work R2 R3

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 © 2015 oneM2M Partners TP WPM R02 5

Backup

Method of Work See also TP 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. © 2015 oneM2M Partners TP WPM R02 7