Issues with ALPN section #286
Description
https://github.com/n0-computer/iroh.computer/blob/main/src/app/docs/concepts/protocol/page.mdx
- It does not seem correct to suffix ALPN with 's' and form a plural of it. There is one negotiation. The negotiation deals with many protocols (plural).
- There is an unfinished sentence: "Each protocol registerted The"
- The section should make it clear that there is no officially registered protocol id for iroh yet in the IANA registry. This is not a problem (yet) since iroh endpoints will probably run on their own port and do not share port 443 with an HTTP server.
- I do not think that ALPN is part of the quic spec. First it's a separate RFC. And second I believe that ALPN is rather part of TLS and preceds quic?
I finally watched a presentation on quic to understand what this ALPN thing is. Maybe add a sentence explaining ALPN? And a paragraph on quic?
e.g.
- quic is a successor of http2. It supports multiple independent data streams over the same connection.
- footnote: http2 also supports multiple streams. However a missing tcp packet in one stream would also halt all other streams due to the ordering property of tcp packets.
- quic allows to negotiate the application level protocol already in the initial TLS handshake and thus speeds up connection establishment. This is called application level protocol negotiation (ALPN). Protocols are identified with protocol ids registered with the IANA
- iroh protocol IDs are not yet registered with the IANA which is not a problem as long as iroh endpoints run on their own ports.