Lines Matching refs:LLQ

36 TCP's standard three-way handshake makes the full four-packet LLQ setup
40 sent is formatted as described in the LLQ document, however there is
43 So when the server receives an LLQ (or a standard query), it looks to
76 All private LLQ operations are TSIG-enabled and sent over a secure
80 connection after initial LLQ setup and sending subsequent events and
91 processing of an LLQ refresh. Prior to these changes, dnsextd would
93 LLQ by comparing both the IP Address and port number of the request
100 When setting up a semi-private LLQ (where the request and initial answer
104 need to pass the UDP event port number in the LLQ setup request
111 2) Upon setup every LLQ must NAT map two ports. Upon tear down every LLQ
114 3) Every LLQ opens up two sockets (TCP and UDP), rather than just the
117 All of this just to avoid sending two bytes in the LLQ setup packet
119 additional UDP socket for every private LLQ, port mapping both the TCP
122 the LLQ setup packet to specify a different UDP port for change event
124 packets on a single UDP port, instead of a different one for each LLQ.
146 setting up an LLQ over TCP. This isn't a terrible problem right now,