From d8ecf4545f5d550713b77decceded0606d9fe6e4 Mon Sep 17 00:00:00 2001 From: Torsten Grote Date: Wed, 17 Feb 2016 17:48:12 +0000 Subject: [PATCH] add device and transport properties to the response --- IntroductionClient.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/IntroductionClient.md b/IntroductionClient.md index 8def8cb..4be3965 100644 --- a/IntroductionClient.md +++ b/IntroductionClient.md @@ -23,6 +23,12 @@ The introduction protocol uses three message types. It should be noted that all * (bool) Whether the introduction is accepted or not. The following list items are **only** included if the introduction was accepted * (int) The timestamp of the current time * (raw) An ephemeral public key which will be used to derive a shared secret (see [BPQ](BQP)) + * (raw) the `DeviceId` of the device used to respond + * (string) the name of one `TransportId` + * (dictionary) the `TransportProperties` of the transport with the previous ID + * (string) the name of another one `TransportId` (optional) + * (dictionary) the `TransportProperties` of the transport with the previous ID (optional) + * ... **3: ACK** - This should be send by a contact that previously responded to an invitation and has received the response of the other contact. If the facilitator receives this, she should forward it to the other introducee with the correct introduction ID. The content is a BDF list with two elements: * (int) The type of the message, here **3**