envoyproxy/envoy
Voir sur GitHubnetwork: address interface should pair port:proto
Open
#17 429 ouverte le 20 juil. 2021
area/listenerhelp wantedtech debt
Métriques du dépôt
- Stars
- (27 997 stars)
- Métriques de merge PR
- (Merge moyen 8j) (378 PRs mergées en 30 j)
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.