Draft milestone: Waku Capability Discovery/Push

[kaiserd]

This milestone issue tracks the specification and implementation of identify and identify/push
as simple Waku v2 capability discovery and capability push, respectively.

Note

For now, we only cover the frist issue of this milestone, which specifies identify and identify/push as libp2p protocols that may directly be used by Waku v2. The reason is that these two protocols are anyway used by the libp2p connection establishment layer Waku v2 is based on.
The rest of the tasks, namely introducing new Vac specific protocols with better anonymity properties, will be addressed in the future.

Issues

• update(RFC10): add identify protocols to libp2p protocol list rfc#527
• New RFC: 39/WAKU2-CAPABILITY-DISCOVERY rfc#520
• New RFC: 40/WAKU2-CAPABILITY-PUSH rfc#521
• Implement Waku capability discovery
• Implement Waku capability push

[oskarth]

@kaiserd

1. Is it accurate that this is in icebox? I.e. not planned to be worked on for long period

• if so makes sense to unassign yourself

2. Is this one of the most immediate milestones for the Discovery track after PEX?

[kaiserd]

@oskarth

1. Is it accurate that this is in icebox? I.e. not planned to be worked on for long period

yes. Until we decide to move on from libp2p identify.
Because libp2p uses identify anyways, and we don't need any functionality past that for now, we decided to use stock identify for now.

• if so makes sense to unassign yourself

done

2. Is this one of the most immediate milestones for the Discovery track after PEX?

There is no immediate milestone after PEX on the Discovery track for now. They are all "future work".
I moved this milestone into "future items" on the roadmap.
(I'll work on anonymity after PEX, as anonymity has more immediate impact.)

[oskarth]

The is no immediate milestone after PEX on the Discovery track for now. They are all "future work".

I'll remove the milestone label then too, that way it is more clear what "now" and "next" looks like for each track.

[kaiserd]

Ownership of this issue has been moved to Waku: waku-org/pm#101