-
Notifications
You must be signed in to change notification settings - Fork 4.7k
/
quic_transport.proto
34 lines (25 loc) · 1.47 KB
/
quic_transport.proto
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
syntax = "proto3";
package envoy.extensions.transport_sockets.quic.v3;
import "envoy/extensions/transport_sockets/tls/v3/tls.proto";
import "google/protobuf/wrappers.proto";
import "udpa/annotations/status.proto";
import "validate/validate.proto";
option java_package = "io.envoyproxy.envoy.extensions.transport_sockets.quic.v3";
option java_outer_classname = "QuicTransportProto";
option java_multiple_files = true;
option go_package = "github.com/envoyproxy/go-control-plane/envoy/extensions/transport_sockets/quic/v3;quicv3";
option (udpa.annotations.file_status).package_version_status = ACTIVE;
// [#protodoc-title: quic transport]
// [#comment:#extension: envoy.transport_sockets.quic]
// Configuration for Downstream QUIC transport socket. This provides Google's implementation of Google QUIC and IETF QUIC to Envoy.
message QuicDownstreamTransport {
tls.v3.DownstreamTlsContext downstream_tls_context = 1
[(validate.rules).message = {required: true}];
// If false, QUIC will tell TLS to reject any early data and to stop issuing 0-RTT credentials with resumption session tickets. This will prevent clients from sending 0-RTT requests.
// Default to true.
google.protobuf.BoolValue enable_early_data = 2;
}
// Configuration for Upstream QUIC transport socket. This provides Google's implementation of Google QUIC and IETF QUIC to Envoy.
message QuicUpstreamTransport {
tls.v3.UpstreamTlsContext upstream_tls_context = 1 [(validate.rules).message = {required: true}];
}