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

Issues for DECISION in TP Endorse R. Brennan as co-rapporteur of TS-0001 (replacing G. Foti) © 2013 oneM2M Partners 2

Issues for DISCUSSION in TP WG2 leadership would like to encourage those who contributed to WG2 features to ensure those are addressed in WG3 for stage 3 aspects © 2013 oneM2M Partners 3

Items for INFORMATION © 2013 oneM2M Partners 4

Highlights WI-0002 TS-0001 Architecture – Enforced priorities Not all contributions were handled -> conference calls – Agreed way forward for essential (sometimes controversial) subjects needed to declare a freeze Triggering Charging Security Access Right/Role/Subscription – Discussed how to handle features that will not be part of R1 (features to be moved to R2) – Continuous coordination with other WGs WG4: Provided the basis for SEC section in TS0001 -> THANKS WI-0011 TS 0007 (Services) – Agreed skeleton – Initial discussion on architecture – Initial input on architecture © 2013 oneM2M Partners 5

Highlights Agreement in principle to freeze TS-0001 one week after availability of the output draft. Extract from method of work – Deliverable Freeze:A Technical Plenary (TP) and/or Working Group (WG) action on a draft deliverable, restricting further technical input to essential changes and corrections – From 7.2 Deliverable management – Step 4: Freeze a)The Working Group (and/or Technical Plenary) may determine that the technical content of a draft deliverable is complete (given consideration of the WI scope and workplan), and may freeze the deliverable for technical input. b)A deliverable freeze shall restrict further technical input to essential changes and corrections. © 2013 oneM2M Partners 6

Highlights Agreement in principle to put TS-0001 under Change Control mode Extract from method of work – The Working Group (and/or Technical Plenary) may determine that the content of a draft deliverable is sufficiently advanced that it will utilize the Change Control process. a.1) New Technical Specification (TS), Technical Report (TR) or other deliverable types may be placed under Change Control at the discretion of the group a.2) New Technical Specification (TS) deliverables shall be placed under Change Control no later than the Freeze date. a.3) Approved Technical Specification (TS) and Technical Report (TR) deliverables shall always be under Change Control

Guidelines for change control Includes an informative introduction containing the problem(s) being solved, and a summary list of proposals. The second part containing proposals: Follows the principle of completeness, where all related changes within a deliverable are simultaneously proposed to be made E.g. A change impacting 5 tables should not only include a proposal to change only 3 tables. Includes any changes to references, definitions, and acronyms in the same deliverable. Follows the drafting rules Has content that does not conflict with the content of an already approved text, by modification, deletion or the addition of an editor’s note. Has been spell-checked and is grammatically correct, to the extent practicable Change bars for modifications shall be used. The change should include the current and surrounding clauses to clearly show where a change is located and to provide technical context of the proposed change. Additions of complete sections need not show surrounding clauses as long as the proposed section number clearly shows where the new section is proposed to be located. Each CR should contain changes related to only one particular issue/problem. Multiple changes in a single CR shall be clearly separated by horizontal lines with embedded text such as, start of change 1, end of change 1, start of new clause, end of new clause. When subsequent changes are made to content of a CR, then the accepted version should not show changes over changes. The accepted version of the CR should only show changes relative to the baseline approved text.

Next Steps Need to provide guidelines for next steps – What is considered essential change/correction – Guidelines will be available within one weel Decisions will be made on a case by case basis © 2013 oneM2M Partners 9

Next Meetings / Calls © 2013 oneM2M Partners 10