From 2330c47a35d1fb317fb5bd9b79315d9b55122770 Mon Sep 17 00:00:00 2001 From: blu3beri Date: Thu, 19 May 2022 20:04:09 +0200 Subject: [PATCH] docs(0699): mention of pickup v2 Signed-off-by: blu3beri --- features/0699-push-notifications-apns/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/features/0699-push-notifications-apns/README.md b/features/0699-push-notifications-apns/README.md index 5976ce2c0..ce9172380 100644 --- a/features/0699-push-notifications-apns/README.md +++ b/features/0699-push-notifications-apns/README.md @@ -119,6 +119,7 @@ When an agent wants to send a push notification to another agent, the payload of { "@type": "https://didcomm.org/push-notifications-apns", "message_tag": "", + "message_id": "", ... } ``` @@ -127,6 +128,7 @@ Description of the fields: - `@type` -- Indicator of what kind of notification it is. (This could help the notification-receiver with parsing if a notification comes from another agent, for example) - `message_tag` -- Optional field to connect the push notification to a DIDcomm message. As defined in [0334: jwe-envelope](https://github.com/hyperledger/aries-rfcs/tree/main/features/0334-jwe-envelope) or [0019: encryption-envelope](https://github.com/hyperledger/aries-rfcs/tree/main/features/0019-encryption-envelope). +- `message_id` -- Optional field to pickup the message from the mediator that the notification was linked to. As defined in [0685: Pickup Protocol 2.0](https://github.com/hyperledger/aries-rfcs/blob/main/features/0685-pickup-v2/README.md). ## Drawbacks