RFC 8764: Apple's DNS Long-Lived Queries Protocol
In plain English — editorial summary, not part of the RFC
Apple's DNS Long-Lived Queries (LLQ) is a mechanism for extending the DNS protocol to support change notification, thus allowing clients to learn about changes to DNS data without polling the server. From 2005 onwards, LLQ was implemented in Apple products including Mac OS X, Bonjour for Windows, and AirPort wireless base stations. In 2020, the LLQ protocol was superseded by the IETF Standards Track RFC 8765, "DNS Push Notifications", which builds on experience gained with the LLQ protocol to create a superior replacement. The existing LLQ protocol deployed and used from 2005 to 2020 is documented here to give background regarding the operational experience that informed the development of DNS Push Notifications, and to help facilitate a smooth transition from LLQ to DNS Push Notifications.
Document record
- Document ID
- RFC8764
- Published
- June 2020
- Authors
- S. Cheshire; M. Krochmal
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8277Using BGP to Bind MPLS Labels to Address PrefixesCurrent
October 2017
- RFC 3134Terminology for ATM ABR BenchmarkingCurrent
June 2001
- RFC 3116Methodology for ATM BenchmarkingCurrent
June 2001
- RFC 2843Proxy-PARCurrent
May 2000
- RFC 2761Terminology for ATM BenchmarkingCurrent
February 2000
- RFC 2689Providing Integrated Services over Low-bitrate LinksCurrent
September 1999
- RFC 2682Performance Issues in VC-Merge Capable ATM LSRsCurrent
September 1999
- RFC 2383ST2+ over ATM Protocol Specification - UNI 3.1 VersionCurrent
August 1998
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?