--- /dev/null
+@book{spurgeon,
+ author = "Charles Spurgeon",
+ title = "Ethernet: The Definitive Guide",
+ publisher = "O'Reilly Media",
+ edition = "1st",
+ year = 2000
+}
+
+@misc{seattle,
+ title = "{Floodless in SEATTLE: A Scalable Ethernet Architecture for Large Enterprises}",
+ author = "Changhoon Kim and Matthew Caesar and Jennifer Rexford"
+}
+
+@misc{moose1,
+ title = "{Addressing the Scalability of Ethernet with MOOSE}",
+ author = "Malcolm Scott and Daniel Wagner-Hall and Andrew Moore and Jon Crowcroft"
+}
+
+@misc{moose2,
+ title = "{A Prototype Implementation of MOOSE on a NetFPGA/OpenFlow/NOX Stack}",
+ author = "Daniel Wagner-Hall"
+}
+
+@misc{dwh,
+ title = "{NetFPGA Implementation of MOOSE}",
+ author = "Daniel Wagner-Hall"
+}
+
+@misc{xen,
+ title = "{Xen and the Art of Virtualization}",
+ author = "Paul Barham and Boris Dragovic and Keir Fraser and Steven Hand and Tim Harris and Alex Ho and Rolf Neugebauer and Ian Pratt and Andrew
+Warfield"
+}
+
+@misc{boostgraph,
+ title = "{The Boost Graph Library (BGL)}",
+ author = "Jeremy Siek and Lieu-Quan Lee and Andrew Lumsdaine",
+ howpublished = "\url{http://www.boost.org/doc/libs/1_46_1/libs/graph/doc/index.html}"
+}
+
+@misc{dijkstra,
+ title = "{A Note on Two Problems in Connexion with Graphs}",
+ author = "E. W. Dijkstra",
+ journal = "Numerische Mathematik 1"
+}
+
+@misc{facebook,
+ title = "{Open Compute Project}",
+ author = "Facebook Inc.",
+ howpublished = "\url{http://www.opencompute.org/datacenters/}"
+}
+
+@misc{github,
+ title = "{GitHub - Social Coding}",
+ author = "GitHub Inc.",
+ howpublished = "\url{http://www.github.com}"
+}
+
+@misc{abramson,
+ title = "{The ALOHA System - Another alternative for computer communications}",
+ author = "Norman Abramson",
+ institution = "University of Hawaii"
+}
+
+@misc{osi,
+ title = "{OSI Reference Model - The ISO Model of Architecture for Open Systems Interconnection}",
+ author = "Hubert Zimmermann",
+ booktitle = "IEEE Transactions on Communications"
+}
+
+@misc{ns-comparison,
+ title = "{A performance comparison of recent network simulators}",
+ author = "Elias Weingartner and Hendrik vom Lehn and Klaus Wehrle",
+ institution = "RWTH Aachen University"
+}
+
+@misc{cerf74,
+ title = "{A Protocol for Packet Network Intercommunication}",
+ author = "Vinton G. Cerf and Robert E. Kahn"
+}
+
+@misc{rfc768,
+ title = "{RFC 768 - User Datagram Protocol}",
+ author = "J. Postel",
+ institution = "ISI",
+}
+
+@misc{rfc791,
+ title = "{RFC 791 - Internet Protocol}",
+ institution = "DARPA"
+}
+
+@misc{rfc863,
+ title = "{RFC 863 - Discard Protocol}",
+ author = "J. Postel",
+ institution = "ISI",
+}
+
+@misc{rfc1035,
+ title = "{RFC 1035 - Domain Names - Implementation and Specification}",
+ author = "P. Mockapetris",
+ institution = "ISI",
+}
+
+@misc{rfc1122,
+ title = "{RFC 1122 - Requirements for Internet Hosts - Communication Layers}",
+ author = "R. Braden",
+ institution = "IETF",
+}
+
+@misc{rfc1883,
+ title = "{Internet Protocol - Version 6 (IPv6)}",
+ author = "S. Deering and R. Hinden",
+ institution = "Xerox PARC and Ipsilon Networks",
+}
+
+@misc{rfc2328,
+ title = "{OSPF Version 2}",
+ author = "J. Moy",
+ institution = "Ascend Communications, Inc.",
+}
+
+@misc{rfc2616,
+ title = "{Hypertext Transfer Protocol - HTTP/1.1}",
+ author = "R. Fielding and J. Gettys and J. Mogul and H. Frystyk and L. Masinter and P. Leach and T. Berners-Lee",
+ institution = "UC Irvine and Compaq and W3C and MIT and Xerox and Microsoft",
+}
+
+@misc{ieee802-3u,
+ title = "{IEEE Standard for Local and Metropolitan Area Networks - Supplement - Media Access Control (MAC) Parameters, Physical Layer, Medium Attachment Units and Repeater for 100Mb/s Operation, Type 100BASE-T}",
+ author = "IETF"
+}
+
+@misc{ieee802-3ab,
+ title = "{IEEE Standard for Local and Metropolitan Area Networks - Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications - Physical Layer Parameters and Specifications for 1000 Mb/s Operation over 4 pair of Category 5 Balanced Copper Cabling, Type 1000BASE-T}",
+ author = "IETF"
+}
+
+@misc{ieee802-1d,
+ title = "{IEEE Standard for Local and Metropolitan Area Networks - Media Access Control (MAC) Bridges}",
+ author = "IETF",
+}
+
+@misc{icann-030211,
+ title = "{Available Pool of Unallocated IPv4 Internet Addresses Now Completely Emptied}",
+ author = "ICANN",
+ howpublished = "\url{http://www.icann.org/en/news/releases/release-03feb11-en.pdf}",
+}
+
\subsubsection{Physical Layer}
-The stack starts at the bottom with the physical layer. This is primarily concerned with the physical interconnection of the two computers and how the basic signalling works in terms of cabling or radio. Standards on this layer include 100BASE-T \cite{ieee802-3y} and 1000BASE-T \cite{ieee802-3ab} - commonly known as Fast Ethernet amd Gigabit Ethernet respectively.
+The stack starts at the bottom with the physical layer. This is primarily concerned with the physical interconnection of the two computers and how the basic signalling works in terms of cabling or radio. Standards on this layer include 100BASE-T \cite{ieee802-3u} and 1000BASE-T \cite{ieee802-3ab} - commonly known as Fast Ethernet amd Gigabit Ethernet respectively.
\subsubsection{Data Link Layer}
As network traffic increased, and more computers were added to local area networks, the reality of all computers sharing a single shared media with which any packet would collide with other traffic became impractical. This was exacerbated by distant computers being far away from each other, descreasing the utility of Carrier Sense, increasing the likelihood of collision, which is followed by a process where each host backed off before trying again, thus decreasing utilisation of the network.
-The solution to this was to split the single colision domain into a set of domains which would be joined together using a network bridge to form a single collision domain. \cite{802.11d} The bridge, or switch as it is also known due to the manner in which it operates, filters traffic between the different collision domain, only sending traffic where it is required. As the number of hosts on the network, and the speed of network traffic increased, more and more collision domains were created. Modern Ethernet networks are entirely switched networks with each host having a full duplex link to the local switch.
+The solution to this was to split the single colision domain into a set of domains which would be joined together using a network bridge to form a single collision domain. \cite{ieee802-1d} The bridge, or switch as it is also known due to the manner in which it operates, filters traffic between the different collision domain, only sending traffic where it is required. As the number of hosts on the network, and the speed of network traffic increased, more and more collision domains were created. Modern Ethernet networks are entirely switched networks with each host having a full duplex link to the local switch.
The next problem was that as networks became more vital to operation, it became desirable to have redundant links. In order to allow this the switches were often aranged in a way that formed loops. However, the Ethernet protocol relies on traffic being sent to a tree, and not a graph with cycles in it, in order to prevent broadcast traffic from cycling the network endlessly using up all the available bandwidth. In order to solve this Ethernet uses a spanning tree protocol in order to convert the graph of switches into a tree. This tree is not guranteed to a minimum spanning tree, instead it is guaranteed that all switches have the shortest possible path to a root bridge which may be specified by the network administrator in top end switches. The current iteration of this protocol is the Rapid Spanning Tree Protocol - RSTP and this disables links until that condition is met. In practical terms this means that redundant links which could be used to increase the available network bandwidth are instead disabled. Should the state of the network change, they will be re-enabled to allow the network to continue to operate.
projects / ii-diss.git / commitdiff