Calling an not implemented optional fault should be a sender error.

[HansBusch]

No description provided.

[melanconj]

Not sure I agree, the sender has sent a potentially valid command, it is the receiver that isn't implementing it/supporting it. It felt correct before

[HansBusch]

I see two potential cases:

1. the device signals the availability of a method via its capability but doesn't implement. This is clearly a device aka receiver issue.
2. the device doesn't signal the availability of a method via its capability and the client nevertheless calls it. This is clearly a client aka sender issue.

A well implemented device should respond as 2. and a badly implemented one as 1.

As the device is the one that decides I prefer option 2. If it missbehaves it is a bug.

[bsriramprasad]

As we are trying to update core spec, we need to validate the impact on the DTT and or relevant tests that can get affected by this.

[MariaYa0091]

This fault is widely used at DTT which have impact on both feature discovery procedure and test cases (to check feature support for older endpoints without capabilities).

Just replacing fault at DTT will have impact for already existing implementations.

As a solution DTT could be change to expect any of env:Receiver/env:Sender, but at will not be a simple update (because of different places involved) .

Also please take in account that the same changes to be done for the real Clients.

[HansBusch]

Then suggest to keep as is and add annotation to table 4 that the fault may be caused by sender although labeled as env:receiver.

[bsriramprasad]

@sujithhanwha

• if you approve this, it will be set for merge, while the above discussion points to adding a clarification than doing requirement change, Or did I miss something?

[sujithhanwha]

@sujithhanwha

• if you approve this, it will be set for merge, while the above discussion points to adding a clarification than doing requirement change, Or did I miss something?

@bsriramprasad , didn't notice maria's feedback. I am ok with Hans suggestion of adding a note and keep the error as is.