QUIC API mega-issue

[geoffkizer]

This is a mega-issue for tracking all issues related to QUIC API definition and semantics.

• Should QuicStream require Flush? QuicStream: Consider requiring Flush to guarantee data is sent #44782
• Define QuicConnection stream limit handling: [QUIC] Decide how to handle QUIC stream limits #32079
• Shutdown/Abort/Dispose handling for QuicStream: [QUIC] Design of Shutdown for QuicStreams in System.Net.Quic #756, [QUIC] Finalize QUIC stream abort model #32075
• Dispose behavior for QuicConnection and QuicListener: [QUIC] Finalize QUIC dispose model #32142
• Issues with QuicListener.Start and QuicListener.LocalEndPoint: [QUIC] QuicListener.ListenEndPoint returns a port of 0 if Start() hasn't been called #2262
• QuicConnection.RemoteEndPoint should be IPEndPoint: QuicConnection.RemoteEndPoint should be IPEndPoint, not EndPoint #43000

If I've missed anything, or new issues are added, please comment.

If you have thoughts on particular API issues, please add them to the linked issues above.

cc @scalablecory @stephentoub @jkotalik @Tratcher @halter73 @davidfowl @rzikm

[ghost]

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

Issue Details

Description:	This is a mega-issue for tracking all issues related to QUIC API definition and semantics. Should QuicStream require Flush? QuicStream: Consider requiring Flush to guarantee data is sent #44782 Define QuicConnection stream limit handling: [QUIC] Decide how to handle QUIC stream limits #32079 Shutdown/Abort/Dispose handling for QuicStream: [QUIC] Design of Shutdown for QuicStreams in System.Net.Quic #756, [QUIC] Finalize QUIC stream abort model #32075 Dispose behavior for QuicConnection and QuicListener: [QUIC] Finalize QUIC dispose model #32142 Issues with QuicListener.Start and QuicListener.LocalEndPoint: [QUIC] QuicListener.ListenEndPoint returns a port of 0 if Start() hasn't been called #2262 QuicConnection.RemoteEndPoint should be IPEndPoint: QuicConnection.RemoteEndPoint should be IPEndPoint, not EndPoint #43000 If I've missed anything, or new issues are added, please comment. If you have thoughts on particular API issues, please add them to the linked issues above. cc @scalablecory @stephentoub @jkotalik @Tratcher @halter73 @davidfowl @rzikm
Author:	geoffkizer
Assignees:	-
Labels:	area-System.Net.Quic
Milestone:	[object Object]

[wegylexy]

Please see wegylexy#1 for datagram support, thanks.

[wegylexy]

created #53533 for datagram API suggestion just now

[ManickaP]

Closing as this is covered by #69675 #68902 and #67560