Leveraging goaway messages to dynamically inform connection peers of IoT events
In one embodiment, an Internet of Things (IoT) device in a network establishes connections with a plurality of peers. The device identifies an event involving the IoT device. The device generates a GOAWAY message that includes metadata regarding the event within a metadata field of the message. The GOAWAY message indicates that the IoT device is not accepting new connections. The device sends the GOAWAY message to one or more of the peers.
1. A method comprising:
establishing, by an Internet of Things (IoT) device in a network, connections with a plurality of peers;
identifying, by the IoT device, an event involving the IoT device;
generating, by the IoT device, a GOAWAY message that includes a 32-bit Error Code field, a Connection ID field, a 16-bit Reason Phrase Length field, and a variable-length Reason Phrase field, wherein the Reason Phrase field includes metadata regarding the event, and wherein the GOAWAY message indicates that the IoT device is not accepting new connections; and
sending, by the IoT device, the GOAWAY message to one or more of the peers.
2. The method as in claim 1 , wherein the upcoming event comprises one of: an upcoming roaming event, an upcoming power down event, or an upcoming sleep event.
3. The method as in claim 1 , wherein the upcoming event comprises one of: a drop in sensor accuracy or a drop in sensor validity.
4. The method as in claim 1 , wherein the GOAWAY message is a HyperText Transfer Protocol version 3 (HTTP/3) message.
5. The method as in claim 1 , wherein generating the GOAWAY message comprises:
selecting the one or more peers from among the plurality of peers, based on the identified event; and
including connection identifiers (IDs) for the connections between the IoT device and the selected one or more peers in the GOAWAY message.
6. The method as in claim 5 , wherein each connection IDs comprises a flow label, a source Internet Protocol version 6 (IPv6) address, and a destination IPv6 address.
7. The method as in claim 1 , wherein the metadata specifies a back-off time used by the one or more peers to adjust how they handle data from the IoT device during the back-off time.
8. The method as in claim 7 , wherein the one or more peers ignore data from the IoT device during the specified back-off time.
9. The method as in claim 1 , wherein the 32-bit Error Code field of the GOAWAY message is associated with the event.
10. An apparatus, comprising:
one or more network interfaces to communicate with a network;
a processor coupled to the network interfaces and configured to execute one or more processes; and
a memory configured to store a process executable by the processor, the process when executed configured to:
establish connections with a plurality of peers;
identify an event involving the apparatus;
generate a GOAWAY message that includes a 32-bit Error Code field, a Connection ID field, a 16-bit Reason Phrase Length field, and a variable-length Reason Phrase field, wherein the Reason Phrase field includes metadata regarding the event, and wherein the GOAWAY message indicates that the apparatus is not accepting new connections; and
send the GOAWAY message to one or more of the peers.
11. The apparatus as in claim 10 , wherein the upcoming event comprises one of: an upcoming roaming event, an upcoming power down event, or an upcoming sleep event.
12. The apparatus as in claim 10 , wherein the upcoming event comprises one of: a drop in sensor accuracy or a drop in sensor validity.
13. The apparatus as in claim 10 , wherein the GOAWAY message is a HyperText Transfer Protocol version 3 (HTTP/3) message.
14. The apparatus as in claim 10 , wherein the apparatus generates the GOAWAY message by:
selecting the one or more peers from among the plurality of peers, based on the identified event; and
including connection identifiers (IDs) for the connections between the apparatus and the selected one or more peers in the GOAWAY message.
15. The apparatus as in claim 14 , wherein each connection IDs comprises a flow label, a source Internet Protocol version 6 (IPv6) address, and a destination IPv6 address.
16. The apparatus as in claim 10 , wherein the metadata specifies a back-off time used by the one or more peers to adjust how they handle data from the apparatus during the back-off time.
17. The apparatus as in claim 16 , wherein the one or more peers ignore data from the apparatus during the specified back-off time.
18. The apparatus as in claim 10 , wherein the 32-bit Error Code field of the GOAWAY message is associated with the event.
19. A tangible, non-transitory, computer-readable medium storing program instructions that cause a device to execute a process comprising:
establish connections with a plurality of peers;
identifying, by the IoT device, an event involving the IoT device;
generating, by the IoT device, a GOAWAY message that includes a 32-bit Error Code field, a Connection ID field, a 16-bit Reason Phrase Length field, and a variable-length Reason Phrase field, wherein the Reason Phrase field includes metadata regarding the event, and wherein the GOAWAY message indicates that the IoT device is not accepting new connections; and
sending, by the IoT device, the GOAWAY message to one or more of the peers.
20. The computer-readable medium as in claim 19 , wherein generating the GOAWAY message comprises:
selecting the one or more peers from among the plurality of peers, based on the identified event; and
including connection identifiers (IDs) for the connections between the IoT device and the selected one or more peers in the GOAWAY message.