search

quicwg / multipath

In-progress version of draft-ietf-quic-multipath
Other
49 stars 17 forks source link

Abandon Frame needs Error Code definition #414

Open gloinul opened 1 month ago

gloinul commented 1 month ago

Section 7.2: Should Error Code reference the number space defined by transport or the IANA Registry?

Yanmei-Liu commented 1 month ago

Actually I find that the current draft lack of the definition for path abandon close error code. The error code registered in IANA Registry is used for Connection Close Frame. We definitely need to add this part.

huitema commented 1 month ago

Do we really want to replicate the structure of connection close, with 2 frame types, one "abandon by application" and the other "abandon by transport"? Or do we want to follow the example of "Stream Reset" and "Stop Sending", which just carry an application defined code?

I am for "application defined", because I think there are only two cases in which the transport originates an Abandon packet "by itself": abandon on timer, and abandon in response to an abandon by the peer. Using error code=0 for these two cases seems like a fine simplification.