migrations needed after updating go-libp2p v0.24.0 update

[marten-seemann]

Checklist

• My issue is specific & actionable.
• I am not suggesting a protocol enhancement.
• I have searched on the issue tracker for my issue.

Description

Updating to go-libp2p v0.24.0 will require a few changes / migrations on the kubo side. I'm creating this issue to keep track of these changes.

This issue is not actionable until v0.24.0 was released.

QUIC v1 codepoint

QUIC now uses a new code point to signal support for QUIC version 1 (RFC 9000). The existing code point now means signals support for QUIC draft-29. On the IPFS network, there are many nodes that support only draft-29. See multiformats/multiaddr#145 for more context.

Required kubo changes:

• create a migration that adds listen addresses for QUIC v1, i.e. adds a /ip{4,6}/<ip>/udp/<port>/quic-v1 address for every /ip{4,6}/<ip>/udp/<port>/quic address

WebTransport support

It's now possible to run QUIC and WebTransport on the same port (see libp2p/go-libp2p#1759).

Required kubo changes:

• create a migration that adds a WebTransport listen address, i.e. adds a /ip{4,6}/<ip>/udp/<port>/quic-v1/webtransport address for every /ip{4,6}/<ip>/udp/<port>/quic-v1 address. Note that WebTransport doesn't support QUIC draft-29

[BigLep]

@Jorropo : how is the migration work going for you?

[BigLep]

Migrations are happening in ipfs/fs-repo-migrations#162

[Jorropo]

@BigLep I implemented both of the required migrations in: ipfs/fs-repo-migrations#162
I'll have to fix and add tests.