Lior Okman

Soon Envoy Gateway will support `BackendTLSPolicy` ( #2247 ), at which point the protocol between the Envoy Proxy and the backend will most likely be negotiated with ALPN. At that...

The `useClientProtocol` added in #2433 solves this issue.

> But EnvoyPatchPolicy can't solve all problems. +1 I suggest adding some more hook functions to the interface to support the additional listener types: TCP, and UDP listeners as well...

Building on the discussion above and in the community meeting, the latest proposal becomes this: Extension server developers that want to receive context on calls to the `HTTPListener` modification hook...

> -1 on Envoy Gateway managing status of the Extension Resource, it has no way to knowing what good or bad or partial states looks like. While EG can't know...

> my only open question is what do the targets mean behind the scenes? For now, I think we should only target the Listener hook, which means exclusively `Gateway` CRD...

> we've learnt the hard way in EG of not dealing with target not found cases, and simply ignoring them, more in #2520 In this case, then how about EG...

> The decision that needs to be made here is two fold > > 1. What does targeting multiple resources look like - is it similar to the upstream recommendation...

> reg 1. - requires a little more brainstorming - should we start off with targetRefs or also support label based targets , this > affects the top level API...

Yes, I think that a target selector can definitely be a part of the `PolicyReferences` structure.