6/WAKU1: Remove confirmations-enabled from status-options

[Samyoul]

Background

Setting confirmations-enabled in status-options data packets doesn't seem to have any functional role. Currently the confirmations-enabled setting communicates to the peer that a host will send ConfirmationRequests.

See here for details on previous discussion with @cammellos

Questions

• Why does the node need to know that the peer will send ConfirmationRequests?
• Should the host refuse ConfirmationRequests if the peer doesn't set the confirmations-enabled?

Proposal

• Decide if the confirmations-enabled in status-options data packets serves a useful role
• Decide if deprecating confirmations-enabled is desirable
• Decide if expanding the utility of confirmations to communicate more useful info is desirable
• Implement the agreed changes, if any, in the specs

[oskarth]

6/WAKU-1 spec not under active development, not a priority unless there is a strong need (PRs welcome in that case).