luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

Add note about RPC multiplexing and TLS content type mutual exc… (#6698)

This commit is contained in:
Matt Keeler 2019-10-30 09:24:30 -04:00 committed by GitHub
parent c2d9041c0f
commit ae57e736d2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
agent/pool/conn.go
View File

@ -17,4 +17,14 @@ const (
// that is supported and it might be the only one there
// ever is.
RPCTLSInsecure = 7
// NOTE: Currently we use values between 0 and 7 for the different
// "protocols" that we may ride over our "rpc" port. We had an idea of
// using TLS + ALPN for negotiating the protocol instead of our own
// bytes as it could provide other benefits. Currently our 0-7 values
// are mutually exclusive with any valid first byte of a TLS header
// The first TLS header byte will content a TLS content type and the
// values 0-19 are all explicitly unassigned and marked as
// requiring coordination. RFC 7983 does the marking and goes into
// some details about multiplexing connections and identifying TLS.
)