envoyproxy/envoy
Ver no GitHubnetwork: address interface should pair port:proto
Open
#17.429 aberto em 20 de jul. de 2021
area/listenerhelp wantedtech debt
Métricas do repositório
- Stars
- (27.997 stars)
- Métricas de merge de PR
- (Mesclagem média 8d) (378 fundiu PRs em 30d)
Description
As per the discussion here: https://github.com/envoyproxy/envoy/pull/17414
In a perfect world our Address interface should include proto with port, as the operating system treats TCP:1234 differently from UDP:1234. Unfortunately, this will have very large implications on the overall code structure. There are a few things we might consider here:
- Remove port from the primary Address interface, as certain use cases do not actually care about port and proto. For example DNS, IP tagging, etc.
- Introduce a AddressAndPort interface which includes an address as well as a port/proto pair. Then, any port must have an associated proto with it as well.
Either way this needs some thinking and prototyping.