Skip to content

docs(ocm): define notification success responses #430

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

Open
MahdiBaghbani wants to merge 5 commits into from
Open

docs(ocm): define notification success responses #430

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
7c81d99
docs(ocm): define notification success responses
MahdiBaghbani Nov 10, 2026
f2cccd4
docs(ocm): qualify contact denial receipts
MahdiBaghbani Nov 10, 2026
dce958f
docs(ocm): drop contact receipt exception
MahdiBaghbani Nov 11, 2026
4c62940
docs(ocm): clarify notification responses
MahdiBaghbani Nov 12, 2026
7de5af5
docs(ocm): scope notification response handling
MahdiBaghbani Nov 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions IETF-OCM.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1449,6 +1449,13 @@ payload and identity bindings.
* A receiver MAY return HTTP 501 for a known, valid notification type
whose operation it does not implement.

## Response

A receiver that accepts a notification MUST respond with HTTP 201 and
no body. Senders SHOULD treat any 2xx response as confirmation of
receipt and MUST ignore its body. Receipt does not confirm completion
of the requested action.

## Share Acceptance and Updating

A notification MAY be sent by a recipient to let the provider know that
Expand Down
5 changes: 2 additions & 3 deletions spec.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -214,9 +214,8 @@ paths:
responses:
"201":
description: >
Receiver succesfully received the notification. The response body
MAY contain a JSON object with response data, depending on
the actual notification.
Notification accepted. The response has no body. Receipt does
not guarantee a state change or distributed completion.
"400":
description: >
Invalid notification envelope or malformed payload for a known
Expand Down
Loading