Michiel De Backker

@rob-deutsch I agree with your thoughts above. It would be interesting to create a super strict, minimal version of SDP. Some thoughts: - I think we should probably add limits...

@SkyBeastMC It seems the `dialMe` protocol currently only allows for exchanging a peer id and multi addresses: ```protobuf message DialMe { message Peer { required bytes id = 1; //...

Maybe we can add it to the spec discussion.

The [go-webrtc-aside-transport](https://github.com/Jorropo/go-webrtc-aside-transport) implements signaling over another transport.

@aarshkshah1992 Are there plans to 'abstract' the signaling? AKA have the signaling path be injected into transports that require it. That would allow protocols that need signaling to be developed...

The [go-webrtc-aside-transport](https://github.com/Jorropo/go-webrtc-aside-transport) uses DTLS for security.

That does seems strange to me. According to https://pkg.go.dev/github.com/libp2p/[email protected]/mux#MuxedStream: > Close closes the stream. ... Future reads will fail. @raulk could you give us some clarity on this?

Ok, does that mean the go-libp2p-testing suite is violating this behavior or are we overlooking something? It seems to first close the steam and then try to read it using...

Yea, makes sense. This means: 1. We need a PR on go-libp2p-testing to correct the closing behavior to: CloseWrite, ReadAll, CloseRead (or Close). 2. We'll need to refine this transport...

Actually, point 2 in my previous comment may not apply. This transport is currently not meant to do stream muxing by itself. Is is supposed to use an external muxer...