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

2. Background of CSFs in TS-0001 CSE comprises the set of “service functions” that are common to the M2M environments and specified by oneM2M. Such service functions are exposed to other entities through Reference Points Mca, Mcc, and Mcn. There are 13 “service functions” supported inside the CSE and these are referred to as CSFs. These are described in Clause 6.2. Annex-A provides a mapping of CSFs and their various sub-functions to the stage 1 requirements. Lot of work has gone into describing the 13 CSFs and the sub-functions supported by each. This has helped in the development of the M2M Architectural framework and ensuring that the stage 1 requirements are addressed. © 2013 oneM2M Partners 2

3. Issues with Clause 6.2 CSF descriptions need to be reviewed for accuracy and consistency. There are many editor’s notes and some TBDs in the CSF descriptions. The “shall” requirements need to be checked. There is no mechanism to verify if the CSF “shall” requirements are addressed adequately in Rel-1. The intent of CSFs is to identify the service functions that need to be supported by the CSE. CSFs can interact with each other but these interactions are not specified as there is no intent to standardize their interactions within a CSE. However, CSE-to- CSE interactions are specified. To the reader of TS-0001, CSFs give an impression that they inter-work with each other and somewhere their interactions must be described and standardized. But beyond section 6.2, where they are described, their usefulness is not apparent in the remaining spec. Except for a few CSFs (such as CMDH, DMR, REG, DMG etc.), the normative aspects of the CSFs are not borne out in the later part of TS-0001. This leaves us vulnerable to lack of interoperability between implementations. © 2013 oneM2M Partners 3 So, what should be done with these CSFs?

4. Some proposed options © 2013 oneM2M Partners 4

5. Option-1 Keep CSF descriptions in the main body of the spec – Clause 6.2, but mark this clause as informational only. Clearly mention that these CSFs are mainly identified to come up with the key service functions of the oneM2M system to help in the development of the oneM2M Architectural framework. Review all CSF descriptions for accuracy and consistency, and resolve all Editor’s Notes (clean-up). Remove the “shall” words from the CSF text descriptions as these are hard to verify. Make CSF descriptions more general. Align Annex-A with the revised CSF descriptions. © 2013 oneM2M Partners 5

6. Option-2 Do all steps of Option -1, but keep clause 6.2 as normative. Invite contributors of the CFSs to address the normative aspects, by verifying if the “shall” requirements are addressed in Rel-1 or are for future releases. Align Annex-A with the revised CSF descriptions. © 2013 oneM2M Partners 6

7. Option -3 Clean-up the CSF descriptions as mentioned in Option-1. Move CSF descriptions into an informative Annex. Align Annex-A with the revised CSF descriptions. © 2013 oneM2M Partners 7

8. Next Steps © 2013 oneM2M Partners 8

9. Next Steps Agree that the issues listed in slide 3 need to be addressed. Discuss the proposed options in slides 5-7, and select one (or modified one) to go forward with. Form an offline activity for CSF clean-up exercise, to be completed by TP#11. © 2013 oneM2M Partners 9