26/08/26 Bi-Weeky libp2p Spec Meeting

[johannamoran]

Attendees

@seetadev
@johannamoran

Spec Lifecycle Stages

1. RFC [piloting]
2. Working Draft [POC in implement + Spec PR]
3. Candidate recommendation [ >2 implementations with interop recommended]
4. Recommendation [> 3 implementations and interop completed with applicable]

Agenda

Two new PRs discuss on previous Bi-Weekly Spec call. : Encrypted Client Hello (ECH) and topic extensions for QUIC announced. See directly below. Number 1 and 2 below.

---

NEW PRs requesting review and feedback

#735 —[ gossipsub: downscore peers on protocol violations](https://github.com/libp2p/specs/pull/735)

---

Existing PRs updates

1. 1. [TLS Handshake to enable support for RFC 9849: TLS Encrypted Client Hello}]

Relevant Links
#730

UPDATE SINCE 12/08

• Inviting maintainer implementations to review and experiment with QUIC and ECH.

2. [Topic Streams Extension addition in Gossipsub: moves topic scoped application messages to separate long-lived streams] [link]

Relevant Links
libp2p/test-plans#860

UPDATE SINCE 12/08
This PR is being handled as part of the broader gossip sub work, which also includes the memory leak fixes.

Next Steps
There's a strategic plan to coordinate the gossip sub interop work (PR 729) with the memory leak PR (705) to push both toward candidate recommendation status together once the interop piece is completed

3. gossipsub: add SPREAD extension spec

[Spec PR] #726

UPDATE SINCE 12/08 and Next Steps Spec meeting

• @gmelodie has shared substantial feedback on this PR and awaiting review.

4. Object Cache [link]

Background
This is a Waggle PR opened by rust maintainer.

UPDATE SINCE 12/08

• Discussion with nim-libp2p maintainer at yesterday libp2p monthly maintainer call requesting feedback
• A new addition was made today, where they are trying to work on this from a flood sub angle.

Next Steps

---

Spec PRs ready to merge

1. WebRTC Direct V2 [Now at candidate recommendation]

Relevant Links

• [Summary] by lidel on WebRTC-Direct + Chrome changes (specs#672 comment at WebRTC-Direct: Chrome may be removing ICE credential munging #672 (comment) )
• [Spec PR Link] docs: webrtc-direct-v2 #715
• [Issue Link] WebRTC-Direct transport at risk due to Chrome changes (ICE credential munging): alignment and next steps go-libp2p#3499
• [js-libp2p PR Link] feat: webrtc-direct-v2 js-libp2p#3480
• [py-libp2p PR Link] feat(webrtc): add WebRTC transport scaffolding (spec compliance + tests) py-libp2p#1309 (comment)
• [go-libp2p Reference Link] feat(webrtc): stable /certhash across restarts go-libp2p#3512

UPDATE SINCE 29/07 Spec meeting

• WebRTC Direct V2 was implemented and available for general use in new go-libp2p go-libp2p (v0.49.0) and py-libp2p (py-libp2p 0.7.0) releases.

Next Steps

• Waiting on js-libp2p @dozyio to implement minor modifications and add it to the Spec.
• @lidel completed WebRTC Direct V2 Transport Interop testing between go-libp2p and js-libp2p sucessfully.
• Spec PR almost ready for merge and therefore moving towards Spec Lifecycle Stage 4: Recommendation.

2. Add signedPeerRecord and discussion of message sizes to identify #709

AOB