1. Discussion for Testing related Activities Group Name: TP Source: JaeSeung Song, KETI, jssong@sejong.ac.krjssong@sejong.ac.kr Meeting Date: 2014-09-22 Agenda Item: Discussion TP-2014-0486-discussion_for_testing

2. Expectations for Testing related Activities oneM2M has to define its own testing strategies Collect test related requirements for various Rel-1 features oneM2M has to bring many testing related members If there exist expert groups or organisations outside of oneM2M, oneM2M has to make a strategy for collaboration and keeping the full control of the testing specifications oneM2M also has to thinking about performing interoperability and conformance testing. How these testing can be performed. oneM2M needs to have working groups (either a new one or using e xisting ones) to handle this. And How?

3. Available Options Option 1: Create a new dedicated working group for testing  manages all testing related activities such as developing test specifications, organizing testing events, etc. Option 2: Create a new working group mainly for coordination and planning  decide what are required for testing and coordinate with corresponding working groups. For example, this new WG can request WG3 to create a new WID for CoAP test specs. Option 3: Create a sub-working group under working groups that need to develop testing related specs. Option 4: Each working group creates WIDs for their own testing specs. Option 1: Create a new dedicated working group for testing  manages all testing related activities such as developing test specifications, organizing testing events, etc. Option 2: Create a new working group mainly for coordination and planning  decide what are required for testing and coordinate with corresponding working groups. For example, this new WG can request WG3 to create a new WID for CoAP test specs. Option 3: Create a sub-working group under working groups that need to develop testing related specs. Option 4: Each working group creates WIDs for their own testing specs.

4. Option 1  So far, in the email discussion, “Option 1” is the most preferred wa y forward.  But details need to be discussed further. For example, o the scope of a new test working group; o required specifications for Rel-1; o ways of collaborating with existing WGs; o ways of collaborating with organisations outside of oneM2M  Draft schedule (In case, we agree on option 1) : o TP#13 (Phoenix, USA): consensus on a high-level way forward a nd collect comments. o TP#14 (Busan, Korea): define the scope of the new testing WG. Agree on ToR for the testing WG. o TP#15 (USA): create the testing WG and start actual work.

5. Open questions?  What is the meaning of “oneM2M compliant”?  The scope of oneM2M testing related scope? -Binding Protocols (CoAP, HTTP, MQTT) -Procedures: registration, subscription, announcement, discover y, etc. -Device Management -Security -Semantics  What about certification?