<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hello.</p>
<p>We'd like dnstap to represent the new-ish standardized
transports. In our use case it will be sufficient to trivially
extend the corresponding enum, so we suggest to do that step now
and we can think of additional related extensions later. Any
comments?</p>
<p>Concrete example with two added lines:<br>
</p>
<pre>// SocketProtocol: the transport protocol of a socket. This specifies how to
// interpret "transport port" fields.
enum SocketProtocol {
UDP = 1; // User Datagram Protocol (RFC 768)
TCP = 2; // Transmission Control Protocol (RFC 793)
DOT = 3; // DNS over TLS (RFC 7858, only TCP-based)
DOH = 4; // DNS over HTTP(S) (RFC 8484, any HTTP version)
}
</pre>
<p><a class="moz-txt-link-freetext" href="https://github.com/dnstap/dnstap.pb/issues/8">https://github.com/dnstap/dnstap.pb/issues/8</a></p>
<p>--Vladimir<br>
</p>
</body>
</html>