draft-ietf-dnsext-mdns-31.txt   draft-ietf-dnsext-mdns-32.txt 
DNSEXT Working Group Levon Esibov DNSEXT Working Group Levon Esibov
INTERNET-DRAFT Bernard Aboba INTERNET-DRAFT Bernard Aboba
Category: Standards Track Dave Thaler Category: Standards Track Dave Thaler
<draft-ietf-dnsext-mdns-31.txt> Microsoft <draft-ietf-dnsext-mdns-32.txt> Microsoft
24 June 2004 25 June 2004
Linklocal Multicast Name Resolution (LLMNR) Linklocal Multicast Name Resolution (LLMNR)
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed, patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with and any of which I become aware will be disclosed, in accordance with
RFC 3667. RFC 3667.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
skipping to change at page 4, line 41 skipping to change at page 4, line 41
A host that listens to LLMNR queries, and responds to those for A host that listens to LLMNR queries, and responds to those for
which it is authoritative. which it is authoritative.
Sender Sender
A host that sends an LLMNR query. A host that sends an LLMNR query.
2. Name resolution using LLMNR 2. Name resolution using LLMNR
LLMNR is a peer-to-peer name resolution protocol that is not intended LLMNR is a peer-to-peer name resolution protocol that is not intended
as a replacement for DNS. LLMNR queries are sent to and received on as a replacement for DNS. LLMNR queries are sent to and received on
port TBD. IPv4 administratively scoped multicast usage is specified port 5355. IPv4 administratively scoped multicast usage is specified
in "Administratively Scoped IP Multicast" [RFC2365]. The IPv4 link- in "Administratively Scoped IP Multicast" [RFC2365]. The IPv4 link-
scope multicast address a given responder listens to, and to which a scope multicast address a given responder listens to, and to which a
sender sends queries, is 224.0.0.252. The IPv6 link-scope multicast sender sends queries, is 224.0.0.252. The IPv6 link-scope multicast
address a given responder listens to, and to which a sender sends all address a given responder listens to, and to which a sender sends all
queries, is FF02:0:0:0:0:0:1:3. queries, is FF02:0:0:0:0:0:1:3.
Typically a host is configured as both an LLMNR sender and a Typically a host is configured as both an LLMNR sender and a
responder. A host MAY be configured as a sender, but not a responder. A host MAY be configured as a sender, but not a
responder. However, a host configured as a responder MUST act as a responder. However, a host configured as a responder MUST act as a
sender to verify the uniqueness of names as described in Section 4. sender to verify the uniqueness of names as described in Section 4.
skipping to change at page 9, line 32 skipping to change at page 9, line 32
6.0.5.0.4.0.E.F.F.F.3.0.2.0.1.0.0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa 6.0.5.0.4.0.E.F.F.F.3.0.2.0.1.0.0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa
IN PTR host1. IN PTR host1.
IN PTR host1.example.com IN PTR host1.example.com
An LLMNR responder might be further manually configured with the name An LLMNR responder might be further manually configured with the name
of a local mail server with an MX RR included in the "host1." and of a local mail server with an MX RR included in the "host1." and
"host1.example.com." records. "host1.example.com." records.
In responding to queries: In responding to queries:
[a] Responders MUST listen on UDP port TBD on the link-scope multicast [a] Responders MUST listen on UDP port 5355 on the link-scope multicast
address(es) defined in Section 2, and on UDP and TCP port TBD on address(es) defined in Section 2, and on UDP and TCP port 5355 on
the unicast address(es) that could be set as the source address(es) the unicast address(es) that could be set as the source address(es)
when the responder responds to the LLMNR query. when the responder responds to the LLMNR query.
[b] Responders MUST direct responses to the port from which the query [b] Responders MUST direct responses to the port from which the query
was sent. When queries are received via TCP this is an inherent was sent. When queries are received via TCP this is an inherent
part of the transport protocol. For queries received by UDP the part of the transport protocol. For queries received by UDP the
responder MUST take note of the source port and use that as the responder MUST take note of the source port and use that as the
destination port in the response. Responses SHOULD always be sent destination port in the response. Responses SHOULD always be sent
from the port to which they were directed. from the port to which they were directed.
skipping to change at page 22, line 35 skipping to change at page 22, line 35
authenticate LLMNR responses. In a small network without a authenticate LLMNR responses. In a small network without a
certificate authority, this can be most easily accomplished through certificate authority, this can be most easily accomplished through
configuration of a group pre-shared key for trusted hosts. configuration of a group pre-shared key for trusted hosts.
6. IANA Considerations 6. IANA Considerations
This specification creates one new name space: the reserved bits in This specification creates one new name space: the reserved bits in
the LLMNR header. These are allocated by IETF Consensus, in the LLMNR header. These are allocated by IETF Consensus, in
accordance with BCP 26 [RFC2434]. accordance with BCP 26 [RFC2434].
LLMNR requires allocation of a port TBD for both TCP and UDP. LLMNR requires allocation of port 5355 for both TCP and UDP.
Assignment of the same port for both transports is requested.
LLMNR requires allocation of link-scope multicast IPv4 address LLMNR requires allocation of link-scope multicast IPv4 address
224.0.0.252. LLMNR also requires allocation of link-scope multicast 224.0.0.252, as well as link-scope multicast IPv6 address
IPv6 address FF02:0:0:0:0:0:1:3. FF02:0:0:0:0:0:1:3.
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC1035] Mockapetris, P., "Domain Names - Implementation and [RFC1035] Mockapetris, P., "Domain Names - Implementation and
Specification", RFC 1035, November 1987. Specification", RFC 1035, November 1987.
[RFC1321] Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321, [RFC1321] Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321,
April 1992. April 1992.
skipping to change at page 26, line 39 skipping to change at page 26, line 39
Open Issues Open Issues
Open issues with this specification are tracked on the following web Open issues with this specification are tracked on the following web
site: site:
http://www.drizzle.com/~aboba/DNSEXT/llmnrissues.html http://www.drizzle.com/~aboba/DNSEXT/llmnrissues.html
Expiration Date Expiration Date
This memo is filed as <draft-ietf-dnsext-mdns-31.txt>, and expires This memo is filed as <draft-ietf-dnsext-mdns-32.txt>, and expires
November 22, 2004. December 22, 2004.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/