WG 3 Progress Report at TP13 Group Name: oneM2M TP13 Source: Raymond Forbes, LM Ericsson, Meeting Date: to Agenda Item: TP#13, Item 10, Reports from Working Groups

Issues for DECISION in TP © 2013 oneM2M Partners 2 CR Packs for following Work-items – TS-0004 v0.7.0 (Core Protocol) Rapporteurs: Shingo Fujimoto & Nobuyuki Uchida see PRO TS-0004WI-0009 Core Protocol - CR Pack Progress at 75% – Available to TP.13 for approval prior to TS-0004 V0.7.0 – TS-0009 v0.5.0 (HTTP Protocol Binding) Rapporteur: SeungMyeong Jeong see PRO TS-0009WI-0013 HTTP binding - CR Pack Progress at 75% Available to TP.13 for approval prior to TS-0009 v0.5.0 – TS-0010 v0.2.0 (MQTT Protocol Binding) Rapporteur: Peter Niblett see PRO Output_Draft_TS-0010_MQTT_Protocol_Binding_v_0_2_0 Progress at 70% Frozen at the Working Group with the CRs incorporated The updated TS-0004 v0.7.0 (some of the CRs) & TS-0009 v0.5.0 are ready to be checked with CRs incorporated.

Open Action Items for alignment in TP © 2013 oneM2M Partners 3 Item #Document Number(S)Short nameSourceStatus A-PRO PRO PRO ARC ARC AE_CSE_ID_IssueShingo: Fujitsu & Others Open To be solved in WG2 A-PRO ARC ARC PRO R03 Partial Updates – differentiate the primitivesNicolas: ALU, Qualcomm & Huawei Closed A-PRO PRO PRO ARC Presence of attributes in response messageNobuOpen A-PRO PRO R01 PRO R01 Align the Recourse descriptions with the New template in Annex I AllOpen A-PRO ARC Inter-release version negotiation at the APIMadhiOpen A-PRO ARC R01 ARC Common Attributes Phil & Rajesh Open A-PRO PRO R01 Direct Upload/Download M2M dataShingo Open

Items for INFORMATION © 2013 oneM2M Partners 4

Highlights Baselines available – TS-0004 v0.6.2 (Core Protocol) Rapporteurs: Shingo Fujimoto & Nobuyuki Uchida see PRO V0.7.0 – new baseline Progress at 75% when CRs are incorporated – TS-0008 v0.5.0 (CoAP Protocol Binding) Rapporteur: SeongYoon Kim see PRO v0.5.0 – Frozen Progress at 70% - no change – TS-0009 v0.4.3 (HTTP Protocol Binding) Rapporteur: SeungMyeong Jeong see PRO v0.5.0 – New Baseline Progress at 75% when CRs are incorporated – TS-0010 v0.2.0 (MQTT Protocol Binding) Rapporteur: Peter Niblett see PRO Output_Draft_TS-0010_MQTT_Protocol_Binding_v_0_3_0 – Progress at 70% Frozen at Working Group with the CRs incorporated © 2013 oneM2M Partners 5

Issues for INFORMATION in the TP © 2013 oneM2M Partners 6 TS-0004: ItemDocument NumberShort nameSourceLate ? PRO R03TS-0004_Annex_F_Cleanup QualcommAgreed as revised PRO R03Complex_Type_Definitions_for_MIME_Types FujitsuAgreed as R PRO R04Restructuring Common Data Types FujitsuAgreed as R PRO R03TS-0004_sec_7.3.16_cleanup InterDigitalAgreed as R PRO R02TS-0004_sec_7.3.15_cleanup InterDigitalAgreed as R PRO R02TS-0004_updates_on_ac_and_cmdh_policies Qualcomm Inc. (TIA)Agreed as R PRO R03procedure-for-service-layer-managements Huawei Technologies Co.Agreed as R PRO R01aggregate-notifications Huawei Technologies Co.Agreed PRO R01CR_TS-0004_subscription InterDigitalAgreed PRO R02CR_TS-0004_remoteCSE InterDigitalAgreed as R PRO R02CR_TS-0004_node InterDigitalAgreed as R PRO R03CR_TS-0004_contentInstance InterDigitalAgreed as R PRO R02CR_TS-0004_container InterDigitalAgreed as R PRO R02CR_TS-0004_statsConfig InterDigitalAgreed as R PRO R02TS0004 XSD Change Request IBMAgreed as R PRO R04short names Telecom ItaliaAgreed as R PRO R01TS-0004_sec_6_3_2_2_update InterdigitalAgreed PRO R01Event Category in Notification Procedure LG ElectronicsAgreed

Issues for INFORMATION in the TP © 2013 oneM2M Partners 7 TS-0004: ItemDocument NumberShort nameSourceLate ? PRO R03Design principlesIMTAgreed as R PRO R03CR_TS-0004_CSEBaseInterDigitalRevised PRO R02CR_TS-0004_AEInterDigitalAgreed as R PRO R01CR_TS-0004_statsCollectInterDigitalAgreed PRO R02CR_TS-0004_eventConfigInterDigitalAgreed as R PRO R02JSON PrinciplesIBMAgreed as R02

Issues for INFORMATION in the TP © 2013 oneM2M Partners 8 TS-0009 & TS-0010: Contributions about Protocol TS-0009/WI-0013: HTTP binding – 75% Contributions about Protocol TS-0010/WI-0014: MQTT binding – 70% ItemDocument Number Short nameSourceLate ? PRO R02MQTT Editorial CR IBMAgreed as R PRO R01MQTT Primitive Mapping IBMAgreed as R01 ItemDocument Number Short nameSourceLate ? PRO R03 HTTP Binding CRUD operationsFUJITSU Agreed as R PRO R01HTTP Binding OverviewFUJITSUAgreed

Next Steps - Core Spec/TS 0004 © 2013 oneM2M Partners 9 TSIssueVolunteer Core Protocol“TBD”s in the spec. (list of this TBD needs to be categorized first) one of the rapporteurs? authorization check in the generic procedure (clause ) SeungMyeong XSD (see list below)Wolfgang and Peter JSONPhil Brown & Peter Data type definitions (clause 6.3) This needs to be aligned with XSDs and described in the spec. MIME type definition (clause 6.7)SeungMyeong and Shingo filter criteria in query stringShingo data type for typeOfContent in Protocol/Architecture (joint issue)Indication of full update and partia l update Bindingsreview of primitive parameter ma pping PRIORITIES:

Next Steps - Core Spec/TS 0004 Issue regarding generating XSD files – Small update to Annex F to allow the Management Resources to inherit from – Resolution of a number of XML design questions. We have already made decisions on most of these, but there might be a case for changing some of these decisions What (if anything) do we want to be able to validate with the schemas - the actual resources, the request and response primitives, the cn payloads of the request and response primitives? The answers to this could result in a substantial change to Annex F and the schemas we have done to date ChildResourceRef (I have heard a suggestion that we should revisit the idea of allowing child resources to be in-lined) Allowing resource attributes to be serialized in any order Allowing attributes of multiplicity > 1 Use of string-based enumerations in addition to integer ones Conventions/guidance for names of the m2m: types Guidelines for use of anonymous vs named types Extensibility & Versioning © 2013 oneM2M Partners 10

Next Steps - Core Spec/TS 0004 Issue regarding generating XSD files – Systematic review of the text descriptions of the Resources in clause 7 and Annex D, focussing on the parts of them that affect the schemas Check that the attribute lists match TS-0001 Check that the types listed are appropriate (value space and m2m: type name) Look for consistency of the types used across different Resources – Updates to the Common Types and enumerations listed in clause 6.3 Ensure all the m2m: types referenced in clause 7 and Annex D are there Check the content models of the complex types, and the definitions of the simple types against TS – Bring the common types / enumeration files into synch with the text in clause 6.3 – Review & fix up the Resource XSDs. This should be fairly mechanical once step 3 is complete Conformance to the Annex F (especially the copyright text and the namespace declarations) Conformance to the clause 7 and Annex D definition Conformance of cardinalities to TS-0001 Schema validity – Author the missing XSDs – Repeat the process for the parameter definitions (if we decide we need XSDs for them). © 2013 oneM2M Partners 11

Next Meetings / Calls Conference Calls – PRO13.1 Tuesday – 12:00 noon UTC, October 07 – 90 minutes – PRO13.2 Tuesday – 12:00 noon UTC, October 14 – 90 minutes – PRO13.3 Tuesday – 12:00 noon UTC, October 21 – 90 minutes – PRO13.4 Tuesday – 12:00 noon UTC, October 28 – 90 minutes – PRO13.5 face-to-face Wednesday November 05 – Friday November 07– 09:00 Bungang, nr. Seoul; Korea Face to Face – TP.14 Busan, Korea November 2014 © 2013 oneM2M Partners 12