Promoting select RFCs to stable & adapting updated COSS / template

[jimstir]

Reference: vacp2p/rfc#528
Author: kaiserd

This milestone issue tracks the promotion of select RFCs to the stable status,
as well as their adaption to the updated 1/COSS and RFC template.

Blockers

For now, this issue is blocked, waiting for the store flag implementation to be in release versions of at least two Waku implementation, as well as some in-the-wild testing thereafter.
However, many of prerequisite tasks described in this issue can already be started and merged to update draft versions of the respective RFCs. Only the actual promotions to stable are blocked.

• store flag support for for 14/WAKU2-MESSAGE in nwaku release version
• store flag support for 14/WAKU2-MESSAGE in the release version of one further Waku implementation
• wait until store flag support has been successful for some time in the wild

Background

The protocols specified in the following RFCs are ready for the stable status

• 10/WAKU2
• 13/WAKU2-STORE
• 14/WAKU2-MESSAGE
• 15/WAKU-BRIDGE

This milestone issue tracks the tasks necessary for promoting these RFCs to stable.
These tasks comprise

• thorough proofreading for ambiguity or lack of clarity, as well as the respective editing
• adding a category as specified in the updated 1/COSS
• adding tags as specified in the updated 1/COSS
• adding/ordering sections as proposed in our RFC template
  • Theory / Semantics (can be named differently if appropriate)
  • Wireformat / Syntax (can be named differently if appropriate)
  • Security Considerations

In addition to these tasks, 14/WAKU2-MESSAGE should be augmented by a store flag indicating whether a message should be stored or not. As all other RFCs listed above depend on message, this should be done first.

• #532
• #551

Further 21/WAKU2-FAULT-TOLERANT-STORE's wire specification should be merged into 13/WAKU2-STORE
so that RFC 13 reflects what is actually being used. This is important for promoting RFC 13 to stable.

• #552

Promoting 10/WAKU2 to stable requires factoring out parts that depend on non-stable RFCs.
These parts will be covered in a new RFC.

Action Items / Issues

• add ephemeral flag to 14/WAKU2-MESSAGE
• #552
• #551
• RFC 15: promote to stable & update to new structure
• RFC 10: promote to stable & update to new structure
  • promotion to stable includes factoring out parts that depend on non-stable RFCs
• new RFC ??/WAKU2-unstable: covers parts of original RFC 10 that depended on non-stable RFCs