remove redundant requirements

This commit is contained in:
Jazz Turner-Baggs 2025-07-09 11:43:49 -07:00
parent 76c8f9e626
commit 655719fdbd
No known key found for this signature in database

View File

@ -37,7 +37,7 @@ A ConversationType MUST define how to generate conversation_ids
A ConversationType SHOULD define membership requirements and limitations.
A ConversationType SHOULD define privacy and security guarantees.
A ConversationType SHOULD maintain a deterministic decoding tree.
## ConversationType Identifiers
ConversationTypes are identified by the title of the specification. This allows developers to lookup the associated specification.
@ -60,9 +60,7 @@ Care should be taken to ensure that conversation_ids do not conflict.
To disambiguate between different logical layers, payload types sent by a Conversation are referred to as `Frames`.
Conversations are free to determine which frames are needed for their specific use cases.
ConversationTypes MUST define a section which defines all possible frames
ConversationTypes SHOULD maintain a deterministic decoding tree.
## Encryption
@ -78,15 +76,6 @@ When developing new ConversationTypes contributors should consider:
- Channel binding and the impacts on message security.
## Implementation Suggestions (optional)
An optional *implementation suggestions* section may provide suggestions on how to approach implementation details, and,
if available, point to existing implementations for reference.
## (Further Optional Sections)
## Security/Privacy Considerations
This approach puts heavy requirements on ConversationTypes to build their own cryptography without providing much guidance. Finding mechanisms that provide safety while maintaining the flexibility should be prioritized in follow up work.