Subject: [lp-wan] scenarii in draft-toutain-lpwan-coap-traffic-00.txt

From: "Pascal Thubert (pthubert)" <[email-masked]>
Date: Fri, 20 Jan 2017 13:32:28 +0000

Hello Laurent:

Do we agree that the SCHC Gateway will have to be stateful? If so:

3.1.  Scenario 3 - CoAP ack: could we consider an Ack->nack conversion, like the SCHC would absorb the ack, but time out if it is not coming and then send a nack with the Message ID?
 	 alt, it could build a list of pending acks for a period of time  and send only one "packed" response with a list of confirmed Message IDs at the end of the day? Ideally these would be options left to the technology

3.2.  Scenario 4 - REST ack: same kind of logic would have SCHC GW only send a Nack in case of missing Acks, providing the token.

Both:  could we have an option where the SCHC computes the Message ID / token? If there can be a few pending, then the device could signal which with a few bits only?

Take care,

Pascal