Note regarding the new-api-needs-documentation label:

This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, to please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change.

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

There are also places in the loopback server and h/3 tests where "h3" is used and should be replaced as well.

Should Http3Options.Alpn (and relevant references) now be SslApplicationProtocol.Http3.ToString() calls?
It won't actually allocate a new string as that's handled inside the ToString but it does add a reference equality check to each instantiation..

There are also places in the loopback server and h/3 tests where "h3" is used and should be replaced as well.

Should Http3Options.Alpn (and relevant references) now be SslApplicationProtocol.Http3.ToString() calls?
It won't actually allocate a new string as that's handled inside the ToString but it does add a reference equality check call to each instantiation..

Since it's only in tests, it doesn't matter that much. You could also change the type from string to SslApplicationProtocol but I'm not sure how much will that help.