1. MoW Report Group Name: TP21 Source: MoW Convenor, Enrico Scarrone, Telecom Italia, enrico.scarrone@telecomitalia.it Meeting Date: 2016-01-18

2. MoW Activities – 2 calls held from the last TP meeting jointly with M&P – Two issue were discussed DRAFTING RULES New participation type for member based organizations © 2016 oneM2M Partners TP-2016-0010-MoW_Report_at_TP_21 2

3. NEW-updated Drafting rules Updated DRAFTING RULES has been approved at SC29. The approved document was the original presented at July SC 27 meeting (SC-2015-0035).SC-2015-0035 Editorial updates – adding TSDSI, change copyright date. Removal of the mathematical formulae print screens as this option is no longer available in MS Word, Updated paragraphs to remove the possibility of hanging paragraphs Updated the definitions, to assure that the definitions are identified with a capital initial letter Clarifications on normative references and editors notes Added information on Test Methods descriptions © 2016 oneM2M Partners TP-2016-0010-MoW_Report_at_TP_21 3

4. New participation type for member based organizations Requirements, rights and obligations has been fixed New name has been proposed A proposal for an update PA and WP has been developed in the M&P and the Legal SC groups to implement this new oneM2M participation type (SC-2015-0062)SC-2015-0062 The proposal has generated some further discussions in the Steering Committee and seems to be not mature enough to fly. – M&P will continue to work on this, in collaboration with the Legal group © 2016 oneM2M Partners TP-2016-0010-MoW_Report_at_TP_21 4

5. Future planned work – Next calls jointly with M&P: To be planned at this TP © 2016 oneM2M Partners TP-2016-0010-MoW_Report_at_TP_21 5

6. Clause 7.7 of MoW: Version numbering The 3 field version code shall be used to be used as follows: First field from the left: Release 0 = draft spec N = the specification belongs to Release N The number is moved from 0 to N at approval time of the draft deliverable The number is incremented from N to N+1 at the time of the generation of a new version. Second field from the left: technical content The number is set to 0 at any increase of the Release field. The number is increased at any update of the technical content of the deliverable. Third field from the left: editorial modification The number is set to 0 at any increase of the technical content field. The number is increased at any editorial update of the deliverable. © 2016 oneM2M Partners TP-2016-0010-MoW_Report_at_TP_21 6

7. Examples 0.0.0 First draft skeleton 0.1.0 First technical change 0.2.0 Technical change 0.2.1 Editorial update 1.0.0 First approved version Release 1 2.0.0 First Release 2 version - from 0.x.x for a new spec, - from 1.x.x when generated from an approved Release 1 spec 2.1.0 Technical change to Release 2 3.0.0 First Release 3 version - from 0.x.x for a new spec - from 2.x.x when generated from an approved Release 1 spec) © 2016 oneM2M Partners TP-2016-0010-MoW_Report_at_TP_21 7