Had a quick discussion with @raulk, he thought I should mention it here. I've been working on a standard for identifying protocols in a multiaddress like way. The spec can be found here.
There are some issues that still need to be addressed, like being able to specify the transcoder so values can be more than just integers as they are right now. I decided to already open this issue however so it can be discussed transparently on what is still required and if this will be effective for libp2p. It may make sense to standerdize this as part of multiformats and then have libp2p implement its own protocol table.
Had a quick discussion with @raulk, he thought I should mention it here. I've been working on a standard for identifying protocols in a multiaddress like way. The spec can be found here.
There are some issues that still need to be addressed, like being able to specify the transcoder so values can be more than just integers as they are right now. I decided to already open this issue however so it can be discussed transparently on what is still required and if this will be effective for libp2p. It may make sense to standerdize this as part of multiformats and then have libp2p implement its own protocol table.