Skip to content

docs: add ALPN section to TLS and link to inlined muxer negotiation #662

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

achingbrain
Copy link
Member

Adds note about which ALPN protocol to use and links to spec for inlining muxer negotiation.

Avoids things like libp2p/jvm-libp2p#404

Fixes #607
Fixes #496

Adds note about which ALPN protocol to use and links to spec for
inlining muxer negotiation.

Fixes #607
Fixes #496
@@ -122,6 +124,16 @@ How the public key is encoded into the `Data` bytes depends on the Key Type.
- `Secp256k1`: Only the compressed form of the public key. 33 bytes.
- The rest of the keys are encoded as a [SubjectPublicKeyInfo structure](https://www.rfc-editor.org/rfc/rfc5280.html#section-4.1) in PKIX, ASN.1 DER form.

## ALPN

"libp2p" is used as the application protocol for [ALPN](https://en.wikipedia.org/wiki/Application-Layer_Protocol_Negotiation).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Technically, you'd have to register this value with IANA ;)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've created #663 to make sure this doesn't get lost

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Triage
Development

Successfully merging this pull request may close these issues.

TLS spec doesn't mention ALPN libp2p used by implementations tls: specify ALPN
3 participants