RFC 4795: Link-local Multicast Name Resolution (LLMNR)
In plain English — editorial summary, not part of the RFC
The goal of Link-Local Multicast Name Resolution (LLMNR) is to enable name resolution in scenarios in which conventional DNS name resolution is not possible. LLMNR supports all current and future DNS formats, types, and classes, while operating on a separate port from DNS, and with a distinct resolver cache. Since LLMNR only operates on the local link, it cannot be considered a substitute for DNS. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4795
- Published
- January 2007
- Authors
- B. Aboba; D. Thaler; L. Esibov
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 31
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4830Problem Statement for Network-Based Localized Mobility Management (NETLMM)Current
April 2007
- RFC 4831Goals for Network-Based Localized Mobility Management (NETLMM)Current
April 2007
- RFC 4832Security Threats to Network-Based Localized Mobility Management (NETLMM)Current
April 2007
- RFC 4833Timezone Options for DHCPCurrent
April 2007
- RFC 4755IP over InfiniBand: Connected ModeCurrent
December 2006
- RFC 4857Mobile IPv4 Regional RegistrationCurrent
June 2007
- RFC 4861Neighbor Discovery for IP version 6 (IPv6)Updated
September 2007
- RFC 4862IPv6 Stateless Address AutoconfigurationUpdated
September 2007
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?