Skip to content

Commit bd94a9a

Browse files
authored
Introduce option to link local and OCM addresses (#283)
1 parent 5a5abb1 commit bd94a9a

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

IETF-RFC.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -405,6 +405,15 @@ party is received.
405405
Both servers MAY also allowlist each other as a server with which at
406406
least one of their users wishes to interact.
407407

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

0 commit comments

Comments
 (0)