What are we doing with `IConnectionEndPointFeature`

[BrennanConroy]

IConnectionEndPointFeature was added as part of bedrock in #10321.
But it is only implemented and exposed via DefaultConnectionContext which is only used by test projects in our repo.

We should figure out what to do with this feature.

[davidfowl]

We should implement it

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[davidfowl]

I'll do it in .NET 8 planning 😄

[hexawyz]

I have a usecase where I would like to filter requests based on the endpoint used (using an IEndpointFilter), and it seems the IConnectionEndPointFeature would be a useful tool for this if it was available. (Testing on latest preview in the context of HTTP2/NamedPipe requests: it does not seem to be available, although the relevant information is present in internal classes)

Can we expect this for .NET 8.0, or is it too late?

[BrennanConroy]

Let's try to add this to Kestrel, we already have LocalEndpoint and RemoteEndpoint as fields on the BaseConnectionContext, so seems like we just need to add the feature and expose it in the feature collection.