Lines Matching +full:wire +full:- +full:or
6 // Written in 2013-2014 by Farsight Security, Inc.
20 // "Dnstap": this is the top-level dnstap type, which is a "union" type that
23 // See: https://developers.google.com/protocol-buffers/docs/techniques#union
38 // This field can be used for adding an arbitrary byte-string annotation to
39 // the payload. No encoding or interpretation is applied or enforced.
74 // Match: what aspect of the message or message exchange
101 // the Reponse Policy Zone in wire format.
115 // Message: a wire-format (RFC 1035 section 4) DNS message and associated
124 // +---------+ +----------+ +--------+
126 // | Stub |-SQ--------CQ->| Recursive|-RQ----AQ->| Auth. |
128 // | |<-SR--------CR-| |<-RR----AR-| Server |
129 // +---------+ response | | response | |
130 // +----------+ +--------+
134 // arrow on the diagram above has been marked with a two-letter Type
180 // perspective of the DNS server. The client may be a stub resolver or
181 // forwarder or some other type of software which typically sets the RD
183 // may be a simple forwarding proxy or it may be a full recursive
250 // This is a 16-bit UDP or TCP port number, depending on SocketProtocol.
254 // This is a 16-bit UDP or TCP port number, depending on SocketProtocol.
257 // The time at which the DNS query message was sent or received, depending
258 // on whether this is an AUTH_QUERY, RESOLVER_QUERY, or CLIENT_QUERY.
262 // The time at which the DNS query message was sent or received.
266 // The initiator's original wire-format DNS query message, verbatim.
269 // The "zone" or "bailiwick" pertaining to the DNS query message.
270 // This is a wire-format DNS domain name.
273 // The time at which the DNS response message was sent or received,
274 // depending on whether this is an AUTH_RESPONSE, RESOLVER_RESPONSE, or
279 // The time at which the DNS response message was sent or received.
283 // The responder's original wire-format DNS response message, verbatim.