While defining PassiveQUICEstablishment as acting as a QUIC server (i.e., waiting for a connection from a client), I'm wondering whether the endpoint's role (client or server) has an impact on BGP.
Before the connection is established, an endpoint can assume either role, depending on which node takes the active role in opening the QUIC connection. §5.3/rfc9000 (Operations on Connections) indicates that, except for actively opening a connection (vs. listening), either role has the same operational capabilities on session maintenance.
However, only clients can initiate a QUIC connection migration. BGP-related applications (VM mobility, maybe even graceful restart) may require either endpoint to initiate migration. There may be others.
-02 introduces a capability to indicate the role at the BGP level, which must match the QUIC connection. The specific applications (mobility, GR) still need some thought.
While defining PassiveQUICEstablishment as acting as a QUIC server (i.e., waiting for a connection from a client), I'm wondering whether the endpoint's role (client or server) has an impact on BGP.
Before the connection is established, an endpoint can assume either role, depending on which node takes the active role in opening the QUIC connection. §5.3/rfc9000 (Operations on Connections) indicates that, except for actively opening a connection (vs. listening), either role has the same operational capabilities on session maintenance.
However, only clients can initiate a QUIC connection migration. BGP-related applications (VM mobility, maybe even graceful restart) may require either endpoint to initiate migration. There may be others.