???(Uze Choi) wrote: > There is already draft for this in Conditional observe in CoAP. > https://tools.ietf.org/html/draft-li-core-conditional-observe-02 > > How about to implement it into the IoTivity. This will enable various > usecases.
Hi Uze, several proposals have been made over the past couple of years for options that would inform the server about more detailed client requirements for an observation relationship. None of these gained traction. I think the main reason for this was that those details are often very application specific, and it is hard to generalize them into a small number of widely applicable options. One obvious way to supply additional information is adding query parameters. What details are supplied can then be controlled by the application. (The next question, of course, is how the client finds out about these options -- but that is just an instance of link discovery.) Now I haven't read the entire thread yet so I don't know how this aspect relates to the "multicast" in the subject. Will find out later... Gr??e, Carsten
