| @@ -8,25 +8,25 @@ work of the IETF Zero Configuration Netw | | | @@ -8,25 +8,25 @@ work of the IETF Zero Configuration Netw |
8 | | | 8 | |
9 | The Zeroconf Working Group has identified three requirements for Zero | | 9 | The Zeroconf Working Group has identified three requirements for Zero |
10 | Configuration Networking: | | 10 | Configuration Networking: |
11 | 1. An IP address (even when there is no DHCP server to assign one) | | 11 | 1. An IP address (even when there is no DHCP server to assign one) |
12 | 2. Name-to-address translation (even when there is no DNS server) | | 12 | 2. Name-to-address translation (even when there is no DNS server) |
13 | 3. Discovery of Services on the network (again, without infrastucture) | | 13 | 3. Discovery of Services on the network (again, without infrastucture) |
14 | | | 14 | |
15 | Requirement 1 is met by self-assigned link-local addresses, as | | 15 | Requirement 1 is met by self-assigned link-local addresses, as |
16 | described in "Dynamic Configuration of IPv4 Link-Local Addresses" | | 16 | described in "Dynamic Configuration of IPv4 Link-Local Addresses" |
17 | <http://files.zeroconf.org/draft-ietf-zeroconf-ipv4-linklocal.txt> | | 17 | <http://files.zeroconf.org/draft-ietf-zeroconf-ipv4-linklocal.txt> |
18 | | | 18 | |
19 | Requirement 2 is met by sending DNS-like queries via Multicast (mDNS). | | 19 | Requirement 2 is met by sending DNS-like queries via Multicast (mDNS). |
20 | | | 20 | |
21 | Requirement 3 is met by DNS Service Dicsovery (DNS-SD). | | 21 | Requirement 3 is met by DNS Service Discovery (DNS-SD). |
22 | | | 22 | |
23 | Self-assigned link-local address capability has been available since | | 23 | Self-assigned link-local address capability has been available since |
24 | 1998, when it first appeared in Windows '98 and in Mac OS 8.5. | | 24 | 1998, when it first appeared in Windows '98 and in Mac OS 8.5. |
25 | Implementations for other platforms also exist. | | 25 | Implementations for other platforms also exist. |
26 | | | 26 | |
27 | The mDNSResponder project allows us to meet requirements 2 and 3. | | 27 | The mDNSResponder project allows us to meet requirements 2 and 3. |
28 | It provides the ability for the user to identify hosts using names | | 28 | It provides the ability for the user to identify hosts using names |
29 | instead of dotted-decimal IP addresses, even if the user doesn't have a | | 29 | instead of dotted-decimal IP addresses, even if the user doesn't have a |
30 | conventional DNS server set up. It also provides the ability for the | | 30 | conventional DNS server set up. It also provides the ability for the |
31 | user to discover what services are being advertised on the network, | | 31 | user to discover what services are being advertised on the network, |
32 | without having to know about them in advance, or configure the machines. | | 32 | without having to know about them in advance, or configure the machines. |