Skip to content

RFC 9175: implement Echo and Request-Tag with explicit peer interoperability tests #24

Open

Description

@maikebing

Implement the common standardized RFC 9175 extensions as a separate opt-in slice after the core UDP fixes (#20/#21/#22). Acceptance must include Echo freshness/challenge behavior, Request-Tag identity across Block1 transfer and retransmission, bounded state, malformed/repeated option handling, and interoperability with a pinned libcoap or go-coap peer. Keep token-processing obligations and secure-transport replay/context behavior explicit. Merely adding option constants does not complete the issue.

Activity

  1. maikebing commented on Nov 12, 2026

    @maikebing
    MemberAuthor

    A related existing Block1 concurrency boundary was encountered while testing PR #36. With two pending server-side Block1 requests to the same URI/source and no response yet, Matcher.ReceiveRequest reads ongoing.CurrentResponse.Type while CurrentResponse is null (Matcher.cs around line 243). The test failed with NullReferenceException before the lifecycle assertion. Using distinct URIs isolated the intended lifecycle test; this same-resource path was not fixed in PR #36.

    Please include this case in the #24 acceptance matrix: same peer/resource with concurrent or superseding bodies, distinct Request-Tag values when negotiated, retransmission of the same tag, and legacy untagged behavior. The library must define association/rejection behavior and avoid a null dereference. Request-Tag constants alone would not resolve that contract. This is an observed code-test failure, not an interoperability result.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions