2nd Interoperability testing issues Group Name: TP WG Source: Mahdi Ben Alaya, WG6 Vice Chair, Sensinov Keebum Kim, TTA Meeting Date: TP #23

1. Unstructured SP-relative Resource ID format The examples provided In TS-0001-V1.13.3 to describe unstructured SP-relative Resource ID is not correct: A “slash” shall be added at the beginning. TS-0001-V1.13.3 Table 7.2-1:

2. Notification Content Type mandatory or optional ? In TS-0001 Notification Content Type is optional: Table 9.6.8-2: In XSD 1.6.0: Notification Content Type is mandatory: CDT-subscription-v1_6_0: <xs:element name="nct“ type="m2m:notificationContentType"/>

3. App-id and AE-ID of announced resource optional or mandatory ? According to TS-0001: App-id and AE-ID of Announced AE are optional According to XSD 1.6: App-id and AE-ID of Announced AE mandatory <xs:element name="api" type="xs:string"/> <xs:element name="aei" type="m2m:ID"/>

4. ParentID empty or absent in CSEBase resource ? In TS-0004, for CSEBase, the value of ParentID shall be an empty string. TS-0004-V1.7.0 (2016-March-18): In TS-0001, the parentID is specified in all resource types except CSEBase TS-0001-V1.13.3 (2016-March-27): 5

5. Node child resource in RemoteCSE The remoteCSE shall not contain a Node resource. However Node is mentioned as child resource type in TS-0001. TS-0001-V1.13.3 Table 9.6.1.1-1 6

6. Default filterUsage value interpretation If the filterUsage parameter is not provided, the Retrieve operation is a generic retrieve or a conditional retrieve ? In TS-0004-V1.7.0 Table 8.1.2-2 : (Generic retrieve) In TS-0001-V1.13.3 Table 6.3.4.2.31 (Conditional retrieve)

7. Content-Location VS Location Incosistency between HTTP spec and oneM2M spec: According to HTTP specification the “Location” header shall be used to set the URL of the created resource. However oneM2M uses another header called “content-location” (Dedicated for other purposes according HTTP). OneM2M TS-0009-V1.5.1 The Content-Location header of HTTP response messages shall be set to the URI of the created resource, when responding to a Create request primitive.(...) Hypertext Transfer Protocol – HTTP/1.1 14.14 Content-Location : The Content-Location entity-header field MAY be used to supply the resource location for the entity enclosed in the message when that entity is accessible from a location separate from the requested resource's URI. (…) The meaning of the Content-Location header in PUT or POST requests is undefined. 14.30 Location: The Location response-header field is used to redirect the recipient to a location other than the Request-URI for completion of the request or identification of a new resource. For 201 (Created) responses, the Location is that of the new resource which was created by the request. 8

8. How to limit the nesting levels when using “attribute+child-resource” In TS-0001-V1.13.3 it is possible to limit the nesting levels when using “attribute+child-resource” but it is not clear how ? Clause 8.1.2: Table 8.1.2-2 A dedicated filter criteria for nesting level is missing.

9. Returned attribute after creation request ? In TS-0001-V1.13.3 clause 10.1.1.1: after creation the CSE shall return all mandatory attributes. In TS-0001-V1.13.3 clause 8.1.2: After creation the CSE shall return all assigned/modified attributes values.

10. Deleting an ACP that is used in a resource What happens when an ACP used by a resource is deleted. The resource will not be accessed anymore. Shall the CSE verify the existing owners before deleting an ACP ?

11. Remove all membersIDs of a group after a delete request fanout Sending a delete request to a fanout point results in deleting all members resources from the group. In this case, shall the CSE also removes all the memberIDs of the deleted resources from the group ? The logical answer here is yes, however this is not possible because the group requires at least 1 memberId (mondatory). Or shall the CSE removes the group resource entirely ?

12. NodeLink attribute RO or RW ? The NodeLink attribute is RO for AE and CSEBase resources. However, it is RW for RemoteCSE resource? Is this a mistake in the specification or there is a kind of logic behind this configuration.

13. Latest and oldest of empty container Latest and oldest are mandatory attributes. So, how to represent “latest” and “oldest” of an empty container ? TS-0001 Annex C.2 <?xml version="1.0" encoding="UTF-8"?> <m2m:container resourceName="12xx"> … <latest>//IN-CSEID.m2m.myoperator.org/96739</latest> <oldest>//IN-CSEID.m2m.myoperator.org/34722</oldest> </m2m:container>

14. Return “latest” and “oldest” when result content = attributes ? When a request is sent to retrieve a container using result content = attributes, it is not clear if the CSE shall return virtual resources like latest and oldest ? TS-0001-V1.13.3 Clause 8.1.2

15. Security in Mca is not mandatory Very risky In TS-0003 Clause 6.1.2.2.1, security on Mca is strongly recommenced but not mandatory. Given that AE-IDs are not considered as sensitive data (shared in the URIs, Representation, etc.), any entity having access to the non secured Mca can use any AE-IDs as “from” to access non authorized resources. The risk in oneM2M is very high compared to other non secured solutions (e.g. based on login/password) due the fact that AE-IDs are exposed by the CSE.

16. How to generate Unstructured-CSE-relative-Resource-ID in AE creation request ? Shall the Unstructured-CSE-relative-Resource-ID be equals to AE-ID- Stem for AE creation request ? Or the CSE can use the AE-ID-Stem to generate a different ResourceID (e.g adding a slash, etc.) ? TS-0001-V1.13.3 clause Step 005c: The Registrar CSE shall select an AE-ID-Stem starting with a 'C' character and use it for the Unstructured-CSE-relative-Resource- ID for the <AE> resource to be created on the Registrar CSE and continue with action (4) of Step 002 of the non-registration related CREATE procedure in clause 10.1.1.1. 17

17. ACP verification when ACPI does not exist in resource To verify ACP for resource without ACPI shall the CSE check the parent resource ACPI or check “the default ACP of the system” ? TS-0001: The meaning of “Does not exist” is ambiguous here. Two possible comprehensions: ACPI attribute does not exist in the received representation (e.g. Container created with no ACPI) ACPI does not exist in the resource type (e.g. Schedule)

18. Multihop Retargeting issues In the following configuration an AE registered to the IN-CSE cannot access a resource under the ASN-CSE using retargeting because the ASN-CSE is not visible by the IN-CSE. IN-CSE MN-CSE ASN-CSE

19. Correlate notifications to request when using Non blocking asynchronous In TS-0001, for non blocking asynchronous, the result of the requested operation shall be send as notification. The <Request> resource type is not used, so no possible correlation between notifications and the corresponding request. In TS-0001-V1.13.3 sec. 8.1.2: nonBlockingRequestAsynch {optional list of notification targets}: (...). The result of the requested operation needs to be sent as notification(s) to the notification target(s) provided optionally within this parameter as a list of entities or to the Originator when no notification target list is provided. (...) In TS-0001-V1.13.3 sec. 8.2.2.3: In the asynchronous case, a Hosting CSE that does not support the <request> resource type shall respond to an acceptable request with a response containing an Acknowledgement without a reference to a resource containing the context of the request.

20. Error info representation ? oneM2M does not standardize the resource structure of message errors. For the time being, each company chooses its own payload format to give some details about a specific error. (E.g. plain text, XML, JSON, etc.) An XSD should be provided to avoid interoperability issue. AE would need a clear representation of the error info to be parsed.

21. XSD validation of resource representation The CSE shall validate resource representation against the XSDs schemas. TS-0004 v1.7.0 section 7.3.2.1: (…) The received resource representation (e.g. in plain XML, binary XML or JSON) shall be validated against the provided schema definitions. Is it necessary to respect the order of attributes for XML ? How about object order in JSON ? Current XSDs are provided for update or for Create ?

Thank you for attention