175
edits
Difference between revisions of "Sprints/2020 March Duesseldorf"
Jump to navigation
Jump to search
Sprints/2020 March Duesseldorf (view source)
Revision as of 16:31, 4 March 2020
, 16:31, 4 March 2020no edit summary
| Line 3: | Line 3: | ||
== Goal == | == Goal == | ||
This Sprint is focussed on creating the next iteration of the OMEMO XEP. | This Sprint is focussed on creating the next iteration of the OMEMO XEP. | ||
=== Detailed TODO === | |||
* 12-byte IVs | |||
* Restructure PEP usage to use '''one''' device node with multiple items (One item for each device); Maintain index node? (so we have something to +notify on) | |||
* Describe usage of OMEMO in MUCs (MUST be non-anonymous, RECOMMENDED to be members-only, …) | |||
* PEP access model SHOULD (or RECOMMENDED) to be open (explain security consequences of that.) | |||
* Describe in more detail how devices get activated inactivated (message from a device, or PEP event, what ever comes last) | |||
* Describe optional ''server please give me one pre-key+idenity key and then remove the pre key'' protocol | |||
* Shorter element names for elements that are often repeated | |||
* Complete session by sending key transport message upon receiving a prekey message. | |||
=== Responsibilities === | |||
Who does what. TBD | |||
=== Process === | |||
Since multiple people are going to work on multiple parts of the XEP simultaneously we probably need a git and commit early and often. Other and better ideas welcome. | |||
== Dates and Times == | == Dates and Times == | ||