X-Git-Url: http://git.rohieb.name/skm-ma-ws1314.git/blobdiff_plain/fa6284da96446dd4a438bfb72d0e51c367dd3647..d6d1c8b170ced9f0fcd46f7a18458a7bcb2d52b9:/sec-address-allocation.tex

diff --git a/sec-address-allocation.tex b/sec-address-allocation.tex
index d2d0625..0ca0764 100644
--- a/sec-address-allocation.tex
+++ b/sec-address-allocation.tex
@@ -5,14 +5,14 @@ IP layer, a device needs to configure one of its network interfaces with an IP
 address that can be reached from the network that the device wants to connect
 to. Letting the user choose and configure IP addresses manually is a cumbersome
 when it comes to several devices. Deploying a central server for assigning IP
-addresses automatically from a pre-configured address pool is possible (e.~g.
-using the DHCP protocol~\cite{rfc2131}), however, there is also the alternative
+addresses automatically from a pre-configured address pool is possible (e.~g. by
+using DHCP~\cite{rfc2131}), however, there is also the alternative
 to use a distributed protocol which enables the devices on a network to choose
-addresses in accordance with each other so no IP address is used twice.
+addresses in accordance with each other, so no IP address is used twice.
 
 In respect to the Internet of Things, this decentralized approach has the
-advantage that devices can easily be used in different scenarios, even when
-central deployment does not exist, and it also allows them to change their
+advantage that devices can easily be used in different deployments, even where
+central infrastructures do not exist, and it also allows them to change their
 addresses dynamically in order to react to changes in the network.
 
 There are two major protocols which are used for dynamic configuration of IP
@@ -42,18 +42,17 @@ Stateless Address Auto\-configuration} use an IPv6 address from the subnet
 which can be random, or based on the interface's MAC address. Most likely, this
 interface identifier is unique in the network, so a unique IPv6 address is
 obtained by combining the subnet prefix and the interface identifier.
-Nonetheless, to ensure that no other device use the generated IPv6 address, the
+Nonetheless, to ensure that no other device uses the generated IPv6 address, the
 device performs \term{Duplicate Address Detection} on the network by
-broadcasting
-its generated address with \term{Neighbor Advertisement} messages and listening
-for \term{Neighbor Solicitation} messages. If such a message is received from
-another hosts, the generated address cannot be used by the device and must be
-discarded, and the address generation process is repeated until a unique
-address has been found.
+broadcasting its generated address with \term{Neighbor Advertisement} messages
+and listening for \term{Neighbor Solicitation} messages. If such a message is
+received from another hosts, the generated address cannot be used by the device
+and must be discarded, and the address generation process is repeated until a
+unique address has been found.
 
 In contrast to IPv4 Link-Local Addressing, IPv6 Stateless Address
-Autoconfiguration can also be used with a central server. In this case, a
-central server broadcasts \term{Router Solicitation} messages on the network
+Autoconfiguration can also be used with a central server. In this case, the
+server broadcasts \term{Router Solicitation} messages on the network
 which contain a global network prefix. The hosts on the network can then use
 that prefix instead to configure a global IPv6 address.
 
