Network2/Architecture: Difference between revisions
< Network2
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
{{Network2 header}} |
{{Network2 header}} |
||
Prerequisite concepts: [[Network2/Concept/Link|link]], [[Network2/Concept/Layer|layer]], [[Network2/Concept/Network|network]], [[Network2/Concept/Address|address]], [[Network2/Concept/Internetwork|internetwork]], [[Network2/Concept/Name|name]] |
|||
Based on these scenarios, we imagine our network as being organized into three kinds of composable layers: |
Based on these scenarios, we imagine our network as being organized into three kinds of composable layers: |
||
Revision as of 05:56, 29 July 2009
Prerequisite concepts: link, layer, network, address, internetwork, name
Based on these scenarios, we imagine our network as being organized into three kinds of composable layers:
- a link layer, usually implemented via 802.3 wired Ethernet, 802.11b/g wifi in either ad-hoc or infrastructure mode, or various sorts of tunneling over IPv4, perhaps across NATs and firewalls,
- an internetworking layer, based on IPv6 (tutorial documentation), and
- a naming layer, based on DNS, for binding logical addresses from networks with different failure modes to stable human-memorable names
We find this layered conceptual model helpful for estimating dependency ("what has to work before this layer can work?") and cost ("what does it cost to traverse this layer?").