projects
/
skm-ma-ws1314.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
9fd9db3
)
dns extensions: slight reformulation
author
Roland Hieber
<rohieb@rohieb.name>
Fri, 17 Jan 2014 07:22:39 +0000
(08:22 +0100)
committer
Roland Hieber
<rohieb@rohieb.name>
Fri, 17 Jan 2014 07:23:54 +0000
(08:23 +0100)
sec-dns-extensions.tex
patch
|
blob
|
history
diff --git
a/sec-dns-extensions.tex
b/sec-dns-extensions.tex
index
e266ba6
..
93921fd
100644
(file)
--- a/
sec-dns-extensions.tex
+++ b/
sec-dns-extensions.tex
@@
-15,12
+15,12
@@
group\footnote{\url{http://zeroconf.org}}.
\term{Multicast DNS} (mDNS)~\cite{rfc6762} describes an extension to the Domain
Name System that allows DNS resource records to be distributed on multiple hosts
in a network, therefore avoiding central authorities and enabling every host to
\term{Multicast DNS} (mDNS)~\cite{rfc6762} describes an extension to the Domain
Name System that allows DNS resource records to be distributed on multiple hosts
in a network, therefore avoiding central authorities and enabling every host to
-publish its own entries. For that purpose, a special
domain, usually
-
named \code{.local}, is used
.
+publish its own entries. For that purpose, a special
top-level domain, is used,
+
usually named \code{.local}, which contains those entries
.
Software that supports mDNS listens on the reserved
link-local multicast address \code{224.0.0.251} (for IPv4 queries) or
Software that supports mDNS listens on the reserved
link-local multicast address \code{224.0.0.251} (for IPv4 queries) or
-\code{
FF02::FB
} (for IPv6 queries) on UDP port 5353 for incoming queries.
+\code{
ff02::fb
} (for IPv6 queries) on UDP port 5353 for incoming queries.
Queries sent to those multicast address and port are standard DNS queries.
If a host receives a query and knows about the queried resource, it responds to the
querying host with a standard DNS response. The querying host can then simply
Queries sent to those multicast address and port are standard DNS queries.
If a host receives a query and knows about the queried resource, it responds to the
querying host with a standard DNS response. The querying host can then simply
@@
-32,7
+32,7
@@
next section).
Another feature of Multicast DNS is the reduction of traffic through
\term{Known-Answer Suppression}. It allows a querying host to specify already
known resources in its query when querying resources that could exist on more
Another feature of Multicast DNS is the reduction of traffic through
\term{Known-Answer Suppression}. It allows a querying host to specify already
known resources in its query when querying resources that could exist on more
-than one host (e.
~
g., SRV records). The hosts matching those resources then do
+than one host (e.
\,
g., SRV records). The hosts matching those resources then do
not generate a response, thus reducing the messages in the network and saving
bandwidth, which is usually a scarce resource in wireless networks.
not generate a response, thus reducing the messages in the network and saving
bandwidth, which is usually a scarce resource in wireless networks.
This page took
0.031858 seconds
and
4
git commands to generate.