Skip to content

Commit 15bf06e

Browse files
committed
Introduce option to link local and OCM addresses
1 parent ceb6096 commit 15bf06e

1 file changed

Lines changed: 10 additions & 1 deletion

File tree

IETF-RFC.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -403,13 +403,22 @@ party is received.
403403
Both servers MAY also allowlist each other as a server with which at
404404
least one of their users wishes to interact.
405405

406+
In addition, if the identity provider of either server supports the
407+
registration of external users, it may happen that the just received
408+
email contact from the other party matches an external user already
409+
known in the local identity provider, and therefore already present
410+
in the address book. In such a case, implementers MAY support linking
411+
of the two identities belonging to that same user, so that when a Share
412+
Creation gesture is made to that recipient, both a regular share and an
413+
OCM Share Creation Notification are issued.
414+
406415
Note that Invites act symmetrically, so once contact has been
407416
established, both the Invite Sender and the Invite Receiver MAY take on
408417
either the Sending Party or the Receiving Party role in subsequent
409418
Share Creation events.
410419

411420
Both parties MAY delete the other party from their address book at any
412-
time without notifying them.
421+
time without notifying them.
413422

414423
### Security Advantages
415424

0 commit comments

Comments
 (0)