Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Read Composite with the overlapping path is not possible #1486

Open
Warmek opened this issue Jul 27, 2023 · 2 comments
Open

Read Composite with the overlapping path is not possible #1486

Warmek opened this issue Jul 27, 2023 · 2 comments
Labels
question Any question about leshan

Comments

@Warmek
Copy link
Contributor

Warmek commented Jul 27, 2023

Version(s)

v2.0.0-M11

Which components

Client and Server

Tested With

No response

What happened

Read Composite with the overlapping path is not possible

We know that there was discussion but we need it for ETS (LightweightM2M-1.1-int-229)

How to reproduce

Preconditions:
The Client supports Configuration C.1 as defined in Annex C
The client is registered with the L2M2M Server
The client supports mandatory resources of Lw2M2M Server and Device Objects

Test Procedure:

  1. Server performs a Read-Composite (CoAP FETCH) on the following combination of Objects, Object Instances, Resources, and Resources Instances:
    Device Object (/3)
    L2M2M Server Object Instance (/1/x, where x in a LwM2M Server Object Instance)
    Lifetime Resource (/1/x/1)
    Error Code Resource Instance (/3/0/11/0)
    "Accept: Content-format" is set either to SenML CBOR or SenML JSON

Pass-Criteria:
A. Client accepted the request and replied with 2.05 Content. Message payload contains requested data. The content format is either: SenML CBOR or SenML JSON
supports

Relevant Output

No response

@Warmek Warmek added the bug Dysfunctionnal behavior label Jul 27, 2023
@sbernard31
Copy link
Contributor

I guess you are talking about 6.1.3.19 LightweightM2M-1.1-int-229 – Read-Composite Operation from Enabler Test Specification (Interoperability) for Lightweight M2M Draft Version 1.1 – 12 Sep 2019, correct ?

FMPOV,

  1. This use case still doesn't make sense to me. Why reading /1/x and 1/x/1 as 1/x/1 is include in /1/x ? In real life what is the use case for this ?
  2. Not sure but I will not be surprised this is rather a bug in ETS draft OR at least a not so good idea to use this corner case for an interoperability test.

So let's try to get answer from OMA : OpenMobileAlliance/OMA_LwM2M_for_Developers#568

@sbernard31 sbernard31 added question Any question about leshan and removed bug Dysfunctionnal behavior labels Jul 27, 2023
@Warmek
Copy link
Contributor Author

Warmek commented Aug 23, 2023

AVSystem, IoTerop and 6D Tech LwM2M Server implementation of ETS 229 are suporting Read Composite with the overlapping paths, as-is, since the status is "passed" with some clients (for example Paradox client)

https://github.com/OpenMobileAlliance/OMA_LwM2M_for_Developers/wiki/Mar-2021--Virtual-TestFest-Product-Listings

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Any question about leshan
Projects
None yet
Development

No branches or pull requests

2 participants