Skip to content

[Test Failed] TC_SC_4_1 Step 19 appears to require commissionable subtypes in _services._dns- sd._udp.local. response, which is stricter than RFC 6763 #72928

Description

@wqx6

Test issue(s)

While running TC_SC_4_1.py, the test failed at Step 19 when verifying commissionable subtype advertisements.

The DUT successfully responded to a direct PTR browse for the long discriminator subtype at Step 18:

  Query:
  _L15._sub._matterc._udp.local.

  Response:
  8F4905086CB33025._matterc._udp.local.

However, Step 19 then performed service type discovery via _services._dns-sd._udp.local. and expected the returned service type list to include commissionable subtype browse names such as:

_L15._sub._matterc._udp.local.
_S0._sub._matterc._udp.local.
_CM._sub._matterc._udp.local.

The discovered subtype list was empty, causing the test to fail: Details='_L15._sub._matterc._udp.local.' not found in [] 'Long Discriminator Subtype' must be present.

RFC 6763 Section 9 defines _services._dns-sd._udp. as a service type enumeration meta-query. It says the PTR rdata is the two-label service type plus domain, for example:

_matterc._udp.local.

It does not appear to require responders to include subtype browse names such as:

_L15._sub._matterc._udp.local.

This failure can be reproduced when testing with ESP32 light example(Disable minimal mdns[CONFIG_USE_MINIMAL_MDNS]).

testfailure.log

Platform

esp32

Anything else?

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    Status
    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions