[TC-CNET-4.11] The provided reference log conflicts with the description of the requirement at step 13.

From chip-test-scripts created by xilizhang1: CHIP-Specifications/chip-test-scripts#687

Summary Title:

step13: Verify that the TH successfully connects to the DUT. But the reference log value is "False"

Description:

Steps to reproduce:

Use two Raspberry Pi for simulation testing, one as the reference DUT and the other as the TH (both Raspberry Pi version: v2.8.1-official)

Logs:

============DUT log=========
[1696661554.926464][2843:2843] CHIP:IM: Received Read request
[1696661554.926549][2843:2843] CHIP:DMG: ReadRequestMessage =
[1696661554.926582][2843:2843] CHIP:DMG: {
[1696661554.926608][2843:2843] CHIP:DMG: AttributePathIBs =
[1696661554.926638][2843:2843] CHIP:DMG: [
[1696661554.926664][2843:2843] CHIP:DMG: AttributePathIB =
[1696661554.926695][2843:2843] CHIP:DMG: {
[1696661554.926722][2843:2843] CHIP:DMG: Endpoint = 0x0,
[1696661554.926749][2843:2843] CHIP:DMG: Cluster = 0x31,
[1696661554.926780][2843:2843] CHIP:DMG: Attribute = 0x0000_0001,
[1696661554.926806][2843:2843] CHIP:DMG: }
[1696661554.926831][2843:2843] CHIP:DMG:
[1696661554.926855][2843:2843] CHIP:DMG: ],
[1696661554.926882][2843:2843] CHIP:DMG:
[1696661554.926908][2843:2843] CHIP:DMG: isFabricFiltered = true,
[1696661554.926930][2843:2843] CHIP:DMG: InteractionModelRevision = 1
[1696661554.926952][2843:2843] CHIP:DMG: },
[1696661554.927024][2843:2843] CHIP:DMG: IM RH moving to [GeneratingReports]
[1696661554.927146][2843:2843] CHIP:DMG: Building Reports for ReadHandler with LastReportGeneration = 0 DirtyGeneration = 0
[1696661554.927178][2843:2843] CHIP:DMG: RE:Run Cluster 31, Attribute 1 is dirty
[1696661554.927197][2843:2843] CHIP:DMG: Reading attribute: Cluster=0x0000_0031 Endpoint=0 AttributeId=0x0000_0001 (expanded=0)
[1696661554.927224][2843:2843] CHIP:DMG: AccessControl: checking f=1 a=c s=0x000000000001B669 t= c=0x0000_0031 e=0 p=a
[1696661554.927259][2843:2843] CHIP:DMG: AccessControl: allowed
[1696661554.932586][2843:2843] CHIP:DL: Current connected network: "EDT-liz"
[1696661554.933233][2843:2843] CHIP:DMG: Sending report (payload has 76 bytes)...
[1696661554.933450][2843:2843] CHIP:EM: <<< [E:41228r S:43006 M:134093789 (Ack:50834063)] (S) Msg TX to 1:000000000001B669 [219D] --- Type 0001:05 (IM:ReportData)
[1696661554.933522][2843:2843] CHIP:IN: (S) Sending msg 134093789 on secure session with LSID: 43006
[1696661554.933777][2843:2843] CHIP:DMG: OnReportConfirm: NumReports = 0
[1696661554.933825][2843:2843] CHIP:DMG: ReportsInFlight = 0 with readHandler 0, RE has no more messages
[1696661554.935324][2843:2843] CHIP:DMG: IM RH moving to [AwaitingDestruction]
[1696661554.935382][2843:2843] CHIP:DMG: All ReadHandler-s are clean, clear GlobalDirtySet

=========================TH log======
[1696661554.888709][3777:3779] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0031 Attribute 0x0000_0001 DataVersion: 3665788991
[1696661554.888807][3777:3779] CHIP:TOO: Networks: 1 entries
[1696661554.888863][3777:3779] CHIP:TOO: [1]: {
[1696661554.888896][3777:3779] CHIP:TOO: NetworkID: 53485F54455354
[1696661554.888924][3777:3779] CHIP:TOO: Connected: FALSE
[1696661554.888949][3777:3779] CHIP:TOO: }
[1696661554.889156][3777:3779] CHIP:EM: <<< [E:41228i S:13574 M:50834064 (Ack:134093789)] (S) Msg TX to 1:0000000000000001 [219D] --- Type 0000:10 (SecureChannel:StandaloneAck)
[1696661554.889209][3777:3779] CHIP:IN: (S) Sending msg 50834064 on secure session with LSID: 13574
[1696661554.889389][3777:3779] CHIP:EM: Flushed pending ack for MessageCounter:134093789 on exchange 41228i
[1696661554.889688][3777:3777] CHIP:CTL: Shutting down the commissioner
[1696661554.889730][3777:3777] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1696661554.889760][3777:3777] CHIP:CTL: Shutting down the controller
[1696661554.889790][3777:3777] CHIP:IN: Expiring all sessions for fabric 0x1!!

Additional Info:

Reference the Main spec"Version 1.2-prerelease-ipr, 2023-09-05 15:21:34 -0700: Draft" 11.8.5.4 section
Connected Field
This field SHALL indicate the connected status of the associated network, where "connected" means
currently linked to the network technology (e.g. Associated for a Wi-Fi network, media connected
for an Ethernet network).

We want to confirm that this correct value should be False or TRUE ?

2.We not only see this problem on the Raspberry Pi, but also on other chip devices. Is this an SDK issue?