Lines Matching +full:one +full:- +full:wire

6 // Written in 2013-2014 by Farsight Security, Inc.
20 // "Dnstap": this is the top-level dnstap type, which is a "union" type that
21 // contains other kinds of dnstap payloads, although currently only one type
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
48     // One of the following will be filled in.
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     //                              +----------+           +--------+
132     // Each arrow has two Type values each, one for each "end" of each arrow,
134     // arrow on the diagram above has been marked with a two-letter Type
230     // One of the Type values described above.
233     // One of the SocketFamily values described above.
236     // One of the SocketProtocol values described above.
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.
266     // The initiator's original wire-format DNS query message, verbatim.
270     // This is a wire-format DNS domain name.
283     // The responder's original wire-format DNS response message, verbatim.