On Tue, Mar 27, 2012 at 13:31, Carsten Bormann <[email protected]> wrote: > Can we try to separate the message and request/response layers? >
Having the Token Option in the request/response layer leads to a problem in the separation. In this state machine graph I made the assumption that proper session matching is applied before applying state transitions. In my point of view "proper session matching" means checking (loc-host, loc-port, rem-host, rem-port, token). Legenda: "loc: Local", "rem: Remote", "host: IP Host", "port: UDP Port", "token: CoAP Token Option" If I remove the Token Option from the session matching condition (i.e., I check [loc-host, loc-port, rem-host, rem-port]), I can't devise any real state since I can still receive any message in any state, and transition to any other state depending upon the Token contained in it... Suggestions? Best, Angelo
_______________________________________________ Lwip mailing list [email protected] https://www.ietf.org/mailman/listinfo/lwip
