-
-
Notifications
You must be signed in to change notification settings - Fork 119
Fix CoAP ping response over unreliable transport #604
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.
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
base: master
Are you sure you want to change the base?
Conversation
As per RFC 7252, the CoAP ping (empty, confirmable message) must be responded to with a reset message. Resolves plgd-dev#603
WalkthroughThe pull request simplifies the logic in the Changes
Sequence Diagram(s)sequenceDiagram
participant Client
participant Conn
Client->>Conn: Send empty confirmable message (CoAP ping)
Conn-->>Client: Respond with Reset (using incoming message ID)
Assessment against linked issues
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🧰 Additional context used🪛 golangci-lint (1.64.8)udp/client/conn.go651-651: File is not properly formatted (gofumpt) 🔇 Additional comments (1)
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
As per RFC 7252, the CoAP ping (empty, confirmable message) must be responded to with a reset message.
Resolves #603
Summary by CodeRabbit