From: Richard Whitehouse <github@richardwhiuk.com>
Date: Wed, 20 Apr 2011 18:25:05 +0000 (+0100)
Subject: Inital draft of MOOSE section
X-Git-Url: https://git.richardwhiuk.com/?a=commitdiff_plain;h=3e55aca583223ef15297670c4692474e59a6013f;p=ii-diss.git

Inital draft of MOOSE section
---

diff --git a/introduction.tex b/introduction.tex
index a63cfeb..ff5b8eb 100644
--- a/introduction.tex
+++ b/introduction.tex
@@ -66,6 +66,22 @@ Another limitation is that when the spanning tree protocol converts the network
 
 \subsection{MOOSE}
 
+% TODO: Make this section clearer. Add graphic
+
+MOOSE - Multi-level Origin-Organised Scalable Ethernet is a proposed improvement on the Ethernet protocol design to backwards compatible with the large number of ethernet controllers currently in the market place. MOOSE requires only the replacement of switches in the target network, or in some cases simply installing the MOOSE code on the existing switches.
+
+MOOSE performs in place rewriting of Ethernet datagrams on the switch in order to provide the aggregation of addresses on a per switch basis. By providing for routing information within the address, the MOOSE switch allows for traffic to be routed between MOOSE switches, allowing for better utilisation of network links.
+
+This alleviates the problems associated with the deployment of STP, and also allows smaller state tables as each switch only needs to know about it's local hosts and the other switches, resulting in a significantly lower size of state table.
+
+The address a host will be rewritten to is calculated by looking at the switch it is assigned to. Each switch has a unique identifier. This is the concatenated with a unique identifier for the host. For example, the switch with a MOOSE address of 02:00:01:00:00:00, with the first three bytes being the unique host identifier, 02:00:01, will have hosts with addresses such as 02:00:01:00:00:01 and 02:00:01:00:00:02, where 00:00:01 and 00:00:002 are the unique host identifiers.
+
+In the state table, a MOOSE switch contains a mapping between host identifiers and MAC addresses and ports, and a separate state table mapping between switch identifiers and ports. By aggregating all of a switch's hosts under a single entry in the state table, a vast reduction in size is achieved. 
+
+When a packet enters the switch, if it contains a normal Ethernet address, it is rewritten to a MOOSE address and this mapping is stored in the table. It is then directed using the host identifier for switch local traffic and the switch identifier for non local traffic.
+
+MOOSE addresses are identified by looking at the second bit in the most significant byte. This is set to universally administered for almost all Ethernet devices (as assigned by the IEEE). MOOSE only uses addresses with this set to locally administered allowing them to differentiated.
+
 \subsection{Simulation}
 
 \subsection{Context}