Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Added connection close+reset case to Connection Health section #140

Merged
merged 1 commit into from Apr 21, 2017
Merged

Added connection close+reset case to Connection Health section #140

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 5 additions & 1 deletion draft-ietf-core-coap-tcp-tls.md
View file
Open in desktop
Expand Up @@ -513,6 +513,10 @@ resource and it does not receive any notification for some time),
it can send a CoAP Ping Signaling message (see {{sec-ping}}) to test
the connection and verify that the CoAP server is responsive.

When the underlying TCP connection is closed or reset, the signaling state
and any observation state (see {{observe-cancel}}) associated with the reliable
connection are removed. In flight messages may or may not be lost.

# CoAP over WebSockets {#websockets-overview}

CoAP over WebSockets is intentionally similar to CoAP over TCP; therefore,
Expand Down Expand Up @@ -1703,7 +1707,7 @@ the health of the connection (and all its active observations) by sending a CoAP
Ping Signaling message ({{sec-ping}}) rather than individual requests to confirm
active observations.

## Cancellation
## Cancellation {#observe-cancel}

For CoAP over UDP, a client that is no longer interested in receiving notifications can "forget"
the observation and respond to the next notification from the server with a reset message to cancel
Expand Down